Stage 1 · Free
Most evaluation setup errors do not happen on session one — they happen on session one because something was not prepared on day zero. The starting balance and drawdown distance were not confirmed from the agreement. The platform position size limit was not set. The first week's news calendar was not checked. The journal had no entries before the first trade. None of these take long to fix. All of them are harder to fix while a session is running. This article is the day-zero checklist: four steps to complete before the first session of a funded futures evaluation begins.
Part 1 of 4 — Confirm the evaluation agreement
The agreement is the source of truth for the evaluation — not the firm's marketing page, not the dashboard label, not what someone in a community said the numbers were. Confirm the numbers from the agreement itself.
Six numbers from the evaluation agreement are inputs to decisions that run from the first session through the last: (1) Starting balance — the account dollar amount that sets the day-one trailing drawdown floor and the drawdown distance for the sizing formula. For most standard accounts this equals the labeled account size tier; for promotional accounts it sometimes differs. Read the evaluation starting balance article for the full scenario where the starting balance and the label diverge: what the funded futures evaluation starting balance is and how it sets the day-one floor. (2) Profit target — the cumulative net profit required to close the evaluation. The profit target and the minimum trading days together determine the earliest possible pass date when combined with the consistency rule ceiling. (3) Trailing drawdown distance (DTF) — the dollar distance between the account's highest balance ever reached and the trailing drawdown floor. Used to calculate the initial floor position (starting balance minus DTF) and the per-session sizing limit (DTF divided by 10). (4) Daily loss limit (DLL) — the maximum dollar loss allowed in a single session before the platform closes all positions and locks trading for the day. Used to calculate the per-trade risk limit (DLL divided by 4). (5) Consistency threshold — the maximum percentage that any single session's net profit can represent of the running cumulative total. Common thresholds are 25%, 30%, and 40% depending on the firm. A session that exceeds the threshold is not a violation on its own — it creates a consistency hold that blocks the evaluation from passing until additional sessions bring the best-day percentage below the threshold. (6) Minimum trading days — the minimum number of qualifying sessions that must be completed before the profit target can close the evaluation. A qualifying session is any session in which at least one trade was completed — winning, losing, or breakeven sessions all count at most firms. See the full mechanics in funded futures minimum trading days.
The evaluation agreement is distributed in three common forms depending on the firm. At Apex Trader Funding, the evaluation terms and parameters appear in the account confirmation email and in the firm portal under the account details section. At Topstep, the performance agreement is accessible in the Member Statements area of the trading platform and is also emailed at account activation. At Earn2Trade, the evaluation parameters are in the account confirmation email and in the trading platform dashboard under account details. At firms using the Rithmic platform backend (Apex, Earn2Trade, some smaller firms), the account parameters visible in the platform — account size, trailing drawdown threshold, and daily loss limit — should match the agreement values. Confirm the dashboard display against the agreement numbers rather than reading only the dashboard, because dashboard labels vary by platform skin.
For the consistency threshold and minimum trading days, the evaluation terms document is the reliable source — not the dashboard, which typically does not display these parameters directly. If the evaluation was purchased at a discounted or promotional price, check whether the promotional terms modified any of the six parameters from the standard tier values. Promotional evaluations sometimes carry a different profit target multiplier, a different minimum trading day count, or a different starting balance from the standard account at the same labeled tier. Confirming all six from the agreement document — not from memory of the standard tier or from a community post about the promotional terms — takes under five minutes and eliminates the risk of a misremembered parameter creating an incorrect calculation before the first session.
From the six agreement parameters, four derived inputs must be calculated before the first session: (1) Initial floor = starting balance minus trailing drawdown distance. Example: $50,000 starting balance with a $2,000 DTF gives an initial floor of $48,000. Verify this against the floor value displayed on the evaluation dashboard — if they do not match, contact the firm before placing any trades. (2) Per-session sizing limit = DTF divided by 10. Example: $2,000 DTF gives a per-session limit of $200. This is the maximum dollar loss the session is allowed to produce before the daily loss limit closes positions, expressed as an operating ceiling rather than the hard DLL limit. (3) Per-trade risk limit = DLL divided by 4. Example: $2,500 DLL gives a per-trade limit of $625. This is the maximum risk on any single trade, sized so that four consecutive max-loss trades reach but do not exceed the DLL. (4) Consistency ceiling input = the single-session net profit at which the consistency threshold would trigger. Example: if the consistency threshold is 30%, and after 10 sessions the cumulative is $1,200, a session producing more than $360 creates a consistency hold. On day zero, the ceiling input cannot be calculated precisely because the cumulative is zero — but noting the threshold percentage before session one means the ceiling check is automatic during the evaluation without having to look up the rule mid-session.
Recording all ten values — six agreement fields plus four derived inputs — in the evaluation journal before session one means none of them need to be recalculated mid-session or after a bad trade. The funded futures evaluation journal article covers the minimum viable journal format that pre-populates these ten fields and adds per-session log entries from session one onward.
Part 2 of 4 — Platform setup
Platform setup errors on session one — oversized positions, unexpected overnight holds, login issues — are avoidable. The setup takes under 10 minutes on day zero.
The per-session sizing limit (DTF divided by 10) is a dollar amount — it must be converted to a contract ceiling for the primary instrument before the platform limit can be set. The conversion requires the instrument's tick value and the stop distance the process typically uses. Contract ceiling = floor((DTF divided by 10) divided by (stop ticks multiplied by tick value)). For MNQ with a 5-tick stop and a $0.50 tick value, $200 per session supports floor(200 divided by (5 multiplied by 0.50)) = floor(80) = 80 contracts — which is well above normal sizing. For ES with a 4-tick stop and a $12.50 tick value, $200 per session supports floor(200 divided by (4 multiplied by 12.50)) = floor(4) = 4 contracts. The instrument matters significantly for this calculation. Confirm the correct stop-width assumption for the primary instrument against the actual process, not a theoretical minimum stop, and set the platform maximum position size to the calculated ceiling before session one.
On NinjaTrader, the position size limit is accessible in Account settings under Max Position (Long) and Max Position (Short). On platforms using the Rithmic backend (Apex, Earn2Trade), the firm typically imposes an account-level position limit that appears in the trading platform account dashboard — confirm the displayed firm limit against the calculated ceiling and use the lower of the two. If the firm limit is already tighter than the calculated ceiling, no additional platform limit is needed. If the firm limit is higher than the calculated ceiling, add a platform-side order template or maximum order size setting to enforce the lower ceiling per session. See the full pre-session sizing routine and the binding-constraint shift check in funded futures position sizing checklist.
Most funded futures evaluations permit overnight positions but most funded futures trading processes do not include them as a regular feature of the approach. The overnight flag in the platform — sometimes called "flatten at end of session" or "auto-flatten" — should be on (set to close all positions at session end) unless holding overnight is an intentional part of the trading plan. Leaving the flag off when overnight holds are not planned creates two risks: accidental overnight exposure from forgetting to close a position at session end, and the EOD trailing drawdown floor advance that occurs at settlement regardless of whether the position is profitable at close. The trailing drawdown floor advances at settlement for EOD firms even on positions that are open and losing at the time of settlement — a mechanism that can compress floor-room without a realized gain. See the full mechanics in funded futures overnight positions.
On NinjaTrader, the auto-flatten setting is in Account properties under "Flatten & Cancel" with a configurable time. On Rithmic platforms, the setting is typically in the risk management panel or administrator portal. Confirm the setting is active before session one by checking the platform on day zero rather than assuming the default. If overnight holds are planned for specific setups, confirm that the evaluation agreement permits overnight positions for the instruments being traded before the first session — some firms restrict overnight holds on specific instruments even when the account is generally permitted to hold overnight.
Three final platform checks on day zero: (1) News calendar import: add the economic calendar feed to the trading platform or trading workspace. NinjaTrader supports calendar overlay via third-party providers. TradingView has a built-in economic calendar. At minimum, add the next four FOMC dates, the next two NFP dates, and the next two CPI dates to a note or calendar event as a fallback if the platform does not display calendar events. The news calendar check is used in Part 3 of this article for the first-five-sessions review and then daily as part of the pre-session routine going forward. (2) Login credentials test: log in to the evaluation account and confirm all platform connections — data feed, broker connection, and account credentials — are active before the first session. A connection issue discovered 10 minutes before session one reduces the usable trading window; the same issue discovered the evening before can be resolved without pressure. (3) Instrument configuration: confirm the primary instrument's contract specification is correct in the platform — tick size, tick value, point value, and session hours match the standard contract specification for the evaluation period. Verify that the correct front-month contract is loaded and that a contract rollover notification or plan is in place if the evaluation spans a quarterly rollover date.
Part 3 of 4 — News calendar check for the first five sessions
A news event on session two of an evaluation carries more DLL risk than the same event on session 20. The first five sessions have the largest possible impact on the consistency denominator from a single event. Checking the calendar before session one allows the first week's posture to be set deliberately.
Four scheduled economic events produce the price moves most likely to exceed the DLL in a single session on funded futures accounts: (1) Non-Farm Payroll (NFP) — releases the first Friday of each month at 8:30 AM ET. ES and NQ typically gap 20-40 points on an NFP miss or beat; CL and GC move on the employment-to-demand read. (2) FOMC rate decision — releases eight times per year, typically on a Wednesday at 2:00 PM ET with a press conference at 2:30 PM ET. The 2:00 PM window carries volatility comparable to a major gap event and persists through the press conference. (3) CPI (Consumer Price Index) — releases monthly, typically mid-month at 8:30 AM ET. A hot or cold CPI print moves ES, NQ, and bonds sharply in the first 5 minutes. (4) EIA Crude Oil Inventory Report — releases every Wednesday at 10:30 AM ET and moves CL (crude oil futures) significantly. Traders on CL as the primary instrument treat EIA weeks the same as NFP weeks for DLL planning purposes. The full event-by-event framework — including the post-news protocol for finding setups after the 10-minute spike window — is in how to handle news events on a funded futures account.
The check is a date-against-calendar comparison: list the first five weekdays after the evaluation start date, then cross-reference against the economic calendar for high-impact events. The relevant economic calendar sources with confirmed event dates are ForexFactory (forexfactory.com/calendar — filter by High Impact for USD), the CME Group economic calendar, and the Federal Reserve FOMC schedule (federalreserve.gov/monetarypolicy/fomccalendars.htm for confirmed FOMC dates). NFP always falls on the first Friday of the month — if the evaluation starts in the first three weeks of a month, the first-Friday NFP date is calculable by counting days from the start date. CPI typically falls on the 10th through 15th of the month — check the BLS CPI release calendar (bls.gov) for the exact date in the evaluation month. FOMC dates are announced by the Federal Reserve months in advance and do not move.
If a high-impact event falls within the first five sessions, flag the session with the event time and the pre-planned posture decision. The posture options are: (a) Flat for the day — no trades placed on the event day; the minimum trading days clock does not advance for most firms unless at least one trade is placed, so a flat day is a rest day, not a qualifying day. (b) Sized down for the post-news setup — wait for the 10-minute spike window to close after the event, then enter a setup at half the normal position ceiling. This allows the session to count as a qualifying day while limiting DLL exposure during the news window. (c) Normal session with early cutoff — trade the pre-news window (before 8:25 AM ET) and close all positions before 8:30 AM ET, then stand aside through the event. This approach captures pre-news movement and counts as a qualifying session while avoiding the event window entirely.
The consistency rule threshold applies to the running cumulative net profit — not to an all-time account balance or to a fixed denominator. In the first five sessions, the cumulative is small. A large winning session in sessions one through five creates a best-day percentage that is difficult to dilute below the threshold without many additional sessions. Example: consistency threshold is 30%, five sessions into the evaluation. Running cumulative after four sessions: $700. Session five has a news-event gap that produces a $450 gain. Best-day percentage: $450 divided by ($700 plus $450) = $450 divided by $1,150 = 39.1%. The session created a consistency hold. Clearing the hold requires either additional sessions that grow the cumulative without a comparable single-day spike, or — at firms where a separate session cap exists — being within the threshold range over the next payout window. The same $450 day on session 18, when cumulative is $2,000, produces $450 divided by $2,450 = 18.4% — well below the 30% threshold. Early-session news events carry consistency risk that later-session news events do not, because the denominator is small. See the full consistency rule mechanics in the consistency rule explained.
Part 4 of 4 — Journal preparation
A journal with no entries before session one is a journal that requires setup after the first loss or the first win. Pre-populating it on day zero ensures the first session's result has somewhere to go immediately.
Ten fields belong in the evaluation journal before session one begins: six agreement values and four derived inputs. Agreement fields: (1) starting balance, (2) profit target, (3) trailing drawdown distance (DTF), (4) daily loss limit (DLL), (5) consistency threshold percentage, (6) minimum trading days. Derived inputs: (7) initial floor (starting balance minus DTF), (8) per-session sizing limit (DTF divided by 10), (9) per-trade risk limit (DLL divided by 4), (10) evaluation start date plus earliest possible pass date (start date plus minimum trading days — the floor on timeline, not a prediction). Two additional contextual fields worth recording on day zero: the primary instrument and the firm name. If the evaluation is on a multi-step structure (two-step or step-up), record the phase count and the parameters for each phase separately. Confirm the evaluation start date — the date that session one will actually occur — against the account activation confirmation from the firm. Some evaluations have a 24-48 hour post-purchase activation window; the start date is the activation date, not the purchase date.
These ten fields are the minimum viable day-zero journal state. The full evaluation journal format — including the per-session log fields, the running consistency denominator calculation, and the post-failure diagnostic columns — is in the funded futures evaluation journal article, which describes the minimum viable journal as a 10-field per-session log and explains what 20 sessions of data produces for the four post-failure diagnostic steps.
With the ten day-zero fields pre-populated, session one's log entry requires only the session-specific results: (1) session date, (2) primary setup used (entry condition that triggered the trade), (3) contracts traded (must be at or below the per-session contract ceiling from day zero), (4) entry price and stop price, (5) exit price, (6) ticks captured and dollar result, (7) session net P&L (sum of all trades), (8) running cumulative net P&L (session one result only), (9) best-day percentage (session one P&L divided by cumulative — equals 100% for a positive session one, irrelevant for a losing or breakeven session one), and (10) floor position after the session (calculated from the closing balance against the initial floor, or confirmed from the dashboard at EOD for EOD firms). Filling these ten fields immediately after the session closes — not the next morning — means the session is logged while the trade decisions are still fresh and before the next session's preparation begins.
The floor position field is the most important post-session field to confirm from the dashboard rather than calculate manually, particularly at EOD firms where the floor advances at settlement. At intraday firms, the floor may have advanced during the session to the intraday high minus DTF — confirm the final floor value from the dashboard at session end, not from a mid-session calculation. Record the confirmed dashboard floor value in the journal immediately after the session closes. A floor value that differs from the calculated floor by more than a rounding difference warrants a call to the firm to confirm the account was settled correctly.
The evaluation journal's value is not in the passing scenario — it is in the failing scenario. When an evaluation fails, the journal is the data source for the four-step post-failure diagnostic: which sessions produced losses, what the sizing was in each session, whether the failure was a single session or a multi-session pattern, and whether the breach came from position size, stop management, or news exposure. A journal that has entries from session one onward — with consistent field definitions and daily floor position — allows the diagnostic to start immediately after the failure without reconstructing the data from memory or from platform reports. A journal that has no pre-populated day-zero fields may have missing or inconsistent early-session entries, because the fields were added after the first few sessions when it became clear a log was needed. Inconsistent early entries are the sessions most likely to contain the cause of a failure, because failures often begin in the first week when the process is not yet routine under the evaluation's specific constraint set.
Pre-populating the journal on day zero is not paperwork — it is the evidence standard that makes the post-failure diagnostic possible. The how to recover after a failed funded futures evaluation article covers the four-step diagnostic and the five-session evidence bar before restarting, both of which require a journal with consistent data from session one forward to execute correctly.
Four steps before session one: confirm all six gate parameters from the evaluation agreement and calculate the initial floor and both sizing inputs; set the platform position size limit to the DTF-divided-by-10 contract ceiling, confirm the overnight flag, and test login credentials; check the first five scheduled sessions against the major economic news calendar and decide in advance whether to be flat, sized down, or hold for a post-news setup on any flagged sessions; and pre-populate the evaluation journal with the ten day-zero fields so the first session result can be logged immediately after the close.
Six parameters: starting balance (sets the initial floor and DTF sizing input), profit target (the cumulative net profit gate), trailing drawdown distance or DTF (used for floor calculation and per-session sizing), daily loss limit or DLL (used for per-trade risk limit), consistency threshold percentage (typically 25–40%), and minimum trading days. From these six, calculate: initial floor (starting balance minus DTF), per-session limit (DTF divided by 10), per-trade limit (DLL divided by 4), and the earliest possible pass date (start date plus minimum trading days).
Convert the per-session dollar limit (DTF divided by 10) to a contract ceiling using the instrument's tick value and typical stop distance: contracts = floor of (per-session limit divided by (stop ticks multiplied by tick value)). On NinjaTrader, set Max Position in Account settings. On Rithmic-connected platforms, confirm the firm-set account limit against the calculated ceiling and use the lower of the two. If the firm limit is higher than the calculated ceiling, add a platform order template or maximum order size to enforce the lower limit per session.
List the first five weekdays after the evaluation start date and cross-reference against the economic calendar on ForexFactory or the CME Group calendar, filtering for high-impact USD events. NFP releases the first Friday of each month at 8:30 AM ET. FOMC dates are published months in advance by the Federal Reserve. CPI typically releases between the 10th and 15th of each month at 8:30 AM ET. EIA crude oil inventory releases every Wednesday at 10:30 AM ET. For any flagged session, decide in advance: flat for the day, sized down for the post-news setup window, or a pre-news only session with early cutoff before 8:30 AM ET.
Ten fields: starting balance, profit target, DTF, DLL, consistency threshold percentage, minimum trading days, initial floor (starting balance minus DTF), per-session sizing limit (DTF divided by 10), per-trade risk limit (DLL divided by 4), and the evaluation start date plus earliest possible pass date (start date plus minimum trading days). With these ten pre-populated, session one's log entry requires only the session-specific result fields — entry, exit, P&L, cumulative, best-day percentage, and floor position — which can be filled immediately after the close without recalculating any inputs.
Day zero is 30 minutes. Session one is the live start. There is no setup window between them.
The Jalen Method includes the day-zero checklist as a pre-evaluation standard, not an optional step. The same routine that catches a wrong starting balance on a promotional account on day zero would take three sessions of confusion to discover once trading has started. First 100 founding seats at $19/mo — locked for life.