Liquidity

What Is Liquidity Engineering?

Liquidity engineering is the idea that price is drawn toward places where stop and pending orders cluster, such as obvious highs and lows, and often runs those orders before it picks a direction. It is a smart-money-concepts model for reading charts, not a proven mechanism, and its value lies in reading what price does after it reaches the orders.

The IIF Liquidity Matrix: active and filled liquidity rows by price level, with sizes in USDT
The IIF Liquidity Matrix: active and filled liquidity rows by price level, with sizes in USDT.
In this guide

Key takeaways

  • Liquidity rests where many traders put stops and pending orders: equal highs and lows, prior swing points, session highs and lows, and round numbers.
  • A sweep is the event, not the signal. What price does next, close back inside or hold beyond the level, decides the read.
  • Closes back inside within a few candles point to a sweep; several closes beyond the level point to a breakout.
  • After one pool is taken, the next untouched pool in the direction of the higher-timeframe structure is the likely draw.

Where liquidity rests on a chart

Here, liquidity means resting orders: stop-losses, breakout entries and limit orders waiting at a price. A TradingView chart does not show them, so you infer them from where traders are likely to have put them. The reasoning is simple. Traders learn the same rules, so they put their stops in the same places.

The places that collect the most orders are the ones everyone can see:

  • Equal highs and equal lows. Two or more swing points at nearly the same price invite stops just beyond them: buy stops above equal highs, sell stops below equal lows.
  • Prior swing highs and lows, especially the last one before a strong move.
  • Session and day extremes: the Asian session range, the previous day’s high and low, the weekly open.
  • Round numbers, such as 60,000 on BTC or 1.1000 on EUR/USD, where both limit orders and stops gather.
  • Range edges, where breakout traders place entries and range traders place stops.

How a pool builds before it is taken

Pools rarely appear from nowhere. The common sequence has three parts:

  • Compression. Price grinds into a level, often making equal or slightly lower highs, and each touch adds stops just beyond it.
  • Inducement. A small move that looks like a breakout, or like a clean rejection, draws traders in, and their stops join the pool.
  • The run. Price moves through the level quickly, triggers the stops, and fills the orders waiting on the other side.

The run is often fast, with long candles and wicks, because triggered stops become market orders. That speed is why a sweep can look exactly like a breakout while it is happening.

Be careful with the word engineered. Nobody has to plan a sweep for it to happen. When many orders sit at one price, any move into that price gets fuel from them. The model describes where price tends to travel, not who sends it there.

Sweep or breakout: reclaim versus acceptance

A sweep and a breakout start the same way: price trades through the level. The difference is what happens next, and you can only see it once a few candles have closed.

Sweep (rejection)Breakout (acceptance)
After the level is takenPrice closes back inside the prior rangePrice closes beyond the level and keeps closing there
On the retestThe level holds from the original sideThe level holds from the new side
Structure afterwardsOften a shift in the opposite directionNew swings keep building in the direction of the break
How far beyondUsually a wick or a short excursionA sustained move that does not come back

A rule you can apply by hand: once a high is taken, wait for candles to close. If price closes back below the high within a few candles and the next rally fails to close above it again, treat it as a sweep. If price closes above the high and keeps closing there, treat it as a breakout and stop looking for a reversal. How many closes depends on your timeframe; what matters is that you decide on closes, not on wicks.

IIF applies the same idea with fixed numbers. Its Block Sweep signal waits, by default, for four consecutive closes back inside an order block before it prints, and it ignores moves that travel too far beyond the zone, because those are breakdowns rather than sweeps.

Choosing the next draw

Once one pool is taken, the useful question is which pool price is likely to reach next. Traders call it the draw on liquidity. Three checks narrow it down:

  • Higher-timeframe structure. In a higher-timeframe downtrend, pools below price are the more likely draw, and sweeps of highs tend to produce pullbacks rather than reversals. In an uptrend, the reverse.
  • Untouched before touched. A pool that has not been tested still holds its orders; one that was already swept has spent them.
  • Distance and obstacles. The nearest untouched pool with no higher-timeframe order block in the way is the easiest target.

When the three checks disagree, the honest answer is often that there is no clear draw, which is itself useful: it means waiting.

