Prop-Firm Evaluation Pacing and Funded-Account Risk

Prop-firm evaluation pacing is a plan, written before the evaluation starts, for how a trader’s risk-per-trade and decision permissions are allowed to change across the evaluation’s phases — the opening stretch, after one or more losses, near a profit target or loss threshold, and at the transition into a funded account. Pacing is not a reaction to any single trigger. It is the schedule that decides, in advance, which risk state applies at each phase, so a trigger event can be checked against a pre-written expectation instead of decided for the first time under pressure.

That scope is narrower than it sounds. The prop-firm discipline guide covers structuring personal execution rules across funded and evaluation trading broadly. Prop-firm target chasing and overtrading near an evaluation deadline each diagnose one specific trigger — proximity to a profit target, and a salient deadline — after it has already changed behavior. How to adjust risk during a drawdown supplies the risk-ladder mechanics for reducing and restoring size once a loss sequence is active. This article sits above those: it is the phase-by-phase plan that decides which of those tools applies when, and it owns one job none of them do — the risk-behavior transition from evaluation to funded trading.

What pacing means when provider rules vary

A pacing plan is trader-controlled. It exists inside whatever external constraints a specific program imposes, but it is not derived from those constraints, because they are not uniform. Maximum daily loss, maximum overall loss, minimum trading days, and profit-target structure differ by provider, program type, and account size, and provider terms change. FTMO’s current Trading Objectives, for example, define maximum daily loss and maximum loss limits that must be met concurrently with other objectives — a specific structure that does not describe every program.

That variation is why a pacing plan cannot be a fixed universal schedule (“risk 1% for the first five days, then 0.5%”). It has to be a rule for producing a schedule from a program’s actual terms: the account size, the loss limits, any minimum-day requirement, and the trader’s own tested risk-per-trade. Two traders on different programs can follow the same pacing framework and end up with different numbers, because the framework asks the same four questions of different inputs.

Set the trader-controlled risk envelope

Before pacing can be scheduled, the envelope it schedules has to exist. Trading risk management is the parent process for defining account-level, session-level, and trade-level exposure; pacing does not replace that process or redefine planned risk. It adds one input that a generic risk plan does not need: an evaluation has a start, a scored middle, and an end, and the account-level capacity question — “what can this account afford to lose and still have a realistic number of attempts left” — has a different answer on day one than it does with one loss limit remaining.

Two numbers from the existing risk envelope carry into the pacing plan without being redefined here:

Normal risk-per-trade, set by the trader’s own tested position-sizing method, independent of the evaluation.
The applicable provider-defined loss or drawdown constraint, taken directly from the program’s current terms — static, trailing, daily, or end-of-day, depending on the provider — verified against current provider documentation rather than assumed from memory or a forum summary. How prop-firm drawdown rules change risk behavior covers why that specific mechanic — how the floor updates, and separately, what value a breach is checked against — not just its size, changes what a rule-aligned pacing response looks like.

Pacing uses both numbers to decide how much of the normal risk-per-trade is available at each phase — it does not recalculate either one.

How to build a prop-firm evaluation pacing plan

A pacing plan is a short table, written and reviewed before the first trade, mapping evaluation phase to a risk multiplier and an explicit rationale. The multiplier is a fraction of the normal risk-per-trade defined above, not a new number invented for the evaluation.

Phase	Entry condition	Risk-per-trade	Rationale
Opening	Evaluation has just started; no phase-specific reduction has been triggered	Normal risk-per-trade	Use only the pre-validated normal risk that already fits the program’s applicable constraints; nothing yet requires reducing it
Mid-evaluation	A meaningful fraction of the applicable loss/drawdown constraint has been used, or another applicable condition — a minimum-day requirement, an expiration, or a rebill date — is approaching	Reduced risk-per-trade	Less remaining rule-constrained risk capacity supports fewer comparable attempts; see the loss-sequence phase below
Near threshold	Close to the profit target, the loss limit, or a time-based deadline	Pre-committed response, not an ad hoc decision	This is the trigger zone the diagnostic articles below cover; the pacing plan’s job is to say which response was already chosen
Funded transition	The evaluation is passed and a funded-stage account begins	Explicit reset decision, stated in advance	Covered on its own below — this is not simply “back to normal”

