ICT CISD + Order Block on TradingView: The Full Combined Framework

If you have ever been at an order block, watched price touch it, and then watched it blow straight through - you already know the problem. The OB was real. The setup looked correct. And it still failed.

The reason is almost always the same: you entered at the location without waiting for confirmation that the location was active. Order blocks are not guaranteed reversal zones. They are potential reversal zones. CISD is what converts potential into confirmed.

Order Blocks and CISD Are Not Two Concepts - They Are One Trade

Most ICT education presents order blocks in one section and CISD in another. This framing creates the false impression that they are separate tools you can use independently. They are not. They are two parts of the same entry framework.

The order block is the location: the price level where institutional orders were placed and where the market is likely to react when price returns. CISD is the confirmation: the structural close on the lower timeframe that confirms the reaction has started and delivery mode has shifted.

The Full ICT OB + CISD Sequence

The complete sequence has four steps. Each one must be present for the setup to be valid. Skipping any step degrades the probability significantly.

1. 1.HTF identifies an unmitigated order block - a clear last opposing candle before a strong displacement move on the 1H, 4H, or daily chart. The OB zone is the body of that candle (open to close).
2. 2.Price returns to the OB zone - it pulls back from the displacement move and re-enters the OB body. This is the retracement into the institutional order area.
3. 3.A liquidity sweep occurs at or near the OB - price takes out a nearby swing low (for bullish setups) or swing high (for bearish setups). This sweep is not optional. It is what activates the OB.
4. 4.CISD fires on the lower timeframe - after the sweep, a displacement candle on the 5m or 15m closes beyond the prior internal swing in the direction of the HTF move. This is the entry signal.

Every step matters. An OB that gets returned to but not swept is not yet confirmed. A sweep that occurs without a CISD close afterward is just a fake-out with no follow-through. The CISD is what locks the sequence in.

What Makes an Order Block CISD-Ready

Not every order block is ready for a CISD entry. The sweep is the filter. Before the sweep occurs, the OB is just a zone. After the sweep clears nearby liquidity, the conditions for a CISD entry exist.

This is the distinction traders miss most often. They see price at an order block and look for CISD without asking whether a sweep has happened. If it has not, any close they see is not a CISD - it is just lower timeframe noise inside a higher timeframe zone.

• →Unmitigated OB: price has not fully traded through the OB body since it formed
• →HTF bias aligned: daily or 4H structure supports the direction you are trading
• →Sweep confirmed: a nearby swing has been taken out at or near the OB zone
• →LTF displacement: a candle on the 5m or 15m closes beyond prior internal structure
• →CISD level defined: the close of the displacement candle marks your entry level

Bullish OB + CISD: Step-by-Step

Here is how the bullish version plays out in sequence. The bearish setup runs in reverse at the opposite pole.

1. 1.On the 1H chart, identify the last bearish candle before a strong bullish displacement. That candle's body is your bullish OB zone.
2. 2.Price pulls back into the OB zone. You are now in a wait state - not yet an entry.
3. 3.Price sweeps below the OB low or a nearby equal low. This clears buy-side liquidity and activates the OB.
4. 4.Drop to the 5m chart. Watch for a displacement candle that closes above the prior internal swing high. The close of that candle is the CISD level.
5. 5.Enter at market or on a retrace to the CISD level. Stop goes below the sweep low (the liquidity wick). Target is the HTF draw - the next liquidity pool or POI above.

How to Identify a CISD Inside an Order Block on TradingView

Manually identifying this on TradingView requires two chart windows or a multi-timeframe layout. Here is the process:

1. 1.Mark the OB zone on your 1H or 4H chart. Use a horizontal box from the open to close of the last opposing candle.
2. 2.Set an alert when price enters the OB zone - you do not need to watch the chart constantly.
3. 3.When price enters the zone, switch to the 5m chart. Identify the most recent internal swing high (for bullish) or swing low (for bearish) formed after the sweep.
4. 4.The CISD fires when a candle closes above that internal swing high (bullish) or below that internal swing low (bearish) with a body that covers meaningful distance - not a doji or small close.
5. 5.Mark a horizontal line at the close of that candle. That is your CISD level and your entry zone.

The key variable is the internal swing. You are not looking for a close above the HTF OB high - that would mean price has already moved significantly. You are looking for a close above the LTF internal structure formed after the sweep within the OB zone.

CISD at the OB Body vs CISD Below the OB

Where exactly the CISD fires within the OB zone changes your entry precision. There are two common scenarios:

Scenario one: the sweep dips just below the OB low, then CISD fires with price still inside or just below the OB body. This is the ideal scenario. Your entry is within the OB zone itself, stop is tight below the sweep wick, and the move back to the OB high and beyond is your immediate target.

Scenario two: the sweep runs deeper, price trades well below the OB, and CISD fires after a significant move. In this case you are entering after price has already made a portion of the move. Risk-reward is reduced and the stop is wider. This setup is still tradeable but lower quality than a CISD that fires inside the OB zone.

Why the OB Mitigates When CISD Fires

When CISD fires inside or near the order block, the OB begins to mitigate. Mitigation means the institutional orders sitting in that zone are being filled. The OB formed because institutions had unfilled buy orders at that price level. When price returns and delivery shifts back to the upside, those orders are executing.

This is significant for trade management. Once an OB is fully mitigated - price has traded through the entire OB body and continued - the zone is no longer valid as a future reference. For your current trade, mitigation means the OB is doing exactly what it was supposed to do. The CISD fire is the moment that mitigation process begins in earnest.

A fully mitigated OB should no longer be marked on your chart. It has been consumed. This is why you only trade unmitigated order blocks - and why the CISD is what triggers the mitigation process, not the initial touch of the zone.

OB Entry Alone vs CISD + OB Entry: The Comparison

The trade-off is clear: OB entry alone fires more often but with less confirmation. CISD + OB entry fires less often but with structural confirmation that the zone is active and the sweep has cleared opposing liquidity.

How SMC X Handles the OB + CISD Combination on TradingView

Manually correlating OB zones across timeframes while watching for a CISD on the lower timeframe is demanding. You need to track the HTF OB zone, monitor for the sweep, then switch to the LTF and watch for the displacement close - all in real time.

SMC X handles the confirmation layer automatically. When price returns to a key zone and the full sweep and displacement sequence completes, the CISD level prints on the TradingView chart. You see the OB context on the higher timeframe and the CISD entry level on the lower timeframe without manually cross-referencing both.

The indicator also fires alerts when a CISD prints, so you are not watching the chart waiting for the sequence to complete. You get notified when the entry has confirmed, then execute at the CISD level or on the next candle.

For traders already familiar with <a href='/blog/what-is-order-block-ict'>ICT order blocks</a> and the <a href='/blog/cisd-indicator-tradingview'>CISD concept</a>, SMC X removes the manual execution bottleneck. The logic is already built in - you apply the indicator and watch for the signal rather than watching for every variable in the sequence yourself.

If you have been studying these concepts and still struggling with timing, the issue is usually not understanding - it is execution speed. See <a href='/blog/why-ict-entries-keep-failing'>why ICT entries keep failing</a> and how the OB + CISD framework addresses the most common breakdown points.

Frequently Asked Questions

For more on this topic, see <a href='/blog/best-smc-indicator-tradingview-entry-signals'>the best SMC indicators for entry signals on TradingView</a> and how SMC X compares to manual setups.