Two examples on real charts

Both captures are real TradingView charts with IIF loaded. The numbered steps match the markers on each chart. The first sweep turned into a reversal; the second did not, and the difference was the higher-timeframe structure.

BTC, 12 hours: a sweep of the highs, then the pool below

BTC 12-hour TradingView chart with IIF: a sweep above prior highs, weekly bearish order blocks forming above price, and the decline into a bullish order block marked Mitigated
BTC, 12-hour chart with IIF. The dashed line marks the prior highs; the numbers match the steps below.
  1. 1Price pushes above a cluster of prior highs, then closes back inside the bearish order block it had broken above, and IIF prints Sweep. The buy stops above the highs were taken, and buyers could not hold the new high.
  2. 2On the way down, weekly bearish order blocks (labelled 1W OB) form above price. Rallies into them now meet supply.
  3. 3The next large untouched pool is the bullish order block far below. Price reaches it, fills the gaps inside it, and IIF marks the block Mitigated.
  4. 4A smaller block fails (Break), and a bullish Shift line forms as price steadies inside the zone.

The sweep of the highs was the start of the move, not the whole read. What confirmed it was the failure to get back above the highs and the new bearish blocks that formed on the way down.

EUR/USD, 1 hour: a sweep that only produced a pullback

EUR/USD 1-hour TradingView chart with IIF: a bullish sweep at a low, a bounce that stalls inside a 12-hour bearish order block, lower highs, and failed blocks as the decline continues
EUR/USD, 1-hour chart with IIF and 12-hour (720-minute) order blocks. The numbers match the steps below.
  1. 1At the low on the left, price closes below a bullish order block and then back inside it, and IIF prints a bullish Sweep.
  2. 2The bounce runs into a 12-hour bearish order block (labelled 720 OB) and stalls inside it.
  3. 3Price makes lower highs under the next 12-hour bearish block.
  4. 4Blocks below fail (Break), and the decline continues.

The sweep was real, but the higher-timeframe structure was bearish, so it bought a pullback rather than a reversal. Reading the sweep alone would have suggested the opposite.

Common mistakes

Most bad liquidity reads come from one of five habits:

  • Treating every sweep as a reversal. Many sweeps are pauses inside a trend, as in the EUR/USD example.
  • Marking every high and low. A chart covered in pools says nothing. Keep the obvious ones: equal highs and lows, the last swing before a strong move, session extremes.
  • Deciding on wicks. A wick through a level is neither a reclaim nor a breakout until candles close.
  • Ignoring the higher timeframe. A sweep against the higher-timeframe structure is a pullback until structure says otherwise.
  • Forgetting that a taken pool is spent. Once a level is swept, its orders are gone. It can still act as support or resistance, but it is no longer a pool.

Step through a sweep

The simulator below walks through the four states of a pool: an active pool resting at prior highs, the sweep through it, a reclaim back inside the range, and the other outcome, where price accepts beyond the level and continues. It plays through on its own, and you can click any step to see it again.

The point to take from it: the same sweep can end in a reclaim or in acceptance, and only the closes after the sweep tell you which.

Stop orders pile up above the highs

Price tests the same high three times without breaking it. Short sellers place their stop losses just above it, and breakout traders put buy orders there too, so a pool of orders builds up.

How to map liquidity by hand on TradingView

You need no indicator for this. Horizontal lines and a higher-timeframe chart are enough.

  1. 1

    Start on the higher timeframe

    Open a timeframe four to six times your trading timeframe, for example 4 hours if you trade the 1-hour chart. Note the trend and mark its last swing high and low.

  2. 2

    Mark the obvious pools

    On your trading timeframe, draw horizontal lines at equal highs, equal lows, the previous day’s high and low, and the nearest round number. Stop at three or four lines on each side of price.

  3. 3

    Pick the likely draw

    Choose the nearest untouched pool in the direction of the higher-timeframe structure. If none qualifies, there is no draw, and no trade idea yet.

  4. 4

    Wait for the closes

    When price takes a pool, do nothing until candles close. Closes back inside followed by a failed retest make a sweep; several closes beyond make acceptance.

  5. 5

    Update the map

    Grey out the pool that was taken and look for the next one. A swept level is no longer a pool.

