The Universal ICT Entry Checklist: One Framework for Every Model

What Is an ICT Entry Checklist?

An ICT entry checklist is a fixed set of pre-trade questions every setup must answer before you commit risk. Whatever the model, a valid entry passes the same core checks: bias, location, liquidity, time, confirmation, risk, and invalidation. If one core check fails, you skip the trade.

The insight behind a universal ICT entry checklist is that the model is just the trigger. A Silver Bullet, an Order Block tap, and an FVG entry look different on the chart, but the skeleton underneath is identical. Standardizing that skeleton is what separates a repeatable process from impulsive clicking.

Below is the checklist organized in seven layers, then a copy-usable version, scoring rules for A+ versus B setups, how it adapts per model, and a worked example run start to finish.

The 7 Layers of the ICT Entry Checklist

Work these top-down. Each layer is a gate — you only drop to the next once the current one passes. The order matters: bias and location filter out most of the noise before you ever look for a trigger.

1. HTF Bias and Draw on Liquidity

What is the daily and 4H bias, and where is the Draw on Liquidity? Price is always delivered toward a magnet — an old high, an old low, a resting pool. Which side is price reaching for, and am I trading toward it? If your entry fights the higher-timeframe draw, it is countertrend by definition and the check fails.

2. Premium / Discount Location

Am I buying in discount or selling in premium of the current dealing range? Mark the range from a clean swing high to swing low, split it at the 50% Equilibrium, and locate price. Longs belong below equilibrium (discount); shorts belong above it (premium). Buying in premium or selling in discount means you are paying a bad price even when the direction is right.

3. Liquidity

What pool was just taken, and is there liquidity to target? A high-quality entry usually follows a Liquidity Sweep — stops above equal highs or below equal lows get run, then price rejects. Then confirm a destination: a clean opposing pool for price to draw toward. No source pool swept, or no target to reach, means weak fuel on both ends.

4. Time

Am I inside a valid window? ICT entries cluster in defined Kill Zones — London open, New York AM, and the afternoon window — plus macro times. Dead sessions (late NY, mid-Asia drift) produce low-displacement chop that mimics setups and fails to follow through. If it is a dead window, the check fails even if price looks perfect.

5. Confirmation

Did the trigger actually print? The confirmation stack is: a sweep of liquidity, then Displacement or a market-structure shift (MSS) in your direction, then a clean PD Array to enter on — an order block or a fair value gap left by that displacement. No displacement means no institutional intent; you are guessing at a reversal instead of reading one.

6. Risk

Is the structural stop defined and the reward-to-risk at or above my minimum? The stop goes beyond the structure that invalidates the idea — past the swept wick, not an arbitrary dollar figure. Measure from there to the target pool.

If R:R is below your floor (many traders use 1:2 or better), the setup fails on math regardless of how it looks. Then size the position so the stop distance equals a fixed percent of the account.

7. Invalidation

What specifically kills this idea? Name the price and the condition before you enter — "a 15m close back above the swept high" or "price fills the FVG and keeps going." An entry without a written invalidation is an entry you will rationalize holding. This check is what makes the stop a decision instead of a hope.

The Copy-Usable ICT Entry Checklist

Keep this on a sticky note or in your journal template. Run it top to bottom, out loud if it helps:

1. Bias: Daily/4H direction is ___ and I am trading toward the draw on liquidity. (Y/N)
2. Location: Entry is in discount for longs / premium for shorts of the dealing range. (Y/N)
3. Liquidity: A pool was just swept, and a clear opposing pool exists as a target. (Y/N)
4. Time: I am in a kill zone or valid macro window, not a dead session. (Y/N)
5. Confirmation: Sweep + displacement/MSS + a PD array (OB or FVG) to enter on. (Y/N)
6. Risk: Structural stop is defined, R:R is at or above my minimum, size is set. (Y/N)
7. Invalidation: I have written the exact price/condition that kills this trade. (Y/N)

How to Use It: One Filter, Pass or Skip

The checklist is a filter, not a scorecard you negotiate with. The rule is simple: all seven core checks must pass, or you skip. A setup that nails bias, location, and confirmation but fails the time check is still a skip — chop outside kill zones is where clean-looking patterns go to die.

This is deliberately strict because the enemy is your own impatience, not the market. When a chart is mid-move and you feel the urge to "just get in," the checklist forces the pause that separates a trade from a reaction. If running the seven questions takes thirty seconds and one answer is No, you just avoided a low-quality entry for free.

Over time the filter also fixes overtrading. Most accounts do not bleed from bad entries so much as from too many marginal ones. A hard pass/skip rule caps how many trades clear the bar in a session, which naturally concentrates your risk into the few setups where every layer lines up. Fewer, cleaner entries is the point, not a side effect.

Scoring A+ vs B Setups

Passing all seven is the minimum bar for any trade. Grade quality by how much confluence stacks on top:

