1. Home
  2. Research
  3. Trader lessons
  4. A trading journal that actually helps

A trading journal that actually helps

What to record for every trade, how to measure it in R after costs, and a weekly review that tells you whether you have an edge or a lucky run.

Free tutorial 8 of 10 · Beginner · 5 min read · By Theoneste NZAKIZWANIMANA

Why most journals do not help

Many journals record feelings and screenshots but not the numbers that decide whether a strategy works. Others are filled in after the trade, when memory has already edited the story. A useful journal is written before the outcome, records every trade including the ones you skipped, and measures everything in R after costs.

Your journal is also the only evidence you will ever have for a discretionary edge. Nobody can backtest your judgement; only an honest record can test it.

Fields to record for every trade

FieldWhenWhy
Date, time, market, timeframeBefore entryTo find patterns by session and market
Setup name and reason (one line)Before entryTo compare setups, not stories
Screenshot with entry, stop and target markedBefore entrySo the plan cannot be edited afterwards
Entry, stop, target, position sizeAt entryTo compute 1R and planned risk-reward
1R in moneyAt entryTo convert every result into R
Spread at entry, commission, swapAt entry and exitCosts decide most results
Exit price, time and reasonAt exitStop, target, time or manual
Result in money and in R, after costsAt exitThe number that matters
Rule followed? (yes / no, what changed)At exitSeparates the strategy from mistakes
Setups seen but not taken, and whySame dayYour filter must beat your skipped trades

Worked example: five trades in R

1R = $100 on every trade; results after spread and commission

Trade 1: target hit, +$180 = +1.80R

Trade 2: stopped, -$100 = -1.00R

Trade 3: stopped with slippage, -$105 = -1.05R

Trade 4: target hit, +$210 = +2.10R

Trade 5: stopped, -$100 = -1.00R

Total = +0.85R; average = +0.85 / 5 = +0.17R per trade

Standard deviation of the five results = about 1.63R

t = 0.17 / (1.63 / square root of 5) = about 0.23

Conclusion: a good week, and statistically indistinguishable from luck

This is the most important habit a journal teaches: a small sample tells you almost nothing. If results vary by about 1R per trade, an average of about +0.14R needs roughly 200 trades to reach t 2.

The weekly review

  1. Update the running totals: number of trades, total R, average R per trade after costs.
  2. Split the average by setup, market and session. Do not act on splits with only a handful of trades.
  3. Check costs: total spread, commission and swap in R this week. Are they growing as a share of your results?
  4. Compare taken trades with skipped setups. If the skipped ones did as well, your selection added nothing.
  5. Review rule breaks: how much R did trades where you broke the plan add or cost?
  6. Write one sentence: what you will keep doing and what you will stop. Change nothing about the strategy itself until its planned test length is complete.

Keep the review short and mechanical. Its purpose is to keep the numbers honest and the test intact, not to redesign the strategy every Friday. Changes belong at the end of the planned test, decided on the full record, and logged with the date so you can count them later.

Make the journal a test, not a diary

  • Decide in advance how many trades the strategy gets before you judge it, and what average R would count as success.
  • Every few hundred trades, run a coin-flip test on your entries (see the luck test tutorial).
  • Keep a separate log of every strategy or setting change, with the date. That count is the size of your search, and it tells you how high your bar must be.
  • Never edit a past entry. Add a correction line instead, dated.

Common journal mistakes

  • Recording pips or dollars instead of R. Different stop sizes make pips incomparable; R is not.
  • Leaving out costs. Record the spread at entry and any commission and swap; in our tests they decided most results.
  • Writing after the outcome. Memory rewrites the reason for the trade once you know how it ended.
  • Only recording trades taken. Without skipped setups you cannot tell whether your filter helps.
  • Changing the strategy weekly. Each change starts a new test; a log of changes is the count of your tries.
  • Judging on a handful of trades. Our five-trade example had a t of about 0.23.

A simple spreadsheet with one row per trade and the fields above is enough. Add three summary cells (number of trades, total R, average R) and update them every week. The habit matters far more than the tool.

Limits

Journals also suffer from selection: traders who stop writing after a bad week, or start after a good one, make their own records look better than their trading. Record every trade, every week.

Key takeaways

  • Record the plan before the outcome, and every trade including skipped setups.
  • Convert every result into R after spread, commission and swap.
  • Five good trades (t about 0.23 in our example) prove nothing; plan for hundreds.
  • Review weekly, but change the strategy only at the end of its planned test.

Education only, not investment advice. Results quoted from TradeLab research are historical simulations; trading can lose more than you expect.

Check a strategy before you risk money on it

Send us your bot or strategy and get an independent report that uses your broker's costs.

What to send us

  • The bot files: an MT5 expert advisor, Python code or written rules
  • The markets and timeframes it trades
  • Your broker, so the test uses its spreads and financing
Email your bot