How Do You Scan for CISD Setups?
You scan for CISD setups with a CISD scanner that watches every pair and timeframe for one sequence: a reverse candle, a body-level break, and a resulting fair value gap. Fire all three in order and it flags a confirmed change in state of delivery.
Doing this by eye means staring at dozens of charts across multiple sessions, waiting for a fast three-step pattern to complete before it scrolls off the screen. Automation removes the watching so you only judge the flags that actually printed.
Recap: What a CISD Setup Is Before You Scan for It
A change in state of delivery (CISD) marks the moment order flow flips from bearish to bullish delivery, or the reverse. It is the ICT community's precise version of a market-structure shift (MSS). Before you can scan for it, you need the exact three-part definition the scanner encodes.
- The reverse candle(s) — the last opposing-close candle (or run of them) at the extreme of the prior move, marking where delivery stalled.
- The body-level break — price closes back through the open/body level of that reverse candle, not just its wick. The body close is what confirms intent, because a wick alone can be noise.
- The resulting fair value gap — the break is delivered with enough force to leave a Fair Value Gap (FVG), the imbalance that separates a real displacement from a slow drift.
All three must land for the shift to count. A break with no FVG is weak delivery; an FVG with no clean body break through the reverse candle is just momentum. For the full anatomy, read the dedicated definition below in the related paths — this guide stays on how to find it, not what it is.
Why Manual CISD Scanning Doesn't Scale
The sequence is precise, fast, and easy to see in hindsight — which is exactly what makes it painful to catch live by hand. A manual workflow asks you to hold three moving conditions in your head across a large watchlist.
Consider the arithmetic. If you follow 40 pairs on the 4H, 1D, and 1W, that is 120 chart-timeframe combinations. To catch a CISD as it forms, you would re-check each one at every candle close: reverse candle, then body break, then gap. Miss the close and the setup is already old.
You also have to be honest about the body-versus-wick distinction on every chart, resist marking a shift that has not confirmed, and remember which reverse-candle level you were tracking on each pair. Bias and fatigue creep in fast. A scanner applies the same rule to all 120 combinations the instant each candle closes, without shortcuts.
What a CISD Scanner Detects
A purpose-built CISD scanner does not "predict" a shift — it constructs one from closed candles and surfaces the geometry. LiquidityScan's CISD engine runs on the 4H, 1D, and 1W timeframes and looks for the full three-step build, then renders it on the chart.
The MSS construction and FVG confirmation
The engine identifies the reverse candle, waits for a body-level break through it, and requires the resulting fair value gap. Only when the FVG is present does it register the event as a confirmed MSS. That FVG requirement is the filter that separates a genuine change in state of delivery from an ordinary structure break with no displacement behind it.
This is where a rule beats a human. A trader eyeing a chart is tempted to call the shift the moment price pokes through the reverse candle's high or low. The engine refuses until the body closes through and the gap prints, because delivery that fails to leave imbalance tends to get filled and reverse.
Encoding the FVG as a hard condition removes the most common false positive in manual CISD marking.
The levels it draws
For each detected event the scanner paints three things you can act on:
- The MSS level — the body level whose break confirmed the shift, now a reference the market has already respected once.
- A 50% Fibonacci — the equilibrium of the move, the classic Optimal Trade Entry (OTE)-adjacent zone traders watch for a retrace.
- A proximity zone — the band around the level where a pullback becomes actionable, so you know when price is "back in range" without measuring by hand.
Historical CISD events become chart markers, so you can scroll back and see how a pair has delivered these shifts before. The engine keeps a maximum of three active events per symbol and timeframe, and each event expires after 200 candles — old, stale structure is cleared rather than left cluttering the chart.
Why no-repaint and closed candles matter
Every LiquidityScan engine, including CISD, evaluates confirmed, closed candles only — the live forming bar is always dropped. This matters more here than almost anywhere, because the whole setup hinges on a body close through a level.
An indicator that reads the in-progress candle can show a "break" that un-prints when the candle closes back inside. A closed-candle CISD flag does not repaint: once it appears, the structure that produced it already happened.
The "High-Prob MSS" Classification in the NY AM Window
Not every change in state of delivery carries the same weight, and the scanner reflects that with a time-based tag. When the breakout candle closes inside the New York AM window — roughly 09:00 to 14:00 New York time — the event is classified "High-Prob MSS". Outside that window it is simply labelled "MSS."
The logic is straightforward ICT: the NY AM session is a primary kill zone, when volume and institutional participation concentrate and delivery is most likely to be intentional rather than thin drift. A body break that leaves an FVG during that window is more likely to be real order flow.
The tag is a context filter, not a promise — it tells you the shift fired during a high-participation period, and you still supply the judgment.
Being able to scan specifically for High-Prob MSS events is one of the clearest reasons to use a CISD scanner over manual marking: the time-of-day classification is applied automatically to every flag, so you can prioritize the sessions that historically deliver cleaner structure.
Practically, this lets you triage. A feed full of CISD events across a large watchlist is more useful when you can immediately see which shifts printed inside the NY AM kill zone versus during thin Asian hours.
You are not discarding the plain MSS tags — a weekly MSS carries weight regardless of the intraday clock — but on the 4H timeframe the High-Prob tag is a fast first filter for where to spend attention.
A Workflow: From Scanner Flag to Your Own Execution
The CISD scanner visualises structure. It does not grade win or loss, and it does not hand you an entry, stop, or target — that is your job. Here is an honest end-to-end workflow.
Step 1 — Read the flag and its context
When a CISD event appears, check the timeframe, the direction of the shift, and whether it is tagged High-Prob MSS. A weekly bullish MSS is a very different context to a 4H MSS printed outside the kill zone. Confirm the flag agrees with your higher-timeframe Draw on Liquidity (DOL) before you care about it.
Step 2 — Wait for the retrace into the zone
The signal is the beginning, not the trigger. Let price pull back toward the MSS level, the 50% Fib, and the proximity zone the scanner drew. Chasing the breakout candle itself gives you a poor location; the retrace into equilibrium is where the reward-to-risk becomes reasonable.
Step 3 — Execute with your own risk parameters
Define your entry inside the zone, place your stop beyond the structure that would invalidate the shift, and set targets against the next liquidity pool — all decided by you. The scanner has told you where a confirmed change in state of delivery occurred and where a pullback is actionable. It has not told you to trade.
A worked example
Say the CISD scanner flags a bullish MSS on BTCUSDT 4H. The market had been selling off, so the reverse candle is the last down-close candle at the swing low. A following green candle then closes above that reverse candle's body at roughly 61,800, and the displacement leaves a fair value gap between about 61,300 and 61,650.
Because that breakout candle closed at 10:30 New York time, the engine tags it "High-Prob MSS." It draws the MSS level at 61,800, a 50% Fib near 61,500, and a proximity zone around the FVG.
You do nothing on the breakout. Two candles later price retraces into the 61,300–61,650 gap and taps the 50% Fib. That is your context: a confirmed shift, a NY-AM tag, and price back in the zone.
You decide an entry near 61,500, a stop below the reverse-candle low that would negate the structure, and a first target at the buy-side liquidity above the prior swing high. If price had closed back below the reverse-candle low, the shift is failing and you stand aside — the scanner shows the structure, you read whether it holds.
Manual CISD Spotting vs a CISD Scanner
| Dimension | Manual CISD spotting | CISD scanner |
|---|---|---|
| Coverage | The handful of charts you can watch at once | Every pair on 4H, 1D, 1W simultaneously |
| Sequence check | You hold reverse-candle → break → FVG in your head | All three conditions enforced by rule, in order |
| Body vs wick | Judged by eye; easy to fudge | Requires a closed-body break, no exceptions |
| Repaint risk | You may mark a "break" that un-prints intrabar | Closed-candle only; flags do not repaint |
| NY-AM classification | You check the clock manually per setup | Auto-tagged High-Prob MSS when in the window |
| Levels drawn | You measure the MSS level, 50%, and zone by hand | MSS level, 50% Fib, and proximity zone rendered |
| Outcome grading | None either way — you judge context | None — it visualises structure, not win/loss |
The table makes the division of labor clear. A CISD scanner buys you coverage, consistency, and no-repaint discipline. The trade decision — entry, stop, target, and whether the context deserves risk at all — stays entirely with you.
Frequently Asked Questions
Does a CISD scanner tell me when to buy or sell?
No. LiquidityScan's CISD engine visualises structure: it renders the MSS level, a 50% Fib, and a proximity zone, and tags NY-AM events as High-Prob MSS. It does not grade win or loss and gives no entry, stop, or target. You supply the risk decision and read whether the shift holds.
What timeframes does the CISD scanner run on?
The CISD engine detects on the 4H, 1D, and 1W timeframes. It keeps a maximum of three active events per symbol and timeframe, and each event expires after 200 candles so stale structure is cleared automatically rather than lingering on the chart.
What makes an event "High-Prob MSS" instead of just "MSS"?
Timing. If the breakout candle closes inside the New York AM window — about 09:00 to 14:00 NY time — the shift is tagged High-Prob MSS, because that kill zone concentrates institutional participation. Outside that window it is labelled MSS. The tag is context, not a performance guarantee.
Can CISD flags disappear or repaint after they appear?
The flags do not repaint. Detection runs on confirmed, closed candles only, so a CISD event reflects a body break that has already completed. Events do expire after 200 candles by design, and only the three most recent per symbol and timeframe are kept active, but a printed flag is stable.
Related query paths
Scan for the setup here, then deepen the underlying concepts in query-journey order — from the CISD definition through MSS mechanics to the full stop-hunt-to-reversal application.
- What Is CISD in ICT Trading? (Change in State of Delivery) — the full definition of the setup this scanner detects.
- CHoCH vs MSS: The Real Difference in ICT — why the body-break MSS the engine flags is not the same as a CHoCH.
- What Is a Fair Value Gap (FVG)? — the imbalance that confirms real displacement behind the break.
- A Precise New York AM Kill Zone Strategy for ICT Traders — the session behind the High-Prob MSS classification.
- Liquidity Sweep Then MSS: Reversal Guide — how a CISD fits the full stop-hunt-to-reversal sequence.
- How the LiquidityScan Scanner Works — how closed candles become a detected, no-repaint flag.
- How to Catch Asian-Range Sweeps Every Session — a related angle on asian range sweep scanner.