Prop Firm Trading Journal: What to Track by Stage

A prop firm trading journal should track which account, stage (such as an evaluation phase or a funded account), evaluation attempt, and, where the provider uses one, payout measurement window each trade belongs to. It should also track a dated and versioned copy of the provider’s rules for that stage, the trader’s own personal rules for that stage, the decision-time context of each trade (planned risk, account state, and a reason written before the outcome), separate classifications for personal-rule adherence and for provider status, and a review whenever the account changes stage. A generic trade log records what was traded. A prop-firm journal also records which rule set was in force, because the same result can mean different things under different stage rules.

That is why a prop-firm journal needs its own structure. Provider rules differ by program, by variant, and by stage, and they change. A journal that stores only fills and P&L cannot later answer the review questions that matter in this setting: did the trader follow their own plan, did the account break a provider rule, was an evaluation objective simply not yet met, and did behavior change when the account moved from evaluation to funded? Those are four different questions, and a journal that folds them into one label will answer all of them badly.

This guide covers the record structure only. It does not recommend a provider, a risk level, or a pacing schedule, and nothing here states a provider’s rules for your account; only the provider’s current documentation and dashboard do that. The prop firm discipline guide covers which personal guardrails to write around provider constraints, and prop-firm evaluation pacing covers how risk should change across an evaluation’s phases. This article is about the journal that makes both of those reviewable.

What should a prop firm trading journal track?

A prop firm trading journal should track five connected layers:

Layer	What to record	Question it answers
Account and stage	Provider, exact program and variant, account ID, account-size label, actual starting balance, simulated or live status, stage, attempt ID, stage dates and outcome	Which account, which stage, which attempt?
Provider rule snapshot	Each applicable rule or objective, its value, calculation basis, timing, trading-day boundary, source, verification date, and snapshot version	Which external rules applied at the time?
Personal rules	The trader’s own limits, re-entry and cutoff rules, after-loss conditions, and pre-authorized exceptions, versioned by stage and effective date	What did the trader intend to do?
Session and trade record	Planned risk, actual initial risk, account state at the decision point with its data provenance, setup qualification, reason written before the outcome	What was decided, and in what account state?
Review	Personal-rule adherence, provider rule status, objective status, payout eligibility, and outcome, each recorded separately; transition snapshots and later comparisons	Did execution follow the plan, and did it change when the stage changed?

The first two layers are what a generic journal usually lacks. The last three exist in any serious journal, but in a prop-firm account each of them has to be read against the first two. A planned risk of $400 means something different with $1,800 left above a provider’s loss floor than with $500 left.

Start with an account and stage record

Each account gets one header record, and each stage of that account gets its own entry. Complete it once, when the stage begins:

Provider, program, and variant, exactly as the provider labels them. “FTMO Challenge: 1-Step” and “FTMO Challenge: 2-Step” carry different rule sets; so do Topstep’s Standard and Consistency payout paths.
Account ID.
Account-size label and actual starting balance, as two fields. They are not always the same thing. Topstep, for example, states that the 50K, 100K, or 150K label on an Express Funded Account refers to buying power, and that the account balance starts at $0.¹ A journal that writes “$50,000 account” there will compute every distance and percentage wrongly.
Simulated or live, taken from the provider’s own statement rather than assumed.
Stage: evaluation phase 1, verification, funded account, or whatever the provider calls it.
Attempt ID, if the evaluation has been reset or repurchased.
Stage start date, and end date and stage outcome when it ends: passed, failed, reset, closed, or moved to another stage, as the provider reports it.

The attempt ID matters more than it looks. Without it, trades from a failed attempt and a new attempt blur into one history, and a review can no longer tell whether a pattern belongs to one account under one set of pressures or to the trader across several. Treat each attempt as its own sample.

Link each trade to the stage entry, not only to the account. When an account moves from evaluation to funded, the rules around it change even if some identifiers do not.

Keep a versioned provider-rule snapshot

Write down the rules and objectives that apply to the current stage when the stage begins, with the source and the date you checked them. Do not rely on memory or on a forum summary. For each rule or objective:

rule ID (your own label, e.g. PX-EVAL-R1):
provider's name for it, as worded:
type: account rule / evaluation objective / payout condition
applies to (program, variant, stage):
value:
calculation basis (balance, equity, closed P&L, net P&L; denominator):
timing (when it updates; when it is checked):
trading-day boundary and time zone, if relevant:
consequence if not met or breached, as the provider states it:
source URL:
date verified:
effective date (only if the provider documents one):
snapshot version:
corrected by (correction ID, if any):

Two fields do most of the work. Type stops a missed objective from being recorded as a breach. Snapshot version keeps history intact: each version is an observed record of what the trader read and understood on its verification date, and its contents are never edited afterward; the only later addition is a pointer to a correction record. When the provider changes a rule, add a new version. Leave the effective date blank unless the provider actually publishes one; the verification date records when you checked, not when the rule began.

An observed snapshot is not proof of what the provider actually applied. If you later find a snapshot was wrong, keep it unchanged and add a short correction record:

correction ID / date discovered:
snapshot corrected (kept as recorded):
what was recorded vs. what actually applied:
evidence for the applicable rule (provider source, date verified):
effective date (only if the provider documents one):
provider statuses reassessed (which records, new status or unverified):

Then reassess provider status for the affected records against the verified applicable rule, not against the mistaken reading. If the rule that actually applied on those dates cannot be established from provider evidence, those statuses become unverified. The original reasons and personal-rule adherence labels stay as recorded: they describe what the trader knew and decided at the time, and the correction record sits beside them rather than rewriting them. A trader’s mistaken reading can explain a decision; it never establishes provider compliance.

Both examples below were checked against the providers’ pages on September 22, 2026, and the payout-related claims were rechecked on September 23, 2026. They are illustrations of why the fields are needed, not a statement of your account’s rules, and both providers can change them.

FTMO, 1-Step. The FTMO Challenge: 1-Step has a Profit Target of 10% of Initial Simulated Capital; FTMO states there is no Profit Target on the FTMO Account that follows. The 1-Step Best Day Rule requires that the Best Day does not represent more than 50% of Positive Days’ Profit, the sum of closed profits and losses from all profitable trading days, with each trading day starting at 00:00 CE(S)T. It applies to passing the 1-Step Challenge and to Reward eligibility on the FTMO Account (1-Step). FTMO states that exceeding the Best Day limit is not treated as a rule breach; the trader needs to keep trading until the Best Day is 50% or less of Positive Days’ Profit.² That is an objective not yet met. Maximum Daily Loss and Maximum Loss are different: FTMO states that equity dropping below either limit means the rule is considered violated.² FTMO’s page lists the Best Day Rule under the 1-Step program, not under the 2-Step, which has its own objectives (10% then 5% Profit Targets and a Minimum Trading Days rule). A 1-Step snapshot should not be copied into a 2-Step journal.

Topstep, Trading Combine to Express Funded Account. Topstep describes the standard Trading Combine as having one rule, the Maximum Loss Limit, and two objectives: the Profit Target and the Consistency Target.³ However, traders in its Responsible Trading Program (RTP) receive an additional Daily Loss Limit on new Trading Combines. Record the rules assigned to the specific account rather than assuming the standard rule set applies universally.⁴ The Consistency Target involves three separate numbers with different denominators. The original Profit Target is set by account size. The best-day percentage is Best Day Profit ÷ Total Profit. And 55% of the original Profit Target marks the best-day level that triggers an increase (Topstep’s best-day recommendation for a $3,000 target is less than $1,650); if the single best day exceeds it, the adjusted effective Profit Target becomes Best Day ÷ 0.55. A best-day percentage above 55% while total profit is still small does not by itself change the original target. Losses do not reset the best day, and the best day locks at 3:10 PM CT.⁵ Record the provider’s dashboard status for this objective, not only your own calculation. The Trading Combine trading day runs from 5:00 PM CT to 3:10 PM CT the next calendar day, and profits do not carry over to the Express Funded Account.³ In the Express Funded Account, the trader normally chooses a Standard or Consistency payout path at activation.⁶ That choice is not always open: Topstep states that a trader placed in its Responsible Trading Program who passes a Trading Combine is limited to the Consistency path, with Standard unavailable until the program is completed, apart from stated carve-outs for accounts that predate placement.⁴ Record the path the provider actually assigned. Only the Consistency path adds a 40% objective: largest single-day net profit ÷ total net profit must be 40% or below, with at least three trading days of at least one trade each, to be payout eligible. Above 40%, the payout objective is not currently met and Topstep’s instruction is to keep trading. After a payout is requested, the calculation resets and the new window starts on the next trading day; trades on the request day do not count toward it.⁵⁶

