Craft
How to journal a trade so the numbers can talk
Traders abandon journals because they try to write a memoir per fill. The desk does not need a memoir. It needs a row that can be summed, filtered, and argued with. Everything else is optional color.
The minimum row
- When it opened, and the session that implies (Asia, London, NY).
- Symbol and side. Without these, “I trade gold” is an anecdote.
- Initial risk — the stop you actually used, not the one in the playbook PDF.
- Net P&L after costs. Gross vanity is how people keep a strategy that does not pay.
- One mistake tag or “in plan.” Not five. One.
That row is enough to compute win rate, payoff, R, drawdown, and the hour-of-day bucket. An AI coach that reads your history instead of a generic prompt needs exactly this. It cannot infer a stop you never wrote down.
Import, then tag
If you are on MT5, do not re-type the fills. Import the HTML statement, land it on the right account, then add the human layer: plan, grade, note. The file knows the money. Only you know whether the stop was real.
Same-day or it did not happen
A tag added three days later is a story about the person you wish you were. Journal before the next session, even if the note is one word: late, news, size.
What to ignore
- Long recaps of macro that you already read in the briefing. Link the session, don’t paste the Fed.
- Tag soup. If every trade has six labels, none of them will have a sample size.
- Moving losers into “demo” after the fact. The journal should be harder to lie to than Twitter.
Do this for twenty sessions. Then look at the broke-plan bucket and the hour bucket. That is the whole product: not a prettier equity curve — a smaller set of things to stop doing.
Key takeaways
- Same-day notes beat Sunday essays. Tag the mistake while you still hate it.
- R-multiple and initial risk matter more than a screenshot of the winner.
- Session and symbol buckets are how an AI coach finds hours that actually pay.
- Import the broker file, then add the human fields the file will never have.
Frequently asked questions
Do I need a screenshot for every trade?
No. Screenshots help for the two or three tickets you will study. The fields that feed analytics are time, symbol, side, risk, P&L, and the mistake tag.
What if I scalp and have 40 tickets a day?
Import first. Then tag only the breaks. In-plan scratches can stay quiet. The leak is the story.