How to Journal Smart Money / ICT Trades
ICT journaling means logging order blocks, FVGs, liquidity sweeps, BOS/CHoCH confirmation, and killzone timing for every trade you take.
Start Free TrialNo credit card required
Fields to Track
Order Block Level
The foundation of every ICT entry. Log the exact order block you traded from — including timeframe, type (bullish/bearish), and whether price mitigated it or swept through. Without this, you can't review whether your OB identification is actually accurate.
Fair Value Gap (FVG)
FVGs are your confirmation that institutional displacement occurred. Track whether an FVG was present, its size relative to recent range, and whether price filled it before your entry. Over time, this data shows which FVG types lead to continuation vs reversal.
Liquidity Sweep (Y/N + Level)
ICT entries often require a liquidity sweep before reversal. Log whether a sweep occurred, what level was taken (previous high/low, equal highs/lows, session high/low), and the depth of the sweep. This separates valid setups from premature entries.
BOS / CHoCH Confirmation
Break of structure or change of character confirms your directional bias. Track which timeframe the BOS/CHoCH occurred on, the specific candle that broke structure, and whether you waited for it or anticipated it. Anticipating BOS is one of the most common ICT mistakes.
Session / Killzone
ICT methodology is session-dependent. London and New York killzones produce the highest-probability setups. Log which killzone you traded in and whether the move aligned with typical session behavior. Trading outside killzones is a discipline leak that only your journal will catch.
Premium / Discount Zone
Were you buying in discount or selling in premium? Log the equilibrium level and whether your entry was on the correct side of it. This single field eliminates a huge category of low-probability trades when you review your data.
Displacement Candle
Displacement confirms institutional intent. Record whether a displacement candle preceded your entry, its size relative to average range, and the volume spike if visible. Entries without displacement are lower probability — your journal data will prove this over time.
Institutional Order Flow Bias
Your higher-timeframe directional bias based on order flow. Log whether you were trading with or against the HTF bias, and what evidence supported it (HTF BOS, weekly OB, daily FVG). This field forces you to confirm alignment before entering.
Entry Model Used
ICT has multiple entry models — optimal trade entry, breaker block, mitigation block, FVG entry. Tag which model you used so you can compare win rates and expectancy across models. Most traders discover they perform best with one or two models, not all of them.
Draw on Liquidity (Target)
Every ICT trade should have a defined draw on liquidity — the target where you expect price to reach. Log the specific level (opposing liquidity pool, FVG fill, OB mitigation) and whether price actually reached it. This measures your target selection accuracy.
Sample Journal Entry
Date: 2026-03-05 Pair: GBP/USD Direction: Long Entry: 1.2638 Exit: 1.2679 Pips: +41 Lots: 0.30 Risk: 1.5% Session: London Killzone (07:00-10:00 GMT) Order Block: Bullish OB at 1.2630 (15m TF), unmitigated from previous session FVG: Present between 1.2635-1.2645, price filled 50% before entry Liquidity Sweep: Yes — swept Asian session low at 1.2625 before reversing BOS/CHoCH: CHoCH on 5m at 1.2642, confirmed bullish shift Premium/Discount: Entry in discount (below 1.2660 equilibrium) Displacement: Strong bullish displacement candle at 07:14 GMT, 18 pips body HTF Bias: Bullish — Daily BOS above 1.2580, trading into weekly FVG Entry Model: OTE (Optimal Trade Entry) at 79% fib of displacement leg Draw on Liquidity: Previous day high at 1.2685 Notes: Textbook London reversal. Asian range built liquidity below 1.2625, London swept it and displaced bullish into the 15m OB. Waited for CHoCH confirmation before entry. Took profit at 1.2679 — 6 pips below the draw on liquidity. No re-entry after exit.
Review Process
Validate the order block — pull up the chart and confirm the OB you logged actually existed on the timeframe you claimed. Many traders retroactively identify OBs that weren't visible in real-time. If your OB identification accuracy is below 70%, your pattern recognition needs more screen time.
Check killzone compliance — were you actually inside the London or New York killzone when you entered? Log every trade taken outside killzones separately. If more than 20% of your trades happen outside killzones, you have a discipline problem, not a strategy problem.
Confirm BOS/CHoCH before entry — review whether you waited for structure to break or whether you anticipated it. Anticipation trades should have a separate tag so you can compare their win rate against confirmed entries. The data almost always favors patience.
Evaluate premium/discount accuracy — were you genuinely in discount for longs or premium for shorts? Calculate the equilibrium of the dealing range and check your entry against it. Entries on the wrong side of equilibrium have measurably lower expectancy.
Assess draw on liquidity accuracy — did price reach your target? Track target hit rate separately from trade win rate. If you're winning trades but consistently missing your DOL, your targets are too ambitious or your partials are too early.
Why ICT Traders Need a Journal More Than Anyone
Smart Money Concepts and ICT methodology are among the most detail-heavy approaches in forex trading. You’re not just tracking price — you’re tracking order blocks, fair value gaps, liquidity sweeps, market structure shifts, killzone timing, and institutional order flow. Every trade involves multiple confluences that must align before entry.
That complexity is exactly why most ICT traders plateau. They understand the concepts but can’t tell which ones are actually working in their trading. Without logged evidence, you’re relying on memory and confirmation bias — the two worst tools for evaluating a complex methodology.
Your journal is the only way to know which ICT concepts you’re applying correctly and which ones you’re misidentifying.
The Problem With Generic Journals for ICT
A standard trading journal gives you entry, exit, P&L, and maybe a notes field. That’s fine for a simple breakout strategy. For ICT, it’s useless.
Consider what you lose without ICT-specific tracking:
- You can’t measure your order block identification accuracy over time
- You don’t know if your FVG entries outperform your breaker block entries
- You can’t prove whether London killzone setups actually produce better results than New York for your style
- You have no data on how often you enter before displacement confirms the move
Without these data points, your “review” is just watching replays and feeling good or bad about trades. That’s not analysis — it’s entertainment.
How to Structure Your ICT Journal
Log the Narrative, Not Just the Numbers
Every ICT trade tells a story: liquidity was built, it was swept, displacement confirmed intent, and price delivered to an order block in a discount zone during the London killzone. Your journal should capture that narrative in structured fields, not buried in a free-text notes section.
When each element has its own field, PipJournal can analyze patterns across hundreds of trades. You’ll see that your win rate on OTE entries during London is 62%, but drops to 38% when you trade the same model during Asian session. That’s the kind of insight that changes how you trade — and it’s invisible without structured logging.
Track What You Didn’t Trade
ICT is as much about the trades you avoid as the ones you take. When a setup forms but you don’t enter — whether from hesitation, lack of confirmation, or being away from the screen — log it as a missed trade. Include the same fields: what was the OB, was there a sweep, did displacement occur?
Over time, missed trade data reveals one of two things:
- You’re correctly filtering out low-probability setups (good discipline)
- You’re hesitating on valid setups and leaving money on the table (execution problem)
Your journal is the only way to tell the difference.
Killzone Discipline Is Measurable
One of the most common mistakes ICT traders make is stretching their trading hours. A setup appears at 11:30 GMT — technically outside the London killzone — and you rationalize taking it because “the move is still going.”
Your journal should tag every trade with its killzone status: inside London, inside New York, overlap, or outside killzones. After 50+ trades, calculate your expectancy for each category. The data almost always shows that out-of-killzone trades have lower expectancy, worse risk-reward ratios, and higher emotional stress.
PipJournal tracks session timing automatically, so this analysis takes seconds instead of hours of spreadsheet work.
Premium vs. Discount: The Simplest Filter
ICT’s premium/discount framework is elegant: buy in discount, sell in premium. But under live market pressure, traders routinely violate this rule. They chase entries in no-man’s-land — near equilibrium where the edge disappears.
Log the equilibrium level for every dealing range you trade. Tag your entries as premium, discount, or equilibrium. After a month of data, compare your P&L across these three zones. If your equilibrium trades are breakeven or negative, you’ve found the simplest filter to improve your results: stop taking them.
Your Weekly ICT Review
Set aside 30 minutes every weekend to review your ICT journal entries. Focus on these questions:
- What percentage of my trades were inside killzones? Target: 80%+
- How accurate was my order block identification? If OBs are getting mitigated through instead of holding, your identification criteria need tightening.
- Am I entering before or after displacement? Pre-displacement entries should be flagged and their win rate compared against confirmed entries.
- Are my trades aligned with HTF bias? Counter-trend trades on the lower timeframe should be a small minority.
- Which entry model is performing best? Let the data decide which models deserve your capital.
PipJournal’s AI co-pilot runs this analysis automatically and surfaces patterns you might miss — like a gradual decline in killzone compliance or an entry model that’s underperforming over the last 30 trades.
Stop Guessing, Start Measuring
ICT methodology gives you a framework. Your journal gives you the feedback loop. Without data, you’re just watching price action and hoping your pattern recognition improves. With structured ICT journaling, every trade becomes a data point that sharpens your execution.
The traders who master ICT aren’t the ones who watch the most YouTube content. They’re the ones who log every order block, every sweep, every killzone entry — and let the data tell them what’s working.
PipJournal is built to handle that level of detail. Start journaling your ICT trades today.
Common Journaling Mistakes
Treating every consolidation candle as an order block — not every cluster of candles before a move is an institutional OB. If you're identifying 10+ order blocks per session, you're seeing patterns that aren't there. Your journal will reveal this through low OB hit rates.
Entering before displacement confirms the move — ICT is a confirmation-based methodology. Entering at the first touch of a level without waiting for displacement and BOS is just support/resistance trading with fancier labels. Track how many trades you enter before vs after displacement.
Trading outside killzones because the setup 'looked good' — killzones exist because institutional order flow concentrates during specific hours. A perfect OB at 2am GMT is not the same setup as the same OB at 8am GMT. Your journal data will prove this if you track session timing honestly.
Ignoring higher-timeframe bias — taking a bearish 5-minute setup inside a bullish daily order block is fighting the institutional flow. Log HTF bias for every trade and compare win rates for aligned vs misaligned trades. The difference will be significant.
Not logging failed setups — the setups that didn't trigger are as valuable as the ones that did. If price swept liquidity, displaced, but you didn't enter because of hesitation, log it as a missed trade. This data reveals whether your issue is analysis or execution.
Frequently Asked Questions
Do I need a special journal for ICT trading?
You need a journal that lets you track ICT-specific fields — order blocks, FVGs, liquidity sweeps, killzone timing. Generic journals that only track entry, exit, and P&L miss the data that actually matters for improving your ICT execution. PipJournal lets you add custom fields for every concept in your methodology.
How many fields should I track per ICT trade?
Eight to ten fields minimum. Order block, FVG, liquidity sweep, BOS/CHoCH, session, premium/discount, displacement, and your entry model. It sounds like a lot, but these fields take 2-3 minutes to fill in and generate the data you need to actually improve. Skipping fields means skipping insights.
Should I journal paper trades when learning ICT?
Absolutely. Journaling paper trades builds the habit and gives you data to review before you risk real capital. Mark them as paper trades in your journal so they don't mix with live performance metrics. The review process is identical — you're training pattern recognition either way.
How does PipJournal help ICT traders specifically?
PipJournal lets you create custom fields for every ICT concept — order blocks, FVGs, killzones, BOS/CHoCH. It tracks your performance by session, by entry model, and by setup type. The AI co-pilot identifies patterns in your data like killzone compliance drift or declining OB accuracy that you might not notice manually.
What makes PipJournal different from other trading journals?
PipJournal is the only trading journal built exclusively for forex traders, featuring an AI behavioral co-pilot, session-based analytics, and $179 lifetime pricing with no recurring fees.
Start Journaling Your Trades
Stop guessing, start tracking. PipJournal makes it easy to journal every trade and find your edge.
Start Free TrialNo credit card required