The answer: passing changes the rule engine, not just the account label
FTMO Futures keeps the EOD-trailing maximum-loss structure after evaluation, but other controls change. The profit target and evaluation consistency objective no longer describe the Sim-Funded finish line, contract capacity switches to EOD-profit tiers, and payout eligibility becomes active. PRO keeps a hard daily-loss consequence. GROWTH moves from no separate evaluation DLL to a daily pause.
A plan can therefore look attractive in the challenge and become a poor fit after passing. Compare the lifecycle before choosing the evaluation.
Phase-by-phase canonical matrix
This table renders both programs and both reviewed phases from the reviewed catalog. Not verified means the field is not owned by that phase or is not present in the source; it is not replaced with an assumption.
| Program / phase | Target | Daily loss | Maximum loss | Consistency | Contracts | Payout path |
|---|---|---|---|---|---|---|
| PRO Evaluation | $3,000 | $1,000 · breach | $3,000 · EOD trailing | 50% best-day limit | 5 mini / 50 micro | Not verified |
| PRO Sim-Funded | Not verified | $1,000 · breach | $3,000 · EOD trailing | None / Not verified | 2→5 mini / 20→50 micro by EOD profit | Every 5 qualifying days |
| GROWTH Evaluation | $3,000 | None | $2,000 · EOD trailing | 40% best-day limit | 5 mini / 50 micro | Not verified |
| GROWTH Sim-Funded | Not verified | $1,000 · pause | $2,000 · EOD trailing | None / Not verified | 2→5 mini / 20→50 micro by EOD profit | Every 4 qualifying days |
Exact 50K phase snapshot from the reviewed catalog, checked Sep 17, 2026. Missing fields are not inferred.
The evaluation target stops being the next objective
During evaluation, profit target and consistency jointly determine whether the account is pass-ready. Reaching the nominal target can still leave a concentrated history ineligible. After the transition, the reviewed Sim-Funded rows do not carry another evaluation target. The decision becomes survival, contract-tier state and payout eligibility rather than “pass the same challenge again.”
Do not keep a green evaluation badge as the journal's active objective. Version the account phase, close the evaluation record, and open a Sim-Funded state with its own rules. The consistency guide explains the final evaluation denominator without carrying it into the wrong phase.
PRO's daily rule stays hard
The reviewed PRO daily-loss rule is a breach in evaluation and remains a breach in Sim-Funded. A trader who survived the challenge by staying well inside that boundary does not gain a softer consequence after passing. The phase change adds payout and dynamic-contract states, but it does not forgive the same large losing session.
That continuity can be useful because the strategy does not need a second interpretation of its daily stop. It can also be the dominant risk when a history contains rare, large sessions. Replay the same net daily series through both phases and preserve the first event.
GROWTH adds a daily pause after evaluation
GROWTH evaluation has no separate daily-loss limit. In the reviewed Sim-Funded row, a daily threshold appears with a pause consequence. The account remains governed by the maximum-loss floor, so a session can hit the daily pause without ending the account, or touch the total floor and breach it.
This is a new operational control rather than a reversal of the product's evaluation promise. A trader choosing GROWTH for no evaluation DLL still needs a session-stop workflow after passing. The full rule explainer separates breach, pause and delayed eligibility.
The EOD floor stays, but available room remains program-specific
Both programs retain their reviewed EOD-trailing maximum-loss distance and lock behavior across the transition. That continuity does not mean the active floor is identical. PRO and GROWTH begin with different room at the same account label, and the floor state depends on the highest eligible end-of-day result reached by the actual account.
Carry forward the official floor state rather than reconstructing a new account from the starting balance. The EOD replay guide shows the ordered state needed to reproduce the transition.
Contract capacity can step down immediately
Evaluation uses fixed caps. Sim-Funded begins at a lower tier and scales with accumulated EOD profit. A strategy built around several entries or scale-outs may therefore require a quantity rewrite just after passing. That is not a cosmetic setting: different rounding can alter risk, average price, exit logic and the comparability of the journal.
Use the contract-limit matrix to test the first post-pass tier before paying. Record any strategy adaptation as a new version instead of claiming that the evaluation history continued unchanged.
Payout eligibility introduces several new states
Sim-Funded adds qualifying-day thresholds, request share, per-request cap, profit split and a new-profit condition. These do not collapse into one “payout percentage.” An account can be active and profitable while the next request is not yet eligible. An eligible request is not an approval, and an approval is not payment evidence.
PRO and GROWTH differ in qualifying sequence and how much eligible profit can enter a request. The exact payout matrix should be evaluated after the phase transition, never pasted into the evaluation verdict.
How to replay the lifecycle
- Reconcile the evaluation history to net source results and official day boundaries.
- Run target, daily-loss, maximum-loss and consistency logic through the pass state.
- Copy the official final floor state into a new Sim-Funded rules version.
- Apply the first contract tier before any new order.
- Track daily pause or breach consequences with the correct program.
- Start payout-cycle fields only when the Sim-Funded phase actually begins.
Bottom line
Do not choose FTMO Futures from the challenge card alone. PRO carries its hard daily boundary forward. GROWTH introduces a post-pass daily pause. Both change contract capacity and add payout states. The better lifecycle is the one the same reconciled strategy can execute before and after the transition.