Two details from these pages show why the snapshot stores the provider’s own wording. Topstep’s two pages name the Consistency-path numerator slightly differently (“Largest Single-Day Net Profit” and “Largest Winning Day”), and the Trading Combine target is described both relative to the Profit Target and through a Best Day ÷ Total Profit formula. Record the wording and the source for each. If the calculation is ambiguous for your case, mark it unverified and use the provider’s dashboard figure, not your own interpretation.

Loss limits: four separate facts

For every loss limit, record four things separately, because they answer different questions about the same number:

When the floor updates. Fixed, or trailing, and on what: intraday equity, end-of-day balance, or something else.
What value is monitored for a breach. Balance, equity, or net P&L.
Whether unrealized P&L counts.
What happens when the limit is touched.

Topstep’s Maximum Loss Limit illustrates why. Topstep states that the limit trails upward as the end-of-day balance grows and never moves down, locking at the starting balance in the Trading Combine and at $0 in the Express Funded Account. It updates at the end of each trading day but is monitored in real time, both realized and unrealized P&L count toward it, and touching it triggers liquidation. In the Trading Combine that means liquidation for the rest of the day and ineligibility for funding until a Reset; in the Express Funded Account the account is closed.¹ The floor moves once a day, but the account is checked at every moment against it.

Your journal can record these facts and your own estimate of distance to the floor. It cannot establish whether the account complied. Only the provider’s records do that, and a trader-maintained journal should never be read as evidence of provider compliance.

Separate provider rules from personal rules

Keep the provider snapshot and the trader’s personal rules in separate sections. The provider rule defines what the program permits; the personal rule defines what the trader intended to do inside that permission.

	Provider rule	Personal rule
Who sets it	The provider	The trader, before the session
Example	A maximum loss limit defined by the program	A personal daily stop set above that floor
What a departure means	Whatever the provider’s terms say: a breach, or an objective not yet met	A process deviation, whether or not the account was harmed
Who determines status	The provider’s records	The trader, against the written plan

Version the personal rules the same way as the provider snapshot. For each stage, record a rule-set ID and version, the effective date, and:

risk rules: maximum planned risk per trade and the personal daily stop;
re-entry and session cutoff rules;
after-loss conditions and what changes when they trigger;
pre-authorized exceptions: each exception written before the session, with its condition. An exception written after the decision is not pre-authorized, and no personal exception can override a provider rule.

When a personal rule changes, create a new version with the old value, the new value, the reason, and the effective date. Every review then uses the version that applied when the decision was made, not today’s version. That change log is also what later shows whether a rule was adjusted deliberately at a stage transition or drifted mid-evaluation.

Record each decision with its context

Before the session, record the stage, the personal rule-set version in force, the permitted setups, and the account state at the start. During the session, record only what a later review cannot reconstruct:

Setup qualification: did the setup meet the trader’s written criteria?
Planned risk before entry: the loss if the initial stop is hit as planned, in dollars, stated as distance from planned entry to initial stop × size × contract or point value. Say whether commissions are included.
Actual initial risk at entry, when known: the same calculation from the actual fill to the stop actually placed.
Account state at the decision point: distance to each provider loss floor, progress on each objective, and consistency position, each with its provenance: provider-reported (read from the provider’s dashboard), trader-entered (typed from memory or a platform estimate), independently calculated (worked out by the trader from recorded values), or unverified.
Reason, written before the outcome, in one or two sentences, including whether any provider threshold or deadline was part of it.

After the trade, record the realized result separately. Keep three numbers distinct: planned risk, actual initial risk, and realized P&L. If you also track the worst open loss during the trade (maximum adverse excursion), give it its own field; it is neither the initial risk nor the result. If you express results in R-multiples, define R as the planned risk in dollars for that trade, and keep that definition fixed.

Manually recorded values are not broker-verified or provider-verified just because they were recorded. If the dashboard figure was not checked, the provenance field says so. Do not fill a gap with a precise-looking estimate.

