What Does Liquidity Mean in ICT Trading?
In conventional financial education, liquidity refers to how easily an asset can be bought or sold — a highly liquid market has many buyers and sellers and tight spreads. While that definition is correct, it is not what ICT traders mean when they talk about liquidity. In the ICT framework, liquidity specifically refers to the resting orders — stop losses, limit orders, and pending orders — that cluster at significant price levels.
These resting orders are invisible on your chart. You cannot see them directly. But you can infer where they are by reading price structure. Retail traders, following conventional technical analysis, place their stop losses at predictable locations: below support levels, below swing lows, below equal lows, and above resistance levels, above swing highs, above equal highs. This predictability creates clusters of resting orders at those levels.
These clusters are liquidity pools. When institutions need to fill a large buy or sell order, they need a counterparty — someone willing to take the other side of the trade. The retail stop losses at those predictable levels are exactly that counterparty. The institution moves price to the liquidity pool, triggers the retail stop losses, and fills its own large order against those triggered stops.
Buy-Side and Sell-Side Liquidity Defined
Buy-Side Liquidity (BSL) is the cluster of orders resting above price. It consists primarily of two types: stop losses from traders who are short (their stop losses are placed above the price they shorted at, so above swing highs and resistance levels), and buy stop orders from breakout traders who place buy limits just above resistance expecting a breakout. Both types of orders sit above the market, both are buy orders — hence buy-side liquidity.
Sell-Side Liquidity (SSL) is the mirror: the cluster of orders resting below price. It consists of stop losses from traders who are long (placed below their entry, so below swing lows and support levels), and sell stop orders from breakdown traders who place sell limits just below support expecting a breakdown. Both are sell orders — hence sell-side liquidity.
The most concentrated liquidity pools form at the most obvious chart levels: equal highs (multiple candles touching the same high price create a dense BSL cluster), equal lows (SSL cluster), prior week highs and lows, round number prices, and prior day highs and lows. The more obvious the level, the more retail traders place orders there, and the more valuable the liquidity pool is to an institution needing to fill a large position.
The draw on liquidity is the ICT term for the nearest significant liquidity pool that price is currently heading toward. It is your price target — the level where the algorithm is delivering price because that is where the next significant cluster of resting orders is located.
Identifying the draw on liquidity is the second step of the ICT top-down analysis process (after establishing the
daily bias). On the daily chart, you look above price for the nearest BSL (if bullish bias) or below price for the nearest SSL (if bearish bias). That level is the draw — the destination of the current price delivery.
The draw on liquidity tells you where to target your trades. If the draw is the prior week high (BSL above), your long trades target the prior week high. If it is the prior month low (SSL below), your short trades target the prior month low. Every ICT trade has a defined draw on liquidity — trades without a clear draw are speculative.
Why Obvious Levels Always Seem to Get Swept
If you have traded for any length of time using conventional technical analysis — support, resistance, trend lines, equal highs and lows — you have experienced the frustration of placing a stop just below support only to see price dip exactly to your stop level before reversing sharply higher. This is not random. It is the liquidity mechanism in action.
Your stop loss, and thousands of other traders who placed stops in the same location, created a liquidity pool. The institution needed to fill a large buy order. It moved price down to where your stop was, triggered it (and every other stop at that level), and used your sell order to fill its buy order. With its buy position now filled, the institution drove price higher — the real direction it intended all along.
Understanding this mechanism does not make you bitter about stops being hit. It makes you a better trader. Instead of placing stops at obvious levels where the sweep will hit you, you either place stops beyond the sweep target (so you survive it), or you wait for the sweep to occur and then enter in the direction of the institutional move after the liquidity is collected.
Liquidity Pools by Timeframe: Hierarchy of Significance
Not all liquidity pools are equal in significance. The hierarchy is determined by how long the level has been building and how many traders have placed orders at it. A prior year high has been building BSL for 12 months — thousands of traders have placed stops above it. A 15-minute swing high from earlier today has been building BSL for 2-3 hours — far fewer traders have stops there. The older and more widely-watched the level, the more significant the liquidity pool.
The practical hierarchy from highest to lowest: All-time highs/lows (years of BSL/SSL building), prior year highs/lows (annual reference levels), prior quarter highs/lows (quarterly IPDA shift levels), prior month highs/lows (monthly reference), prior week highs/lows (the most commonly used daily trade targets), prior day highs/lows (intraday targets for same-session delivery), and intraday equal highs/lows (the immediate kill zone targets).
For day trading: focus primarily on the prior week and prior day levels as your main draw on liquidity targets. For swing trading: focus on prior month and prior quarter levels. For position trading: prior year and all-time highs/lows become the relevant targets. Matching the liquidity target timeframe to your trade holding period produces better-defined targets and avoids the common mistake of targeting a 2-week-old level when day trading a 1-hour setup.
How News Events Create Instant Liquidity Pools
Major news events (NFP, CPI, FOMC) create instant, highly significant liquidity pools because they attract enormous retail order flow within a very short time. In the 30 minutes before a major news event, retail traders place their anticipated directional bets — creating BSL above current price (buy stops from those expecting a breakout higher) and SSL below (sell stops from those expecting a breakdown lower). In the 5 minutes before the release, a visible cluster of stops sits just beyond both the recent high and recent low.
The institutional response is predictable: as the news releases, price often spikes in one direction (sweeping one side of the pre-news liquidity), then reverses sharply and drives to the other side. The initial spike is the news-driven sweep of one liquidity pool; the reversal is the institutional delivery using that collected liquidity to drive price to the opposite pool. This is the news-event Judas Swing — identical in structure to the session-open Judas Swing but compressed into minutes rather than hours.
Trading news events directly is high-risk due to the speed of delivery and the wide spreads that brokers impose during the release. However, the post-news environment (5-15 minutes after the release) often presents clean ICT setups — the liquidity has been swept, the FVG from the news spike is clearly visible, and the direction of the post-news delivery aligns with the daily bias. These post-news FVG entries are among the cleanest setups of the day on high-impact news days.
Watch: What Is Liquidity in ICT Trading? Buy-Side and Sell-Side Explained
Frequently Asked Questions