Journal examples · How-to

Trading Journal Examples: Three Decisions Worth Recording

A journal is useful when it records what you knew before the outcome. These examples show how to log a planned trade, a rule-breaking loss, and a correct decision to wait without turning any one result into a performance claim.

TradeStreamAI Editorial Team · Published September 26, 2026 · Editorial and product methodology

Quick answer

A practical trading journal entry records the date, market, setup, direction, planned risk, result in R when a trade was executed, and one specific lesson. A skipped setup can be logged as WAIT with no realized R. TradeStreamAI's free browser journal uses those fields and exports them as CSV.

A practical workflow

  1. Step 1

    Record the plan first

    Write the market, setup, direction, entry condition, invalidation, and planned percentage risk before the outcome is known.

  2. Step 2

    Record execution separately

    After the decision, note whether you traded, waited, moved the stop, changed size, or exited differently than planned.

  3. Step 3

    Calculate R only for trades

    Divide the realized result by the initial money risk. Leave a skipped WAIT decision without a realized R value.

  4. Step 4

    Review repeated conditions

    Group entries by setup and market, then identify recurring process mistakes or confirmations that helped you skip poor setups.

At a glance

Illustrative entryResult fieldUseful lesson
EUR/USD range retest · BUY · 0.5% planned risk+2REntered only after a completed retest candle; check whether this rule holds across a larger sample.
MNQ breakout chase · BUY · 0.5% planned risk−1REntry occurred after price moved beyond the planned level; define a maximum chase distance.
BTC/USD resistance test · WAIT · 0% executedBlankNo candle close beyond resistance; note the condition that would have changed the decision.

Example one: a winning trade

Suppose an EUR/USD range retest was planned with 0.5% account risk and a defined invalidation point. The trader waited for a completed candle, took the trade, and realized +2R. The useful note is not ‘the setup works’; it is that the entry followed the written rule and the initial risk was known.

One positive result does not establish an edge. Over a larger sample, compare similar retests in the same session and market. Track fees and slippage separately if the journal's Result (R) field does not include them.

Example two: a loss with a process error

An MNQ breakout idea had a planned entry, but price moved before the trader acted. The trade was entered anyway and ended at −1R. The result is a loss, but the actionable note is that entry occurred beyond the planned zone. A later review can ask whether chases produce poorer results than on-time entries.

Do not rewrite the original plan after the loss. Keep planned and actual behavior distinct, even if the free journal's compact fields require putting that distinction in the Lesson text.

Example three: WAIT is a decision

A BTC/USD chart touched resistance but did not close beyond it. The trader chose WAIT and logged the condition that would have justified a later review. There is no realized P/L and no R result. Calling this a ‘saved loss’ would require knowing what would have happened in a trade that never occurred.

Skipped setups are valuable because they reveal whether rules are followed under uncertainty. Keep them out of executed-trade win-rate calculations, but include them when reviewing decision quality.

What a compact journal cannot prove

A seven-column journal does not record exact fills, fees, order IDs, or full screenshots. Add those in a spreadsheet if your review requires them, but do not invent missing values from memory. A few examples are teaching aids, not backtested evidence of a profitable strategy.

For a weekly review, filter to one setup, compare planned risk with observed outcomes, and choose one behavior to change. Consistency in naming setups and recording losses matters more than a polished dashboard.

  • Separate plans from hindsight
  • Keep WAIT entries out of realized P/L
  • Record fees when evaluating performance
  • Use enough observations before drawing conclusions

Common questions

Should I journal trades I skipped?

Yes. Log the reason for WAIT and the condition that would have changed your decision, but leave realized R blank.

What is a useful lesson after a losing trade?

Describe an observable behavior, such as entering after the planned price or moving a stop, rather than writing a vague judgment about the trade.

Can I import the TradeStreamAI journal into a spreadsheet?

Yes. Export CSV from the free browser journal, then import it into Excel or Google Sheets. The data does not sync automatically.

Educational decision support. Chart analysis cannot guarantee a result, and all prices, contract values, and execution conditions require independent verification.