Institutional Imbalance Framework

How IIF tracks liquidity on a live chart

The Institutional Imbalance Framework keeps the map from the last step up to date for you. Its Liquidity Matrix splits the recent price range into rows and shows two columns: Active, the structural volume that has not been dealt with yet, and Filled, the volume that has already been swept or filled. In Pivots mode the Active column shows untested swing-point pools and the Filled column shows pivots that were swept; in Imbalances mode it does the same for fair value gap volume.

Rows where Active volume is high and Filled volume is low are marked as rebalance levels: the shortlist of levels with the strongest reason to be visited. The sweep itself comes from a separate signal. Block Sweep prints when price closes beyond an order block edge and then proves acceptance back inside it, with an optional CVMI pressure filter.

  • Liquidity Matrix: Active and Filled rows, sourced from pivots or from fair value gaps.
  • Rebalance levels: high Active, low Filled, marked automatically.
  • Block Sweep: a close beyond an order block, then a reclaim proven on closes.
  • Alerts for sweeps and the other events, including webhooks, so you do not have to watch the chart.
IIF on a BTC 12-hour chart, March to April 2024: the Liquidity Matrix Active and Filled columns at the right edge, price bouncing 9.5% from the rebalance level at 67,500 to the all-time high, then trading up into the level at 72,500 and falling 18%
IIF on BTC, 12-hour chart: the Liquidity Matrix columns on the right, and price turning at its rebalance levels (◆) as it reaches them.

Marking liquidity versus reading it

Marking levelsReading liquidity
Which poolsEvery high and low becomes a target.Only obvious, structurally relevant pools are kept.
The sweepAny wick beyond a level is read as a reversal.Sweep, reclaim and acceptance are read separately, on closes.
DirectionAny pool can be the target.The draw follows the higher-timeframe structure.
After the eventOld levels stay on the chart forever.Swept and accepted levels lose priority; the map is updated.

Questions about liquidity engineering

Is liquidity engineering real?

Stop and pending orders really do cluster around obvious highs, lows and round numbers, and price often moves fast through those levels because triggered stops become market orders. What is not proven is intent: the model does not show that anyone plans these moves. Treat it as a way to read charts, judged by how well it works for you, not as a fact about how markets are run.

What is engineered liquidity?

Engineered liquidity is a pool of orders that built up at one obvious price because the chart kept inviting traders to put them there: equal highs after several rejections, or a tight range under a round number. Traders say liquidity was engineered when price compressed into the level, drew in breakout entries and stops, and then ran through it. The term describes how a pool forms, not proof that anyone planned it.

What is the difference between a liquidity sweep and a stop hunt?

They describe the same event. A stop hunt is the older name, and it implies someone is deliberately hunting stops. A sweep describes only what happened: price traded through a level where stops were likely resting.

How do you trade a sweep and reclaim?

Wait for the sweep, then for closes back inside the prior range, then for a retest of the swept level that fails to close beyond it again. Only then does the sweep become a reversal idea, and only if it agrees with the higher-timeframe structure. The stop usually goes beyond the sweep’s extreme. None of this guarantees the trade works.

Is every liquidity sweep a reversal?

No. A sweep can lead to a reversal, a continuation or a range. Reclaim and acceptance after the event matter more than the sweep itself.

Which timeframe works best for liquidity?

The method works on any timeframe, but pools on higher timeframes hold more orders and matter more. A common approach is to find the draw on a timeframe four to six times higher than the one you trade, then read sweeps and closes on your own timeframe.

Is there an indicator for liquidity engineering on TradingView?

Several community scripts mark highs, lows and sweeps. IIF goes further: its Liquidity Matrix separates untested from already-swept liquidity, marks rebalance levels, and its Block Sweep signal waits for a proven reclaim on closes. You can also do everything in this guide by hand with horizontal lines.

Track these levels on your own chart

The Institutional Imbalance Framework marks structure, fair value gaps, order blocks, liquidity and imbalance pressure on TradingView, and keeps track of which levels are still active.

This guide is education about reading charts, not financial advice. The concepts describe how traders interpret price; none of them predicts the market, and trading carries a real risk of loss.