• A+ setup: passes all seven, and multiple confluences align — HTF and LTF bias agree, the entry sits inside a nested PD array (OB overlapping an FVG), displacement was strong, and R:R is 1:3 or better. Size these at your normal risk.
• B setup: passes all seven, but confluence is thin — bias is mixed across timeframes, displacement was modest, or R:R barely clears your floor. Either skip it or take reduced size, and never let a B masquerade as an A.

The count of aligned confluences is your grade. More independent reasons to be in the trade — location, swept liquidity, time, structure, a clean array — means a higher-probability entry. Fewer reasons means a coin-flip you dressed up.

How the Checklist Adapts to Any Model

The power of a universal checklist is that it does not change per strategy — only the confirmation layer's specifics do. A Silver Bullet entry and an order block entry pass the same skeleton:

The model tells you where the trigger lives; the checklist tells you whether the trigger is worth trading. Swap the confirmation column for any other entry — breaker, OTE zone, CISD, Judas swing reversal — and the other six checks are unchanged.

A Worked Example Through the Checklist

Take a realistic BTCUSDT scenario. Daily is bullish and the obvious draw is an old high near 72,000 that has not been taken. That is check one: bias up, draw sits above, we want longs toward it.

Overnight, price drops into the lower third of the 4H dealing range, below the 50% equilibrium around 68,400. Check two passes — we are hunting a long in discount.

During the London open kill zone, price wicks below a shelf of equal lows at 67,900, sweeping sell-side liquidity, then snaps back. Check three passes: a pool was taken and the 72,000 target remains. Check four passes too — we are inside the London window, not a dead session.

On the 5-minute, that reclaim prints strong displacement up through the prior swing (an MSS), leaving a clean FVG between 68,100 and 68,300. Price pulls back into that gap. Check five passes: sweep, displacement, and a PD array to enter on.

We long the FVG at 68,200 with the stop below the swept wick at 67,850 — check six: risk is roughly 350 points, target 72,000 is about 3,800 points, so R:R clears 1:5 easily. Check seven: invalidation is a 5m close back below 67,850, which would say the sweep failed.

All seven pass, confluence is deep, and this grades as an A+ long.

Printable Use and Common Mistakes

Print the seven-item list and keep it beside your charts, or paste it as the top block of every journal entry. Logging the Y/N answers per trade enforces the filter in real time, and it builds a dataset.

After fifty trades you can review which check you most often skip on losers — and that pattern is usually where your edge is leaking.

The mistakes that break the checklist are behavioral, not technical:

• Skipping checks when impatient: a fast-moving chart tempts you to enter on confirmation alone and backfill bias and location afterward. That is not running the checklist; it is justifying a trade you already took.
• Taking B setups as A: quietly upgrading a thin-confluence trade to full size because you "feel" it. The count of confluences is the grade — feelings do not add a confluence.
• Negotiating a failed check: deciding the dead-session time check "doesn't matter this once." The filter only works if a No is final.
• No written invalidation: entering without naming the kill price, then widening the stop live.

A scanner can surface candidates that already show a swept pool and fresh displacement, but the ict entry checklist is yours to run — the tool narrows the field, you make the pass/skip call on every one of the seven layers.

Frequently Asked Questions

How many checks must pass to take an ICT entry?

All seven core checks. The ict entry checklist is a filter, not a points system you average out. If bias, location, liquidity, time, confirmation, risk, and invalidation are not all satisfied, you skip. Grading A+ versus B happens only among setups that already pass all seven, based on how much extra confluence stacks on top.

Does the checklist change for different ICT models?

No. Six of the seven checks are identical across every model. Only the confirmation layer's specifics differ — a Silver Bullet uses a session FVG, an order block entry uses a return to an unmitigated block. The bias, location, liquidity, time, risk, and invalidation checks stay the same regardless of trigger.

What is the single most-skipped check?

Time. Traders find a clean pattern outside a kill zone and take it anyway, then wonder why it never displaces. Dead sessions produce low-conviction moves that imitate setups. Enforcing the time check alone removes a large slice of low-quality entries with no chart-reading skill required.

Can I automate the ICT entry checklist?

Partly. A scanner can flag the mechanical conditions — a swept pool, displacement, a fresh PD array in the right session. But bias interpretation, R:R judgment, and writing the invalidation are decisions. Automation narrows the candidate list; you still run the seven layers before committing risk.

Related query paths

Work outward from the checklist into the concepts each layer depends on, in the order a trader learns them:

• Draw on Liquidity (DOL) in ICT — nail the bias layer by predicting where price is being delivered.
• How to Draw Premium & Discount Zones (ICT Guide) — mark the dealing range so the location check is objective.
• PD Array ICT Explained: A Trader's Guide to Premium & Discount — understand the arrays your confirmation layer enters on.
• ICT Kill Zones Complete Guide: A Pro Trader's Framework — pass the time check by trading only valid windows.
• ICT Risk Management Framework — turn the risk and invalidation layers into a repeatable system.
• Build a Complete ICT Trading Model — assemble the checklist into a full step-by-step model.
• Do ICT Kill Zones Still Work in 2026? A Data-Driven Reality Check — a related angle on do ict kill zones still work.