The best FTMO trading journal is not the one with the most charts. It is the one that keeps the exact program state, risk-rule inputs, source timestamp, and trade evidence together—and tells you when the data is too stale to support another order.
This guide covers the current FTMO CFD 1-Step and 2-Step evaluation routes. FTMO has announced futures trading (currently in beta); details are being finalized — see our upcoming coverage. Do not apply the CFD formulas or component rows below to that separately governed product.
FTMO Account MetriX and the current agreement remain controlling. A journal is a reconciliation and decision layer: it can preserve your calculations and behavior evidence, but it cannot grant extra loss capacity, prevent a breach, or turn a delayed import into live account equity.
1. FTMO rules you must track every single day
Start the journal with identity, not P&L. Record firm, product, phase, account size, account type, platform, server timezone, and lifecycle state. A 1-Step Challenge, 2-Step Challenge, Verification, and subsequent FTMO Account do not share one generic rule row.
The two loss calculations need different inputs:
- Maximum Daily Loss: FTMO defines an equity floor using the account balance captured at 00:00 CE(S)T minus the program's daily-loss amount. Equity includes open-position P&L, swaps, and commissions. The resulting floor remains active until the next reset.
- Maximum Loss: the 2-Step route uses a static floor tied to Initial Simulated Capital. The 1-Step route uses an end-of-day trailing floor based on the highest qualifying midnight balance and does not move down between reward resets.
- Completion objectives: 2-Step uses separate Challenge and Verification phases with minimum trading days. 1-Step uses one Challenge and a Best Day condition that can require more positive-day profit even after the nominal target is reached.
Rule-counted equity = current balance + open P&L + swaps − commissions.
Daily buffer = rule-counted equity − active daily floor.
Maximum-loss buffer = rule-counted equity − active maximum-loss floor.
Usable pre-trade buffer = smaller active buffer − reserved open/pending risk − your execution cushion.
The current percentages, price, target, minimum days, payout timing, markets, platforms, and verified date are rendered in the exact server component above. Keep those live values out of copied journal instructions. For a complete floor-and-buffer record, use the prop-firm drawdown tracker.
2. What to journal in each FTMO phase
Use one trade ledger but separate state tables for each account and phase. Carrying the same formulas forward without changing the program key is a common way to calculate the wrong floor correctly.
FTMO Challenge: 1-Step
Track the balance captured at the daily reset, daily equity floor, highest qualifying end-of-day balance, trailing maximum-loss floor, positive-day profit, Best Day, and target state. The Best Day test is an objective, not a hard breach: if it is not met, the trader continues until the concentration condition is satisfied.
FTMO Challenge: 2-Step — Challenge
Track the daily equity floor from the current reset balance, the static maximum-loss floor from Initial Simulated Capital, target progress with all positions closed, and distinct trading days based on the FTMO day boundary. The general Discipline Score is informational; the documented Trading Objectives are what determine completion.
FTMO Challenge: 2-Step — Verification
Create a new phase record rather than overwriting the Challenge row. The target changes while the daily and static maximum-loss models continue. Preserve the Challenge evidence for strategy review, but do not add its P&L or trading days to the Verification calculations.
Subsequent FTMO Account
Remove evaluation-only target and minimum-day assumptions where FTMO does not apply them, preserve the correct loss model for the selected route, and add reward-cycle state. A reward can change the reference state, so archive the pre-reward snapshot and create the next cycle explicitly.
If you are still planning the evaluation, the FTMO preparation guide turns these states into a rehearsal sequence without promising that journaling alone causes a pass.
3. What to track for every trade
The trade row should explain both the economic result and whether the decision was valid before the outcome was known.
- Identity and sourceAccount ID, program, phase, platform, source file or sync route, import batch, and source timestamp. Never merge two FTMO accounts merely because they share a nominal size.
- Open and close time in two zonesPreserve platform time and normalized UTC, then derive the FTMO CE(S)T trading day. Day-boundary errors can misstate both Daily Loss and Best Day calculations.
- Logical trade and executionsKeep the source tickets or fills, but assign them to one logical trade when you scale in, scale out, or partially close. Document the grouping rule so win rate and expectancy stay reproducible.
- Gross result, swaps, commissions, and net resultDo not calculate rule-counted equity from a profit column that excludes costs. Reconcile each component with Account MetriX or the platform report.
- Initial risk and realized RRecord planned stop risk before entry and final net result after costs. Lot size alone cannot show whether risk was consistent across instruments or stop distances.
- Setup, session, and news contextUse a small controlled tag set, plus a factual event flag. Do not infer that FTMO requires a specific setup distribution; the purpose is to test your own repeatability and prohibited-practice risk.
- Plan compliance and evidenceCapture the planned condition, invalidation, screenshot, deviation reason, and whether the order respected your own pre-trade stop. Outcome and process should remain separate columns.
- Rule state before and after the tradeStore active floors, rule-counted equity, open/pending exposure, remaining buffer, target/day/Best-Day state, source URL, and timestamp. If open equity is missing, mark the result Unknown, not safe.
Size from the smaller verified buffer and the strategy's tested risk, not from the simulated account label. The prop-firm position-sizing workflow shows how to convert an exact floor into a per-trade cap without inventing a universal percentage.
4. Daily review template for FTMO traders
Run the review after the FTMO day has closed and again before the next order if account state changed. A fixed five-minute promise is not useful; completeness matters more than speed.
For strategy statistics, keep the same population definition from day to day. Our expectancy guide explains why mixing executions, logical trades, breakevens, and gross results can reverse the conclusion.
5. The mistakes that kill FTMO challenges
These are journal-control failures, not claims about the most common behavior in FTMO's private population.
Using yesterday's floor after the reset
The new daily limit depends on the balance captured at FTMO's day boundary. A local calendar date or platform timezone can place a trade in the wrong day.
Fix: Store the FTMO reset timestamp, source balance, calculated floor, and next reset countdown before trading.
Ignoring open P&L and costs
A closed-trade journal can show room while rule-counted equity is already lower because of floating loss, swaps, or commissions.
Fix: Treat a closed-only import as incomplete for live rule decisions and reconcile with Account MetriX.
Applying the 2-Step static floor to 1-Step
The programs use different maximum-loss models. A generic “FTMO drawdown” column hides the reference balance and creates the wrong buffer.
Fix: Key every state row by program and phase; reject an import whose identity does not match the configured rule set.
Treating an informational score as a secret pass rule
FTMO states that its general Discipline Score is informational. The documented objectives and forbidden-practice terms—not an invented review percentage—determine the evaluation outcome.
Fix: Use consistency metrics to improve your process, but label firm rules only when the primary source says they apply to that exact program.
Letting one outcome redefine risk
A win does not validate an oversized or out-of-plan trade, and a loss does not invalidate a correctly executed setup. Outcome-only journals reward the same behavior that later consumes the buffer.
Fix: Compare initial planned risk, actual maximum exposure, rule buffer, and plan compliance before reading the result.
Assuming an import is live monitoring
File uploads and periodic synchronization can lag, duplicate, or omit state. A dashboard assembled from incomplete records cannot reliably warn about the next order.
Fix: Display last-source time and coverage limits. When the firm state is newer, the journal must defer to it.
6. Setting up your FTMO journal with TSB
Trader's Second Brain is our product. Use it when its exact import route and prop-review workflow reduce the manual reconciliation burden; do not present it as the authority for FTMO rules.
Step 1: Verify the import route
TSB recognizes structured import profiles across 328 source formats, including supported MetaTrader reports and synchronization routes. Coverage is route-specific. Test a representative FTMO export and compare tickets, times, gross result, swaps, commissions, and net result before relying on the normalized ledger.
Step 2: Configure exact program identity
Select FTMO, then the exact 1-Step or 2-Step program, phase, account size, and platform. Never clone a generic FTMO template into a different route without reloading its canonical rules and verified date.
Step 3: Separate retrospective and live state
Imported closed trades support review, setup analysis, and consistency checks. Live loss capacity additionally depends on current balance, open P&L, swaps, commissions, pending exposure, and the FTMO reset. If any required field is missing or stale, the tracker should show Not verified or Unknown.
Step 4: Attach the decision evidence
Add setup, initial risk, invalidation, screenshot, deviation, and lesson to the normalized trade. Then run the daily reconciliation sequence above. A separate qualitative workspace can help, but it is optional; the canonical rule and evidence record should not depend on two-way synchronization that has not been verified.
Build the FTMO Review Around Exact Rules
Current TSB monthly and lifetime access values render from server product truth. First verify your source route, then inspect the workflow with one representative import.
Check the exact import route See the TSB review workflowTSB cannot override FTMO Account MetriX, guarantee open-equity coverage, block an order, or prevent a breach. Reconcile the source and keep the exact rule state current.
If you prefer to prototype the tracker before selecting software, the Notion prop-firm tracker guide explains the same identity, source, and stale-state requirements without claiming automatic firm synchronization.
