ICT (Inner Circle Trader) concepts have transformed how a generation of traders reads the forex market. Order blocks, fair value gaps, liquidity sweeps, killzones, displacement — these aren’t just fancy names for price action. They’re a framework for understanding institutional order flow and positioning yourself on the right side of it.
But here’s the problem most ICT traders face: they study the concepts, practice them on charts, and take trades based on them — without ever measuring which concepts actually work in their hands. They know the theory but don’t have data on their execution.
An ICT-specific trading journal fixes this. By tracking the right fields, you turn vague pattern recognition into measurable, optimizable data. After 50-100 trades with proper logging, you’ll know exactly which ICT concepts produce results for you and which ones are costing you money.
Why Generic Journals Don’t Work for ICT Trading
A standard trading journal tracks the basics: pair, direction, entry, exit, stop loss, take profit, P&L. These are necessary but insufficient for ICT traders.
When your journal tells you that your win rate is 52% and your average R:R is 1.5:1, that’s useful information — but it doesn’t tell you anything about your ICT execution. It doesn’t reveal whether your order block entries outperform your fair value gap entries, whether you’re more profitable in London killzone or New York, or whether higher timeframe confluence actually improves your results.
ICT trading is a multi-layered approach. Each trade involves at least 3-4 concept layers: the market structure context, the specific entry model, the killzone, and the liquidity narrative. Without tracking each layer, you can’t isolate which variables are driving your performance — and you can’t improve what you can’t measure.
ICT-Specific Fields to Track
Beyond the standard trade data (which you should still capture — pair, direction, entry, exit, risk, outcome), here are the ICT-specific fields that make your journal analytically powerful.
1. Entry model
Tag every trade with the primary ICT concept used for entry:
- OB — Order block (bullish or bearish)
- FVG — Fair value gap (entry at the gap fill)
- BB — Breaker block
- MB — Mitigation block
- OTE — Optimal trade entry (Fibonacci retracement zone)
- LS — Liquidity sweep (entering after the sweep)
After 50 trades, filter by entry model and compare win rates, average R:R, and expectancy across concepts. You might discover that your order block entries have a 60% win rate while your breaker block entries sit at 38%. That single insight — stop taking breaker block trades, or study them further — can meaningfully shift your equity curve.
2. Market structure context
Every ICT entry should occur within a defined market structure. Tag the context:
- Bullish BOS — Break of structure to the upside (looking for longs)
- Bearish BOS — Break of structure to the downside (looking for shorts)
- Bullish CHoCH — Change of character suggesting reversal to upside
- Bearish CHoCH — Change of character suggesting reversal to downside
- Range — No clear structure break (consolidation)
This field reveals whether you’re better at trading with established structure (BOS entries) or at catching reversals (CHoCH entries). Most ICT traders are significantly better at one than the other — the journal tells you which.
3. Killzone
ICT’s killzone framework divides the trading day into specific windows where institutional activity concentrates. Tag every trade with the killzone:
- Asian — 8:00 PM - 12:00 AM EST
- London — 2:00 AM - 5:00 AM EST
- New York AM — 7:00 AM - 10:00 AM EST
- New York PM — 1:30 PM - 4:00 PM EST
- Off-killzone — Any time outside these windows
PipJournal’s session analysis feature aligns naturally with this framework, showing your performance during each killzone automatically. Over time, you’ll identify which killzones produce your highest win rate and expectancy — and which ones you should skip.
4. Liquidity target
Before entering an ICT trade, you should have a liquidity target — the pool of stop losses or pending orders that price is expected to sweep or target. Log what liquidity you identified:
- Buy-side liquidity — Equal highs, swing high, previous day high
- Sell-side liquidity — Equal lows, swing low, previous day low
- Session liquidity — Asian high/low, London high/low
- None identified — No clear liquidity target
Trades with clearly identified liquidity targets almost always outperform trades without them. Your journal data will quantify exactly how much this variable matters in your trading.
5. Displacement presence
Displacement — a strong, fast move in one direction that indicates institutional commitment — is a key confirmation in many ICT entry models. Did you see displacement before entry?
- Yes, strong displacement — Clear, impulsive move with large-bodied candles
- Yes, moderate displacement — Movement present but not as convincing
- No displacement — Entered without displacement confirmation
This binary tag, tracked over 50+ trades, answers a critical question: does waiting for displacement improve your results? If yes, how much? That data informs whether you should be more patient with entries.
6. Higher timeframe alignment
ICT methodology emphasizes the higher timeframe narrative. Was your entry aligned with the HTF direction?
- Aligned — Entry direction matches the daily/weekly bias
- Counter-trend — Entry opposes the HTF direction
- No clear HTF bias — Higher timeframe is indecisive
Most ICT traders assume HTF alignment improves results. Your journal data will confirm or deny this assumption with your actual trading data — not theory.
7. Time of day (specific)
Beyond the killzone tag, log the exact time of your entry. ICT concepts often perform differently at specific times within killzones. For example, you might discover that your best entries consistently occur between 2:30 AM and 3:15 AM EST (early London) rather than during the full London killzone.
This granularity is impossible to capture without logging, and the patterns are invisible without analysis.
How to Log ICT Concepts in PipJournal
PipJournal’s tagging system is flexible enough to capture all ICT-specific fields without requiring a custom-built journal. Here’s how to set it up:
Custom tags for entry models: Create tags for each ICT concept (OB, FVG, BB, MB, OTE, LS). Apply the relevant tag to each trade during post-trade logging.
Setup notes: Use the notes field to describe the full ICT narrative — the market structure, the liquidity that was targeted, the displacement quality, and the HTF alignment. Keep it concise but specific:
“Bearish BOS on H1. London killzone. Buy-side liquidity swept at Asian high. Strong displacement down. OB entry on the retest. HTF aligned (daily bearish). Targeting sell-side liquidity at previous day low.”
This level of detail takes 60-90 seconds to write and provides everything you need for your weekly review.
Screenshots: Attach a chart screenshot showing your ICT markup — order blocks, FVGs, liquidity pools, and structure. During your weekly review, these screenshots let you reassess your analysis quality without relying on memory.
ICT Session Analysis
One of the most valuable analyses for ICT traders is performance broken down by killzone. PipJournal’s session analytics do this automatically for the standard forex sessions, which map closely to ICT killzones.
After 30-50 trades, look for these patterns:
- Which killzone has your highest win rate? Most ICT traders find a significant performance gap between sessions.
- Which killzone has your best R:R? You might win less often in one killzone but capture larger moves when you do.
- Which killzone has the best expectancy? This is the metric that matters most — the combination of win rate and R:R that produces the highest expected return per trade.
If London killzone trades have 2x the expectancy of New York PM trades, that’s a clear signal to concentrate your effort. You don’t need to stop trading New York entirely — but you should recognize that London is where your ICT edge is strongest and prioritize accordingly.
Building Your ICT Review Process
Weekly review: concept performance
Every weekend, run through your tagged trades for the week:
- Filter by entry model. Which ICT concepts produced profitable trades? Which didn’t?
- Filter by killzone. Which sessions performed best?
- Check displacement correlation. Did waiting for displacement improve results?
- Check HTF alignment. Did aligned trades outperform counter-trend trades?
After 4-6 weeks, patterns emerge that transform your ICT trading from “I trade all the concepts I’ve learned” to “I trade the 2-3 concepts that produce the best results in the sessions where my edge is strongest.”
Monthly review: concept refinement
Monthly, zoom out and assess your overall ICT performance:
- Which concepts should you drop? (Negative expectancy after 30+ trades)
- Which concepts deserve more focus? (High expectancy, but you’re not taking enough of them)
- Are there killzones you should eliminate? (Consistently negative performance)
- Is your market structure read improving? (Increasing accuracy on BOS/CHoCH calls over time)
This evidence-based refinement is what separates ICT traders who plateau from ICT traders who continuously improve. The concepts don’t change — your execution of them does, and the journal measures that execution.
Common ICT Journaling Mistakes
Logging concepts but not measuring them
Many ICT traders write detailed notes about their order blocks and FVGs but never filter and analyze the data. Notes without analysis is a diary, not a journal. Use your tags to create measurable, comparable datasets across concepts.
Not tracking what you didn’t take
When you see an ICT setup but decide not to take it, log it as a “missed” or “passed” trade. Over time, this data shows whether your pass decisions are correct — maybe you’re avoiding setups that would have been winners, or maybe you’re correctly filtering out low-probability concepts.
Over-complicating the log
You don’t need to log every Fibonacci level, every inducement, every sub-concept within your ICT framework. Focus on the 5-7 fields listed above. A journal you actually maintain beats an exhaustive one you abandon after two weeks.
For a complete guide to building a sustainable journaling habit, read our guide on how to keep a trading journal. For forex-specific journaling workflows, see our step-by-step guide on how to journal forex trades.
The Bottom Line
ICT trading is a skill-based approach that rewards precision, patience, and pattern recognition. A journal built for ICT concepts lets you measure your precision, validate your patience, and quantify your pattern recognition — with your own data, not theoretical backtests.
Track your entry models. Tag your killzones. Log your liquidity targets. Measure displacement quality. After 50-100 trades, you’ll have a clear picture of which ICT concepts produce the best results in your hands — and that knowledge is worth more than any mentorship, course, or YouTube video.
The concepts are the same for every ICT trader. Your execution is unique. The journal reveals the difference.
PipJournal is the only trading journal built exclusively for forex traders. Its custom tagging system handles ICT concepts natively — order blocks, FVGs, killzones, and market structure. The AI co-pilot analyzes your tagged data to surface which concepts drive your edge. $179 for lifetime access, no monthly fees. Start your 14-day free trial and let your data refine your ICT trading.
People Also Ask
What should I track in an ICT trading journal?
Beyond standard trade data (pair, direction, entry, exit, stop loss), ICT traders should track: the specific ICT concept used (order block, fair value gap, breaker block, etc.), the market structure context (bullish or bearish BOS/CHoCH), the liquidity target that was swept before entry, the killzone (Asian, London, New York AM, New York PM), time of day, displacement presence, and whether the trade aligned with the higher timeframe narrative. Tracking these ICT-specific fields lets you analyze which concepts produce the best results in your trading.
Why do ICT traders need a specialized journal?
Generic trading journals track basic metrics like win rate and P&L, but they can't analyze ICT-specific performance. An ICT trader needs to know: which order blocks produce the highest win rate, whether London killzone entries outperform New York, which liquidity sweep patterns lead to the most reliable displacement, and whether higher timeframe alignment improves their results. Without tracking these variables, you can't optimize your ICT approach — you're just trading concepts without measuring which ones actually work for you.
What are the best ICT killzones to trade?
The primary ICT killzones are: Asian session (8:00 PM - 12:00 AM EST), London open (2:00 AM - 5:00 AM EST), New York AM (7:00 AM - 10:00 AM EST), and New York PM (1:30 PM - 4:00 PM EST). The London and New York AM killzones typically produce the highest-probability setups because they coincide with the most institutional order flow. However, the best killzone for you depends on your specific edge — which is exactly what your journal data should reveal.
How do I log ICT concepts like order blocks and FVGs?
Create a tagging system with standardized labels for each ICT concept: OB (order block), FVG (fair value gap), BB (breaker block), MB (mitigation block), LS (liquidity sweep), BOS (break of structure), CHoCH (change of character). Tag each trade with the primary concept used for entry and the market structure context. Over time, this lets you filter your journal by concept and compare performance across different ICT entry models.
Can PipJournal be used for ICT trading?
Yes. PipJournal's custom tagging system lets you create ICT-specific tags for order blocks, fair value gaps, liquidity sweeps, killzones, and market structure. The session analysis feature aligns with ICT's killzone framework, showing your performance during Asian, London, and New York sessions. The AI co-pilot can detect patterns in your tagged data — like whether your OB entries outperform your FVG entries, or whether London killzone trades have higher expectancy than New York trades.