The reason field matters because of hindsight. In Fischhoff’s 1975 experiments, participants who were told how an event turned out judged that outcome as more likely than participants who were not told, and they were largely unaware of how much the outcome information had changed their judgment.⁷ Those were general judgment tasks, not trading, and the study does not show that a journal entry prevents hindsight bias or improves results. The practical point is simpler: a reason written before the outcome is a contemporaneous record that a later review can compare against, where a reason reconstructed after a loss or a pass is already mixed with the result.

Classify each decision on separate dimensions

A single label such as “aligned” or “breach” mixes up questions with different answers and different authorities. Record these as separate fields:

A. Personal-rule adherence — each eligible decision against the personal rule-set version in force at the time. An eligible decision is any entry, exit, size or stop change, or choice to continue past a personal limit that a personal rule governs. One trade usually contains at least two decisions (entry and exit), so decision counts and trade counts are reported separately. Each eligible decision gets exactly one label:

Aligned: the decision matched the personal rules.
Pre-authorized exception: a written exception that existed before the decision applied, and its documented condition was met. An exception with no written condition on record is not pre-authorized.
Deviation: the decision departed from a personal rule with no pre-authorized exception.
Unclassified: the record does not show which of the above applies. A decision known to have happened, for example from a platform fill, but never journaled is unclassified, never assumed aligned.

B. Provider rule status — for each provider account rule, such as a maximum loss limit:

Rule compliant: confirmed from the provider’s records.
Rule breached: reported by the provider.
Unverified: not yet confirmed. The absence of a breach notice is not confirmation.
Not applicable: the rule does not apply to this stage.

C. Evaluation objective status — for each objective, such as a profit target or consistency target: met, not yet met, not applicable, or unverified. An objective that is not yet met is not a rule breach.

D. Payout eligibility, where the stage has payouts: eligible, not currently eligible, not applicable, or unverified. Not currently eligible is not an account failure unless the provider says so.

E. Outcome — recorded last and separately: realized P&L, account outcome (for example, still active or closed), and stage outcome (for example, passed or failed).

The dimensions are independent. An aligned decision can lose money. A deviation can be profitable. And a provider breach can happen on a day when every decision followed the plan. In that last case, the decisions stay aligned; the finding is about plan compatibility, whether the plan as written could reach the provider’s limit, and it is recorded as a separate review item rather than relabeled as a deviation after the fact.

Keeping outcome out of the adherence field matters for the same reason as the reason field. In Baron and Hershey’s 1988 studies, participants rated the same decision, made with the same information, as better thought out when it was followed by a good outcome than by a bad one, even when they said outcomes should not matter.⁸ Those were hypothetical medical and gambling decisions made by others, not trading reviews, so they do not show how much any trader’s review is affected. They do show why a journal should not let the result set the adherence label. A pass or a payout makes the decisions before it feel justified; a deviation that ends in a pass is still a deviation.

For the session as a whole, also record why it ended: because the plan said so (cutoff, personal daily stop, re-entry limit), or for another reason. “Stopped because the best day was near the consistency level” is aligned if the plan said to stop there. If it did not, it is a deviation in the cautious direction, and it is still worth reviewing.

A worked example: one decision, evaluation to funded

The example below is hypothetical. “Provider X” is fictional, and its rules are invented to show the recordkeeping, not taken from any real firm. Its “rule sheet”, “dashboard”, and dates exist only inside the scenario: “simulated dashboard record” below marks what would be provider-reported in a real account, not anything independently verified. The personal-rule values are illustrations, not recommendations.

1. Evaluation stage record (stage ID S1)

Provider X / Evaluation / variant: Standard / account PX-4471
Account-size label: 50K     Starting balance: $50,000
Status: simulated (per the fictional rule sheet)
Stage: evaluation   Attempt: A2   Start: 2026-09-01

2. Illustrative provider rule snapshot PX-EVAL v1 (fictional rule sheet; illustrative verification date 2026-09-01; no effective date given)

R1  account rule   Loss floor: $2,000 below the highest end-of-day balance;
                   updates at end of day; monitored intraday on equity,
                   unrealized P&L included; touching it fails the attempt.
O1  objective      Profit target: $3,000 above starting balance.
O2  objective      Best day ≤ 50% of total profit, where best day is the
                   highest closed profit on one trading day. If exceeded,
                   the effective profit target becomes best day ÷ 0.50.
                   Not a breach.
Trading day: ends 16:00 ET.

