How Prop-Firm Drawdown Rules Shape Risk Behavior

Prop-firm drawdown rules change risk behavior along two independent dimensions: whether the loss floor is fixed or moves, and whether a breach is measured against realized balance or against live equity that includes open positions. Each combination creates a different decision pressure — a growing cushion, a provider recalculation boundary, or an open position’s unrealized risk. A personal guardrail only fits the account when it is built against the specific, verified mechanic that account actually uses.

This sits upstream of prop-firm evaluation pacing, which schedules risk changes across an evaluation’s phases by taking the applicable provider constraint as a given input — this article explains why different constraint mechanics create different decision environments in the first place. It is also distinct from a personal daily loss limit, which is a boundary the trader chooses and can redesign at will. A drawdown mechanic is a fixed feature of the specific program, verified from that provider’s own current terms rather than assumed from memory of a different account, and the trader’s task is to build the guardrail the mechanic actually calls for.

The drawdown mechanics that actually differ between programs

Two independent dimensions determine how a drawdown rule behaves, and a trader needs the answer to both for the specific program being traded — not a general impression of “trailing versus static.”

Dimension A — how the floor is set or updated. A static floor remains fixed at a provider-defined level rather than trailing upward with qualifying gains while that rule remains in effect. A trailing floor moves instead, but only some trailing floors update automatically from a provider-defined balance snapshot — a specific point, such as a daily 00:00 recalculation, at which the account’s balance is checked and used to reset the floor going forward. An open position running to a new high before that snapshot does not move the floor on its own.

Dimension B — what value is monitored for a breach. This is independent of Dimension A. A floor can be static and still be checked against live equity continuously — balance plus open profit or loss — meaning an unrealized loss alone, never closed, can trigger the limit before any position closes. A floor’s update basis and its breach basis do not have to match, and providers do not pair them the same way.

FTMO’s current Trading Objectives give three verified examples of these dimensions inside a single provider. Its 2-Step Maximum Loss is static: calculated once as the Initial Simulated Capital minus the applicable Maximum Loss Amount — 10% of Initial Simulated Capital — and it does not recalculate.¹ Its 1-Step Maximum Loss is an end-of-day trailing limit instead: it recalculates daily at 00:00 CE(S)T, using the highest account balance recorded at 00:00 CE(S)T on any preceding trading day — or the Initial Simulated Capital, if that figure is higher — minus the same Maximum Loss Amount; FTMO states this limit “can only increase, but never decrease.”¹ Both versions are monitored against equity — balance plus open positions’ profit or loss, swaps, and commissions — so in either version an open loss can trigger the limit before a position closes.¹ FTMO’s Maximum Daily Loss runs on the same 00:00 CE(S)T schedule but is a separate rule: it recalculates from the account balance recorded at that time, minus the applicable Maximum Daily Loss Amount (3% of Initial Simulated Capital for 1-Step, 5% for 2-Step). It is a separately calculated rule that applies concurrently with the Maximum Loss and the account’s other Trading Objectives — meeting one does not make the other irrelevant.¹

Topstep’s standard 50K, 100K, and 150K Trading Combine belongs to the same broad structural category as FTMO’s 1-Step Maximum Loss — both use a provider-defined end-of-day balance snapshot to move a trailing floor, rather than an intraday unrealized-equity peak — without using an identical formula; Topstep’s own dollar amounts, update timing, and lock behavior are specific to that program.² Topstep states its Maximum Loss Limit (MLL) “updates at the end of each trading day but is monitored in real time throughout the session,” and that it “rises as your end-of-day balance grows, but never moves down.”³ Once it reaches the account’s starting balance, Topstep states the MLL “locks permanently” — which stops the floor from trailing any higher, not from remaining active.³ Both realized and unrealized P&L count toward the limit, and touching it “at any point during the trading day” liquidates the account immediately, whether the floor is still trailing or has already locked.³ Topstep also offers other program variants with different mechanics — including a Topstep Labs Static Trading Combine whose Maximum Loss Limit does not trail at all⁴ — so the standard Combine’s mechanic should never be assumed for every Topstep account without verifying the specific program.

Verified rule	Floor type	What updates the floor	When it updates	What is monitored for breach
FTMO 2-Step Maximum Loss	Static	Nothing — fixed at Initial Simulated Capital minus Maximum Loss Amount	Never recalculates	Equity, continuously¹
FTMO 1-Step Maximum Loss	Trailing (can only increase)	Highest 00:00 CE(S)T balance on a preceding trading day, or Initial Simulated Capital if higher	Daily, at 00:00 CE(S)T	Equity, continuously¹
FTMO Maximum Daily Loss	Resets daily	Account balance recorded at 00:00 CE(S)T	Daily, at 00:00 CE(S)T	Equity, continuously within the day¹
Topstep standard Trading Combine MLL (50K/100K/150K)	Trailing, then locks	End-of-day balance; locks once it reaches the starting balance	End of each trading day	Balance and unrealized P&L, continuously³

