Institutional Order Flow
Also: IOF, institutional orderflow, draw on liquidity, order flow (ICT definition)
Institutional Order Flow (IOF), as defined by ICT, is NOT the DOM (depth of market), level-two data, or footprint chart data showing tick-level buying and selling volume. Instead, IOF is read through PRICE ACTION STRUCTURE — the arrangement of PD arrays, liquidity pools, market structure swings, and algorithmic delivery signatures on a time-based candlestick chart. IOF represents the underlying directional program (buy program or sell program) being executed by the algorithmic market maker, visible through the interaction of price with previously established fair value gaps, order blocks, breakers, and liquidity pools. The core of reading IOF is: (1) identifying the DRAW ON LIQUIDITY — the most significant buy-side or sell-side pool the algorithm has not yet reached, (2) understanding WHICH side of the market is being accumulated (smart money accumulating longs = bullish IOF; accumulating shorts = bearish IOF), and (3) recognizing the TIME component — IOF delivery is time-structured through macro windows, not random. A balanced price range (BPR) within IOF analysis is when a single candle delivers both buy-side and sell-side relative to adjacent candles, creating a stronger FVG context for entry. Wicks/tails on candlesticks are treated by the algorithm as gaps, with their midpoint = consequent encroachment.
Identification7
- DO NOT use DOM, level-2 ladder, or footprint chart data to read IOF — ICT explicitly rejects these as the basis for IOF analysis.
- Read IOF through: higher-timeframe weekly/daily draw on liquidity, PD array confluence, macro timing, and SMT divergence.
- Identify the DRAW ON LIQUIDITY: the nearest significant unvisited buy-side (above old highs) or sell-side (below old lows) pool that the algorithm is targeting.
- Confirm bias direction through: weekly chart inefficiency and liquidity context, daily PD array reactions, SMT divergence between correlated instruments.
- Balanced Price Range (BPR): occurs when a large up-close candle has a preceding down-close candle delivering sell-side on its left, AND the up-close candle delivers buy-side (SIBI). This dual-delivery context makes the FVG within the BPR a higher-conviction entry zone.
- Wicks/tails = algorithmic gaps: consequent encroachment of a wick = midpoint of the wick, used as CE for that gap.
- Mitigation block distinction: high-low-higher high = MITIGATION block (not breaker). Mitigation blocks are better used as TARGETS than entries. Bearish BREAKERS are stronger resistance than mitigation blocks.
Entry4
- IOF framework determines BIAS and DRAW ON LIQUIDITY. Entries are made using specific PD arrays aligned with the established IOF direction.
- Within a bullish IOF: buy at discount PD arrays (FVGs, order blocks, breakers, inversion FVGs) targeting the draw on buy-side liquidity.
- Within a bearish IOF: sell at premium PD arrays targeting the draw on sell-side liquidity.
- Balanced Price Range FVGs are preferred entry zones due to their dual-delivery context.
Stop1
- Stop placement per entry PD array. IOF framework determines which side of the market to be on, not the stop level.
Target3
- The identified draw on liquidity is the IOF target.
- PD arrays along the delivery path are intermediate targets (mile markers).
- Mitigation blocks encountered along the delivery path are used as targets, not entries.
Invalidation2
- IOF read via DOM/footprint data can be spoofed — orders above/below the market can be placed and pulled before price reaches them. This is why ICT rejects these tools.
- IOF based on PD arrays invalidates when the draw on liquidity has been met and price begins forming the opposite structure.
Inferred Conditions (Unvalidated)
- SMT divergence between ES and NQ (or other correlated instruments) within the IOF framework confirms accumulation and the expected directional delivery.
- When a balanced price range exists within the IOF delivery zone, ICT is willing to trade larger position sizes (up to 15-20 contracts vs. a standard FVG entry of ≤10 contracts).
ICT Quotes
"When I say institutional order flow, I'm seeing institutional order flow in price action. It's not DOM data. Institutional order flow is not this — this is reporting numbers that can be spoofed."
"My PDAs are always always the head of this. It's always ahead of DOM/footprint data. I tell you exactly what we'd be seeing, what would be expected in terms of price delivery, and it delivered perfectly flawlessly. No necessity on having any of this stuff here."
"The number one thing is draw on liquidity. You have to know where price is likely to draw to — higher or lower — and not just for the sake of a few handles. You have to have a directional bias. If you don't have that skill set, you will not be consistently profitable, period, end of story."
"A bounced price range is when a market moves from a range where it's offered both sides — buy side and sell side delivery. When you have on the opposing side one singular candle, it kind of creates this island reversal type pattern. It makes it stronger when you have on the opposing side one singular candle delivering on the upside."
"We have to trust order flow. What kind of order flow? The things I started to show you in the beginning of this presentation — I don't subscribe to those things. I don't have any faith in them. My faith is based on where I believe the market is gonna go. I can see where orders are going to be anyway before your ladders, your depth of market, before your footprint confirms what I already and my students already expect."
"Mitigation blocks are better used for targeting purposes. Mitigation block can be traded through. Breakers are kind of like they're pretty formidable in the path of price action."
Timeframes
Version History2 versions
ICT YT - 2023-07-17 - ICT Mentorship 2023 - Deep Dive Into Institutional Order Flow.srt
"This is going to be a discussion and lecture on institutional order flow. The idea of order flow using a DOM, which is depth of market — this is not institutional order flow. Institutional order flow …"
Formal deep-dive lecture explicitly defining ICT's IOF as distinct from DOM/footprint data. Introduced Balanced Price Range (BPR) as a high-conviction FVG qualifier. Refined mitigation block vs. breaker hierarchy (mitigation = target; breaker = entry + resistance). Established draw on liquidity as the primary analytical directive.
16 - ICT 2026 Smart Money Concepts Lecture ⧹ February 10, 2026.en.srt
"sell side of bounce buy sign and efficiency institutional order flow entry drill. Soon as it trades up into that, we want to see if we're bearish. My fair value gap, okay, it needs to show a willingne…"
INSTITUTIONAL ORDER FLOW ENTRY DRILL: ICT names a specific entry technique called the 'institutional order flow entry drill.' When price trades into a SIBI (sellside imbalance buyside inefficiency), the trader looks for the FVG to 'show a willingness to stay open' — the upper half remains unfilled. This is the highest probability bearish FVG. Combined with an order block showing a 'change in the state of delivery' on a 15-second chart, this creates a precision entry. The entry drill is the process of confirming institutional order flow direction through the FVG's behavior (staying open vs filling), not through DOM or volume data.
Notes
This lecture is primarily a contrast/clarification lecture: ICT uses the first half to debunk the popular use of DOM/footprint data as "order flow" and then defines his own meaning of IOF. Key takeaway: ICT's IOF = PD array-based price action reading with time component (macros) + draw on liquidity identification. The Balanced Price Range (BPR) concept is introduced informally here as a qualifier for FVG strength — when a FVG has both a buy-side delivery candle and sell-side delivery candle on opposite sides, it is a higher-quality entry zone. The mitigation block hierarchy clarification (mitigation block < breaker in terms of resistance/support strength) is a 2023 refinement relevant to breaker-block.yaml.
Asymmetry Notes
IOF is symmetrical — buy programs and sell programs use the same analytical framework, just in opposite directions.