FTMO Futures Contract Limits: Evaluation vs Sim-Funded

Exact contract limits by account size and phase

The matrix below is server-rendered from the reviewed canonical catalog. Evaluation limits are fixed by account size. Sim-Funded limits rise through end-of-day profit bands and are shared by the reviewed PRO and GROWTH programs.

The arrows in the decision are phase transitions, not performance promises. The first Sim-Funded tier is the capacity available before additional eligible EOD profit moves the account into another band.

Evaluation capacity is the ceiling, not a position-size recommendation

A maximum contract count answers what the program permits. It does not answer what one trade should risk. Two positions with the same contract count can have very different tick values, stop distances, volatility, and correlated exposure. A micro contract is smaller than its corresponding mini, but the risk calculation still needs the exact instrument, tick value, quantity, stop distance, commissions, and slippage assumption.

Start with the strategy's historical stop distribution and calculate risk per contract. Round down to an integer quantity, then compare that quantity with the active program cap. The prop-firm position-sizing guide explains why a percentage of the account label is not enough.

The post-pass reset in capacity can change execution

Suppose an evaluation trade normally uses several entries and scale-outs. Passing does not prove that the structure fits the first Sim-Funded band. If the new cap is lower, the trader has four honest choices: reduce the number of legs, use the corresponding micro contract, redesign the exit structure, or wait for a higher band. Silently keeping the old plan would make the journal's “same setup” label false.

Record the active phase and contract tier beside every imported trade. A history produced under the evaluation cap should not be replayed as if the same quantity was allowed from the first Sim-Funded session. The phase-transition guide shows the other rules that change at the same moment.

EOD-profit scaling needs an auditable state

The reviewed Sim-Funded schedule keys contract capacity to accumulated end-of-day profit bands. That means capacity is a state derived from a specific close, not a label the trader can infer from an intraday high. Store the source day boundary, eligible EOD profit, active tier before the trade, and active tier after the close.

If the official dashboard and the journal disagree, the dashboard state governs trading. Preserve the discrepancy for review instead of forcing the local calculation to match. Withdrawal activity can also change retained profit and therefore deserves a separate post-request check. The payout guide keeps request eligibility and retained balance distinct.

Mini and micro counts cannot be added as if they were identical

The catalog shows mini and micro capacity for the corresponding contract family. It does not authorize arbitrary mixtures whose combined exposure exceeds the program rule. Before using both sizes, verify how the released dashboard converts mixed positions, whether ten micros count as one mini for the selected product, and how pending orders are treated. If that conversion is not explicit in the final terms, mark it Not verified.

A safe journal stores instrument, contract class and quantity separately. It never collapses “five contracts” into one comparable risk number across equity indexes, rates, commodities and currencies.

Three concurrent accounts multiply operational risk

The reviewed launch catalog lists up to three concurrent accounts. That is a coverage fact, not a recommendation to open or mirror three accounts. Multi-account execution adds synchronization, allocation, copy-policy, platform-routing and evidence risks. One missed stop or rejected order can make nominally identical accounts diverge.

Model each account independently first. Then test the aggregate open risk and whether the intended execution method is allowed. The multi-account tracking guide explains why a combined P&L view must preserve the underlying account rule states.

A six-step contract-fit test

1. Select the exact program, account size, phase and current EOD-profit tier.
2. Calculate risk per contract from the instrument's tick value and the strategy's actual stop distance.
3. Round quantity down and preserve the planned entry and exit legs.
4. Compare the resulting mini/micro exposure with the active cap.
5. Repeat at the first Sim-Funded tier, not only at the evaluation maximum.
6. Re-run after a payout, rule-version change or account-state discrepancy.

TSB has processed 600K+ cumulative imported trades across 330 recognized source profiles. Those counters show ingestion scale; they do not determine the correct quantity for this trader. The decision still comes from the selected history and exact contract specification.