Two things follow from these four verified rows, and neither is a claim about every program. First, a single provider can layer more than one drawdown-style rule at once with different mechanics, as FTMO does with its Maximum Loss and Maximum Daily Loss running concurrently. Second, Dimension A and Dimension B do not have to move together: both trailing examples verified here update only from an end-of-day balance snapshot, yet both are still monitored against live equity in real time — the floor’s update basis does not determine its breach basis. Some program descriptions outside these two providers describe a floor that itself rises from an intraday unrealized-equity peak rather than an end-of-day snapshot; that variant is not verified here, so confirm it directly with the specific provider rather than assume it from a general description.

How each mechanic can shape a trader’s decisions

Official provider documentation establishes the mechanics above. What follows is this article’s own reasoning about the decision pressure each mechanic can create — not a further provider claim, and not a claim that any mechanic determines what a given trader will do.

A static floor does not rise as qualifying profits accumulate, so the covered distance to it can start to look like discretionary room. All else equal, a static floor stays where it started while equity grows, and that widening gap is a genuine, verifiable fact about the account, not an illusion. The decision pressure it can create is treating that growing distance as license for a size increase disconnected from the trader’s own predefined risk rule. A useful review question: would this size increase still be justified by the trader’s own risk-per-trade rule if the provider’s floor were not visible at all?

An end-of-day or balance-snapshot trailing floor can create pressure around the provider’s own recalculation boundary. Because the floor only updates at a defined snapshot rather than from every intraday high, an open, unrealized gain sitting above the current floor has not yet raised it. That structure can create pressure to convert open profit into realized balance before the snapshot, and then to avoid giving that balance back before the snapshot is taken — for example, ending the session after preserving a higher balance into the provider-defined snapshot, or skipping an otherwise plan-justified trade to avoid giving that improved balance back before the snapshot. None of this is required by the rule itself; it is a plausible pressure the rule’s timing can introduce, and it may not occur for a given trader on a given day.

Continuous, equity-based breach monitoring is the mechanic most directly linked to a measurable error, and it applies under a static floor exactly as it does under a trailing one. A trader who mentally tracks distance to the floor using only realized P&L can be closer to the actual limit than believed, because an open, unrealized loss already counts toward it even though nothing has been booked. This is the clearest case in this article of a mechanic producing a specific, checkable mistake rather than only a diffuse pressure.

A locked floor stops trailing upward — it does not stop functioning. Once a trailing floor reaches its lock point, as Topstep’s does at the starting balance, future profits no longer push it higher, but the locked level remains an active threshold that a large enough loss can still reach. The decision pressure this can create is the trader reading the stabilized floor as reduced restriction and expanding size or exposure elsewhere — a decision that has nothing to do with the drawdown floor and everything to do with a separate risk choice the lock does not touch. Risk escalation in trading covers that classification problem directly; a floor lock is simply one more trigger that can produce it. The drawdown risk itself has not gone away — only the floor’s ability to rise has.

Observable signs the mechanic is shaping the decision

An exit or an added trade decided specifically around a provider’s snapshot boundary — ending the session right after preserving a higher balance into the snapshot, or avoiding a further trade specifically to protect that balance through it — when the position’s own management rule pointed to holding or gave no signal either way.
A size increase justified by “the floor is far behind me now,” with no reference to the trader’s own tested risk-per-trade or the account-level capacity rule from trading risk management.
Added exposure taken specifically because a floor lock stopped the trailing movement, on an account where the drawdown floor was never the only or largest risk being managed, and where the locked floor remains active regardless.
A liquidation traced to an open, unrealized loss the trader believed still had room, because the loss was tracked against a realized-P&L mental tally rather than the equity-based breach the program actually applies.
The same personal guardrail carried unchanged from one account to another without first checking whether the two accounts’ verified mechanics actually match.

That last pattern is distinct enough from an ordinary rule violation to need its own check.

The edge case: one guardrail, two different account mechanics

A trader running more than one funded or evaluation account at once — especially across different providers or program types — can carry one account’s mental model of its floor into a decision on a different account that updates or measures a breach differently. The failure this produces is not a size increase taken against a known rule; it is the wrong rule applied with genuine confidence. Concrete versions of this error include treating an end-of-day trailing floor as if it were static once its most recent snapshot has passed, tracking only realized balance on an account whose provider actually monitors live equity, assuming a locked floor is no longer an active threshold, or carrying one provider’s snapshot timing — such as FTMO’s 00:00 CE(S)T recalculation — onto an account at a different provider that runs its own schedule. None of these mechanics transfers from one provider or account to another by assumption.

