A trading journal is a structured record of the decisions behind your trades, not just a list of profits and losses. A useful journal preserves what you planned, what you actually did, the market context, the result, and whether you followed your rules. Its purpose is to create evidence you can review later instead of relying on memory.

The journal should be simple enough that you will actually maintain it. There is no universal number of fields, required review frequency, compliance percentage, or minimum trade count that makes a journal valid. Those choices should follow the questions you are trying to answer and the strategy you are using.

Key takeaways

Record plan and execution separately: intended entry, stop, target, size, and setup should not be overwritten after the result is known.
Track both objective data and decision context. Broker history can show fills; a journal should explain why the trade qualified and whether the plan was followed.
Do not judge a strategy from a tiny or selectively logged sample. A journal is only as useful as the completeness and consistency of its records.
Use the journal to generate questions. Use a separate Trading Performance Metrics guide when you need deeper expectancy, profit factor, drawdown, Sharpe/Sortino, MAE/MFE, or sample-quality analysis.
Chart replay can help you practice recording decisions without risking capital, but replay does not reproduce live fills, liquidity, latency, fees, or the pressure of real money.

What is the difference between a trade log and a trading journal?

The terms are often used interchangeably, but the distinction is useful.

Record	Main purpose	Typical contents
Broker statement / execution history	Confirm what was executed	Symbol, quantity, fill price, time, fees where reported
Trade log	Organize completed trades	Entry, exit, size, result, setup label
Trading journal	Preserve the decision process	Plan, context, trigger, invalidation, execution notes, rule adherence, screenshots, lesson
Backtesting record	Evaluate a defined strategy on historical data	Rules, test sample, costs, assumptions, results

CME Group's trading-plan education recommends keeping a trade log with entry and exit points, targets, time of trade, market observations, and comments explaining why the trade was made. It also emphasizes reviewing both successful and unsuccessful trades rather than looking only at profit and loss.

The practical difference is this: a trade log tells you what happened; a journal helps you inspect why you made the decision.

What should you record in a trading journal?

Start with fields that answer a real review question. You do not need to copy a 30-column template simply because another trader uses one.

A useful baseline is:

Field	What to record	Review question it supports
Date and time	Entry and exit time	Was this trade taken in the intended session or window?
Market / symbol	Instrument traded	Are you mixing results from very different markets?
Strategy version	The exact ruleset or playbook version	Did the rules change during the sample?
Setup	The named setup that qualified	Was this actually a planned setup?
Context	Trend/range state, event condition, higher-timeframe context if relevant	Did the trade occur in the conditions the strategy allows?
Planned entry	Price or trigger planned before execution	Did you enter where intended or chase?
Initial invalidation / stop	The original level that would invalidate the idea	Did risk change after entry?
Planned target or exit rule	The intended exit logic	Was the exit decided before or after seeing P&L?
Planned size	Shares, contracts, lots, or other unit	Was position size consistent with the plan?
Actual fills	Entry/exit prices and quantity	How closely did execution match the plan?
Costs	Commission, spread, fees, funding, borrowing, or other relevant costs where known	Are gross results hiding meaningful trading costs?
Result	Net result and/or a consistent risk-normalized unit	What happened financially?
Rule adherence	Pass/fail or a defined grade	Was the process followed independently of outcome?
Screenshot / chart state	Before/after image or replay reference	Can you reconstruct the decision later?
Short lesson	One factual observation or next question	What deserves follow-up rather than an immediate rule change?

You can add emotion or attention-state tags when they help diagnose a repeated problem, but avoid turning the journal into an essay that is impossible to compare across trades.

If you are completely new to journaling and want a smaller first version, use the beginner trading journal guide. If the problem is maintaining the habit rather than choosing fields, use How to Keep a Trading Journal.

Record the plan before the outcome changes your memory

One of the biggest weaknesses in post-trade journaling is hindsight.

