A prop-firm rule is only usable when five coordinates are fixed: firm, exact program, phase, region, and account size. The server-rendered blocks above hold those coordinates at global/default, 100K, first evaluation stage. They compare three exact CFD programs and show Topstep’s exact futures program separately. Never copy a firm-wide percentage from one plan into another.
“Every rule, one page” means every rule family you must resolve before paying or trading—not every plan a firm has ever sold. The catalog block supplies current verified program inputs, links to the profile and official terms, and shows Not verified where the canonical record cannot support a value. The method and verdict below remain editorial; they do not change automatically when catalog facts change.
1. Full Rules Comparison—Exact Programs, Not Firm Names
Read the component in decision order. Start with market and platform eligibility, then evaluation price, profit target, daily loss, maximum loss mode, minimum days, payout conditions, restrictions, and verified date. A lower headline target is not automatically easier. A strategy can be incompatible with the loss engine, trading-day definition, execution route, or payout gate even when the target looks attractive.
| Rule field | Question it answers | Common reading error |
|---|---|---|
| Market and platform | Can the strategy and required instrument actually be executed? | Comparing a CFD evaluation with a CME-futures evaluation as though the products were interchangeable |
| Evaluation price | What verified amount applies to this exact size and route? | Copying a sale, another region, activation cost, reset, data fee, or a different account size |
| Profit target | What realized result must be reached in this phase? | Ignoring minimum days, consistency, or another pass condition |
| Daily loss | Which daily floor applies, what enters the calculation, and when does it reset? | Treating it as a simple percentage of starting balance |
| Maximum loss | Is the floor static, trailing intraday, or trailing end-of-day? | Using one firm’s drawdown formula for another program |
| Minimum days | Which days qualify and what must happen on them? | Counting calendar days or any session with an open position |
| Payout and restrictions | What later conditions affect reward eligibility or account use? | Reading the maximum split as a guaranteed first payout |
The exact pair pages remain useful when the market branch is already settled: compare the scoped inputs in FTMO versus Topstep, or keep the CFD branch like-for-like with FundedNext versus The5ers. The components can refresh facts; the article’s profile-relative conclusion must be reviewed separately.
2. Translate Percentage Rules Into Account-State Values
A static table of dollar examples becomes misleading when the rule’s reference balance, equity treatment, timezone, or trailing mechanic changes. Translate only after the exact program and phase are selected.
Static maximum-loss floor
reference amount − allowed maximum loss. Confirm whether the reference is nominal starting balance, initial balance after adjustments, or another program-defined amount.
Daily-loss room
Resolve the program’s daily reference, realized and unrealized P/L treatment, commissions, swaps or fees, open risk, and reset timezone. Do not derive it from current balance alone.
Trailing floor
Apply the exact update event: intraday high, end-of-day balance or equity, lock point, and any phase transition. A generic percentage cannot reproduce a program’s state machine.
Consistency headroom
Use the program’s numerator, denominator, qualifying period, rounding, and pass or payout stage. “Best day share” is not one universal formula across firms.
Store both the rule value and the rule version used. The useful session number is not merely “five percent”; it is the exact remaining room under the selected program at the current timestamp, after every event the rule includes. If live equity, fees, conversion, or cash-flow treatment is missing, label the result incomplete.
3. What Each Rule Actually Means
Daily loss limit—the event boundary
Daily loss rules differ in reference point, included P/L, reset time, and whether the control is mandatory or selectable. Ask four questions: What opens the day? Which realized, unrealized, fee, and funding events count? What timezone closes it? Is breach tested continuously or at a defined checkpoint?
A closed-trade export can prove realized results but may not prove intraday floating-equity compliance. A Replay should therefore refuse a clean pass when the selected rule requires live equity that the imported evidence does not contain.
Static vs trailing drawdown—the crucial difference
A static floor stays tied to its program-defined reference. A trailing floor can rise when the relevant balance or equity checkpoint rises. Some trailing floors update intraday; others use end-of-day values; some stop trailing after a lock condition. The trailing-drawdown guide separates these state transitions without pretending one generic formula describes every firm.
Consistency rule—phase, denominator, and consequence
“Consistency” may constrain a best day, require qualifying profitable days, affect the evaluation, gate a payout, or not exist in the selected phase. Those are different rules. Record the exact phase, numerator, denominator, comparison operator, rounding policy, and consequence. The consistency-rule tracker guide shows how to keep that denominator auditable as total profit changes.
Minimum trading days—not calendar time
A minimum-day value is incomplete without the qualifying-day definition. A firm may count any executed day, require a minimum profit, define a session boundary in another timezone, or apply the condition only to one phase. Do not force extra trades merely to satisfy a rule you have not resolved precisely.
Restrictions—strategy compatibility before price
Check news windows, weekend holding, overnight positions, automation, copy or group trading, prohibited strategies, maximum size, scaling, platform, instrument, and inactivity rules. Not verified does not mean allowed; it means the canonical record does not support a conclusion and the official terms must be checked.
FTMO has announced futures trading (currently in beta); details are being finalized — see our upcoming coverage.
4. Account Sizes and Evaluation Prices
Account size is part of the program key, not a cosmetic dropdown. It can change price, target amount, allowed loss, trailing distance, contract limit, and later account state. The SSR component displays the exact 100K evaluation scope used here; select another size on the linked profile or official source instead of multiplying every field yourself.
Live evaluation prices belong to the canonical catalog. A verified amount renders from that record with its checked date; an unresolved amount renders Not verified. This guide does not maintain duplicate literal prices. Also separate evaluation price from recurring subscription, activation, reset, platform, exchange-data, tax, conversion, or withdrawal costs. “Lowest challenge fee” is not a stable answer until those cost classes and the intended holding period are fixed.
5. Scaling Plans—How to Read Them Without Overpromising
A maximum advertised allocation is not the account a trader will receive, the amount of real capital deployed, or a guaranteed path. For each scaling plan, resolve:
- the exact funded program and eligibility cohort;
- the measurement window and required result;
- drawdown, payout, consistency, inactivity, and risk conditions during the window;
- whether scaling changes balance, loss limits, contracts, profit split, or only a display value;
- whether multiple accounts can be combined and which caps apply;
- the official source and verified date for every claim.
Do not infer today’s scaling terms from the evaluation row above. Scaling is a later-stage contract and may use a different policy version. The editorial conclusion is simple: choose a program that fits the current strategy before valuing a distant maximum allocation.
6. Status and Closure Checks—Do Not Send Money on a Stale Claim
A dated “dead firms” list can become wrong in both directions: an operating company can close after publication, and a paused or disputed status can later change. Before payment, require a current canonical coverage status, reachable official domain, exact program terms, supported checkout route, recent verification date, and a clear legal entity. If any of those is unresolved, stop at Not verified.
Social payout screenshots do not establish solvency, regulatory status, or the terms that govern your purchase. Preserve the checkout page, terms version, refund policy, entity name, and receipt. If the program later changes or closes, those records are more useful than a generic reputation score.
The One-Page Decision Order
- Market gate: choose the instrument model and execution route first.
- Loss-engine gate: reject programs whose daily or maximum-loss state machine conflicts with the strategy.
- Restriction gate: verify news, holding, automation, copying, size, and inactivity behavior.
- Pass-condition gate: resolve target, days, consistency, and phase transitions.
- Cost gate: total evaluation, subscription, activation, reset, data, platform, and conversion costs.
- Payout gate: review eligibility, schedule, split, limits, verification, and later funded rules.
The correct result is not “Firm A is best.” It is “Program P, phase H, region R, size S is compatible or incompatible with this declared strategy profile, for these recorded reasons.” If the catalog refresh contradicts that conclusion, the component raises an editorial-review warning rather than silently rewriting the verdict.
Run the Exact Rule Loop in TSB
TSB turns this cheatsheet into an executable evidence contract. Select the exact firm, program, phase, region, and size from the canonical catalog. Prop Replay evaluates the imported trade sequence in order and returns pass, stall, or first breach only when the required evidence supports it. Missing live equity, currency conversion, cash-flow treatment, or a tier rule can block a pass instead of being guessed away.
Journal keeps the underlying trades and account scope inspectable. The Prop Rule Tracker keeps the selected rule version and current pressure visible. AI Coach can then examine the same evidence set through data-quality, plan-compliance, setup-risk, market-regime, rule-testing, and setup-decay lenses. Its job is not to repeat the percentage table: it identifies the supported mismatch, links back to the trades and rule evidence, explains the limitation, and carries one concrete response into Current Focus.
That makes Coach a real decision layer. A generic chatbot says “reduce risk.” TSB can say which rule is under pressure, which recorded decisions created it, what evidence remains missing, and what exact behavior should be tested next—without turning an incomplete export into a false pass.
TSB has processed 600K+ imported trades across its import history, and the source registry recognizes 328 exact broker, exchange, platform, and prop-export profiles. Those values mean imported trades and recognized routes—not users, guaranteed compatibility, or trades analyzed by Coach. Exact route validation and reconciliation still come first.
Choose the exact program Replay my real sequence Turn the first blocker into Current Focus
Bottom Line
Do not compare prop firms as brands. Fix the exact program coordinates, let the server catalog render current verified facts, and read rules in decision order: market, loss engine, restrictions, pass conditions, total cost, then payout. Translate percentages only after the rule’s reference state and event logic are known.
The component owns dynamic facts; this article owns the method and conclusion. TSB adds the full loop the cheatsheet cannot provide alone: canonical selection, chronological Replay, evidence limitations, inspectable trades, a strong Coach diagnosis, and one measurable Current Focus action.
Disclosure: Trader’s Second Brain is our product. Exact program components, rule-source records, Prop Replay behavior, Coach evidence routing, and canonical public-truth values were checked against the local codebase on September 10, 2026. Firm terms can change; use the component’s official-source links and verified dates before any purchase or trading decision. This is educational product analysis, not investment, legal, or tax advice. See our editorial methodology.
