Part of The Trading Journal System series. This builds on the 8 fields worth tracking — you need the data before you can review it.
A week of good notes that nobody reads
Here’s a familiar failure mode: a trader diligently fills in their journal every day for a week — setup, size, plan adherence, the works. Then Monday morning arrives and none of it gets looked at. The notes exist. They just don’t do anything, because nobody ever built in a moment to actually read them back.
A journal that isn’t reviewed is just a diary. The review is where the actual improvement happens — not in the logging, in the looking back. And it doesn’t need to be a two-hour deep dive. It needs to be short enough that you’ll actually do it every single week, which is the same design principle behind keeping the daily journal to four fields instead of forty.
Why Sunday, specifically
Sunday works for three practical reasons. Markets are closed, so there’s no live position pulling your attention mid-review. You have enough distance from Friday’s trades that Monday’s win or Wednesday’s loss doesn’t feel as emotionally loaded as it did in the moment. And it puts the review right before the week it’s meant to influence — Monday’s plan gets built from Sunday’s findings while they’re still fresh.
If Sunday doesn’t fit your schedule, any fixed day works. The point isn’t the specific day — it’s that it’s the same day every week, so the review becomes a routine instead of something you do only when the week went badly.
The 20-minute structure
Minutes 0–5: Pull the numbers, not the memories
Open your journal and pull the week’s totals: number of trades, win rate, average R-multiple, and plan adherence rate (how many trades followed your written criteria versus how many didn’t). Write these four numbers down before you look at anything else. This keeps the review anchored to data instead of whichever trade is loudest in your memory — usually the biggest win or the most painful loss, neither of which represents the average week.
Minutes 5–12: Find the pattern, not the trade
Scan the week’s setup tags. Which setup showed up most? Which one actually made money once you separate it out from the rest? This is where tagging pays off — a week of trades filed under one tag is a small sample of your edge, not just seven unrelated stories.
Look specifically for repetition: did the same mistake show up more than once? One instance of moving a stop is a bad day. Two instances in the same week is a pattern that needs a rule, not just a note.
Minutes 12–18: Pick exactly one adjustment
This is the step most reviews skip, and it’s the one that actually matters. Don’t leave the review with a list of five things to fix — pick one. The trader who tries to fix everything at once usually fixes nothing, because there’s no way to isolate which change actually worked next week.
Frame the adjustment as a rule, not a vague intention. Not “be more patient” — instead, “no entries in the first five minutes after the open.” Not “manage risk better” — instead, “hard stop at $200 daily loss, no exceptions, close the platform.” A rule is testable. A vague intention isn’t.
Minutes 18–20: Write the plan for the week ahead
One sentence: what you’re changing, and how you’ll know if it worked. Something like: “This week, no moving stops once placed. I’ll know it worked if my planned-vs-actual stop field matches on every trade.”
What a real week looks like
Say the week’s numbers show 12 trades, a 50% win rate, but a plan adherence rate of only 60%. Digging into the tags, the “pullback-to-VWAP” setup made money on every instance it was traded according to plan — but three of the losing trades were the same setup traded outside the plan, entered a few ticks early. The adjustment for next week isn’t “trade less” or “find a new setup.” It’s specific: wait for full confirmation on VWAP pullbacks before entering, no early fills. That’s one testable rule, built directly from one week of honest data.
The performance review parallel
Every serious athlete’s coach runs some version of this same weekly loop — review last week’s training log, spot one pattern (fatigue on the third set, a form breakdown late in a run), and adjust exactly one variable for the week ahead. Nobody rebuilds the entire training program every Sunday. They make one change, test it for a week, and see what the data says next Sunday.
Takeaway: Twenty minutes, four numbers, one pattern, one rule. A review that’s simple enough to survive a busy week will teach you more over a year than a two-hour audit you only do twice.
Next up: Tagging Your Setups: How to Find Your Real Edge Buried in Your Own Data — the system that makes this review possible in the first place.