After a winning trade, an entry can look more obvious than it did in real time. After a losing trade, a trader may remember warnings that were not actually part of the original decision. If the original plan is rewritten after the result, the journal stops being reliable evidence.

Before or at entry, preserve the parts of the decision that matter:

why the setup qualified;
the intended entry trigger;
the original invalidation level;
planned position size;
the exit rule or target logic;
any event or execution condition that would cancel the trade.

After the trade, add what actually happened in separate fields rather than replacing the original plan.

Schwab's trade-plan guidance makes a similar distinction: traders can compare completed trades with the original plan, then ask what worked, what did not, and what should be changed next time. That comparison is much more useful when the original plan still exists.

Separate decision quality from P&L

A profitable trade is not automatically a good decision, and a losing trade is not automatically a bad decision.

For example:

A trade can follow every written rule and still lose.
A trader can ignore position-size rules, chase an entry, and still profit because price happens to continue.

If the journal rewards only profit, lucky rule-breaking can appear to be a good habit.

Use two separate columns or grades:

Outcome: what happened financially.
Process: whether the trade followed the defined setup, risk, and execution rules.

The process grade should be based on rules written before the outcome was known. Do not invent an arbitrary universal target such as “80% compliance means the strategy is valid.” A useful compliance threshold, if you use one, should be tied to your own process and the question you are testing.

How should you review a trading journal?

There is no universal requirement to review daily, weekly, or monthly. The right cadence depends on trade frequency and the purpose of the review.

A trader taking several intraday trades may need frequent data-quality checks. A swing trader taking a handful of positions per month may learn little from a weekly performance summary because the sample is too small.

A practical review loop has four stages:

1. Reconcile the record

Check whether all relevant trades are present and whether basic data is correct. Missing losers, skipped trades, or inconsistent labels can distort later conclusions.

2. Review rule deviations

Look for differences between planned and actual:

entered before the trigger;
chased after the original entry area expired;
changed size;
moved the invalidation level;
exited using a rule that was not part of the original plan;
took a trade when a stated no-trade condition was present.

3. Group comparable trades

Compare like with like. Setup A on a one-minute chart should not automatically be pooled with Setup B on a daily chart just because both were profitable.

Useful segmentation can include:

setup;
strategy version;
market;
session;
direction;
volatility or regime label, if defined consistently;
rule-compliant vs rule-violating trades.

4. Create one testable question

Avoid changing several rules after one difficult week. A journal should help you form a question such as:

Are late entries materially worse than planned entries for this setup?
Does this setup behave differently during scheduled event windows?
Are most oversized losses caused by position-size errors or by changed stops?

Then define what evidence would answer the question before changing the strategy.

For a dedicated weekly/monthly/quarterly aggregation process, use the Trading Journal Review System. For one completed trade, use the Post-Trade Review checklist.

Where performance metrics belong

A journal stores the raw evidence. Performance metrics summarize that evidence.

These are related jobs, but they should not be confused.

Your journal may contain fields needed to calculate:

win rate;
average win and average loss;
realized R;
expectancy;
profit factor;
drawdown;
losing streaks;
duration;
MAE/MFE when the required path data exists;
rule-compliance or execution-error rates.

This page does not assign universal “good” thresholds to those metrics. A metric only makes sense with clear definitions, costs, sample context, and a stable strategy version.

Use Trading Performance Metrics for formulas, assumptions, interpretation, drawdown context, Sharpe/Sortino limitations, MAE/MFE, segmentation, and sample-quality controls.

Should you log emotions?

Emotion fields can be useful when they are recorded consistently and tied to a specific decision problem.

Instead of free-text notes such as “felt bad,” use stable categories only when they answer a question:

FOMO / chase pressure;
hesitation after a valid trigger;
frustration after a loss;
boredom / activity seeking;
overconfidence after a win;
distraction or fatigue.

Do not treat an emotion tag as proof that the emotion caused the result. The tag is an observation that may help you identify a pattern worth investigating.

