A prop-firm drawdown tracker should show the exact loss floor, the rule-counted account value, and the usable buffer before the next order. “I am down today” is not enough. The tracker must know which program and phase you are in, when its day resets, whether the floor is static or trailing, and whether open equity, commissions, swaps, or pending risk affect the rule.
The practical goal is not to predict a breach. It is to make the current constraint visible early enough to skip or resize a trade. The comparison above supplies three exact first-stage examples at one normalized account size; the method below remains portable because it uses named inputs instead of copied firm percentages.
The number to track: usable buffer = rule-counted account value − active loss floor − reserved open/pending risk − your execution cushion. If any input is stale or Not verified, treat the output as an estimate and use the firm's own dashboard as controlling.
The Two Limits You Must Track
Many programs expose both a session-level control and a maximum-loss floor, but their names and consequences are not universal. A daily control may be a hard failure rule, an optional lockout, or a pause that leaves the account eligible. Maximum loss may fail the evaluation or close the account. Read the exact program and phase instead of inheriting a rule from the company name.
1. Session or daily-loss capacity
Store the firm's reset time and time zone, the amount or formula, the reference balance, and the counted P&L definition. For example, FTMO's classic 2-Step Maximum Daily Loss uses account equity—balance plus open P&L, adjusted for swaps and commissions—and recalculates at the firm's specified daily boundary. Topstep's current Trading Combine daily-loss control is a separate optional setting, while its Maximum Loss Limit still applies. Those are different controls with different outcomes.
Calculate a session buffer only from the active rule definition:
Daily buffer = Daily floor reference − Current rule-counted value
Usable daily buffer = Daily buffer − Open/pending risk reserve − Execution cushion
Some dashboards express the constraint as loss used rather than distance above a floor. Either representation works if the sign convention is explicit and the same inputs reconcile to the provider's dashboard.
2. Maximum-loss capacity
Store the active maximum-loss floor as a value, not just a headline percentage. A static floor stays tied to a fixed reference. An end-of-day trailing floor can move after a new closing high and then remain fixed during the next session. An intraday trailing floor can move while the session is open. The prop-firm drawdown rules guide explains these rule families; your tracker must still use the exact program row.
Maximum-loss buffer = Rule-counted account value − Active maximum-loss floor
Usable account buffer = Maximum-loss buffer − Open/pending risk reserve − Execution cushion
The active constraint is the smaller usable buffer. If the daily control is optional or non-terminal, display that status instead of labeling every threshold a breach.
Buffer Zones Without Inventing Universal Percentages
The old version prescribed the same four percentage bands to every trader and program. That is not defensible. A buffer zone is a personal operating policy inside the firm's hard rules; it should be calibrated to your tested trade risk, open-position behavior, slippage, and correlated exposure.
| State | Definition | Permitted response | Tracker evidence |
|---|---|---|---|
| Normal | Usable buffer supports planned loss plus cushion | Apply the tested plan | Fresh balance/equity, floor, open risk |
| Reduced | Planned loss no longer fits at normal size | Round size down or take only a smaller valid setup | Post-rounding loss remains inside both constraints |
| Stop | No valid size fits the chosen cushion | Do not open another position | Record the binding rule and timestamp |
| Unknown | Rule, floor, reset, or account value is stale | Pause and verify at the provider | Source URL and verified time are missing or conflicted |
Why “I still have half the limit” is not a sizing rule
Remaining room is a cap, not a target. A trade that technically fits the account buffer may still violate your strategy risk, create correlated exposure, or leave no cushion for spread, commission, slippage, and open-equity movement. Use the smaller of strategy risk, usable daily capacity, and usable maximum-loss capacity. Then round down to a valid unit or contract. The position-size calculation guide shows that conversion.
Make the stop state mechanical
Decide the action before the session. A tracker should output one of three things: planned size fits, smaller size fits, or no trade fits. Avoid a fourth output that means “decide emotionally.” Platform risk controls can add friction, but their behavior must be verified separately and they do not replace the firm's rule engine.
Static vs Trailing: The State You Must Preserve
Static maximum loss
A static floor is anchored to the program's stated reference. Your tracker stores that floor once and recalculates distance above it as the rule-counted account value changes. Profits can widen the distance, but a payout, reset, new phase, or replacement account may create a new reference. Do not carry the old floor into a new account lifecycle.
End-of-day trailing loss
An end-of-day trailing floor requires at least four fields: prior active floor, current session value, the highest eligible closing value, and the next-session floor. Topstep's Maximum Loss Limit rises with end-of-day balance and locks when it reaches the starting balance. Apex's EOD threshold is also calculated from an eligible closing high and enforced during the following session, but current stopping behavior differs by evaluation platform and funded stage. The exact current rows above are therefore examples, not interchangeable templates.
The phrase “end of day” describes when the next floor is calculated, not when enforcement happens. Both firms document real-time enforcement against the already-active floor during the session. A tracker that updates the floor intraday for an EOD program can show less room than the actual rule; a tracker that waits until the close to monitor the active floor can miss a breach.
Intraday trailing loss
An intraday trail needs an eligible high-water mark that updates at the rule's frequency and from the correct balance or equity measure. Never approximate that with the largest closed-trade balance if the rule uses intraday equity. The trailing drawdown walkthrough shows why calculation frequency and enforcement frequency must be stored separately.
Migration rule: changing program, phase, account size, platform, or payout state creates a new tracker configuration. Do not silently reuse a prior floor just because the firm name is unchanged.
Building Your Real-Time Tracker
“Real time” should mean that every displayed value has a timestamp and source—not that a spreadsheet refresh is equivalent to the provider's system. Build the simplest method you can keep reconciled.
Minimum viable pre-trade card
- Identity: firm, exact program ID, phase, region, account size, platform, and account ID.
- Daily rule: current floor or allowance, reset boundary, counted value, and consequence.
- Maximum-loss rule: type, active floor, eligible high-water mark, update frequency, and stop/lock behavior.
- Exposure: open unrealized P&L, pending orders, correlated positions, fees, and planned worst-case loss.
- Decision: normal size, reduced valid size, stop, or verify.
- Evidence: source URL, provider-dashboard timestamp, and the trade or import batch used.
Spreadsheet or Notion tracker
Use separate Account State and Trade/Execution tables. Never overwrite the prior floor; append timestamped snapshots so you can explain why the tracker showed a particular buffer before an order. Protect formula cells, make the reset time-zone visible, and add a reconciliation flag when the calculated value differs from the provider dashboard.
Automated journal tracker
Automation reduces retyping but does not prove rule correctness. Verify the import route, deduplication, trade grouping, time zone, commission treatment, open-equity availability, and program version. If the feed lacks open positions, label the current buffer closed-trade estimate, not live capacity.
Three Drawdown-Tracking Mistakes
1. Replacing the firm's rule with a generic percentage
Company names do not identify one immutable rulebook. Store the exact program and phase, then render live terms from a dated source. A fixed percentage in a note is not a tracker.
2. Mixing daily loss, maximum loss, and personal stops
A personal session stop may be tighter than the firm limit. An optional platform lockout may pause trading without failing the account. A maximum-loss touch may end the evaluation. Display the label and consequence beside every number so a conservative house rule is not mistaken for the official breach rule.
3. Updating after the trade instead of before the order
Post-session review explains what happened; it does not constrain the next order. The check belongs after account reconciliation and before position sizing. When several accounts are active, keep each rule state separate as described in the multi-account tracking workflow.
Who Needs a Different Control
- Automated strategies: the rule model belongs in a tested circuit breaker with independent monitoring, not a manually read card.
- Very high trade frequency: pre-order manual updates may be too slow; use verified platform controls and a feed whose latency and failure behavior are known.
- Multi-day positions: model overnight financing, reset boundaries, gaps, and open-equity rules rather than reusing an intraday session checklist.
- Personal accounts without external program rules: use portfolio drawdown and broker risk controls; do not pretend a prop-program tracker is a universal risk policy.
Where TSB Fits in the Tracker Loop
Trader's Second Brain is our product. It can bring supported trade history into one review workflow through 331 recognized broker, exchange, platform, and prop-export profiles, then keep prop-account review and trade evidence together. For accounts with consistency constraints, the consistency-rule tracker is a separate calculation from drawdown capacity.
TSB does not replace the firm's dashboard, guarantee open-equity coverage, block an order, or prevent a breach. Test the exact source route, reconcile it, and fall back to Not verified whenever the current program or feed does not provide the required input. Full Access offers monthly or lifetime access; check the current plan page before choosing either route.
The Bottom Line: Floor, State, Buffer, Evidence
A defensible drawdown tracker has four layers: an exact active floor, a fresh rule-counted account value, a usable buffer after reserved risk and cushion, and evidence showing where every input came from. It should become more cautious when data is missing, not more confident.
Before every new order, ask: does this exact planned loss fit inside both my strategy budget and the smallest verified program buffer? If the answer is no—or the inputs cannot be reconciled—the correct tracker output is no trade.
