Start here · Stage 1 · Free
The evaluation-day-before checklist tells you what to configure. This article covers how — the specific navigation path on each major platform, the conversion formula that turns a dollar limit into a contract count, the alert threshold that fires before the DLL is reached rather than at it, and how to mark your first five sessions against the news calendar before the first trade is placed.
Part 1 of 4 — What platform setup does before session one
The evaluation agreement defines your DTF, DLL, and position sizing limits in dollar terms. The platform setup translates those dollar limits into contract counts, alert thresholds, and calendar flags — so enforcement is automatic, not manual.
Five things to configure before placing the first trade on a funded futures evaluation account. Each one corresponds to a specific setting in the trading platform that does not exist by default and must be set intentionally.
The evaluation agreement specifies the Daily Trailing Drawdown (DTF) in dollars. The position size limit converts DTF÷10 into the maximum number of contracts per position for each instrument you plan to trade. This limit prevents a single position from consuming more than one-tenth of the daily trailing drawdown in a single movement. The platform setting enforces this limit in contract terms — the software must translate the dollar calculation into a contract count before you can enter the setting. Part 2 of this article covers that conversion and the platform-specific navigation path for Rithmic, Tradovate, and NinjaTrader.
Most platforms allow you to configure a dollar-based alert when cumulative daily P&L falls below a threshold. Set this to 90% of the DLL — so if the DLL is $500, the alert fires at $450 in daily losses. The alert gives you time to exit remaining positions and stop trading for the session before the DLL is actually breached. Part 3 covers the specific distinction between an alert and an auto-liquidate setting, and why the 90% threshold is the right default rather than setting the alert at the DLL itself.
Most funded futures evaluation agreements prohibit overnight positions or require explicit account-level permission for them. The overnight position flag in your platform controls whether the platform will allow positions to remain open at session close. If the agreement prohibits overnight positions, this flag should be off — meaning the platform will reject or alert on any open position approaching settlement. If the agreement allows overnight positions with explicit intent, leaving the flag on requires a conscious decision before each session that includes a position planned to hold. The default should be off; enabling it session-by-session when planned is safer than leaving it on and forgetting.
The economic calendar provides release times for FOMC, NFP, CPI, and EIA events — the four event categories that carry the most DLL risk during a funded futures evaluation. Import the calendar into your platform or set up a standalone calendar source before session one. Filter to high-impact events only; lower-impact releases do not require the same posture adjustment. Part 4 covers the recommended calendar sources and how to mark the first five sessions before session one starts.
Log in to the evaluation account — not the demo or sim account — before the first trading session. Confirm that the account balance matches the agreement's starting balance, that the instrument you plan to trade is listed, and that the dashboard metrics (trailing drawdown floor, DLL remaining, cumulative profit, best-day percentage) are visible and show the day-zero state. Discovering a login issue, an account-link error, or a missing instrument at the start of session one wastes the session and creates decision pressure before the first trade. The five-minute login test before the first live session eliminates this category of problem.
None of these five settings exists in the platform by default. All five must be configured intentionally, using the specific evaluation agreement numbers as inputs. The remainder of this article covers how to do each one — starting with the position size limit, which is the most calculation-intensive setup step and the one where platform behavior differences across Rithmic, Tradovate, and NinjaTrader matter most.
Part 2 of 4 — The position size limit on Rithmic, Tradovate, and NinjaTrader
The formula is the same across all platforms. The navigation path and the enforcement behavior differ. Tradovate auto-closes at the ceiling; Rithmic and NinjaTrader warn but do not automatically exit.
The conversion formula: contract ceiling = floor( (DTF ÷ 10) ÷ (stop ticks × tick value per contract) )
Where:
Example on a $50K account with a $2,500 DTF, trading MNQ with a 15-tick standard stop and a $2.00 tick value per contract:
For ES with a 6-tick stop and a $12.50 tick value: $250 ÷ (6 × $12.50) = $250 ÷ $75 = floor(3.33) = 3 contracts. For NQ with a 15-tick stop and a $20.00 tick value: $250 ÷ (15 × $20.00) = $250 ÷ $300 = floor(0.83) = 0 contracts — NQ requires a wider DTF or a tighter stop to be tradeable under this sizing rule at the $50K tier. See the position sizing checklist for the full formula and instrument comparison across tiers.
In Rithmic (accessed through R | Trader or broker-specific interfaces built on the Rithmic API), the position limit is configured in the Risk Manager panel. Navigate to: Risk Manager → Account-Level Risk → Max Position Size. Find the instrument row for each contract you plan to trade and enter the contract ceiling calculated above.
Important: Rithmic applies the limit per instrument. If you plan to trade both MNQ and ES, set the ceiling separately for each instrument row. A limit set on MNQ does not carry over to ES.
Rithmic enforcement behavior varies by broker configuration. Some setups display a warning when the position size limit is approached and reject orders that would exceed it. Others display a warning but allow the order to fill, then alert after the fact. Confirm with your broker which behavior is active — if your version does not hard-reject oversize orders, the platform limit is advisory rather than enforced, and discipline on the entry size is the actual enforcement mechanism.
In Tradovate, the position size limit is set in: Account Settings → Risk Settings → Max Position Size. Enter the contract ceiling for each instrument.
Critical: Tradovate auto-closes positions that reach the Max Position Size ceiling at market. This is fundamentally different from Rithmic and NinjaTrader, which display warnings but do not automatically exit positions. Because Tradovate will close the position when the ceiling is hit, the setting must be the exact DTF÷10 contract count — not DTF÷10 + 1 as a buffer.
If you set Max Position Size to 9 on an account where the DTF÷10 formula gives 8 contracts, Tradovate will not close the position until you reach 9 contracts — one contract above the evaluation's sizing limit. Holding 9 contracts when the limit is 8 is a position sizing violation. Set the ceiling at exactly 8, so Tradovate closes the position before you can exceed the evaluation's permitted size.
The auto-close behavior also means that if you attempt to add to a position and the new total would exceed the ceiling, Tradovate will reject the add-on order rather than fill it. This is protective — but only if the ceiling is set correctly. Verify the setting after entering it by checking the Risk Settings panel to confirm the displayed value matches your calculated ceiling.
In NinjaTrader, the position limit is configured through: Control Center → Accounts, then right-click the evaluation account and select Properties. Find the Max Position field and enter the contract ceiling for the primary instrument. NinjaTrader's position limit is instrument-specific — set it separately for each instrument in the account properties.
NinjaTrader's enforcement behavior: when a position approaches the Max Position limit, NinjaTrader displays a pop-up warning and prevents orders that would exceed the ceiling. It does not automatically close existing positions. This means the limit prevents adding to a position beyond the ceiling, but it does not exit a position that is already at the ceiling if the market moves against you.
The practical implication: if you are holding 8 MNQ contracts at the ceiling and the market moves in your favor by enough that you want to exit and re-enter, NinjaTrader will prevent re-entry at 9 contracts. It will not, however, automatically exit the 8-contract position if you hold it past a time limit or into the session close. Manual exit discipline remains necessary. The limit is a ceiling on size addition, not an automatic session-end liquidator.
After configuring the position limit on any platform, verify it by checking the setting value is correct against the evaluation dashboard and — on Tradovate — by confirming the displayed risk setting matches the number you entered. A misconfigured limit (set too high, or set in lots rather than contracts on some platforms) provides no protection. The five-minute verification step before session one is the check.
For where the DTF and DLL appear in the evaluation dashboard and how to read the live values before each session, see how to read a funded futures evaluation dashboard.
Part 3 of 4 — The daily loss alert
Most platforms offer both an alert (notification only) and an auto-liquidate trigger (market exit). They are different settings. Setting both correctly is not the same as setting just one.
The daily loss limit (DLL) in the funded futures evaluation agreement is the maximum cumulative net loss permitted in a single trading session before the session is terminated — and in most evaluations, a DLL breach during the evaluation period means the evaluation fails or requires a reset, not just the session ending.
The platform's daily loss alert is a tool that gives advance warning before the DLL is reached. It is not the same as the DLL — it is a configurable notification threshold that lets you take action before the actual limit applies.
The 90% threshold gives you a meaningful warning buffer: if the DLL is $500, the alert fires at $450 in daily losses, leaving $50 of room for an orderly exit from any open position. Setting the alert at 100% of the DLL (at the limit itself) eliminates this buffer — by the time the alert fires, you are at the limit with no clean exit window.
The 90% value is a starting point, not a fixed rule. If your typical stop-loss distance means a single-contract position can lose $40 in one tick sequence, a $50 buffer may not be enough — the position could breach the DLL before the stop-loss executes. In that case, set the alert at 80% of the DLL to give a wider buffer. The buffer should be large enough to exit any open position you typically hold with one full stop-loss execution.
Calculate: buffer needed = typical max loss on an open position at standard position size. Alert threshold = DLL − buffer needed, expressed as a dollar cumulative loss from session start.
Most modern platforms offer two distinct settings:
If your platform has both, configure the alert at 90% of the DLL and the auto-liquidate at 100% of the DLL (the actual DLL value). This gives you a two-stage response: the alert fires first and you exit manually; if the auto-liquidate threshold is reached before you act, the platform exits automatically to prevent the DLL from being breached further.
If your platform has only the alert (notification only), the alert at 90% of the DLL is still valuable — but manual exit discipline is the enforcement mechanism after the alert fires. Confirm which settings your platform offers before session one.
Different platforms track the daily loss alert against different P&L definitions. Some track only realized (closed) P&L — a position at an unrealized loss does not contribute to the alert trigger until it closes. Others track unrealized P&L in real time — an open position at a loss contributes to the alert threshold immediately.
The evaluation agreement defines whether the DLL is measured against closed P&L, open P&L, or a combination. If the agreement uses unrealized P&L (as most evaluations with intraday drawdown models do), set the platform alert to track unrealized P&L as well — so the alert fires before the DLL threshold is reached on the agreement's measurement basis, not on a different definition that may not trigger in time.
If the platform only tracks realized P&L for the alert and the agreement uses unrealized, the platform alert is insufficient on its own. In this case, monitor the open position's floating P&L manually against the DLL threshold rather than relying on the platform alert to fire in time. For how the evaluation agreement defines DLL measurement, see what happens when you breach the daily loss limit on a funded futures evaluation.
Part 4 of 4 — Economic calendar integration
Forex Factory and TradingEconomics are the two reliable calendar sources for funded futures evaluation traders. Both list FOMC, NFP, CPI, and EIA with local-timezone release times.
The economic calendar provides release times for the four events that carry the most DLL risk during a funded futures evaluation. These events are not random — they occur on predictable dates, produce volatility patterns that compress DLL room rapidly, and create false-direction moves that trigger stops at expanded ranges before the true direction develops. Knowing which of your first five evaluation sessions contain one of these events changes the posture for that session before the market opens.
Forex Factory (forexfactory.com) is the most commonly used calendar among futures day traders. After creating a free account, set your local timezone in the account settings — all release times display in your timezone without manual conversion. Use the High Impact filter to show only the events relevant to funded futures traders. Bookmark the filtered view so the high-impact-only calendar is the default each time you open it before a session.
TradingEconomics provides the same data and is integrated into several platforms directly — if your platform has a built-in economic calendar, it is likely pulling from TradingEconomics or a compatible feed. For platforms without a built-in calendar, use the web interface and filter to high-impact events in the same way.
Both sources are accurate for the four high-impact event categories. Do not rely on a broker's in-platform calendar without verifying that it is updated before each session — some platform-embedded calendars update on a delay or do not carry FOMC and NFP consistently. When in doubt, verify the release time against Forex Factory directly before each session that contains one of the four events.
The four event categories to track in the calendar before each session:
Before session one, open the calendar to the date of session one and check forward five sessions for any of the four high-impact events. Mark each flagged session in the journal's pre-populated calendar field (from the day-before article's journal preparation step).
The reason early sessions carry higher news risk than later sessions is the consistency denominator: if a news event in session two produces a large winning session, that session's P&L becomes the best-day figure against a very small denominator (two sessions' total P&L). The best-day percentage — calculated as the best single session's P&L divided by total cumulative P&L — can easily exceed the 30-40% consistency cap when the denominator is only two or three sessions' worth of total profit. A news-gap-fill win on session two that produces $800 in a day where cumulative P&L across the first two sessions is $1,200 puts the best-day percentage at 67% — well above most consistency rule caps. The session win does not violate any rule, but it makes the consistency rule very difficult to clear for the rest of the evaluation.
The three standard postures for a session with a high-impact event in the session window:
For the full post-news protocol and the four events with exact date-lookup instructions, see how to handle news events on a funded futures account.
The day-before checklist in the funded futures evaluation day-before article includes the news calendar check as Step 3. This article covered the how: which sources to use, which events to track, and why the first five sessions are the highest-stakes news window of the entire evaluation. Both steps together — the checklist and the setup — are complete when you can sit down at session one knowing the position limit is set, the alert is configured, and the first week's calendar is already marked.
In Rithmic's Risk Manager, navigate to Account-Level Risk and find the Max Position Size field for each instrument. Enter the contract ceiling from the formula: floor(DTF÷10 ÷ (stop ticks × tick value)). For a $50K account, DTF÷10 = $250. On MNQ with a 15-tick stop and $2.00/tick, the ceiling is 8 contracts. Set it separately for each instrument you plan to trade — a limit on MNQ does not carry to ES. Verify that your broker's Rithmic configuration hard-rejects oversize orders rather than displaying a warning that can be overridden.
Yes — Tradovate auto-closes positions that hit the Max Position Size ceiling at market. This is different from Rithmic and NinjaTrader, which warn but do not automatically exit. Because Tradovate exits at market when the ceiling is reached, set Max Position Size to the exact DTF÷10 contract count — not one above it. Setting it one contract higher means the auto-close fires only after you are already in violation. To set it: Account Settings → Risk Settings → Max Position Size → enter the exact ceiling for each instrument.
Set the alert at 90% of the DLL — for a $500 DLL, that is $450 in daily losses. The alert fires with enough room left to exit cleanly before the DLL is reached. Setting it at 100% of the DLL eliminates the buffer — by the time the alert fires, you are at the limit. If your platform offers both an alert and an auto-liquidate trigger, set the alert at 90% and the auto-liquidate at 100%. Also confirm whether the alert tracks realized P&L, unrealized P&L, or both — the answer must match how the evaluation agreement measures the DLL, or the alert may fire too late.
Forex Factory and TradingEconomics are the two most reliable sources. Forex Factory shows release times in your local timezone after account setup and filters to high-impact events only — the relevant view for funded futures traders. Set your timezone in account settings and bookmark the high-impact filter. TradingEconomics provides the same data and is built into some platforms directly. Verify broker-embedded calendars update before each session — some platforms carry a delayed or incomplete feed for FOMC and NFP.
Yes — but with a modified posture. Three options: (1) flat before and during the event, entry allowed 10 minutes after the initial spike closes; (2) sized-down post-event entries only, no pre-news exposure; (3) pre-news session only, stop trading 30 minutes before the release. On days with less than 50% of daily DLL room remaining, the flat-until-after-event posture is the most conservative and prevents DLL compression by a gap fill. The news events article covers the four events and the full post-news protocol: how to handle news events on a funded futures account.
Platform-specific setup steps from 9 years on live funded accounts — Rithmic, Tradovate, and NinjaTrader.
Most funded traders place their first evaluation trade before the platform is fully configured. The method builds the setup habit first — position limit set, DLL alert calibrated, calendar marked — so the first session starts with infrastructure in place rather than discovered mid-trade. First 100 founding seats at $19/mo — locked for life.