The consistency cap: the prop-firm rule that silently voids more payouts than drawdown ever will

Operators who fail prop firm challenges remember the drawdown rule because it ends the account on the day it fires. Operators who pass the challenge, trade a funded account for two months, then submit a payout request and watch it bounce, they remember the consistency cap. The cap is not a drawdown rule; it is a profit-shape rule. It does not stop your trading; it stops your money. And because it evaluates at payout time, not during the period, the data point that voids your withdrawal can be a winning day from weeks earlier that you forgot about.

What the consistency cap actually measures

The mechanic is the same at every firm that enforces it: at payout submission, the firm computes the share of total realised profit produced by the single best closed day across the period the payout covers. If that share exceeds the published cap, the payout is denied, sometimes with a renegotiated payout amount that synthetically caps the best day at the threshold, sometimes flatly. The firm is not asking whether your strategy is profitable. It is asking whether your profit is repeatable. A 30%-share best day looks to the firm like one good guess in a series of breakevens; a 10%-share best day looks like a process that produces consistent income.

The intent is anti-gambling, not anti-trader. A reckless operator who happens to call FOMC right wins a single huge day and would otherwise look identical, on paper, to a steady process trader with the same total P&L. The cap differentiates them by structure rather than outcome.

Which supported firms enforce it, and at what threshold

Three of the six firms in the current Glitch Executor catalogue enforce a hard consistency cap; the other three either do not have one or apply it only as a soft signal during payout review. Numbers below are from the most recent quarterly firm-rule audit:

Why operators trip the rule without knowing it

The cap punishes a curve shape that looks great on every other metric. Consider two strategies that both produce $5,000 of profit on a $100,000 funded account over four weeks. Strategy A wins $300 a day on twenty days, banks $5,000 with a 6% best-day share, and clears the FundingPips Zero cap comfortably. Strategy B wins $200 a day on fifteen days for $3,000 plus a single $2,000 day on day seven, same total, 40% best-day share, payout denied. Strategy B looks identical on the equity curve to most observers; it has a better Sharpe ratio than Strategy A; and it fails the cap at the first withdrawal.

The operator typically does not remember the $2,000 day was the problem. They remember the strategy as "the one that finally hit", submit the payout, and learn the rule by losing the request. By the time the operator understands what triggered the denial, the data is fixed, they cannot retroactively cap the best day. The remediation path at every firm with this rule is to keep trading until the cumulative profit is large enough that the offending day falls back under the threshold, which can mean weeks of additional risk.

The three position-sizing changes that keep a strategy payout-eligible

1. Size every trade against a 20% cap, not a 15% one

The cap is 15% at FundingPips Zero; the operator should size against an internal 20% safety margin. The reason is that a single winning trade rarely defines the best day, a day with two or three winners stacking is what produces the outsized result. Sizing against 20% gives room for that stacking to land without breaching the published 15%. The position-sizing calculator on Glitch Executor exposes a "consistency-aware" mode that does this math: it caps the per-trade size such that even a perfect-stack day cannot exceed the firm cap, given the strategy's win-rate and risk-per-trade.

2. Stop trading once you exceed the target by 50%

The mathematical insight: the share of profit any single day produces is a function of cumulative profit, which only grows. The denominator never shrinks; the numerator can only grow if you keep trading. The optimal play once you have meaningful profit is to stop, submit the payout, and start the next period fresh. Continuing to trade only adds risk: a losing day cannot pull the best-day share back down because the best day already happened. Pragmatically: at FundingPips Zero, if you have hit the target (or 50% above it) and your best day is under the cap, request the payout that day.

3. Treat news days, gap days, and trend-day catches as one-shots

A single huge day is statistically rare for most strategies and represents the catch end of the distribution rather than the typical case. If a strategy produces a 25%-share day in week one, the rational move is to dial down position size for the rest of the period, not to "let it ride" trying to dilute the best day. Dilution requires every subsequent day to be near-average; one more outsized day extends the share rather than reducing it. The rule rewards a deliberate decision to step back after a big day.

How the in-app backtester models the cap

The firm-rule-aware backtester on Glitch Executor computes the best-day share across the entire backtest period for any firm whose catalogue entry carries a non-zero maxBestDayShareOfProfit. The verdict card shows the running ratio, the worst (highest-share) day, and a flag if the ratio would have voided a payout. Strategies with episodic outsized days fail the cap during the backtest, the same way they would fail in live trading. The Strategy IR also exposes an explicit "consistency budget" property: the largest single-day profit the strategy may book before the next day is required to flatten. The compiler emits this as a hard stop in the deployed cBot or EA so live trading respects the same budget the backtester used.

What this means in practice

Operators evaluating funded accounts should not rank firms by total profit potential. They should rank by realised payout potential, which is total profit times (1 minus expected consistency penalty). On a strategy with a typical 18%-share best day, FundingPips Zero will pay 0%, FTMO will pay 100%, The5ers will pay roughly 83% of the requested amount, and GetLeveraged Turbo will pay 0% or require remediation. The cap is the most important rule to pre-flight after drawdown, and it is the one the in-app backtester is best positioned to model, because the data needed is the same daily-profit series that drives the drawdown calculation.