S
ICT FLOW
HomeFoundationsCoursesMentorship
Courses›Trade Review & Journal Process
Advanced📖 24 min read🏷 Process

TRADE REVIEW & JOURNAL PROCESS

SHARE FREE:

Turn Completed Trades Into Evidence, Not Emotion

ICT Flow EditorialIndependent educational resource

This lesson explains concepts commonly taught in ICT/SMC trading education and presents them as frameworks to study and test. Chart patterns cannot independently prove institutional intent, future price delivery, or profitability. Examples and rules are educational, not trading advice.

Read our editorial standards →

A trading journal is useful only when it changes how you make decisions. The objective is not to write a diary after every loss; it is to collect consistent information so you can discover which conditions help your model and which conditions hurt it. This module turns the journal into a research tool.

Trade Review & Journal Process  --  ICT concept diagram

A structured review process converts individual trades into repeatable evidence about your model

// Lesson Content
Before entering, record the market context while your decision is still unbiased. Write the instrument, date, session, direction, higher-timeframe context, setup name, entry reason, invalidation level, target, planned risk in R, and the condition that would make you cancel the trade. Do not write a perfect story after the trade. Record the information that was actually available at the time. This preserves the difference between a good decision and a lucky outcome.
📌 The pre-trade record is your snapshot of what you actually knew. It is more valuable than a polished explanation written after the result.
Use the same screenshot structure every time so trades can be compared later. A useful minimum set is: higher-timeframe context, execution timeframe, entry/stop/target markings, and the key liquidity or imbalance level you used. Keep the chart clean. Do not add indicators after the fact. Your future review should answer three questions quickly: what did I see, what did I do, and what invalidated the idea?
📌 Consistent screenshots make patterns visible. Inconsistent screenshots make review subjective.
Track every outcome in R rather than only in dollars. A +2R trade and a +$200 trade are difficult to compare when account sizes change; R normalizes the result. Also track maximum adverse excursion (MAE) and maximum favorable excursion (MFE) when your platform or manual review allows it. MAE shows how far a trade moved against you before resolving. MFE shows how much unrealized profit was available. Across a meaningful sample, these measures can reveal whether stops are too tight, targets are unrealistic, or management rules are giving back too much. These are descriptive statistics, not guarantees. Small samples can produce misleading patterns.
📌 Measure the path, not just the final result. R, MAE and MFE show how the trade behaved between entry and exit.
Create a small controlled list of tags instead of writing a different description every time. Example tags: setup, session, direction, HTF alignment, entry quality, management error, rule violation, news exposure, and execution error. Separate model failure from process failure. If the setup met your rules and still lost, that is different from entering early, moving the stop, or trading outside your session. You need that distinction before changing the strategy itself.
📌 Never redesign a model because of one loss. First classify the loss: valid loss, execution error, rule violation, or data-quality problem.
Once per week, review the whole sample rather than the most emotional trade. Calculate total R, win rate, average winner, average loser, largest losing streak, rule-violation count, and performance by setup or session when you have enough observations. Then inspect representative trades: one clean winner, one clean loser, one avoidable loss, and one trade you missed. The goal is not a motivational speech. The goal is to identify one repeatable behavior to preserve and one behavior to remove.
📌 Your weekly review should end with one process rule to reinforce and one process rule to eliminate.
Make changes slowly. If a review shows that losses cluster around a specific session, news window or entry condition, test that hypothesis on historical data before changing the live rules. Use a simple experiment: define the hypothesis, select the historical sample, apply the same rule consistently, compare the old and revised results, and only then decide whether the change deserves a forward test. This prevents the common cycle of losing money, changing the strategy, winning once, changing it again, and never knowing what actually worked.
📌 A journal should create hypotheses. Backtesting and forward testing should decide whether those hypotheses deserve to become rules.
// Test Your Understanding
// KNOWLEDGE CHECK

1. Why record the setup before entry?

2. What does R normalize?

3. What should a weekly review produce?

← Previous
Advanced Risk Management & Position Sizing
Next →
Macro, News & Execution Risk
// What to study next
Continue your ICT journey
Next: Macro, News & Execution Risk →All Modules
ICT Flow -- Educational content only. Not financial advice.