How to Journal ICT / SMC Trades

ICT and Smart Money Concepts trades are more narrative-driven than most strategies — each entry is the conclusion of a multi-step institutional sequence, not a single pattern trigger. Journaling them effectively means documenting the entire sequence: the higher timeframe bias, the draw on liquidity, the sweep, and the displacement — not just entry and exit prices. Traders who track this sequence consistently identify which steps they execute well and which they skip under pressure, producing a concrete roadmap for improvement rather than a list of wins and losses.

Essential Fields to Track

Field	Why It Matters
ICT Model / Concept	Separates expectancy by setup type (Silver Bullet, Power of Three, Judas Swing) so you can identify which models actually produce edge for you
Draw on Liquidity (DOL)	Defines the directional target before entry — without it, you cannot assess whether the trade had institutional logic or was a random level reaction
Key Level Type	Distinguishes order blocks, breaker blocks, FVGs, and mitigation blocks to reveal which level types you read correctly
Liquidity Sweep Confirmed	Records whether a stop run occurred before displacement — the structural prerequisite most ICT traders skip when journaling
Session / Killzone	ICT models are session-specific; this field identifies your strongest and weakest killzones with data rather than feel
Higher Timeframe Bias	Tracks whether your daily or H4 narrative was correct, separating execution errors from narrative errors
Entry Timeframe	Records whether entry came from M1, M5, or M15 displacement, ensuring your setup is replicable and consistent
FVG Present at Entry	Tracks whether a fair value gap refined your entry versus a blind order block touch, enabling direct comparison of both approaches
Displacement Quality	Rates the strength of the move off the level (strong/moderate/weak) — weak displacement is the single most predictive indicator of ICT trade failure
Kill Switch / Invalidation Level	Documents planned versus actual stop placement to measure deviation under pressure

The two most critical fields are the draw on liquidity and the liquidity sweep confirmation. Without the DOL, every losing trade looks like a level failure when it may actually be a narrative failure. Without the sweep log, you cannot tell whether you’re taking textbook ICT entries or jumping in early.

Sample Journal Entry

Date: 2026-08-27 Pair: GBP/USD Session: London Open Killzone (07:15 GMT) Model: Silver Bullet (07:00–08:00 window) HTF Bias: Bullish — daily FVG at 1.2680 supporting price, targeting 1.2818 buyside liquidity Draw on Liquidity: Equal highs at 1.2818 (3-day BSL cluster on H4) Key Level: Bullish Order Block — M15 down-close candle at 1.2704–1.2712 Liquidity Sweep: Yes — M1 wick to 1.2697, sweeping prior London low at 07:11 GMT FVG at Entry: Yes — M1 FVG at 1.2706–1.2710 on displacement candle Entry: 1.2709 (FVG 50% level) Stop: 1.2694 (3 pips below OB origin) — 15-pip risk Target: 1.2818 (full draw — 109-pip reward, 7.3R) Exit: 70% closed at 1.2790 (+81 pips), remainder at 1.2816 (+107 pips). Weighted: +90 pips / +$180 at 0.2 lot Displacement Quality: Strong — 3-candle M1 expansion, average body 78% of total range Emotion: Patient — waited 11 minutes at screen after London open for sweep confirmation Lesson: A 12-pip pullback into the FVG shook out early entries. Full invalidation was 1.2694; the retrace never came close. Trusting the level meant holding through noise.

Review Process

1. Verify the HTF bias first — before evaluating entry quality, confirm whether your daily or H4 narrative was correct. A losing trade with a correct bias is an execution problem. A losing trade with a wrong bias is a narrative problem. These require different fixes.

2. Map the draw on liquidity outcome — did price reach the target liquidity pool? If it fell short, calculate how many pips short and check whether a session close or scheduled news event explains it. Document this as a DOL completion rate per model.

3. Grade each key level (1–3) — score the order block or FVG quality: (1) textbook confluence, (2) acceptable but imperfect, (3) forced or questionable. After 30+ trades, filter your win rate by grade. If grade-3 levels are losing money, stop trading them.

4. Confirm the sweep sequence — review the pre-entry candles and verify the sweep was a sharp run-and-reverse, not a slow drift through the low. Genuine sweeps with displacement within 3 candles produce win rates roughly 20–30% higher than entries taken without a confirmed sweep.

5. Rate displacement quality — count expansion candles and measure average body-to-wick ratio on the entry timeframe. Set a minimum standard (e.g., 3 consecutive candles with bodies above 65% of total range) and flag every trade where you violated it.

6. Weekly killzone comparison — compare your win rate and average R across London open, New York AM, Silver Bullet window, and any other session you trade. Most ICT traders discover that one window accounts for 60% or more of profitable trades. This data justifies cutting screen time outside that window.

7. Monthly model audit — tally expectancy by model name after accumulating at least 30 trades per model. Expectancy below 0.2R per trade after 30+ trades is a signal to pause or retire that model and reallocate focus to higher-performing setups.

Common Mistakes in ICT / SMC Trade Journaling

1. Logging the level type without the timeframe — “order block” is not a complete data point. An M5 order block and an H4 order block have different characteristics, context, and historical performance. Always record both the level type and its originating timeframe, or your level-performance analysis produces misleading results.

2. Omitting the draw on liquidity — this is the most frequent and costly journaling gap. Without the DOL, you cannot determine whether a losing trade failed because of bad execution or because price was not actually targeting the direction you traded. The DOL is the narrative; the entry is just the trigger.

3. Recording emotion only on losing trades — emotional state during patience and conviction (waiting for the sweep, holding through retracement) is equally diagnostic. A journal that only captures emotional data on losses cannot identify the mental patterns that lead to premature entries or early exits on winners.

4. Skipping displacement quality rating on winners — traders assume that if the trade worked, the displacement was fine. Reviewing displacement quality on every trade, including profitable ones, reveals when you got lucky on weak setups and prevents setting unrealistic expectations about future trades with the same entry quality.

5. Treating the ICT model name as a sufficient tag — “Silver Bullet” encompasses dozens of variations: which session, which liquidity was targeted, which level type, which entry timeframe. Tag at least three sub-fields per trade in addition to the model name, or the model-level statistics remain too broad to act on.

How PipJournal Handles ICT / SMC Trades

PipJournal supports the full ICT trade sequence through custom fields that can be added to any trade entry. Traders can create fields for draw on liquidity, key level type, liquidity sweep confirmation, and displacement quality — and these fields become filterable dimensions in the analytics dashboard. Filtering your win rate by “Liquidity Sweep: Yes” versus “No” takes seconds and surfaces one of the highest-leverage insights available to ICT traders.

The tagging system handles model-level categorization. Each trade tagged “Silver Bullet” or “Power of Three” contributes to a running expectancy calculation visible in the performance breakdown, updated after every session. Once a model accumulates 30 trades, the expectancy figure becomes reliable enough to make informed decisions about which setups to prioritize.

PipJournal’s session filter aligns directly with ICT killzone analysis — trades are automatically timestamped and can be filtered by London open, New York AM, Asian range, and custom time windows. For traders using the multi-timeframe journaling approach, this means HTF bias entries and LTF execution entries can be linked and reviewed together, keeping the full ICT trade sequence visible in a single review workflow.