If your issue is specifically missed-move chasing, use the FOMO trading guide. If you already have clear rules but repeatedly fail to follow them, the Execution Gap guide owns that problem.

How chart replay can fit into a journal

Historical replay can help you practice the recording process without risking capital.

One simple workflow is:

Load a historical chart without jumping ahead to the outcome.
State the setup, context, trigger, invalidation, and planned action before revealing future bars.
Advance the chart.
Record the simulated decision separately from what price eventually did.
Review whether the decision followed the rules you defined.

ChartMini can support the chart-replay part of this exercise. It is an educational replay tool, not a broker. Replay cannot reproduce live order queues, real slippage, liquidity changes, latency, broker-specific routing, or the emotional consequences of risking real money.

If you want a journal specifically for simulated/replay decisions, use How to Log Simulated Trades During Replay.

Common trading-journal mistakes

Recording only memorable trades

If you log only unusually large winners and painful losses, the journal is selected after the outcome. That makes setup and behavior comparisons unreliable.

Changing labels halfway through the sample

If “breakout” means one thing in January and another in March, grouping both under the same tag creates a misleading comparison. Version strategy definitions when they change.

Using the journal as a strategy oracle

A journal can expose patterns and questions, but it does not prove causation. “My last five afternoon trades lost” is not enough to establish that afternoons are inherently bad for the strategy.

Treating every review as a reason to change rules

Repeatedly modifying rules can make it impossible to determine what produced the result. Keep changes versioned and deliberate.

Ignoring costs and actual fills

Gross chart outcomes can look better than executed results. Where relevant and available, preserve commissions, spread, financing, borrowing costs, and actual fills separately from ideal chart prices.

Making the journal too complex to maintain

Only collect fields you know how to use. A simple complete journal is generally more analyzable than an elaborate journal with large gaps.

A practical minimum journal template

If you want to start without building a large spreadsheet, use this structure:

Field	Entry
Date / market	___
Strategy version / setup	___
Context	___
Planned trigger	___
Planned invalidation	___
Planned size	___
Planned exit rule	___
Actual entry / exit	___
Costs if known	___
Result	___
Rules followed?	Yes / No / Defined grade
Screenshot or chart reference	___
One factual lesson or question	___

Add fields only when they support a decision you intend to review.

Common questions

What is the most important thing to record in a trading journal?

There is no single universal field, but the most useful records usually preserve both the original plan and the actual execution. Without both, it is difficult to distinguish a strategy problem from an execution problem.

How many trades do I need before reviewing my journal?

You can review data quality and rule adherence immediately, but there is no universal trade count that makes a strategy conclusion reliable. The amount of evidence needed depends on the strategy, trade frequency, market conditions, variability, costs, and the question being tested. Avoid strong conclusions from a small or selectively chosen sample.

How often should I review my trading journal?

Use a cadence that matches your trading frequency and purpose. Frequent traders may check entries often for completeness; lower-frequency traders may need longer before aggregate statistics become meaningful. The Trading Journal Review System covers periodic aggregation in more detail.

Should I track win rate and expectancy in the journal?

The journal should preserve the raw fields needed to calculate them. Detailed formulas, interpretation, sample quality, and other aggregate statistics belong in the Trading Performance Metrics guide.

Is a trading journal the same as backtesting?

No. A journal records decisions and execution from live, paper, or replay practice. Backtesting applies a defined strategy to historical data under stated assumptions. Keep the records separate so simulated, historical, and live evidence are not mixed.

Sources and limitations

CME Group — Keep a Trade Log: examples of trade-log fields and post-session review.
Charles Schwab — Elements of a Smart Trade Plan: comparing completed trades with the original plan and evaluating what worked and what did not.
CME Group — Building a Trade Plan: the relationship between a trading plan, strategy, risk management, and trader log.

A trading journal can improve the quality of your records and make review more systematic. It cannot guarantee profitability, prove a strategy from a small sample, or remove execution and market risk.

Trading Journal Guide: What to Record and How to Review It