The table’s only real content is the rationale column. A multiplier without a stated reason is indistinguishable from an arbitrary preference, and a trader under pressure will find a reason to override an unexplained number faster than a reasoned one.

What changes after one or more losses

Once a loss sequence is active, the mechanics of resizing belong to the drawdown risk ladder: choose one reproducible drawdown measure, define triggers as state transitions, set the reduction independently of the next setup, and restore through staged gates rather than a single good result. Pacing does not duplicate that mechanism. What pacing adds is the pre-decision of whether the ladder is even allowed to move back up before the evaluation ends — because an evaluation, unlike ordinary trading, sits inside whatever minimum-day, expiration, rebill, or loss/drawdown constraints the program actually imposes, which can range from none to several at once, rather than an open-ended account with no applicable limit.

Concretely, a pacing plan should state, before the evaluation starts, whether restoration to normal risk is permitted at all once the mid-evaluation phase begins, or whether the account stays in a reduced state through to the threshold phase regardless of a recovered result. Both choices are defensible; the failure mode is not choosing either one in advance and instead deciding mid-evaluation, with the applicable loss/drawdown constraint and any applicable time condition both visible, which naturally biases the decision toward whichever answer fits the current account balance.

Threshold and deadline pressure

Two triggers can make the number in the “near threshold” row of the pacing table hard to hold: proximity to the account’s own profit target, and a salient deadline. Each has its own diagnostic framework, and pacing’s job is not to repeat that diagnosis:

If the change in behavior is driven by how close the account is to the profit target, prop-firm target chasing covers the two opposite failure patterns — forcing trades to finish faster, and freezing to protect what has already been built — and how to build a reviewable pacing rule for that specific trigger.
If the change is driven by a rebill date, an evaluation expiration, or another salient deadline, overtrading near a prop-firm evaluation deadline covers verifying which clock is actually running and diagnosing whether the deadline entered the decision.

Pacing’s contribution at this phase is narrower than either diagnosis: threshold proximity by itself should not cause an improvised risk change. A change should come from an already defined pacing rule, an applicable provider rule, or another condition explicitly established in advance — and an applicable provider rule always overrides the trader’s own pacing table, not the other way around. Writing the pacing rule before the threshold is visible is what makes the diagnostic frameworks above usable in the moment — they classify a deviation against a rule that already existed, not against a rule improvised after the fact.

Transition from evaluation behavior to funded behavior

This is the phase no existing Costante article owns, and it is where a pacing plan earns its distinct place. Passing an evaluation ends the evaluation’s specific pressures — the applicable loss/drawdown constraint and any minimum-day, expiration, or rebill condition that governed it — and replaces them with a different account governed by its own funded-stage rules: different drawdown mechanics, payout or reward eligibility, consistency requirements, or scaling conditions, depending on the provider. That next account may be simulated or live depending on the program; passing an evaluation does not by itself put a trader’s own money, or the firm’s live capital, on the line. Two opposite behavioral risks are both plausible at this transition, and neither is automatic:

Carried-over assumption	What it looks like in funded trading	Why it no longer fits
Survival mode: “protect the one shot I have”	Freezing on qualified setups, cutting size further than the funded account’s own rules require	The evaluation’s single-attempt framing does not describe a funded account, which may have its own drawdown and recovery process
Validation mode: “the pass proves my process works”	Restoring full or increased risk immediately, treating the pass as evidence the paced-down risk was unnecessarily cautious	Passing an evaluation is a threshold result, not a large enough sample to certify a strategy or a risk process — see the review point below

A pacing plan states, before the transition happens, which risk-per-trade applies on day one of funded trading and what has to be true before it changes — the same discipline the plan already applied to the earlier phases, extended across the one transition that has no loss/drawdown trigger to force the question. Research on implementation intentions — specifying a cue and a response before the situation arrives — has found that this kind of advance commitment can help translate intentions into action across a range of studied goal domains.¹ That evidence concerns advance cue-response planning in general; it does not establish a specific funded-account risk number, and it does not show that a prop-firm pacing plan improves trading outcomes or pass rates. It supports writing the transition decision down before the pass, rather than making it in the relief of having just passed.

Review pacing without using pass/fail as process proof

