How to Track Performance for FTMO Challenges

Tracking an FTMO challenge is not the same as watching whether the account is green. An evaluation combines performance objectives with loss constraints, and a trader can be profitable overall while still putting the account at risk through one concentrated day, excessive drawdown, or inconsistent sizing.

Use FTMO's own dashboard and current official terms as the source of truth for account status. Use a trading journal for a different job: preserving screenshots, normalizing outcomes in R, tagging setups, and identifying the decisions that consume rule headroom.

Build a rule-headroom scoreboard

Before each session, write down the distance between the current account state and each binding limit. Think in headroom, not just current P&L. The key question is not “How much can I make today?” but “How much planned risk can the account safely carry under the current rules?”

• Daily loss used and remaining under the current calculation
• Current equity or balance relative to the maximum-loss threshold
• Progress toward the profit objective
• Required or completed trading days, if applicable
• Open risk across all positions and correlated ideas
• Your own stop-trading limit, which may be tighter than the firm's limit

Do not copy generic percentages from an old article or another account. Rules, account formats, and calculation details can change. Confirm whether open P&L, commissions, resets, or time boundaries affect the official number in your specific challenge.

Track every trade in R

R measures the result relative to planned risk. If the amount you intended to lose at the stop is 1R, a half-sized loss is -0.5R and a gain twice that planned risk is +2R. This makes trades easier to compare when instruments, stop distances, or position sizes differ.

Record planned R before entry and realized R afterward. A gap between them can expose slippage, stop movement, partial exits, or sizing errors. It also makes consistency visible: repeated small planned risks followed by one oversized recovery attempt is a process problem even if that trade wins.

Preserve the setup with screenshots and tags

Save a chart screenshot that shows the context available near entry. In TradeLogger, review the suggested fields rather than accepting them blindly, then tag the setup, session, market condition, emotion, and rule-following. The screenshot helps separate a legitimate setup loss from a trade that never met the plan.

• Setup name and quality grade
• Session and time of entry
• Planned stop, target, and risk in R
• Emotion or pressure before the order
• Whether size matched the written model
• Whether the trade respected personal and firm constraints

Measure consistency without chasing it

Consistency is broader than an official metric. Review whether one day, one setup, or one unusually large trade accounts for most of your result. Also compare average planned risk, number of trades per session, and rule-followed performance. Concentration can signal that the process is fragile even when the challenge dashboard is positive.

Do not force extra trades merely to make a curve look smooth. The goal is repeatable execution, not cosmetic statistics. A no-trade day that followed the plan can be better than a busy day created by target pressure.

Run a daily close and weekly review

1. Reconcile official challenge figures in the FTMO dashboard.
2. Complete missing screenshots and correct journal fields.
3. Total realized R and note remaining personal risk allowance.
4. Mark every rule break, including profitable ones.
5. At week's end, group results by setup, session, and emotion.
6. Choose one measurable behavior to change during the next week.

If headroom becomes narrow, reducing exposure or stopping can be a process decision, not a prediction. TradeLogger can help organize the evidence behind that decision, but it does not calculate or certify FTMO compliance. If you want a structured screenshot and tag workflow beside the official tools, start with a few challenge trades and see whether the review becomes clearer.