Stage 3 · Free
Passing a funded futures evaluation produces an evaluation record — evidence that you followed the rules under those parameters during that attempt. A funded account track record is different: it is the post-activation operating history that shows whether the trading method is producing sustainable output under live funded account constraints. This article covers what a track record actually contains, how many sessions it takes to be meaningful, what the journal must show to make it legible, and how to use it as the input for the three decisions that require it — sizing up, scaling to multiple accounts, and choosing between reset, new evaluation, and continuing.
Part 1 of 4 — What a funded futures track record actually is
The distinction between an evaluation record and a funded account track record matters because they answer different questions. An evaluation record answers: did this trader follow the rules during a funded account simulation under these parameters? A funded account track record answers: is this trading method producing sustainable output under live funded account constraints, across multiple market conditions, across multiple payout periods? The second question requires more evidence and a different kind of journal structure than the first. See how to set up a funded futures evaluation journal for the 10-field per-session log that serves as the foundation for the evaluation record — the funded account track record builds on the same per-session log format but adds the period-level summary layer that evaluation-phase journaling does not require.
Balance history is the funded account's daily balance from activation day forward, showing the floor-lock point, the payout cycle arcs, and the current state. Balance history makes it possible to see whether the account is growing across periods, cycling around the same range, or slowly declining despite profitable individual sessions. A single payout period's net result does not show the trend — only balance history across multiple periods shows whether the account's overall trajectory is positive.
What the balance history reveals that the payout history alone does not: an account that produces two payouts of $1,200 each does not tell you whether the account's floor is rising with each payout or staying locked at the starting value because the balance never exceeded the floor by the drawdown distance. Balance history shows the floor-lock event date and the balance level at which the floor locked — the detail that makes the sizing-up decision an evidence-based calculation rather than a guess. The floor-lock event is the phase boundary in the funded account lifecycle; the balance history is the record that shows when it happened and what the account's trajectory looked like before and after it.
Payout history is the record of each payout the funded account has received: the approved amount, the split rate applied, the approval date, and the implied net profit from the prior period (approved amount ÷ split rate). Payout history is not the same as profit history. Payout history shows the net result after all five gates have been satisfied — profit threshold, split rate, minimum trading days, buffer ceiling, and consistency cap — which is a stricter filter than total profit across the same sessions. An account can generate positive net profit in a period and still fail the payout gates if the consistency cap was triggered or the buffer ceiling reduced the request below the minimum threshold.
What payout history contributes to the track record: the gap between an account's gross profit potential in a period and the actual approved payout is a diagnostic for which gates are binding most often. If the gap is consistently in the consistency cap (Gate 5), the method's profit distribution needs adjustment. If the gap is consistently in the buffer ceiling (Gate 4), the floor cushion is thinner than the sizing supports. Payout history across three or more periods makes this pattern visible in a way that a single period cannot. See how to calculate your funded futures payout before you request it for the five-gate arithmetic that determines what percentage of the account's gross profit period-over-period actually reaches an approved payout.
The consistency record is the most diagnostic component of the funded account track record. For each completed payout period, it captures: the best-day P&L, the period's total net profit, the resulting cap percentage (best-day ÷ total), whether a hold was triggered, and if so how many additional sessions it took to clear the denominator gap. The consistency record across multiple periods reveals whether the profit distribution is stable or whether a single outlier session is driving each period's result.
A consistency record that shows cap percentages of 26%, 29%, and 22% across three periods is a very different story from one that shows 22%, 44%, and 19% — both sets may have avoided holds if the firm's cap is 30% or 40%, but the variance in the second set signals that one outlier session per period is disproportionately influencing the result. A method with high variance in the consistency percentage may produce payouts reliably but is more vulnerable to a single outsized session pushing the ratio past the cap in any given period. Understanding this variance across periods — not just in the most recent period — is what separates managing the consistency rule from being at its mercy. See how the funded futures consistency rule works in the funded phase for the full denominator mechanics and how a rolling window model differs from the period-based structure described here.
The DLL trigger count is how many times the intraday DLL has been reached since funded account activation. The pattern is the context: which sessions produced the triggers, how they were distributed across the session count, and what market conditions were present. A DLL trigger is a behavioral signal — not a terminal event in most firm structures — but the pattern tells you what the single session is telling you about the method's risk exposure in specific conditions.
One isolated trigger in 20 sessions may be statistical variance: a news event, an unexpected market gap, a moment of discipline failure that was not repeated. Three triggers in twelve sessions using the same setup suggests the position size is too large for the setup's stop structure in current volatility — the DLL÷4 formula is producing a ceiling that the stop structure is regularly hitting. Five triggers across two different setups suggests the issue is not setup-specific but volatility-broad: the account is sized for conditions that are less volatile than what the market is delivering. The trigger pattern makes the difference between a single correction (reduce size on one setup) and a method-level recalibration (reduce size across all setups while the volatility regime persists). See how to handle a losing streak on a funded futures account for the decision tree that uses DLL trigger frequency as one of its primary inputs.
The behavioral layer is the per-session log entries that show what setup was used, what size was applied, and what the post-session classification note recorded. Without the behavioral layer, the balance history and payout totals tell you what happened but not why. A period with three DLL triggers and a low consistency cap percentage looks different in the journal if all three triggers occurred on high-impact news days (behavioral evidence: the method is not adjusting for scheduled news) versus if all three occurred on days with no scheduled events (behavioral evidence: the method's sizing is too aggressive for current daily volatility regardless of news).
The behavioral evidence also provides the distinction between a recoverable breach and a structural failure that the reset decision requires. A recoverable breach shows as a cluster of journal entries where the setup was sound but execution deviated — position held past the exit signal, or size was added mid-session in violation of the pre-session ceiling. A structural failure shows as a series of journal entries where the setup and sizing were followed correctly but the outcomes were consistently negative across multiple setups and conditions. The second pattern requires a different response than the first, and the journal's per-session entries are the only source that makes the distinction visible. The evaluation journal article covers how to structure those entries during the evaluation phase; the same structure carries forward into the funded account track record and becomes more valuable with each additional period of data.
Part 2 of 4 — How many sessions and how long
These thresholds are self-imposed standards derived from the signal-to-noise ratio in the track record, not firm requirements. A 15-session record with one payout can support some decisions — whether to continue vs reset, for example — but not others, like whether to add a second account. The minimum is defined by the decision being made and the evidence it requires, not by an arbitrary session count that applies across all method types.
A sizing-formula-based method uses DTF÷10 and DLL÷4 to set per-session contract ceilings rather than relying on session-by-session discretion about position size. For this type of method, the minimum track record that supports structured decisions is 20 funded sessions that include at least two different market condition types: trending (sessions where a directional move sustained for the majority of the session) and mean-reverting (sessions where price oscillated without establishing a sustained direction). Both condition types matter because the formula ceiling that works well in trending conditions — where one direction move pays off cleanly and the stop is rarely at risk — may be too large for mean-reverting conditions where position entries face frequent stop-outs and the DLL is at higher risk.
The 20-session threshold reflects the minimum at which the formula's per-trade ceiling has been exercised enough times across enough conditions to determine whether it is correctly sized. Below 20 sessions, a single outlier winning period can mask a formula that is marginally too large — the winners in trending sessions offset the stop-outs in mean-reverting sessions, and the net result looks acceptable but the DLL trigger pattern is already pointing to a structural sizing problem. The session count threshold and the condition-type variety requirement are both necessary. A 20-session record in only trending conditions does not meet the minimum. A record with both condition types but only 12 sessions does not meet the minimum. Journal entries must include session classification — trending or mean-reverting — so the condition-type distribution can be assessed from the record. The evaluation journal article's setup classification field serves this purpose when carried into the funded account journal structure.
A discretionary method does not fix the position size by formula. The sizing decision is made session by session based on the trader's assessment of the setup quality, the market conditions, and the account state. For this type of method, the consistency window outcome is the primary diagnostic — because the consistency rule's denominator accumulates the discretionary method's profit distribution across the period, and the cap percentage reveals whether the sizing decisions are clustered around a few large sessions or distributed across many sessions.
Two completed consistency windows — two separate payout periods that each reached approved payout status — are required because a single period's consistency outcome may reflect luck in the distribution rather than a stable pattern. A period where the best-day percentage was 24% might indicate disciplined sizing across the period, or it might indicate that one session happened to fall below the cap while the account was producing a large total that made the denominator favorable. A second period that also produces a controlled best-day percentage, under different market conditions, provides stronger evidence that the distribution is stable. The two-payout threshold aligns with the account-stack scaling article's minimum readiness criteria — both require the evidence that two independent consistency window completions provide. See how to scale a funded futures account stack from one account to five for how the two-payout threshold is applied as the readiness bar before adding a second account.
A sizing-formula-based method's key risk is that the formula ceiling is incorrectly calibrated for the account's volatility exposure. This risk is detectable after 20 sessions across two condition types because the formula ceiling and the DLL trigger pattern produce a signal — consistent triggers in one condition type, or no triggers in either — that tells you whether recalibration is needed. A discretionary method's key risk is that the profit distribution is driven by a few outlier sessions rather than consistent execution across many session types. This risk is detectable only after two completed consistency windows because one period's distribution could be luck and two periods' distributions across different market conditions are the minimum evidence for a stable pattern.
Applying the formula-method standard to a discretionary method would underestimate the evidence required. Applying the discretionary-method standard to a formula method would overestimate it — a formula method's key risk (calibration) is visible in session-level data in a way that a discretionary method's key risk (distribution) is not. The self-imposed threshold for each method type is the minimum that makes the track record's outputs useful as decision inputs for the decisions in Part 4 of this article. Below the threshold for the method type in use, the decisions in Part 4 should be made conservatively — defaulting to the more cautious option rather than the more aggressive one, and waiting for additional sessions before acting on a track record that is not yet long enough to be statistically meaningful.
Part 3 of 4 — What the journal must contain for the track record to be legible
The per-session journal entries are the raw data. The three outputs described here are the summary layer that makes the per-session data actionable for multi-period decisions. A track record that lacks these outputs requires the trader to read every session entry to reconstruct what the summary should have contained — which means the track record exists in raw form but cannot be used as a decision input without substantial manual analysis each time. Building the summary layer in the journal from the first funded session forward is what makes the track record useful without additional work at the moment a decision is required.
Average session profit is the sum of all closed session P&L divided by the number of sessions. It is the primary input for pacing math: the profit remaining to reach the next payout threshold divided by the average session profit gives the minimum number of sessions needed to close the gap. This calculation is the same formula that the final-stretch article applies to the last stage of a payout period — the track record's average session profit is the input that makes the calculation accurate rather than estimated. An average session profit figure is incomplete without the session count. A $230 average across 9 sessions is not the same as a $230 average across 24 sessions — the second provides far stronger evidence of stability.
The average session profit is also the outlier reference point. A session that produces three times the average session profit is an outlier by this standard — it may be a legitimate setup result, but it requires a note in the journal and a check against the consistency window's denominator before the next pre-session routine. If the outlier session pushes the best-day P&L above the consistency cap threshold relative to the period total, the consistency hold check becomes critical before the next session. Without the average session profit as a reference point in the journal, outliers are invisible until the consistency cap is triggered. With it, a single session that exceeds two or three times the average is immediately flagged as a potential denominator problem before the next session begins. See what to record in your funded futures trading journal after each payout for how the average session profit figure resets and is re-established in each new payout period.
Streak frequency is how often multi-loss runs occur in the track record and what severity they reach. The losing-streak article's decision tree defines the severity thresholds: two consecutive losses trigger a journal check, three trigger a mandatory check with a size-down, four to five trigger a streak classification, seven or more trigger a full audit and a two-session rest. Streak frequency in the track record is the count of how many times each threshold has been reached across the full funded account history, and what the journal's classification recorded as the cause.
Streak frequency separates statistical variance from behavioral drift from structural sizing problems. One streak of four or more losses in 20 sessions is within the expected range for most methods — even a method with a 60% win rate will produce a run of four losses in approximately one in every 16–20 sessions by pure probability. Two streaks of four or more losses in 20 sessions is within the range but warrants a check. Three or more streaks of that severity in 20 sessions suggests the method has a structural problem — either the position size is too large for the method's stop structure in current conditions, or the method's win rate is lower than the pre-funded evidence suggested. The streak frequency record in the journal makes this pattern visible across the full funded account history. Without it, each streak is addressed in isolation and the pattern that would indicate a structural problem is never assembled into a complete picture. See how to handle a losing streak on a funded futures account for the full decision tree and the protocol for each severity threshold.
Consistency window outcome history is the record of what cap percentage the best-day P&L reached in each completed payout period, whether a hold was triggered, and if a hold was triggered, how many sessions it took to clear the denominator gap. This history is the evidence base for whether the method's profit distribution is stable across periods or whether it varies significantly from period to period based on one or two outlier sessions per period.
A funded account that has completed four payout periods with consistency percentages of 24%, 27%, 23%, and 26% has a stable distribution — the best-day result is consistently around 25% of the period total, which is below most firms' caps and sustainable across different market conditions. A funded account with percentages of 19%, 41%, 22%, and 38% across four periods has an unstable distribution — even if no hold was triggered because the firm's cap is at 40%, the variance signals that some periods produce an outlier session that dominates the result while others do not. The unstable distribution is more vulnerable to a consistency hold in any given period because the outcome depends on whether an outlier session happens to occur. Managing the consistency rule in the funded phase is not about hoping the outlier sessions are small — it is about structuring the sizing and session behavior so that no single session can dominate the period's denominator. The consistency window outcome history is what tells you whether that structure is working across periods. See how to calculate your funded futures payout before you request it for the Gate 5 formula and the denominator-gap clearance math that applies when the ratio exceeds the cap.
Part 4 of 4 — What to do with the track record
The track record's value is not in the reading — it is in the decisions it enables. A track record that accumulates in the journal but is never used as a decision input is a data archive, not a management tool. The three decisions below are the most consequential decisions in the funded account lifecycle: one increases risk exposure (sizing up), one expands the account structure (adding accounts), and one determines the path after a failure (reset, new evaluation, or different firm). Each of these decisions made without the track record is a guess; each made with it is an evidence-based evaluation of the method's performance against its own history.
The sizing-up article's four-step formula check — DLL ceiling, consistency margin, payout buffer, execution pattern stable — provides the framework for the sizing-up decision. The fourth check, "execution pattern stable," is where the track record becomes the operative input. Two specific track record outputs define what stable means in practice. First, the streak frequency output: the most recent 10-session window should contain no losing streak that reached four or more consecutive losses. A streak of that length in the most recent 10 sessions, regardless of the overall balance trajectory, indicates that the current sizing is producing a risk profile inconsistent with stable execution. Adding a contract in that environment amplifies the magnitude of each losing session without evidence that the frequency of those sessions is declining.
Second, the trailing average session profit: the average session profit for the most recent 10 sessions should not have declined more than 20% from the prior 10-session trailing average. A declining average session profit while the balance is growing — because one or two large winning sessions are masking a higher frequency of small losing or breakeven sessions — is a warning that the method's typical session output is weaker than the balance suggests. Sizing up when the trailing average is declining means adding a contract at a time when the per-session net P&L is already moving in the wrong direction. The four-step formula check from the sizing-up article provides the structural gates; the track record's streak frequency and trailing average provide the behavioral evidence that the execution pattern is genuinely stable before an additional contract is added. See how to size up on a funded futures account for the complete four-step check and the three periods where the answer is always no regardless of what the track record shows.
The account-stack scaling article's two-payout requirement uses the payout history as the threshold for adding a second funded account. But the two-payout threshold is not simply "have two approved payouts in the record." The minimum meaningful threshold is two approved payouts where the consistency window outcome history shows that the cap percentage was below the hold threshold in both periods, and the average session profit across both periods was above the minimum pacing threshold for reaching the next payout within a normal period length.
A track record where two payouts were approved because the denominator was very large — meaning many sessions, not disciplined profit distribution — is a weaker foundation for adding a second account than a track record where both payouts cleared because the consistency percentage was deliberately controlled session by session. The distinction: a large denominator can make even a disproportionate best-day session produce a ratio below the cap, which means the payout may have cleared despite inconsistent sizing rather than because of consistent sizing. The consistency window outcome history from the two prior periods tells you which scenario produced the payouts. Only when both periods show controlled consistency percentages across a reasonable session count — not just a large denominator that absorbed an outlier — does the two-payout threshold represent genuine evidence of sustainable execution. See how to scale a funded futures account stack for the full readiness criteria and the four conditions that stop the scaling process regardless of the payout count.
The reset vs new evaluation vs different firm decision is the most consequential use of the track record because it determines what comes next after a funded account failure. The decision framework from the reset article classifies failures as behavioral or structural, and the track record is the evidence base for that classification. A behavioral failure shows in the journal as a cluster of specific sessions where execution deviated from the method's normal pattern — position held past the exit signal, size added mid-session in violation of the pre-session ceiling, news event session entered without the pre-session calendar check. The deviation is identifiable because the journal entries for those sessions look different from the entries for normal sessions, and the failure is clustered around those specific sessions rather than distributed across all sessions.
A structural failure shows in the track record as a declining average session profit across all market condition types, an increasing DLL trigger count across all setups rather than in one specific setup, and consistency percentages that are either rising (the denominator is shrinking relative to the best-day sessions) or erratic across periods. The structural failure pattern means the method's parameters — not the execution — are misaligned with the current funded account constraints, and a reset at the same account tier and instrument produces the same structural failure again. The reset decision in that case is not reset vs continue but new evaluation vs different tier vs different instrument. Without the track record's average session profit history, streak frequency pattern, and consistency window outcomes, the failure classification cannot be made with any evidence — the decision defaults to intuition about whether the failure "felt behavioral" or "felt structural," which is not a reliable diagnostic. See funded futures reset vs new evaluation for the three-way decision framework and how the behavioral vs structural classification drives each option's probability of a different outcome the next time. See how to build a funded futures trading plan for how the track record's three outputs feed into the four-section operating plan that governs each session from pre-session through account-level maintenance.
A funded futures track record is the post-activation operating history of a funded account, not the history of evaluation attempts. It begins on activation day and accumulates across every session, payout period, and account event that follows. Five components make it complete: balance history from activation through each payout cycle, payout history with approved amounts and split rates, consistency record showing the cap percentage reached in each completed period, DLL trigger count and pattern showing the frequency and context of intraday DLL events, and behavioral evidence from the per-session journal entries. An evaluation record answers whether the trader followed the rules during a funded account simulation. A funded account track record answers whether the trading method is producing sustainable output under live constraints across multiple periods and market conditions. Most traders have one component or two — the payout count and the balance — but not the full five-component record that makes decisions about sizing up, adding accounts, and resetting evidence-based rather than intuition-based.
The minimum depends on the method type. For a sizing-formula-based method — DTF÷10 and DLL÷4 for pre-session ceilings — the minimum is 20 funded sessions that include at least two different market condition types: trending and mean-reverting. Both condition types are required because the formula ceiling may be correctly calibrated for one condition and incorrectly calibrated for the other. For a discretionary method — where sizing decisions are made session by session without a formula — the minimum is 20 sessions plus two completed consistency window periods that each reached approved payout status. Two completed windows are required because a single period's consistency outcome may reflect luck in the distribution rather than stable execution across different conditions. These are self-imposed standards, not firm requirements. A 15-session record can support some decisions — whether to continue versus reset, for example — but not others, like whether to add a second account or size up. The minimum is defined by the decision being made.
Three specific journal outputs make the track record legible as a decision input. Average session profit — the sum of all closed session P&L divided by the session count — provides the pacing input for estimating when the next payout threshold is reachable and the outlier reference point for identifying sessions where a single result is disproportionately large relative to the normal distribution. Streak frequency — how often multi-loss runs occur and what severity they reach — provides the behavioral diagnostic that separates statistical variance from a structural sizing problem. Consistency window outcome history — what cap percentage the denominator reached in each completed period and whether a hold was triggered — provides the evidence base for whether the profit distribution is stable or whether outlier sessions are driving each period's result. The per-session journal entries are the raw data; these three outputs are the summary layer that makes the raw data useful for decisions without requiring a full re-read of every session entry each time a decision point arrives.
The sizing-up decision requires two track record inputs in addition to the four-step formula check from the sizing-up article. First, check the streak frequency for the most recent 10 sessions: if any losing streak in that window reached four or more consecutive losses, the execution pattern is not stable enough for an upward sizing move, regardless of the balance level or payout count. A streak of that length in the most recent 10 sessions means the current size is already producing a risk profile that is inconsistent with stable execution — adding a contract amplifies the risk without evidence that the loss frequency is declining. Second, check the trailing average session profit: the average for the most recent 10 sessions should not have declined more than 20% from the prior 10-session average. A declining average session profit while the balance is rising means one or two large winning sessions are masking a higher frequency of losing and breakeven sessions — which is the wrong environment for adding a contract. Both checks must pass before the sizing-up decision is evidence-based. If either check fails, the correct decision is to wait for additional sessions that show the pattern stabilizing before revisiting the size increase.
The reset vs new evaluation decision depends on classifying the failure as behavioral or structural, and only the track record can provide the evidence for that classification. A behavioral failure shows in the journal as specific sessions where execution deviated from the method's normal pattern — oversizing, holding past the exit signal, entering during a news window. The deviation is clustered around those sessions and is not present across all session types and conditions. A structural failure shows in the track record as declining average session profit across all condition types, increasing DLL trigger frequency across all setups, and consistency percentages that are rising or erratic across periods. Behavioral failures support a reset or planned break — the method is sound and a cleaner attempt under better execution produces a different outcome. Structural failures support a different evaluation tier, a different instrument, or a method review — because the same structural problem will produce the same result at a new funded account starting balance if the underlying parameters are not recalibrated. Without the track record's three journal outputs, the classification cannot be made with any evidence and the decision defaults to intuition about whether the failure felt fixable or fundamental — which is not a reliable guide to which response is actually appropriate.
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