3. Personal rule set P-EVAL v3 (effective 2026-09-01): maximum planned risk $400 per trade (entry to initial stop × size × point value, commissions excluded); personal daily stop −$600 realized; one re-entry per setup; no new entries after 11:30 ET; after two consecutive losses, maximum planned risk $200 for the rest of the session. Pre-authorized exception E1: one entry after 11:30 ET is allowed if the entry order was resting before 11:30 ET.

4. The decision (session 6, trading day 6; trade T6-1, decisions D6-01 entry and D6-02 exit)

Account state before entry (simulated dashboard record, 10:02 ET):
  total profit $1,400; best day so far $500
  highest end-of-day balance $51,500 → floor $49,500; distance $1,900
D6-01 entry, 10:05 ET: setup meets written criteria
  planned risk $400; actual initial risk at entry $400
  reason (before outcome): "First qualifying setup today, full planned
  size. Target is $1,600 away; not a reason for this trade."
D6-02 exit, 10:48 ET: at planned target
T6-1 realized P&L: +$1,600 net (the fictional account charges no fees,
  so gross = net); 4R, R = $400 planned risk.
No further trades in session 6; no open position at session end.

5. Classification after the session

A. Personal adherence (P-EVAL v3):  D6-01 aligned; D6-02 aligned
B. R1 loss floor:     Rule compliant (simulated dashboard record, end of day)
C. O1 original $3,000 profit target:  Reached ($3,000 total profit)
   O2 best day:       Not yet met: $1,600 ÷ $3,000 = 53.33%
   Effective target:  $1,600 ÷ 0.50 = $3,200; remaining: $200
   Evaluation:        In progress
D. Payout eligibility:  Not applicable (evaluation)
E. Outcome:  T6-1 +$1,600 net; session 6 realized P&L +$1,600 (1 closed
             trade, no open P&L); account active; stage in progress

A generic journal would log this as ”+$1,600, passed” or as “broke the consistency rule”. Neither is right. The decision was aligned, no account rule was breached, the original $3,000 threshold was reached, and the best-day objective is not yet met, so the effective target is now $3,200. The remaining $200 has to come on another trading day, assuming the $1,600 day stays the best day and no other constraint is triggered: under this fictional rule, more profit on day 6 would add to the best day itself and raise the effective target by more than it adds to total profit. Recording those separately also keeps the rest of the session honest: if the trader then takes a sub-criteria trade after 11:30 “to finish today”, that decision is a personal deviation, and its outcome does not change that label.

Days 7 to 9 add $450 in total, with no day above $1,600. Total profit is $3,450, the best day is still $1,600 (46.4%), and both O1 and O2 are met on day 9.

6. Transition snapshot (recorded 2026-09-11, the day the simulated dashboard shows the pass)

Transition: passed evaluation → funded   Attempt A2 closed: passed
New stage: S2 (funded; header below)
Old snapshot: PX-EVAL v1   New: PX-FUND v1 (fictional rule sheet;
  illustrative verification date 2026-09-11)
Provider changes:  O1, O2 → not applicable
                   funded balance starts at $0; 50K label = buying power
                   loss floor starts at −$2,000, trails end-of-day balance,
                   locks at $0; touching it closes the account
                   new payout condition P1: largest day ≤ 40% of net profit
                   in the payout window, minimum 3 trading days; window
                   resets the trading day after a payout request
Personal changes (P-EVAL v3 → P-FUND v1, effective 2026-09-14):
  max planned risk $400 → $250. Reason: a floor breach now closes the
  funded account instead of ending a repurchasable attempt.
  Cutoff, re-entry, after-loss rule, and E1: unchanged.
Previous-stage behavior: 19 trades, 38 eligible decisions (19 entries,
  19 exits): 34 aligned, 1 pre-authorized exception (E1), 2 deviations
  (both post-cutoff entries), 1 unclassified (an exit with no record).
  Adherence 35 of 37 classified (94.6%); 1 unclassified shown separately.
Previous-stage results (separate): passed on trading day 9; total profit
  $3,450; best day $1,600.
New account state: balance $0; floor −$2,000; payout window W1 opens
  with the first funded session on 2026-09-14.
Post-transition comparison: not yet available.

The funded stage then gets its own header, created before its first session:

Stage S2 / Provider X / Funded / account PX-5820 (newly issued under the
  fictional rule sheet; PX-4471 closed with attempt A2)
