Stage 2 · Free
A funded futures evaluation has two compliance layers that operate independently. The trading platform enforces position size limits and the daily loss limit in real time — when either is breached, the platform acts immediately. The funded futures firm audits compliance in a separate layer after each session or at the end of the evaluation period: recalculating the consistency rule percentage from its own records, verifying trailing drawdown floor accuracy on EOD-model accounts, and checking trade-level compliance against the evaluation agreement. Most traders know the platform layer because it produces immediate visible consequences. The firm's audit layer is less visible — flags can appear days or weeks after a trade was placed, and the categories it monitors differ from what the platform enforces.
Part 1 of 4 — Two monitoring layers
Knowing which layer detected an issue — and what that layer can and cannot see — is the first step in understanding any compliance flag. A flag from the platform's real-time layer produces an immediate, unambiguous platform action. A flag from the firm's audit layer arrives later, through a different channel, and requires a different response.
The trading platform (Rithmic, Tradovate, NinjaTrader, or similar) enforces the evaluation's hard quantitative limits in real time as orders are placed. The three categories enforced at the order level are: the position size ceiling derived from the DTF÷10 formula (the maximum contract count allowed in a single position), the daily loss limit remaining (the platform tracks the running intraday P&L and triggers auto-liquidation or an account halt when the DLL is reached), and the trailing drawdown floor on intraday-model accounts (the platform tracks the floor in real time and closes positions when the balance approaches or breaches the floor).
When the platform's real-time enforcement triggers, the consequence is immediate: the order is rejected before fill, the position is auto-closed, or a session halt is placed on the account. The trader knows immediately — the action appears in the platform's order log. This is the compliance layer most traders understand because it produces visible, real-time consequences. See the funded futures evaluation dashboard guide for how to track DLL remaining and trailing drawdown floor during the session so the platform's enforcement layer rarely needs to intervene. The platform's auto-liquidation is a safety net, not a normal operating condition.
The firm's compliance audit runs separately from the platform's real-time enforcement and examines rule categories the platform does not monitor in real time. The three categories most commonly audited after the session rather than during it are: the consistency rule percentage (the firm's batch calculation of best-day P&L as a percentage of total period P&L, run at end of day or end of period using the firm's own denominator definition from the evaluation agreement), the trailing drawdown floor accuracy on EOD-model accounts (the firm verifies that the floor advanced to the correct level at the prior day's settlement price, not during the intraday session), and trade-level compliance records (the firm's clearing records from the clearing firm, which include exact trade timestamps, instrument codes, and commission-adjusted net P&L for each closed trade).
On EOD-model accounts, the trailing drawdown floor does not advance during the session — it advances only at settlement. This means the platform's intraday floor display may not match the correct post-settlement floor value. The firm's audit layer reconciles this after each trading day. See funded futures trailing drawdown floor mechanics for the EOD vs intraday model distinction and why the floor settlement timing affects how the firm monitors compliance on EOD accounts. See funded futures account metrics tracking for how to track the five metrics between sessions in a way that matches the firm's audit inputs rather than only the intraday dashboard view.
The platform's real-time layer is an execution safeguard: it prevents a position from growing beyond the DTF ceiling and prevents a session from continuing after the DLL is consumed. It is not a complete compliance system — it operates on the data available in the trading session, which does not include end-of-period consistency calculations or clearing-firm-settled net figures. The firm's audit layer is the compliance verification: it uses the clearing firm's settlement records (which are authoritative on net P&L, instrument codes, and trade timestamps) and the firm's own rule interpretation to verify that the evaluation was conducted within the evaluation agreement's terms.
The practical consequence of this structure is that a trader can complete an evaluation session with no platform alerts and still receive a compliance flag from the firm's audit layer afterward. The platform's silence does not mean the firm's audit will be clean. The two systems check different things from different data sources at different times. Understanding this is the prerequisite for interpreting any post-session or post-pass communication from a funded futures firm about an evaluation's compliance status. See how to read a funded futures evaluation agreement for where to find the compliance rules that govern both layers — the agreement's rule language determines what the firm's audit is checking for, independent of what the platform enforced during the session.
Part 2 of 4 — Three post-hoc flag categories
Post-hoc flags are not all violations. Some are calculation discrepancies — the firm's formula produced a different number than the dashboard's display, but the difference is explained by a denominator definition or a settlement timing difference, not by a behavioral error. Distinguishing the two types before responding is the first step after receiving any flag communication.
The most common post-hoc flag category. The firm's settlement records come from the clearing firm and reflect net closed P&L: the gross profit from each trade minus every commission and fee charged on that trade. The evaluation dashboard may display gross P&L — the raw profit before deductions — or it may display net P&L calculated using a different commission rate than the clearing firm applied. When the two figures differ, the firm's clearing record is the authoritative number for the evaluation's profit target check.
The three scenarios that produce net profit discrepancies are: the dashboard displays gross P&L while the firm settles on net (most common — the trader reaches the dashboard's target while the net figure is short); overnight positions settle at the following day's opening price rather than the intraday close the dashboard displayed (producing a different realized P&L than the session-close figure showed); and instrument-specific commission rates differ between what the platform estimated and what the clearing firm charged (futures on some exchanges carry variable exchange fees that are not reflected accurately in the platform's estimated commission display). See why funded futures evaluation passes get rejected for how a net profit discrepancy triggers a post-pass rejection and the buffer formula for avoiding it.
The consistency rule percentage — best-day P&L as a percentage of total period P&L — is calculated by the firm as a batch job, not in real time by the platform. The firm's calculation uses the denominator definition specified in the evaluation agreement, which may differ from the denominator the dashboard displays. The two most common denominator differences are: the dashboard uses net positive sessions as the denominator (excluding losing days from the total) while the firm uses all closed sessions including losses; and the dashboard uses gross P&L in the denominator while the firm uses net P&L after commissions.
When the firm's denominator is larger than the dashboard's denominator, the firm's percentage is lower — the same best-day P&L looks like a smaller share of a larger total, making the cap harder to breach. When the firm's denominator is smaller, the firm's percentage is higher — the same best-day P&L looks like a larger share of a smaller total, and a day that did not appear to breach the cap on the dashboard may breach it in the firm's audit. The consistency rule section of the evaluation agreement specifies the denominator definition. That section — not the dashboard label — is the source of truth for what percentage the firm will calculate. See funded futures account metrics tracking for how to track the consistency denominator between sessions in a way that matches the firm's audit inputs rather than only the dashboard display.
The firm's account integrity review examines whether the evaluation account was traded by one person operating independently. The specific checks vary by firm, but the most common audit methods are: login pattern review (IP addresses, login times, and device identifiers are compared against the account history — logins from multiple geographies in the same session or from unfamiliar IP ranges trigger a flag for review), trade pattern review (the timing, sizing, and instrument sequence of trades are reviewed for patterns that suggest coordination across multiple accounts or a systematic approach the firm restricts), and credential verification (some firms require identity documentation to verify that the person trading the account matches the registered account holder).
Account integrity flags are not limited to credential sharing. Traders using VPNs, cloud-hosted trading setups, or co-location services may generate login pattern flags without any actual rule violation — the IP addresses from a data center or VPN endpoint can match patterns the firm's review system flags for manual review. Account integrity violations that are confirmed — credential sharing, coordinated multi-account trading prohibited by the firm's rules, or documented account sharing — are typically treated as permanent disqualifications from the firm's program rather than failed evaluations eligible for restart. The evaluation agreement's account integrity and termination sections specify the consequences. See how funded futures firm rules actually differ for the rule categories that vary most between evaluation structures and how to identify which categories your firm's agreement covers.
Part 3 of 4 — Real violation vs calculation discrepancy
The diagnostic distinction matters because the response to each type is different. Disputing a real violation as a calculation error damages credibility and does not change the outcome. Accepting a calculation discrepancy as a real violation leads to unnecessary behavioral changes and an incorrect understanding of what caused the flag.
A real violation is a trade or account action that is explicitly prohibited by the evaluation agreement, regardless of whether the platform allowed it. The three categories that most commonly produce real violations in the firm's post-hoc audit are: trades in prohibited instruments (the evaluation agreement listed specific instruments or excluded instrument categories; the platform accepted the order but the agreement did not permit it), trades in restricted session windows (the agreement specified allowed trading hours; the platform did not enforce the window restriction but the trade timestamp falls outside the allowed window in the firm's audit records), and position sizes that exceeded the agreement's contract count ceiling in a specific intraday window the platform enforced only partially.
A real violation is confirmed by checking the specific trade or account action against the relevant clause of the evaluation agreement. If the agreement says the instrument is excluded and the trade is in the excluded instrument, the violation is real and the response is a behavioral correction: add a pre-session instrument verification step, add a session-window time check, or recalibrate the position size process against the agreement's full contract count rules. See funded futures evaluation prohibited instruments and trading hours for the two compliance categories that produce most post-hoc rule breach flags and how to build a pre-session check for both.
A calculation discrepancy is a difference between the firm's computed figure and the dashboard's displayed figure that is explained by a methodological difference rather than a rule violation. The two most common sources are: the denominator definition for the consistency rule (the agreement uses all closed sessions as the denominator; the dashboard uses net positive sessions — same trades, different total, different percentage) and the settlement timing for overnight positions on EOD-model accounts (the firm settles the position at the prior day's official settlement price; the dashboard displayed the intraday mark-to-market value that differed from the settlement price).
A calculation discrepancy is confirmed by tracing the firm's figure back through the evaluation agreement's formula definition. If the firm's number is mathematically correct given the agreement's formula — even if it differs from the dashboard's display — the discrepancy is not a violation, but it does mean the dashboard's display is not a reliable compliance monitor for that specific rule. The correct response is to request the firm's calculation and compare it step by step against the agreement's formula. If the firm's figure matches the agreement's formula and the dashboard's figure does not, the dashboard's display is the source of confusion and the evaluation agreement is the rule that governs. Future evaluations should track that specific metric using the agreement's formula rather than the dashboard's label.
Some flags arrive without enough information to immediately classify as real violation or calculation discrepancy. An account integrity flag that cites a login pattern anomaly may be a false positive from a VPN or a data center IP, or it may reflect actual credential sharing. A consistency rule flag may be a denominator difference, or it may reflect a session where the best-day cap was genuinely exceeded. Before responding to a flag in either category, the correct sequence is: request the specific finding in writing (which trade, which session, which account action triggered the flag), calculate the firm's figure independently using the evaluation agreement's formula definition, and compare the two. The comparison determines whether the response is a factual reconciliation (explaining the calculation difference) or an acknowledgment and behavioral correction (accepting the finding and fixing the process).
Do not respond to a flag with a dispute framed as "the platform didn't stop me" — that framing is irrelevant to the firm's audit, which checks the evaluation agreement rather than the platform's enforcement behavior. Do not respond with an acknowledgment if the finding is a calculation discrepancy that the agreement's formula does not support. Both responses require having the firm's specific figure before drafting any reply. Request the figure first, then respond.
Part 4 of 4 — What to do when a flag appears
The four steps are: get the specific finding, identify the category, apply the correct response type (reconciliation or correction), and locate the dispute resolution clause in the evaluation agreement before taking any formal dispute action. Skipping the first step and responding to a general flag notification before knowing the specific finding is the most common error in the response process.
When a funded futures firm communicates a compliance issue — either during the evaluation or after the pass notification — the first step is always a written request for the specific finding. Ask for: which rule was flagged, which trade or session is cited, what the firm's calculated figure is (net profit total, consistency percentage, specific trade timestamp, or specific account access pattern), and which clause in the evaluation agreement supports the finding. A general flag notification — "your account is under compliance review" or "a potential violation has been identified" — does not contain enough information to diagnose the category or respond appropriately.
The firm's response to this request is itself useful information. A firm with a clear compliance process will provide the specific finding, the specific rule reference, and the specific trade or session cited. A firm that cannot or will not provide these details after a compliance flag is communicating something about its review process that is relevant to your decision about continued participation in the firm's program. Document every communication with the firm's support team — dates, the content of each message, and the firm's response or non-response to specific requests. This documentation is the evidence base for any formal dispute if one becomes necessary.
When the specific finding confirms a real violation — a trade in a prohibited instrument, a session in a restricted window, a position size that exceeded the agreement's ceiling — acknowledge the finding and identify the specific process gap that produced it. The process gap is not "I didn't know the rule" — it is the specific check that was missing from the pre-session routine that would have caught the condition before the trade was placed.
The correction is specific: add the check that was missing. If the violation was a prohibited instrument, add an instrument verification step to the pre-session checklist that requires checking the evaluation agreement's allowed-instruments section before opening any position. If the violation was a restricted session window, add a session-start time check that requires verifying the current time against the agreement's allowed-hours clause before placing the first trade. Behavioral corrections are not effective without a process change — a general reminder to follow the rules produces different behavior than a specific yes/no check that must be answered before the session starts. See how to recover after failing a funded futures evaluation for the full diagnostic and correction protocol that applies equally to violations found during the evaluation and those that surface in the post-pass audit.
When the specific finding reflects a calculation discrepancy rather than a rule violation — the firm's figure differs from the dashboard's display but both can be explained by the denominator definition or settlement timing in the evaluation agreement — the response is a factual reconciliation. Provide the specific calculation you performed, identify the denominator definition or settlement price you used, and ask the firm to identify which step in the calculation produced a different figure in their records.
The reconciliation should be factual and specific: "The consistency rule section of the evaluation agreement states the denominator is [definition]. Using that definition, the best-day percentage on [date] was [calculated percentage]. Please confirm which denominator definition produced [firm's figure] and which clause of the agreement supports that definition." A reconciliation request is not a dispute — it is a request for the firm to show its calculation so you can verify that both calculations are using the same rule definition. If the firm's calculation and your calculation both use the evaluation agreement's formula and produce different numbers, request the trade-level data the firm used as inputs. The clearing firm's settlement records, which the firm's compliance team has access to, are the authoritative source of the trade timestamps and commission-adjusted net figures that feed the calculation.
If a reconciliation request or an acknowledgment of a finding does not resolve the flag — the firm maintains the finding is a violation and you have documentation showing it is a calculation discrepancy, or the firm has cited a rule that does not appear in the evaluation agreement's text — the formal dispute process is the next step. The dispute resolution clause in the evaluation agreement specifies the required format, the contact channel, the timeline, and the escalation path for formal disputes. Read that clause before submitting anything formally: some agreements require disputes to be submitted within a specific number of days after the finding notification; submitting outside that window may waive the dispute right regardless of the merits.
The dispute submission should include: the specific finding the firm communicated, your own calculation showing the discrepancy, the specific clause of the evaluation agreement you are relying on, and the documentation from the firm's communication supporting your position. The dispute is a factual record, not an argument — the goal is to produce a paper trail that shows your calculation and the firm's calculation, identify the specific step where they differ, and ask the firm to resolve the discrepancy by reference to the evaluation agreement's rule language. See how to read a funded futures evaluation agreement for where to find the dispute resolution clause and the other compliance-related sections that bear on the process.
Funded futures firms use two monitoring layers. The first is the platform's real-time enforcement: position size limits based on the DTF÷10 formula, daily loss limit remaining, and auto-liquidation triggers are enforced by the trading platform as orders are placed. A breach of a real-time rule results in an immediate platform action — the position is closed, a halt is placed, or the account is locked. The second layer is the firm's post-session audit: the firm reconciles its clearing records against the platform's trade history, recalculates the consistency rule percentage using its own denominator definition, and verifies trailing drawdown floor accuracy on EOD-model accounts. This second layer can flag violations the platform did not catch in real time — particularly trades in prohibited instruments or session windows that the platform accepted but the evaluation agreement excluded.
Yes. The platform's pass notification is based on the dashboard metrics reaching the profit target — it does not reflect the outcome of the firm's independent compliance audit. The firm's post-pass review includes a trade-level audit that can identify violations the platform did not flag during the evaluation. The three most common categories are net profit discrepancy (the firm's settlement records show a different net figure than the dashboard's gross display), consistency rule calculation differences (the firm's denominator definition produces a different best-day percentage than the trader's dashboard showed), and account integrity findings (credential or pattern-based review). When the post-pass audit finds a violation, the pass is reversed and the funded account is not provisioned.
A platform stop is a real-time enforcement action: the position is closed, the account is halted, or the order is rejected at the moment the limit is breached. The platform knows the DLL remaining and the position size ceiling in real time, and acts the moment those limits are hit. A firm flag is a post-session compliance finding: the firm's audit team reviews the trade records after the session or after the evaluation ends and identifies a discrepancy between the trade history and the evaluation agreement. A firm flag may appear on an account where the platform took no action during the session — because the firm monitors compliance categories the platform does not enforce in real time, such as the consistency rule calculation or the trailing drawdown floor accuracy on EOD-model accounts. The timing difference is the key distinction: a platform stop happens immediately and is unambiguous; a firm flag arrives later and requires a written response.
Not always. The consistency rule percentage is calculated as best-day P&L divided by total period P&L — but the denominator definition varies between firms, and the dashboard may use a different definition than the firm's compliance records. Some dashboards use net positive session P&L as the denominator (sessions where you lost are excluded from the total). The firm's compliance record may use all closed sessions including losing days as the denominator, which produces a lower percentage and makes the cap harder to breach. The denominator source of truth is the evaluation agreement's consistency rule section — not the dashboard label. If the dashboard shows a percentage and the firm's audit produces a different number, the agreement's denominator definition determines which figure is correct.
The first step is to request the specific finding in writing before responding or disputing. Ask for which rule was flagged, which trade or session triggered the flag, and what the firm's calculated figure was. Once you have the specific finding, diagnose whether it is a real violation or a calculation discrepancy. A real violation — a trade in a prohibited instrument, a position in a restricted session window, or a confirmed DLL breach — requires a behavioral correction before the next evaluation. A calculation discrepancy — a denominator difference in the consistency rule, a settlement timing difference on an overnight position, or a gross-vs-net difference — requires reconciliation of the firm's figure against the evaluation agreement's rule language. The dispute resolution clause in the evaluation agreement specifies the process and timeline for formal disputes. Read that clause before submitting anything formally.
Founding 100
The Founding 100 closes when 100 members are in. After that, pricing moves to the standard rate. If you're reading the library and working through evaluations, the founding tier is the time to join.
See the Founding 100 offer