ICT BSL and SSL — Buy-Side & Sell-Side Liquidity

What Are ICT BSL and SSL (Buy-Side and Sell-Side Liquidity)?

BSL (Buy-Side Liquidity) sits above price — above swing highs, equal highs, and prior day highs. SSL (Sell-Side Liquidity) sits below price — below swing lows, equal lows, and prior day lows. In a bullish session, the Judas sweeps SSL below, then price delivers to BSL above as the AMD target. In a bearish session, the Judas sweeps BSL above, then price delivers to SSL below.

Liquidity is the engine of every ICT trade. The ICT Judas Swing sweeps the SSL because that is where the institutional fuel is. Price delivers to the BSL because that is the target the algorithm was programmed to reach. Without understanding BSL and SSL, the AMD cycle is just a shape and the Judas is just a pattern. With them understood, every ICT concept snaps into place.

Why Institutions Need Liquidity Pools

Large institutional participants cannot execute big orders at market without moving price against themselves. A 1,000-contract NQ short position submitted as a market order drives price down before half fills — ruining the average entry. The solution: drive price to a BSL pool where retail buy stops cluster. Those triggered buy stops become the counterparty. The institution sells 1,000 contracts against the retail buy flow at the chosen price. After filling, the institution reverses price downward.

This is why price sweeps key levels before reversing. The sweep is the institutional order-filling mechanism, not random noise. The pool exists because retail traders predictably place stops at obvious highs and lows. Institutions use that predictability to fill large orders. After the fill is complete, they reverse.

What Generates BSL and SSL Pools

Equal highs and equal lows form the densest pools. When price tests the same level multiple times without breaking through, stops accumulate on each test. Three tests means three layers of stops. Equal highs and lows are the highest-priority BSL/SSL pools because their stop density is maximum.

Prior session highs and lows — the PDH and PDL — are watched by every day trader. Retail traders who went long at the PDL placed stops below it. Retail traders who shorted the PDH placed stops above it. The aggregate creates a predictable, dense pool at every PDH and PDL.

Round numbers attract disproportionate stop orders. 21,000 / 21,500 on NQ, 1.0800 / 1.0900 on EUR/USD — traders set stops at round numbers because they are memorable. Institutions specifically target round number BSL/SSL pools, which is why major round numbers are frequently swept before major reversals.

Prior week and prior month extremes accumulate stops from swing traders holding through the weekend. These are the densest multi-session pools — weeks of long traders with stops below the weekly low, weeks of short traders with stops above the weekly high.

The BSL/SSL 6-Tier Hierarchy

The tier determines both the strength of the sweep reversal and the significance of the target. A Tier 1 monthly equal-lows sweep produces a multi-session reversal. A Tier 6 single intraday swing low sweep produces an intraday reversal to the nearest IRL. Calibrate position size and target distance to the tier of the swept pool.

BSL/SSL as Trigger and Target in the AMD Cycle

The AMD cycle makes no sense without BSL/SSL. Every AMD phase maps directly:

Accumulation: Price consolidates between the SSL below and BSL above as stops accumulate at both extremes of the range. The longer the accumulation, the denser the pools at both ends.

Manipulation (Judas Swing): Price is driven into one pool — SSL below on a bullish day, BSL above on a bearish day. The pool is swept: stops trigger, providing counterparty volume for the institutional entry on the opposite side. The Judas always goes to a specific level rather than just "down" — it targets the SSL because that is where the order-fill volume exists.

Distribution: After the manipulation sweep fills the institutional position, price delivers toward the opposite pool. BSL above on a bullish day (T1 and T2 targets). SSL below on a bearish day. Target setting becomes mechanical: mark the BSL levels, pick the nearest as T1, the next as T2.

NQ Session Walkthrough

Pre-session: Daily bias bullish. Prior week high: 21,840 (T2 BSL). PDH: 21,640 (T3 BSL). Asian Range High: 21,488 (T4 BSL). Asian Range Low: 21,332 (T4 SSL). PDL: 21,180 (T3 SSL). Draw on liquidity: T2 BSL 21,840.

9:34 AM — Judas sweeps T4 SSL: NQ drops to 21,298 — 34 points below ARL (21,332). SSL swept. Body closes 21,348 — back inside overnight range. Retail longs stopped out. Institutional long filled.

9:42 AM — MSS fires: Swing high at 21,410 broken by displacement: 21,348 → 21,506. FVG: 21,380–21,508. 50% CE: 21,444. Long fills 21,444. Stop below Judas wick: 21,290 (154 pts).

T1 — PDH 21,640: 196 pts, 1.3R. Hit 11:04 AM. Stop to BE. T2 — prior week high 21,840: 396 pts, 2.6R. Hit Thursday 10:22 AM.

Pre-Session BSL/SSL Marking Workflow

The BSL/SSL map built in pre-session prep defines the session's entire architecture before price moves a single tick. Here is the exact workflow, timeframe by timeframe:

Step 1 — Weekly chart. Mark the prior week high (T2 BSL) and prior week low (T2 SSL). Identify any equal highs or equal lows visible over the last 4–8 weeks — these are your T1 pools. Note which direction the weekly profile suggests delivery is heading. If the weekly is bullish, the T2 BSL (prior week high) is likely the week's delivery target. If bearish, the T2 SSL (prior week low).

Step 2 — Daily chart. Mark PDH and PDL — these are your T3 BSL and SSL. The PDH is the most reliable intraday BSL in the framework. It represents one full session of short sellers with stops above it, plus the prior day's breakout buyers whose buy stops sit just above. The PDL is the equivalent SSL. Also note any daily equal highs or equal lows from the last 5–10 sessions — these are T5 pools if they are intraday, or T1/T2 if they span weekly extremes.