Account-size label: 50K     Starting balance: $0
Status: simulated (per the fictional rule sheet)
Start: 2026-09-14 (first funded session)
Provider snapshot: PX-FUND v1
Personal rule set: P-FUND v1, effective 2026-09-14
Payout window: W1, opened 2026-09-14

7. What had to change for the funded stage: a new stage entry (S2) with its own starting balance, a new provider snapshot version, the objective fields replaced by a payout-eligibility field, a new personal rule-set version with a dated reason, and a payout-window ID so later payout resets can be separated. What did not change is just as useful: the evaluation trades keep their original labels, rule versions, and account states.

Review every stage transition in two steps

A stage transition gets two separate entries, made at different times. Transitions include passing an evaluation phase, failing one, a reset, and moving to a funded account.

Transition snapshot, completed when the stage changes. It records only what is known that day:

transition type and date;
old and new provider snapshot versions and the rules that changed;
personal rules carried over, and changed ones with old value, new value, and reason;
previous-stage results, recorded separately from behavior;
previous-stage behavioral metrics: decision count, adherence, deviations by category, unclassified count;
the new account state.

It does not include post-transition performance, because none exists yet.

Post-transition comparison, completed later, once the new stage has a block of decisions comparable in size to the last block of the old stage. Compare the two blocks on the same measures:

personal-rule adherence;
planned versus actual initial risk;
decision frequency, per session;
deviations by category.

Define adherence rate once and keep it: aligned plus pre-authorized-exception decisions, divided by all classified eligible decisions, using the eligible-decision definition above. The numerator is a subset of the denominator, so the rate cannot exceed 100%. Report the numerator, denominator, and the number of unclassified decisions next to every rate, as in “35 of 37 classified (94.6%), 1 unclassified”. Unjournaled decisions count as unclassified; they are never dropped or assumed aligned. Adherence measures personal rules only: a pre-authorized exception can make a decision count toward it, but it never changes a provider status. Two blocks are two observations, not an experiment; a small change between them is a reason to look at a specific rule, not proof that the stage change caused it. What changes when moving from evaluation to a funded account covers which rules to re-check at that handoff; this journal is where the answers and the later comparison are stored.

A payout is not automatically a new stage. Depending on the provider, a payout can trigger one or more of three different things, and each needs a different record:

A payout-window reset in the same account. On Topstep’s XFA Consistency path, the consistency calculation resets after a payout request, the new window starts on the next trading day, and trades on the request day do not count toward it.⁵ Close the window ID and open a new one; the account and stage stay the same.
A risk-limit reset in the same account. Topstep states that after the first payout, the XFA Maximum Loss Limit is set to $0 regardless of where it was before.¹ Once the provider’s records show it, add a new account-state version with the new floor. The rule snapshot itself does not need to change.
A new account. In FTMO’s 1-Step program, the page says that when a Reward is withdrawn and a new FTMO Account is provided, the Maximum Loss Limit fully resets.² Record that as a new account entry, linked to the previous one, with its own snapshot reference, rather than assuming it continues the old account the way a Topstep XFA does.

Use the provider’s documented mechanism to decide which of these applies. A payout-window change alone does not start a new stage.

For a failed attempt, close the stage entry with the outcome the provider reports. Then review the attempt’s decisions using the classifications above and record any plan-compatibility finding separately. Prop firm challenge mistakes covers how to diagnose the cause of a failure; the journal supplies the evidence. If the evidence does not decide it, record “unclassified” rather than choosing the most comfortable explanation.

A compact prop firm journal template

