After you're funded · Stage 3 · Free
Sizing down is the counterpart to sizing up, but the triggers are different in structure. Sizing up has one gateway — the trailing drawdown floor locking — followed by four recalibration checks. Sizing down has four independent conditions: the balance-floor gap narrowing to where a DLL session at current size would leave dangerous proximity to the floor; the drawdown recovery protocol switching the daily profit stop to DLL ÷ 6 and mandating a corresponding contract reduction; the consistency hold period where full-size sessions could produce a new best day and extend the hold; and the post-streak three-loss checkpoint, which is the explicit behavioral diagnostic that requires size reduction for drift and variance causes. This article covers all four with the specific thresholds and formulas that determine when each applies.
Part 1 of 4 — Formula-mandated size-down: the DTF/10 ceiling and the proactive gap threshold
The DTF/10 ceiling is a per-trade maximum, not a per-session maximum. As the balance declines and the distance to the floor shrinks, each recalculation produces a smaller ceiling — sometimes by a fraction of a contract per session. The proactive step-down addresses the case where the current ceiling is still technically valid but where one DLL session at the current contract count would leave the account in a much tighter position for the following session.
The DTF/10 ceiling is calculated as (current balance − trailing drawdown floor) ÷ 10. As the account balance falls — either from trading losses or from unrealized losses that settle EOD — the numerator shrinks and the formula outputs a smaller ceiling. On a $50K funded account with a $48K floor, the DTF is $2,000 and the DTF/10 ceiling is $200. If the balance falls to $49K (a $1K decline), the new DTF is $1,000 and the new ceiling is $100. The formula does not warn in advance that the balance is approaching a level where the ceiling will step down sharply; it simply recalculates. Traders who do not run the formula before each session may discover the step-down only after they are already in a position at the prior contract count.
The second input — DLL ÷ 4 — sets the per-session maximum and may become the binding constraint before DTF/10 steps down significantly. When DLL ÷ 4 is less than DTF/10, the DLL constraint is already in place and DTF/10 is not the active ceiling. When DTF/10 falls below DLL ÷ 4 as the balance declines, DTF/10 becomes binding and the crossover point defines when the account has moved from normal operations into a zone where floor proximity is the primary constraint. See the full per-session ceiling formula in funded futures account sizing by tier and the five-step pre-session routine in the funded futures position sizing checklist.
The proactive threshold is a pre-session check: calculate the dollar loss from a DLL session at the current contract count (contracts × stop-distance ticks × tick value) and compare it to the current balance-floor gap. If one DLL session at current size would reduce the gap to less than two DLL sessions' worth of room at the same contract count, size down by one contract before the next session. The logic: if you are one DLL session away from a gap that would only support one more DLL session before hitting the floor, you are already at the edge of a position where a two-session drawdown ends the account. Stepping down one contract before the first DLL session maintains more sessions of room.
Worked example: $50K account, $48K floor, gap = $2,000. Trading at 2 MNQ contracts with a 10-tick stop: DLL session loss = 2 × 10 × $2 = $400. After one DLL session: gap = $1,600. At 2 contracts, two more DLL sessions = $800 total = 0.5 sessions of additional room below the $1,600 gap — meaning one more DLL session leaves $1,200 and the next DLL session at 2 contracts would bring the balance to $800 above the floor. That is still above the floor, but the next DLL session after that ends the account. The proactive threshold flags this before the first DLL session, not after. Step down to 1 MNQ contract: DLL session loss = $200. The gap after one DLL session at 1 contract = $1,800 — six more DLL sessions of room. The reduced contract count extends the viable range substantially. Track the balance-floor gap daily as a leading indicator of when this threshold applies; the calculation is one of the six between-session tracking fields described in how to track funded futures account metrics between sessions.
A formula step-down is reactive: the DTF/10 ceiling produces a number that requires fewer contracts than the current session plan. The trader runs the formula, sees the lower ceiling, and trades at the reduced level. A proactive step-down is anticipatory: the formula still permits the current contract count, but the gap analysis shows that the account is one adverse session away from a much tighter constraint. The proactive step-down does not wait for the formula to force it.
The distinction matters most in accounts where the balance has been declining gradually over several sessions without triggering a drawdown recovery entry. In these cases, the DTF/10 formula may still permit 3 contracts when the gap analysis shows the account is one 3-contract DLL session away from a 2-contract limit and two sessions away from a 1-contract limit. Each formula step-down reduces the ceiling for the current session, but the account is already committed to whatever the prior session's size was. The proactive check runs the step-down math one session early, preserving more sessions of margin before the formula forces it. When the floor has not yet locked and the balance is working back toward the floor after a productive period that inflated the prior high, the proactive threshold is especially important because the DTF can compress quickly as the floor advances from that prior high. See how the trailing drawdown floor advances and when it locks in funded futures trailing drawdown floor mechanics — advancement, lock, and floor-room tracking.
Part 2 of 4 — Protocol-mandated size-down: the drawdown recovery entry
The drawdown recovery entry is the structural size-down. It is not triggered by the trader's discretion but by the balance falling to the level that activates the recovery protocol. The size-down that follows is a direct consequence of the smaller profit stop ceiling that the recovery protocol imposes.
In drawdown recovery, the daily profit stop is DLL ÷ 6 — a lower ceiling than the standard pre-session × 0.28 formula. This ceiling limits the session's maximum gain, but it also constrains the per-trade sizing. The contract count must be low enough that: (1) a DLL session at recovery size produces a loss that is survivable given the current balance-floor gap, and (2) the session's potential gain, if the position performs as planned, stays within the DLL ÷ 6 ceiling before the position is closed. These two constraints do not always resolve to the same contract count — the first (loss survivability) typically drives a lower limit than the second (gain ceiling) in most account states. Use the more restrictive of the two as the recovery contract count.
The recovery contract count calculation: determine the maximum per-session loss that leaves the account able to continue — typically the current balance-floor gap minus the DLL, which ensures the account can absorb one more DLL session after the current one before requiring another size reduction. Divide this maximum loss by the stop-distance value per contract (stop ticks × tick value). That quotient, floored to the nearest whole contract, is the recovery contract count. On a $50K account with a $47K floor (gap = $3,000), DLL = $1,000: maximum survivable loss = $3,000 − $1,000 = $2,000. At 2 MNQ contracts with a 10-tick stop, loss = $400 per DLL session. At 2 contracts, a DLL session brings the gap to $2,600 — leaving 2.6 more DLL sessions of room. This is above the minimum threshold; the recovery entry size is 2 contracts in this case. If the gap were $1,500 and DLL = $1,000: maximum survivable = $500. At 2 contracts ($400/DLL session), the account can absorb one DLL session ($500 − $400 = $100 remaining, not enough for another) — so 1 contract ($200/DLL session) is the correct recovery entry size. See the full drawdown recovery protocol in how to recover from a drawdown on a funded futures account.
The drawdown recovery protocol uses a three-question behavioral audit to classify the cause of the drawdown: method drift (deviating from the setup, wider stops, early entries), sizing creep (incrementally larger position sizes without a floor-lock gateway), and volatility exposure (the market moved to a regime where the normal stop distance produces larger losses). Each cause has a different fix, and the size-down level differs slightly by cause.
For method drift: the size-down is to the recovery entry size, and the return criteria require five consecutive process-correct sessions — sessions where the setup was followed exactly, stop placement was standard, and the outcome (win or loss) was secondary to the process. For sizing creep: the size-down returns to the last valid formula-derived ceiling before the creep, not to the recovery entry size — the distinction is that the account declined because the sizing was already higher than the formula permitted, not because the balance itself declined below a structural threshold. For volatility exposure: the size-down may be more aggressive than the recovery entry formula suggests, because the stop-distance value used in the calculation should reflect the current market's actual stop requirements rather than the standard stop distance. A market running wider ranges requires a wider stop, which changes the per-contract DLL session loss in the recovery formula. See the behavioral audit structure in how to recover from a drawdown on a funded futures account.
The recovery size-down is temporary. The return criteria are process-based, not outcome-based: five consecutive process-correct sessions, with zero resets for any session that shows a process deviation regardless of whether the session was profitable. A profitable session with a process deviation restarts the count; a losing session with clean process keeps the count moving forward. This criterion is structurally important: outcome-based return criteria (for example, "three consecutive profitable sessions") incentivize sizing up into a recovering position rather than maintaining discipline at recovery size, because a larger position has a higher probability of producing a larger profit. Process-based criteria do not change the incentive when contract count is variable.
After the five-session process criterion is met, the step-up sequence follows the normal sizing-up protocol: run the DTF/10 and DLL ÷ 4 formulas from the current balance and floor position, confirm the four recalibration checks (DLL ceiling, consistency margin, payout buffer, execution pattern), and add one contract at a time with a session between each step. The recovery period does not reset the sizing-up gateway — the floor-lock status is unchanged. An account that was already past the floor-lock threshold before the drawdown can resume sizing up after completing the five-session recovery criterion; an account that had not yet locked the floor follows the normal locked-floor gateway for any contract additions beyond the recovery entry size. See the full recalibration check in how to size up on a funded futures account.
Part 3 of 4 — Consistency hold clearance: the variance reduction case for sizing down
The consistency hold is the one size-down condition that is not forced by a balance decline or a streak count. It is a variance-management decision: the hold is already in place, the window is still accumulating, and the question is whether reducing contracts materially reduces the risk that the next productive session extends the hold rather than helping clear it.
A consistency hold occurs when the best-day session's gain exceeds a threshold percentage of the cumulative period profit — commonly 25%, 30%, or 40% depending on the firm. During a hold, the window is still open and the consistency denominator (cumulative period profit) keeps accumulating. A session that adds profit to the denominator moves the best-day percentage down if the gain is smaller than the current best day divided by the current threshold percentage. But a session that produces a new best day — a gain larger than the current best day — raises both the numerator and the denominator, potentially keeping or worsening the ratio.
The risk of producing a new best day is highest when: the current best-day ratio is close to the threshold (for example, 28% against a 25% cap — any session gain larger than the current best day would set a new best and keep the ratio above 25%), and the denominator is small (a denominator of $4,000 with a best day of $1,120 at 28% — a new $1,200 session with the denominator at $5,200 produces a ratio of $1,200 / $5,200 = 23.1%, which clears; but a new $1,400 session produces $1,400 / $5,400 = 25.9%, which extends the hold). Full-size sessions have a higher variance of outcomes, including more potential for producing a new best day on a productive setup. Sizing down before the next session reduces the maximum session gain and limits the probability of the new-best-day scenario.
The size-down is most important when the current best-day percentage is within 5 percentage points of the threshold and the consistency window denominator is less than three times the current best day. In this zone, a session at full size that performs close to the best day's gain would either set a new best day (if the gain exceeds the prior best) or barely miss it. The denominator is too small for any realistic session gain to clear the ratio quickly, so the account needs to accumulate several more sessions of smaller gains to dilute the best-day percentage down through the threshold. During this accumulation phase, any single session that produces a large gain is a setback, not progress.
The size-down level during a consistency hold is not a formula-derived minimum — it is the contract count that reduces the expected maximum session gain to a level where, even on a strong setup, the probability of a new best day is low. A practical approach: target a maximum session gain of no more than 75% of the current best day. Calculate the contract count where the session's target gain (using the standard profit stop formula) is at or below that threshold. This is a softer constraint than the DTF/10 or recovery formula — the account is not in danger of closing, it is just in danger of a prolonged hold. See the full consistency rule mechanics and the denominator-gap clearance calculation in funded futures consistency rule: how it works after you pass.
The consistency hold size-down is temporary and ends when the hold clears. The clearance signal is the denominator growing large enough relative to the best day that the ratio falls below the threshold — the formula: best_day ÷ cumulative_period_profit < threshold. Once the ratio is below the threshold on the dashboard, the hold is cleared and the standard contract count (from DTF/10 and DLL ÷ 4) applies again. The size-down does not need to be maintained for a fixed number of sessions; it is maintained until the clearance math is satisfied regardless of how many sessions that takes.
The one scenario where the size-down should not be ended immediately after clearance: if the current period's best day is very large relative to the denominator and the clearance was achieved by accumulating many small-session gains at reduced size, the consistency risk reappears at full size — a session at full size that produces a large gain could immediately restore the hold. In this case, step back up to full size over two or three sessions rather than restoring immediately, monitoring the ratio after each session. If the ratio stays below the threshold for two full sessions at standard size, the clearance is stable and the size-down discipline can be released. Track the denominator and best-day percentage between sessions using the metrics tracking framework in how to track funded futures account metrics between sessions.
Part 4 of 4 — Post-streak adverse run: the three-loss diagnostic checkpoint
The three-loss checkpoint is the most operationally consequential point in the losing-streak protocol because it is the first point where the diagnostic can still be completed quickly. At two losses, the required action is a journal review — no size change. At three, the diagnostic adds a cause classification with a prescribed response that includes a size reduction for two of the three cause types.
The losing-streak protocol uses four consecutive-loss thresholds: 2 losses (journal check), 3 losses (mandatory diagnostic + size-down for drift and variance causes), 4–5 losses (classify the cause before any further sessions), 7+ losses (full audit + 2-session rest, then restart at recovery size). The size-down at the three-loss threshold is the protocol's first active response — the two-loss journal check is diagnostic, but the three-loss response is structural: it changes the contract count for the next session regardless of whether the diagnosis has been completed yet.
The size-down at three losses is not conditional on the cause classification being completed before the next session. If the classification is in progress and the next session is due before it is finished, trade at the recovery entry size until the classification is done. The reason is that the three-loss threshold flags an adverse run that may reflect a real behavioral or environmental change — trading at the same contract count before the classification is complete amplifies the exposure of a potential structural problem. Trading at a reduced size while finishing the diagnostic is a low-cost precaution with high upside: if the cause turns out to be statistical variance (the three-loss run was within the expected distribution of the method's losing rate), the reduced size cost was a few sessions at lower profit ceiling; if the cause turns out to be environmental shift, the reduced size prevented further outsized losses during the worst period.
The post-streak diagnostic classifies the cause into three categories: behavioral drift (setup deviations, wider stops, early entries — wrong result from a valid process), statistical variance (three valid-process sessions that produced losses within the expected distribution — wrong result from a valid process in the normal tail), and environmental shift (the market regime changed in a way that makes the method's edge structurally negative in the current environment — wrong process for the current environment).
Behavioral drift and statistical variance both result in a size-down and continuation — one step below current, to drawdown recovery entry size. The method has real edge; the adverse run is either a process execution problem (drift) or a normal expected cluster of losses (variance). Drift requires a behavioral correction (tighten setup criteria, enforce stop placement); variance requires no change other than the temporary size reduction while the balance recovers. Environmental shift results in a full stop, not a size-down: if the method's edge is not present in the current market environment, trading at a smaller size does not fix the structural problem — it just produces smaller losses from the same failing process. Full stop means no new positions until the environment diagnostic is complete and either (a) conditions match the method's validity criteria again, or (b) the method is adjusted to fit the new environment. See the full three-cause classification and the four-threshold decision tree in how to handle a losing streak on a funded futures account.
The size-down level at the three-loss checkpoint is recovery entry size — the same contract count defined by the drawdown recovery formula: the contract count where a DLL session loss is smaller than the current balance-floor gap minus one DLL, leaving enough room after a DLL session to continue rather than requiring an immediate further reduction. This level is chosen for two reasons: it connects the streak protocol to the recovery protocol when both apply simultaneously, and it is derivable from the current account state without requiring a new set of thresholds or a separate formula.
When the three-loss streak has also caused a balance decline large enough to trigger the formal drawdown recovery threshold, both protocols apply: the streak diagnostic to identify the cause and the recovery protocol for the structural adjustments including the profit stop ceiling. When the three-loss streak has not caused a balance decline below the recovery threshold — the losses were small and the gap is still well above the recovery entry level — the size-down is to recovery entry size as a temporary precaution, but the DLL ÷ 6 profit stop ceiling of the formal recovery protocol does not apply. Only the formal recovery protocol entry (balance-based, not streak-count-based) triggers the DLL ÷ 6 ceiling. The streak-only size-down maintains the standard daily profit stop formula (pre-session × 0.28) at the reduced contract count. Track whether both conditions apply after the three-loss checkpoint by checking the balance against the recovery entry threshold before the next session; the balance metric is one of the six between-session fields in how to track funded futures account metrics between sessions.
Frequently asked
Size down proactively when one DLL session at the current contract count would reduce the balance-floor gap to less than two DLL sessions' worth of room at that same size. Calculate: (current balance − floor) minus (contracts × stop ticks × tick value). If that result is less than twice the DLL session loss at the current contract count, step down by one contract before the next session. The DTF/10 formula will eventually force the step-down on its own — the proactive check triggers it one session earlier to preserve more margin before the formula catches up.
The drawdown recovery protocol mandates a size reduction if the current contract count cannot absorb a DLL session without leaving the account unable to continue. Whether a formal size reduction is required depends on the current contract count relative to the recovery formula: if the account was already at one contract and the formula confirms one contract is survivable at the new gap, no further reduction is required. If the account was at two or three contracts and the formula shows the gap cannot support a DLL session at that count and still have room afterward, a reduction is required. The DLL ÷ 6 profit stop ceiling applies regardless of whether the contract count changes.
No — stopping trading does not clear the hold. The hold clears when the denominator grows large enough relative to the best day that the ratio falls below the threshold. Stopping trading freezes the denominator and the ratio stays above the threshold indefinitely. The correct response is to continue trading at a reduced size that limits the variance of future session gains, accumulating smaller-gain sessions that dilute the best-day percentage gradually. The hold clears when the ratio drops below the firm's threshold on the dashboard; at that point, the standard contract count applies again.
The post-streak size-down at the three-loss checkpoint is triggered by a loss count — three consecutive losses — regardless of the account's balance position. The drawdown recovery size-down is triggered by the balance falling to the recovery threshold — a specific distance below the prior balance high. Both converge on the recovery entry contract count, but only the formal drawdown recovery entry switches the daily profit stop to DLL ÷ 6. A post-streak size-down that does not coincide with a balance-based recovery entry maintains the standard pre-session × 0.28 profit stop at the reduced contract count. When both triggers apply simultaneously — three losses plus a balance decline past the recovery threshold — both protocols run together and the DLL ÷ 6 ceiling applies.
Yes — in a severe adverse run, all four can overlap. A funded account experiencing a losing streak that causes a balance decline could simultaneously trigger the proactive gap threshold (gap narrowing from the losses), the drawdown recovery entry (balance crossing the formal recovery threshold), a consistency hold (if a prior payout period's best day is now a large percentage of a compressed denominator), and the three-loss post-streak diagnostic. When multiple conditions apply, the binding constraint is the most restrictive one — the lowest contract count produced by any of the four formulas. The DLL ÷ 6 profit stop ceiling from the formal recovery protocol applies whenever the recovery threshold is crossed, regardless of whether the size-down was triggered first by the gap threshold or the streak count. The recovery protocol is the structural ceiling; the streak and consistency conditions inform the behavioral response alongside it.
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 funded accounts, the founding tier is the time to join.
See the Founding 100 offer