Step 3 — 4H and 1H chart. Mark the Asian Range High (T4 BSL) and Asian Range Low (T4 SSL). These are the most common Judas Swing targets for the London and NY sessions — the levels the algorithm sweeps before the true directional move begins. Set price alerts 2–3 points above the ARH (BSL) and below the ARL (SSL) so you know exactly when price is approaching each pool.

Step 4 — Bias confirmation. The BSL/SSL map and the daily bias together answer two questions: which pool is today's Judas target (the pool the algorithm will sweep at session open) and which pool is today's delivery target (the pool price will deliver to after the sweep). On a bullish day: SSL = Judas target, BSL = delivery target. On a bearish day: BSL = Judas target, SSL = delivery target. Once you know which is which, the session's expected architecture is complete.

Dense vs Thin Pools — Reading the Stop Order Accumulation

The tier hierarchy gives a structural ranking of BSL/SSL pools. But within each tier, pools vary significantly in density — the number of stop orders that have accumulated at the level. A Tier 3 PDH that was tested three times yesterday has a denser stop cluster than a PDH from a session that never retested its high. Understanding density within the tier hierarchy is what separates experienced BSL/SSL traders from those who treat every tier-3 level as identical.

Three density multipliers: number of tests (each test adds another layer of stops from traders who re-entered after the prior test held), timeframe visibility (a level visible on the daily chart attracts more stops than a 5M-only level because more traders see it and place stops there), and recency (stops placed in the last 1–3 sessions are still active; stops placed 6 months ago have largely been cleared by other entries and exits).

The densest, highest-priority pools combine all three: visually obvious on the daily or weekly chart, tested 3+ times, and formed within the last 1–5 sessions. When such a pool is swept during a kill zone aligned with the daily bias, the reaction is typically the most powerful reversal of the session. These are the setups worth sizing up for — the institutional order fill is maximum because the stop density is maximum.

Common BSL/SSL Mistakes

Marking every swing as BSL/SSL. A single intraday swing with one test is a thin, unreliable pool. Focus on equal highs/lows, PDH/PDL, prior week extremes — levels where stops have genuinely accumulated. The tier hierarchy eliminates 80% of false BSL/SSL marks.

Entering before the sweep confirms. Wait for the candle to close back inside the range after the wick extends beyond the level. The body close is the confirmation. Entering during the wick risks entering a genuine breakout.

Targeting thin Tier 6 pools as T1. The nearest significant BSL — Tier 3 or above — is the correct T1. Single intraday swings without equal companions are partial-close levels at best.

Trading a sweep against the daily bias. A SSL sweep that is reached on a bearish day from above is the destination, not a reversal trigger. Directional context determines whether a pool is the Judas trigger or the delivery target.

Frequently Asked Questions

Advanced BSL/SSL Mistakes

Treating BSL/SSL as support and resistance. This is the most fundamental misunderstanding. Traditional support and resistance assumes price respects levels and reverses from them without being breached. BSL/SSL are the opposite: they are specifically the levels that WILL be breached — briefly — before the reversal. The institutional algorithm needs to trigger the stop orders AT the level to fill its position. A trader who places limit entries AT the BSL level (as if it were resistance) gets filled as the sweep is happening, on the wrong side. The correct entry is AFTER the BSL is swept and price has reversed back inside, on the retrace to the FVG created by the MSS.

Failing to update the map intraday. Once price sweeps a BSL or SSL pool, that pool is collected — it is no longer a live target. The post-sweep map changes. If the session Judas sweeps the T4 ARL (SSL), mark it as collected and focus on the T3 PDL (the next SSL below) as a potential secondary sweep target and the T3 PDH (BSL) as the primary delivery target. Traders who leave collected pools on their chart create false signals — seeing "support" at a level that has already been swept and is no longer active.

Confusing the Judas pool with the delivery target. On a bullish day, the SSL below is swept first (Judas) and the BSL above is the target (delivery). Entering SHORT because "the SSL was broken and price is now below it" is entering in the direction of the Judas — the opposite of the session's true direction. The body-close rule and the MSS exist precisely to prevent this error. Wait for price to close its body back inside the SSL, confirm the MSS, then enter long toward the BSL. The direction of the delivery is always away from the swept pool, not toward it.

Setting Targets Using the BSL/SSL Hierarchy

Target selection in the ICT framework is systematic, not discretionary. Every target is a BSL or SSL pool from the pre-session map. The question is which tier to use for T1 vs T2 vs runner.

T1 (first target, majority of position): The nearest significant BSL (bullish day) or SSL (bearish day) above/below current price. "Significant" means Tier 3 or above — PDH, prior week level, or equal highs/lows. Tier 5–6 intraday levels make adequate partial close levels on volatile days but should not be the primary T1 unless the session context specifically supports them. T1 is where 50–75% of the position closes. Stop moves to break-even after T1 hit.

T2 (runner): The next significant pool above T1 (bullish) or below T1 (bearish). If T1 is the PDH (T3 BSL), T2 is the prior week high (T2 BSL) or the nearest equal highs (T1 BSL) above it. T2 is where the remaining 25–50% of the position closes. T2 is only held if the weekly profile supports an extended delivery and the T1 reaction was minimal (confirming institutional momentum).

Runner beyond T2: Reserved for sessions where all weekly, daily, and intraday BSL/SSL factors align perfectly — weekly Judas day, daily bias clear, Tier 1 pool swept, and the T1 hit was blown through rather than respected. These multi-day runners to monthly or weekly equal highs occur a few times per month at most and should be treated as exceptional rather than standard.