STAGE SETUP (once per stage)
- Stage ID / provider / program / variant / account ID
- Size label / actual starting balance / simulated or live (provider's word)
- Stage / attempt ID / start date / end date / stage outcome
- Provider snapshot version: rule ID / type (rule, objective, payout) /
  value / basis / timing / day boundary / consequence / source /
  verified date / effective date (if published) / corrected by
- Correction records (if any): see the correction template above
- Personal rule set ID + version / effective date:
  max planned risk / daily stop / re-entry / cutoff / after-loss /
  pre-authorized exceptions with written conditions

SESSION (before trading)
- Session ID / date / stage ID + attempt ID
- Provider snapshot version + personal rule version in force
- Account state at start + provenance
- Permitted setups / payout window ID (if applicable)

PER DECISION (during the session; one line each)
- Decision ID / session ID / trade ID (n/a for a session-level decision)
- Type (entry, exit, size or stop change, continue past a limit) /
  time / instrument / side / size / price
- Entries: setup meets criteria? / planned risk / actual initial risk
- Account state at decision + provenance
- Reason before outcome (threshold or deadline in it?)

PER TRADE (when it closes)
- Trade ID / all entry and exit decision IDs / realized P&L, net of
  fees (or state gross) / MAE (optional)

REVIEW (after the session)
- Per decision ID: A. adherence (aligned / pre-authorized exception /
  deviation / unclassified) + rule version applied + exception ID if used
- Per rule ID: B. provider status: compliant / breached / unverified / n/a
- C. Objectives: met / not yet met / n/a / unverified
- D. Payout eligibility: eligible / not currently eligible / n/a / unverified
- E. Outcome: per-trade results (above) / account outcome / stage outcome
- Session summary, derived from the lines above: trades, eligible
  decisions, adherence (n, rate, unclassified), realized session P&L =
  sum of net P&L of trades closed in the session / open P&L at session
  end, kept separate / provider-reported balance or equity + provenance
- Why the session ended / plan-compatibility note (if any)

TRANSITION SNAPSHOT (when the stage changes)
- Type / date / old + new provider snapshot versions / rule changes
- Personal rule changes: old / new / reason / effective date
- Previous-stage results + behavior (counts, adherence, unclassified)
- New account state / post-transition comparison: pending

POST-TRANSITION COMPARISON (after a comparable block)
- Old vs new block: adherence (n, rate, unclassified) / planned vs
  actual risk / decisions per session / deviations by category

Complete stage setup once, and add a new snapshot or rule version only when something changes; sessions and decisions refer to those IDs instead of copying the provider rulebook. Complete the session section before trading. During the session, record only the per-decision fields; classification belongs in the review, so logging does not become a second task while trading. Session totals are summaries of the trade and decision lines, never a replacement for them: a session P&L cannot show which trade produced it, and a session adherence rate is only checkable if each eligible decision has its own label. Sum only like with like: net with net, realized with realized. A realized session total you added up yourself is not the provider’s account P&L or equity, and it is not evidence of provider compliance. For trade-level entries that separate the log, setup, execution, and behavior, see trade journal examples.

Common prop firm journal mistakes

Recording the account but not the stage. Trades from an evaluation and a funded account are then reviewed against one set of rules.

Treating a missed objective as a breach. A consistency or profit objective that is not yet met is logged as “broke the rule”, and the trader reviews an aligned decision as a failure.

Overwriting the rule snapshot. The record of what the trader knew at the time is lost, and old trades are reviewed against new rules. Correct a wrong snapshot with a separate correction record instead.

Recording the size label as the balance. Distances and percentages are computed from a number the account never held.

Merging attempts. A reset account and the original account become one history, and the review loses the boundary between two samples.

Marking the account compliant because nothing was reported. No notice is not confirmation. Until the provider’s records confirm it, the status is unverified.

Judging the evaluation by whether it passed. A pass is a stage outcome under one program’s terms. It is not evidence that each decision followed the plan.

Where Costante fits

A prop-firm journal combines two kinds of record. Provider-side records, such as rules, account balances, rule calculations, account status, and payout eligibility, belong to the provider, and the trader reads them from the provider’s own dashboard. Costante does not connect to a prop firm, broker, or exchange, does not import or sync account data, does not model provider programs, stages, or rule versions, does not calculate distance to a provider limit, and does not enforce provider rules, verify compliance, or confirm payout eligibility. Those layers stay in the trader’s own records.

Costante covers the behavioral side: session planning, self-defined Session Guardrails (Re-entry limit, After-loss risk, Session cutoff, Max loss per trade, and Daily loss guard), pre-trade and in-session checks, low-friction logging of trades and behavioral decisions, and structured review that keeps a good outcome separate from a good process. A funded or evaluation trader can keep the stage record and provider snapshot in their own journal and use Costante for the personal-rule side of each decision. Costante does not guarantee an evaluation pass, funded-account results, profitability, or any behavioral outcome.

Frequently asked questions

What is the difference between a prop firm trading journal and a normal trading journal?

A normal trading journal records trades, setups, and outcomes. A prop firm trading journal also records the account stage, a dated and versioned copy of the provider’s rules for that stage, the trader’s personal rules kept separate from the provider’s, and the account state at each decision. It classifies personal adherence, provider rule status, objectives, and payout eligibility separately, and adds a review whenever the account changes stage.

Is exceeding a consistency rule a breach?

Not necessarily; it depends on how the provider defines it. As of September 22, 2026, FTMO states that exceeding the 1-Step Best Day limit is not treated as a rule breach, and Topstep states that exceeding the Trading Combine’s 55% Consistency Target increases the Profit Target. In those cases the journal records “objective not yet met”, not “rule breached”. Check your own program’s documentation.

Should I keep a separate journal for each prop firm account?

Keep a separate account record, stage entry, and attempt ID for each account, even if all of them sit in one journal. That keeps each account’s rules and each attempt’s sample separate while still letting you compare your behavior across accounts. Comparing performance across multiple accounts covers how to make that comparison without letting a consolidated total hide one account’s results.

What should I record when I pass a prop firm evaluation?

Record a transition snapshot on the day of the pass: the old and new provider snapshot versions, which personal rules you kept or changed and why, the evaluation’s behavioral metrics with counts, the result recorded separately, and the new account state, including the actual starting balance. Leave the funded-stage comparison until the funded stage has a comparable block of decisions.

How do I journal a failed prop firm challenge?

Close the stage entry with the outcome the provider reports, such as a loss-limit breach. Then review the attempt’s decisions against the personal rules in force at the time, keeping the provider status separate, and note any plan-compatibility finding on its own. Mark anything the record cannot decide as unclassified. Start the next attempt as a new entry with its own attempt ID.

Sources

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

Topstep Help Center. What is the Maximum Loss Limit? Accessed September 22, 2026; rechecked September 23, 2026. Supports the trailing, end-of-day update, real-time monitoring, unrealized P&L, and liquidation mechanics, the Express Funded Account’s $0 starting balance and buying-power label, and the reset of the XFA Maximum Loss Limit to $0 after the first payout. Provider terms are subject to change; verify current terms directly with Topstep. ↩ ↩² ↩³
FTMO. Trading Objectives. Accessed September 22, 2026; rechecked September 23, 2026. Supports the 1-Step and 2-Step Profit Targets, the 1-Step Best Day Rule and its non-breach treatment, the Maximum Daily Loss and Maximum Loss rules, and the 1-Step Maximum Loss reset when a Reward is withdrawn and a new FTMO Account is provided. Provider terms are subject to change; verify current terms directly with FTMO. ↩ ↩² ↩³
Topstep Help Center. Trading Combine® Parameters. Accessed September 22, 2026. Supports the one-rule, two-objective structure, the trading-day hours, and the statement that Trading Combine profits do not carry over. Provider terms are subject to change; verify current terms directly with Topstep. ↩ ↩²
Topstep Help Center. What is the Responsible Trading Program? Accessed September 23, 2026. Supports the automatic Daily Loss Limit on new Trading Combines for traders in the program, the restriction of those traders to the XFA Consistency path, and the carve-outs for accounts that predate placement. Provider terms are subject to change; verify current terms directly with Topstep. ↩ ↩²
Topstep Help Center. Consistency at Topstep. Accessed September 22, 2026; rechecked September 23, 2026. Supports the Trading Combine 55% Consistency Target, its adjusted Profit Target and 3:10 PM CT lock, and the Express Funded Account Consistency-path 40% objective, minimum trading days, and payout-window reset. Provider terms are subject to change; verify current terms directly with Topstep. ↩ ↩² ↩³
Topstep Help Center. Express Funded Account™ Parameters. Accessed September 22, 2026; rechecked September 23, 2026. Supports the Standard and Consistency payout paths, the choice at activation, and the Consistency-path objectives and reset. Provider terms are subject to change; verify current terms directly with Topstep. ↩ ↩²
Fischhoff, B. (1975). Hindsight ≠ foresight: The effect of outcome knowledge on judgment under uncertainty. Journal of Experimental Psychology: Human Perception and Performance, 1(3), 288–299. ↩
Baron, J., & Hershey, J. C. (1988). Outcome bias in decision evaluation. Journal of Personality and Social Psychology, 54(4), 569–579. ↩