The evaluation’s outcome and the pacing plan’s adherence are separate questions, and treating one as evidence for the other hides the pattern a review is supposed to find. A trader can pass while having abandoned the pacing table at the first sign of pressure, or fail while having followed it exactly. Neither outcome retroactively changes whether the plan was followed. When a breach does coincide with a missed phase transition, why prop-firm challenge failure follows pacing errors maps each phase’s deviation to the specific failure signature it produces, rather than leaving the connection at “the table wasn’t followed.”

A deviation at a phase transition does not automatically mean the table was wrong or ignored on principle — how decision fatigue can affect prop-firm challenge pacing tests a narrower cause worth checking first: whether adherence at a checkpoint depends on how many other decisions had already occurred that same session, independent of which phase triggered the check.

For each phase transition, record the following; a prop firm trading journal shows where this entry sits next to the account’s dated rule snapshot and session records:

phase entered → date/trigger that defined the entry → risk-per-trade the table specified
→ risk-per-trade actually used → match or deviation → evaluation result (recorded separately)

Classify each transition the same way used elsewhere on this site:

Aligned: the risk-per-trade used matched the table for that phase.
Planned exception: a pre-written exception in the pacing table applied.
Deviation: the risk-per-trade changed because of a threshold, a loss, or the funded transition, without a pre-written exception.
Unclassified: the record does not establish which of the above applies.

A pattern of deviations that still ends in a pass is not evidence the deviations were harmless; it is a sample of one account under one set of market conditions. The review question that matters is whether the table was followed, not whether the evaluation was.

What a pacing plan does not do

A pacing table does not calculate the trader’s normal risk-per-trade, verify a program’s loss rules, guarantee that following the schedule produces a pass, or replace the trade-level risk process it sits on top of. It also cannot retroactively cover a decision whose relevant state is already visible: a rule written after the trader already knows how close the account is to a threshold cannot function as precommitment for that specific decision, because the number was already visible when the rule was written. The same plan can still precommit rules for phases or states that have not yet occurred — the property that makes a rule useful is that it predates the specific state it governs, not that it predates the evaluation as a whole.

Where Costante fits

Costante can support the behavioral execution of a pacing plan by keeping the trader’s relevant written risk caps and stop-rules available before and during a session, surfacing applicable Session Guardrails, logging trade and rule-status context, and separating adherence from outcome during review. Costante does not verify a program’s rules, calculate an evaluation’s remaining loss or drawdown capacity from broker or provider data, determine a funded account’s risk limits, or guarantee an evaluation or funded-trading outcome. The trader remains responsible for building the pacing table itself, for verifying current program terms directly with the provider, and for every risk decision.

Frequently asked questions

What is prop-firm evaluation pacing?

It is a pre-written plan for how risk-per-trade is allowed to change across an evaluation’s phases — the opening stretch, after losses, near a threshold, and at the transition to a funded account — so those changes are decided in advance rather than under pressure.

Should risk-per-trade stay exactly the same throughout an evaluation?

Not necessarily. A pacing plan can call for a lower risk-per-trade in later phases if the account has less remaining rule-constrained risk capacity relative to whatever minimum-day, expiration, or other time condition actually applies — or no reduction at all if the program imposes no comparable constraint. The requirement is that the schedule is written before the phase begins, not that the number never changes.

Do I need to reduce risk after passing an evaluation and moving to a funded account?

There is no universal answer. The relevant point is that the decision should be made and written down before the pass, using the funded-stage account’s own rules, rather than defaulted to either “keep the evaluation’s caution” or “the pass proves I can go bigger” in the moment.

Is evaluation pacing the same as a drawdown risk ladder?

No. A drawdown ladder is a mechanism for resizing after a loss sequence; adjust risk during a drawdown covers that mechanism directly. Pacing is the broader schedule that decides which phase of the evaluation is active and which risk state — including whether the drawdown ladder is even permitted to restore upward — applies at that phase.

Sources

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

For the broader process framework around pacing and rule adherence, see trading discipline.

Gollwitzer, P. M., & Sheeran, P. (2006). Implementation Intentions and Goal Achievement: A Meta-analysis of Effects and Processes. Advances in Experimental Social Psychology, 38, 69–119. ↩