Start here · Stage 1 · Free
A funded futures simulator runs on the same execution environment as the live evaluation. Order types, fills, position size limits, DLL alerts, and the news calendar all behave identically. The one thing simulation cannot replicate is the consequence of a breach — a DLL breach in simulation resets without cost; on a live account it may end the evaluation. This article covers what to do with that environment before placing the first live trade.
Part 1 of 4 — What simulation replicates and what it does not
The gap between simulation performance and live evaluation performance is almost never about execution. It is about the behavioral response when a near-breach feels real.
A funded futures evaluation simulator — whether accessed through a firm's demo environment, a paper trading account on Rithmic or Tradovate, or a built-in simulation mode in the evaluation platform — runs on the same execution infrastructure as the live evaluation. What it replicates and what it does not determines how to use it correctly.
The following elements of the evaluation environment are fully replicated in simulation:
These five elements are what simulation is designed to test. All five should be verified in simulation before the first live trade.
Three elements of the live evaluation environment are not present in simulation:
The implication: simulation is the right environment for the three preparation tasks covered in Parts 2-4 of this article. It is not the environment to use to "get experience with evaluation pressure" — that experience only develops on a live account.
Part 2 of 4 — Method calibration
The average session profit from those 10 sessions is the denominator in the pacing formula. It is also the first signal about whether the method produces the pass rate the evaluation requires.
Method calibration has a specific purpose: produce the numerical inputs needed for the evaluation pacing math before starting the live evaluation. The pacing formula requires an estimate of average session profit to calculate the earliest possible pass date for the profit target gate. Without a calibrated average session profit, the estimate is a guess.
The journal used in simulation should be identical to the live evaluation journal: the same 10 fields per session (entry time, setup type, size, entry/stop/exit prices, ticks, dollars, daily P&L, floor position, session classification). See the funded futures evaluation journal article for the full field list and pre-population instructions.
If the simulation journal uses different fields, the calibration data cannot be directly compared to the live evaluation data. The 10 sessions of simulation data should be readable alongside the first 10 sessions of live evaluation data without reformatting.
Average session profit = total net P&L across all 10 simulation sessions ÷ 10. This number estimates how many sessions the profit target gate will require: sessions needed = profit target ÷ average session profit. For example, if the profit target is $3,000 and the average session profit across 10 simulation sessions is $200, the pacing estimate is 15 sessions — not counting the minimum trading days floor or the consistency rule ceiling, which may extend the estimate further.
A stable average session profit is one where no single session in the last five simulation sessions is more than double or less than half the average. If one session is ten times the average (a large news-gap win, for example), the average is inflated and the pacing estimate will be optimistic. Remove the outlier from the average calculation and note it separately — that session type represents a condition, not the typical session.
For the full pacing formula with all three gates (profit target, minimum trading days, consistency rule), see funded futures evaluation timing.
The consistency denominator is the total cumulative net profit across all sessions in the evaluation. When the denominator is small — in the first three to five sessions — a single large winning session can push the best-day percentage above the consistency rule cap. This is not a method failure; it is an arithmetic consequence of a small denominator. But it is a risk that can be anticipated and managed.
Review the 10 simulation sessions and identify any session where the single-session P&L exceeds 35% of the cumulative P&L at that point. A session that would trigger the consistency cap if it occurred on day two or three of the live evaluation is a signal to consider the flat-until-post-news posture on news event days in the early evaluation window, where the chance of a large outlier session is highest.
Simulation cannot replicate this pressure directly — the denominator in simulation is already large by the time you start the live evaluation. But it can identify whether the method produces the type of session that creates early-denominator risk: large wins relative to the average that are driven by news events, gap fills, or momentum continuation moves.
Part 3 of 4 — Sizing formula validation and platform configuration test
A misconfigured position size limit or DLL alert is not a mistake you want to discover on the first live session. Both are verifiable in simulation at zero cost.
The sizing formula produces a contract ceiling from two inputs from the evaluation agreement: the Daily Trailing Drawdown (DTF) and the Daily Loss Limit (DLL). The formula:
Apply this formula in simulation on the specific instrument and stop distance you plan to use. For example, on a $50K evaluation with a $2,500 DTF and $500 DLL, trading MNQ with a 15-tick stop and $2.00/tick: DTF÷10 = $250, DLL÷4 = $125. The binding constraint is DLL÷4 = $125. Contract ceiling = floor($125 ÷ (15 × $2.00)) = floor($125 ÷ $30) = floor(4.17) = 4 contracts.
Verify in simulation that trading 4 MNQ contracts with a 15-tick stop does not breach the DLL in a single full-stop session: 4 × 15 × $2.00 = $120, which is under the $125 pre-session ceiling. The formula checks out. If the formula produces zero contracts on a planned instrument (common on NQ at smaller tiers with typical stop widths), simulation reveals this before the live evaluation fee is paid. For the full formula across tiers and instruments, see the funded futures position sizing checklist.
Five platform settings should be verified in simulation before the first live session:
For the navigation paths on Rithmic, Tradovate, and NinjaTrader for each of these settings, see how to set up your trading platform for a funded futures evaluation.
Part 4 of 4 — When simulation is complete enough to start the live evaluation
The number of simulation sessions is not the measure. What the sessions produced — stable average session profit, confirmed sizing formula, verified platform settings, one news event handled — is the measure.
A session count minimum (10 sessions, 20 sessions, 30 days) is a proxy for the actual readiness criterion. The actual criterion is four pieces of evidence. All four must be present simultaneously.
Stable means no session in the last five is more than double or less than half the average of those five sessions. If average session profit across the last five simulation sessions is $180 and one of those five sessions produced $380, the average is being carried by an outlier and is not stable. Continue simulation until the last five sessions produce an average where no single session is a statistical anomaly relative to the others.
This stability requirement exists because the pacing formula depends on the average being representative of a typical session. An inflated average produces an optimistic pacing estimate — the live evaluation will take longer than the simulation data suggests, and the consistency rule will require more sessions to clear than expected.
The formula has been run on the specific evaluation agreement numbers (not a generic example tier), the specific instrument you plan to trade on session one, and the stop distance you use in your method. The resulting contract ceiling produces a per-stop exposure that fits within the DLL÷4 pre-session constraint. A formula output of zero contracts on the planned instrument means the instrument is not viable at the planned tier and stop width — this is the condition where switching instruments or tier is the correct decision, not starting the evaluation and discovering the constraint on session one.
Each of the five settings from Part 3 has been tested by triggering it or verifying its behavior, not just configured. The position size limit fires at the contract ceiling. The DLL alert threshold is confirmed in the settings panel and the alert behavior is understood. The overnight flag is set correctly for the evaluation's rules. The news calendar displays release times in your local timezone. The login and dashboard state shows the expected values. A setting that is entered but never verified may be configured incorrectly — on Tradovate, for example, setting Max Position Size in lots rather than contracts sets a ceiling that is effectively meaningless at the wrong unit.
Before the simulation session containing the news event, the calendar was checked, the posture decision (flat until post-event / sized-down post-event only / pre-news session only) was made in writing in the journal, and the session was executed according to that decision. A posture decision made after the event has already occurred is not evidence of news management — it is a retrospective classification. The simulation news event requirement is specifically about making the decision before the market opens on that session and then executing it correctly.
The common mistake in funded futures evaluations — and the one that simulation can prevent — is the trader who knows about the news event but has not decided on a posture before the session. When the event produces a large move that looks like an opportunity, the absence of a pre-session posture decision makes the correct action ambiguous in real time. Making the decision before the session, in simulation, builds the habit before the live fee is at risk. For the full posture options and the post-news protocol, see how to handle news events on a funded futures account.
When all four conditions are met, simulation has served its purpose. Starting the live evaluation before any of the four conditions is met means carrying an unresolved variable into the live account — an unstable average session profit, a sizing formula that has not been confirmed, a platform setting that has not been tested, or a news posture decision that has never been made before a live event. Each of those gaps is cheaper to close in simulation than to discover during a live evaluation with fees at risk.
For the day-before checklist that connects simulation completion to live evaluation launch, see what to do the day before starting a funded futures evaluation.
A funded futures evaluation simulator replicates order execution, fills, platform layout, position size limit enforcement, DLL alert behavior, and news calendar access — all identical to the live evaluation environment. What it does not replicate is the cost of a breach: a DLL breach in simulation has no evaluation consequence, which means simulation cannot train the emotional response to a near-breach or actual breach when fees are at risk.
The right bar is an evidence standard, not a session count. A minimum of 10 simulation sessions gives enough data to calculate the average session profit. The readiness criterion is met when: average session profit is stable across the last five sessions, the DTF÷10 and DLL÷4 formula outputs are confirmed for your planned instrument, all five platform settings have been verified to work correctly, and at least one news event day was handled with a pre-session posture decision. If those four conditions are met in 10 sessions, 10 is enough. If not, continue.
No. Simulation replicates execution mechanics but not the psychological environment. The two conditions that drive evaluation-specific behavioral patterns — real money at risk as evaluation fees, and the consequence of a DLL breach on a live account — are absent in simulation. Traders who perform well in simulation and struggle in the live evaluation are almost always experiencing this divergence: execution is identical, but the behavioral response to near-breach pressure is different when the consequence is real. The trading psychology article covers the three evaluation pressure patterns that appear on live accounts and not in simulation.
The consistency denominator is the total cumulative net profit across all sessions in the evaluation. On the live evaluation, the denominator starts at zero on day one. If session three produces a large win, the best-day percentage can spike above the consistency rule cap even on a legitimate session. Simulation cannot replicate this early-denominator vulnerability because the simulation denominator is already large when the live evaluation starts. But simulation can identify whether your method produces large outlier sessions relative to average — which is the condition that creates early-denominator risk in the live evaluation's first five sessions.
Four conditions must be true simultaneously: (1) average session profit from the last five simulation sessions is stable — no session in those five is more than double or less than half the average; (2) the DTF÷10 and DLL÷4 formula outputs are confirmed for your planned instrument and stop distance; (3) all five platform configuration settings have been verified to fire correctly, not just entered; (4) at least one simulation session included a news event where the posture decision was made before the session opened. When all four are met, simulation is complete. Starting the live evaluation before any of the four is met moves an unresolved variable into a live account with fees at risk.
The simulation framework from 9 years of live funded account preparation — what to run, what to record, and when the data says you are ready.
Most funded traders start the live evaluation before any of the four readiness conditions are met. The method builds the simulation habit first — calibrate the method, validate the sizing formula, test the platform, handle a news event — so session one of the live account starts with the variables already resolved. First 100 founding seats at $19/mo — locked for life.