The anatomy of a liquidity sweep

One event, four acts

Traders talk about liquidity sweeps as if they were single candles. They are not. A sweep is a sequence — a short story with a setup, a raid, a confirmation and a delivery. Learn the acts and you will know which one is still missing before you take a trade.

Act I — The setup: liquidity builds up

Before a pool can be raided it must exist. Liquidity builds up around clean, visible reference points: a tight range with equal highs, a trendline touched three times, yesterday's low sitting naked below a quiet session. Each of these invites a crowd to place stops in the same postcode.

The mental shift this framework asks for: obvious levels are not obstacles — they are inventory. The cleaner the level looks, the more orders the framework assumes rest behind it — an assumption, since a retail chart does not show them. This is why "textbook" support can break by a few points before the move in the other direction begins. The full catalogue of these reference points lives in our guide to liquidity levels.

Act II — The raid: the level is taken

The raid itself is fast and emotionally loud. Price accelerates into the level — a session open or a news print can supply the push — and punches through. Stops trigger, breakout entries fill, and for a moment the tape confirms every fear and every greed simultaneously.

In this reading, that burst of forced orders is the point: it is the counterparty volume a large order needs in order to fill — an inference from price, not something the chart shows. Read this way, the raid is not the beginning of a trend but the liquidity for one.

Act III — The confirmation: displacement back inside

What separates a sweep from a genuine breakout is what happens next. In a sweep, the market turns back: price snaps back through the raided level and closes inside the old range, with conviction — full-bodied candles leaving a fair value gap, read as the footprint of one-sided flow.

This is the act that carries the tradable information, and it has objective criteria:

• A close back beyond the level (not a wick — a close).
• Displacement: an impulsive leg leaving a gap in the reversal direction.
• Ideally, agreement from structure — the reversal launching from or through an order block.

No confirmation, no trade. A level that breaks and stays broken was never a sweep.

Act IV — The delivery: the opposite pool as target

Once the close back inside has printed, the model expects price to travel. The targets it uses are, in order, the equilibrium of the raided range and then the liquidity resting on the opposite side — the untouched pool that becomes the trade's target. When the move comes, a sweep at a daily extreme can travel several times the distance risked beyond the raid point — not every one does. That asymmetry is what makes the pattern compatible with strict prop-firm risk rules: small structural stop, distant structural target.

Recognising the anatomy without hindsight

Hindsight makes every sweep obvious; the live version arrives disguised by speed and emotion. The practical solution is to encode the acts as rules and let software watch the levels — every level, every session, without fatigue. That is the design brief behind SWEEP PROTOCOL: it tracks the obvious levels, ignores the raid until the close back inside prints, and signals only on the closed bar that completes Act III. The sequence does not change, and neither does the rule: wait for the close that completes Act III.

What this article does not do

• No prediction. A setup that meets every condition described here can fail.
• Weak contexts. Around session opens, scheduled releases and thin hours, levels can be traded through and fills can be worse than planned.
• No recommendation. Nothing here is an instruction to trade a specific instrument or level.