ICT Entry Model (Standard Sequence + Targets & Narrative)
The ICT Entry Model is a systematic execution framework built around a repeatable narrative: price raids liquidity, displaces with intent, confirms a structure shift (MSS/CHoCH or BOS depending on context), retraces into a PD array (FVG/OB/Breaker/Mitigation), then delivers to a target liquidity pool. It must be applied with top-down context (weekly/daily profile, day-of-week tendencies, news risk) and should continuously cycle across timeframes to refine bias, identify likely targets, and track how price respects or inverts PD arrays.
Definition
The ICT Entry Model is an event-sequence approach to entering trades: (1) Identify liquidity, (2) Wait for a raid/sweep, (3) Confirm displacement away from the raid, (4) Confirm structure (MSS/CHoCH for reversals or BOS for continuation), (5) Enter on retracement into a PD array at value (premium/discount), and (6) Target opposing liquidity. The model is not a single candle pattern; it is a narrative process that answers: What is price doing, why, and where is it likely delivering next?
Why It Matters
Most losing trades come from entering without narrative confirmation (no raid, no displacement, no structure, no value entry). The ICT Entry Model enforces patience and clarity: you stop guessing direction and instead trade after the market reveals intent. It standardizes stop placement (beyond the raid), improves R:R via PD array entries, and provides a structured way to define targets (internal then external liquidity). Adding weekly/daily profile context and news/day-of-week awareness improves selectivity and prevents trading random volatility.
How to Identify
- (Weekly + Daily Profile): Identify the current weekly and daily context: is price in continuation or reversal conditions (e.g., weekly dealing range extremes, prior week high/low, PDH/PDL, weekly open)?
- (Day-of-Week): Note the day of the week and whether early-week expansion may set up mid-week reversal/continuation; avoid forcing a profile before confirmation.
- (News Filter): Check whether high-impact news is scheduled during the intended execution window; expect engineered volatility around those events.
- (HTF PD Arrays): Mark relevant PD arrays on HTF (daily/4H/1H) and note whether price is respecting them (holding) or inverting them (breaking and reusing as opposite).
- (Liquidity Map): Mark obvious internal/external liquidity on the execution TF: equal highs/lows, prior session highs/lows, PDH/PDL, weekly levels.
- (Raid): Wait for price to trade through a liquidity pool (sweep/raid) and then reject back inside (or show immediate reversal intent).
- (Displacement): Confirm a strong impulsive move away from the raid (large bodies, reduced overlap, clears an internal level).
- (Structure Confirmation): Confirm MSS/CHoCH for reversal context OR BOS for continuation context on the execution timeframe.
- (PD Array for Entry): Identify the PD array created/validated by displacement (FVG, OB, Breaker, Mitigation). Align it with premium/discount and HTF PD arrays.
- (Targets): Define internal target(s) and external target(s) before entry (nearest swing/internal liquidity first, then external liquidity like PDH/PDL/equal highs/lows/weekly highs/lows).
How to Trade
- Prefer execution during high-liquidity windows (London/NY killzones). Outside these windows, reduce size or tighten criteria.
- Ask: What is price doing? Is it accumulating, manipulating, or delivering? Do not trade without a coherent narrative that aligns HTF → LTF.
- Require a clear liquidity raid first (don’t trade the middle of ranges).
- Require displacement away from the raid; do not chase the displacement candle.
- If the model is reversal-based, require MSS/CHoCH. If continuation-based, require BOS with protected swing intact.
- Enter on retracement into the PD array (FVG/OB/Breaker/Mitigation) at value (bullish in discount, bearish in premium).
- Place stop beyond the raid extreme (below sweep low for longs, above sweep high for shorts).
- Target internal liquidity first (nearest swing high/low, internal equal highs/lows, session midpoint/EQ reactions), then external liquidity (PDH/PDL, weekly highs/lows, prior week high/low, range extremes).
- If price breaks through your PD array with acceptance and later retests it from the other side, treat it as an inversion signal and adjust bias/targets.
- Reduce risk after internal target is hit; scale partials at internal liquidity; hold runners only if narrative still supports delivery to external liquidity.
- Re-evaluate bias and targets across timeframes after each major move (raid, displacement, target hit, PD array inversion).
Common Confusions
IF you entered a PD array without a prior raid + displacement + structure confirmation THEN it is not the ICT Entry Model (it is a standalone zone trade).
IF the model is reversal-based (trend was down, then breaks up) THEN require MSS/CHoCH. IF the model is continuation-based (trend already up, breaks prior high again) THEN BOS is more relevant.
IF price breaks through a PD array with acceptance AND later retests it from the other side THEN it is inversion and bias should be updated; a normal retracement respects the PD array boundary and rejects.
IF price sweeps liquidity but does not displace away and confirm structure THEN the sweep may be continuation, not reversal; wait for displacement + MSS.
Explore this concept in Aurora X
Interactive visual examples, AI-powered explanations, and a full library of 90+ ICT concepts.
Try Aurora X FreeRelated Concepts
More Entry Model Concepts
Educational resource only. Not financial advice. Trading involves substantial risk of loss.