On review, this can look identical to an ordinary undisciplined decision. The distinguishing question is whether the trader could correctly state, before the decision, which specific mechanic that account uses. If the answer is no, the finding is cross-account rule confusion, not a motivated deviation, and the fix is different: not a stricter number, but a guardrail keyed to the verified mechanic of each account, checked before the session rather than recalled from a different one. A liquidation that traces to this confusion is more accurately logged as unclassified pending mechanic verification than filed immediately as a deviation, since the record does not yet establish which rule the trader believed was governing the decision.

A check before treating floor proximity as a risk signal

Which specific mechanic does this account use — is the floor fixed, or does it move, and if it moves, does it update from a provider-defined balance snapshot or some other method? Verify this from the program’s own current terms for this account, not from memory of a different one.
Is the breach itself checked against balance only, or against live equity? This determines whether an open, unrealized loss alone can end the account before anything is closed.
If the floor is trailing, has it reached a lock point — where the program’s own terms define one — and does the locked floor remain an active threshold that a large enough loss can still reach?
Would this decision be justified on an account using a different mechanic, or is the current floor’s distance the only reason it looks acceptable right now?

Where Costante fits

The provider defines the external constraint — its own floor mechanic, breach measurement, and lock behavior, verified directly from that provider’s current terms. Costante does not connect to a prop firm or broker, does not receive live account equity, balance, or floor position from any provider, does not import or calculate a program’s drawdown rule, and does not determine whether a floor has locked or been breached.

What Costante can support is the funded-trader guardrail built around that verified constraint: defining a Re-entry limit, After-loss risk rule, Session cutoff, Max loss per trade, or Daily loss guard that fits the specific account, keeping those self-defined rules available for pre-trade and in-session checks, logging decisions with low friction, and reviewing afterward whether the guardrail held. The trader remains responsible for verifying each account’s mechanic with its provider and for deciding what the guardrail should say.

Frequently asked questions

Is a trailing drawdown always riskier than a static one?

Not in a way that holds for every trader. All else equal, a static floor does not tighten as the account establishes new highs, so accumulated profit can widen the trader’s distance from that fixed floor over time. An end-of-day or balance-snapshot trailing floor can instead ratchet upward after a qualifying balance high, which limits how much of that accumulated headroom stays available. That mechanical difference does not by itself establish how any individual trader will behave under either one, and whether a breach is checked against balance only or against live equity — a separate variable — can matter under a static or a trailing floor alike. In a simple model with a constant edge and constant risk per trade, the chance of reaching a trailing floor keeps rising with the number of trades while the chance of reaching a static floor levels off, as risk of ruin in trading shows.

Does Costante track my account’s live drawdown floor automatically?

No. Costante does not connect to a prop firm or broker and does not receive live equity, balance, or floor data from any provider. The trader verifies the current mechanic and floor position directly with the program; Costante supports logging the trader’s own guardrail decisions and review notes, not the provider’s account data.

Can I use the same guardrail across a static-drawdown account and a trailing-drawdown account?

Not without checking it first. A guardrail built assuming one account’s mechanic can misfire on an account that updates or measures a breach differently — see the cross-account edge case above. Verify each account’s mechanic separately before assuming a guardrail transfers.

Does a locked floor mean the account is now safe from a drawdown breach?

No. A lock means the trailing floor has stopped moving upward — not that it has stopped functioning. The locked floor remains an active threshold, and reaching it can still liquidate or violate the account. A lock is separate from a program’s daily loss rule, from the trader’s own position-risk rules, and from any other session guardrail the trader has defined; none of those are affected by whether the drawdown floor has locked.

Sources

Costante provides educational workflow tools, not financial advice. Trading involves risk.

For the broader process framework around exposure and rule design, see trading discipline.

FTMO. Trading Objectives. Accessed September 2026. Provider terms are subject to change; verify current terms directly with FTMO. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷
Topstep Help Center. Trading Combine Parameters. Accessed September 2026. Lists the standard 50K, 100K, and 150K account sizes; account/program terms are subject to change. ↩
Topstep Help Center. What is the Maximum Loss Limit? Accessed September 2026. Provider terms are subject to change; verify current terms directly with Topstep. ↩ ↩² ↩³ ↩⁴
Topstep Help Center. Topstep Labs. Accessed September 2026. Describes the Topstep Labs Static Trading Combine’s non-trailing Maximum Loss Limit as one example of a program variant with a different mechanic than the standard Combine. ↩