The first move of a session is not always the real one
Watch the London open long enough and a pattern emerges: within the first hour, price makes a decisive move in one direction — decisive enough to convince breakout traders and to trigger the stops resting beyond the Asian range. Then, with unsettling regularity, the move dies, reverses, and the opposite direction becomes the trend of the day.
ICT traders named this the Judas swing: the move that betrays you at the open. The framework's reading: it is a cheap way for a large participant to build a position — price is pushed into the obvious pool, the orders resting there are absorbed, and the move that follows goes the other way. That is an inference from price, not an observation of anyone's intent.
The mechanics: sessions build their own liquidity
Every session inherits a range from the previous one, and every range has two shelves of orders: stops above the high, stops below the low. The session open brings the day's first surge in participation — which is when a shelf of resting orders can be taken.
- Asia builds the range. Low volatility accumulates positions and defines clean extremes — the reference pool for London. This is the accumulation leg of the AMD cycle.
- London runs one side. The Judas swing takes the Asian high or low; the model looks for it within the first 90 minutes. In this reading, the stops provide the counterparty volume for a larger position.
- The day can deliver the other way. Once the pool is taken, the model expects a displacement in the other direction — toward the opposite side of the map.
- New York can repeat the pattern against the London range, during the busiest hours of the day.
In this model, a session does not simply "reverse": it takes liquidity first, then moves.
Trading the Judas swing without becoming its victim
Rule 1 — Never trade the first break
The initial run through the session extreme is the move this model expects to fail. Let it happen. Your setup begins after the raid, not during it.
Rule 2 — Demand displacement back inside
A valid Judas reversal closes back through the swept level and leaves a fair value gap in the new direction. No close back inside, no trade — price may simply be trending through the level.
Rule 3 — Respect the delivery window
The model expects a session sweep to resolve in the next session: an Asia raid during London, a London raid during New York. A sweep that fires outside its window is not a setup in this framework. Matching instrument to session matters too — see choosing the best trading session for your asset.
Rule 4 — Anchor the context
A Judas swing has more context behind it when the raid also takes a daily-map level — the previous day low, or a deviation below the Midnight Open — so that session liquidity and daily liquidity point the same way.
Key takeaways
- The Judas swing is a false move at the session open that raids the prior session's range — read as deliberate, not observed as such.
- In this model, each session's range is the next session's first target: Asia for London, London for New York.
- Trade only the confirmed reversal: close back inside plus displacement.
- Strict delivery windows and daily-level confluence separate setups from noise.
From pattern to process
The Judas swing rewards patience and punishes improvisation. The hard part is operational: tracking three session ranges in server time across DST changes, verifying the sweep geometry, and refusing every tempting-but-unconfirmed break. Encoding those rules — as SWEEP PROTOCOL does with its session sweep engine and next-session delivery lock — removes the improvisation; the decision to take the confirmed signal stays yours.
What this article does not do
- No prediction. A setup that meets every condition described here can fail.
- Weak contexts. Around session opens, scheduled releases and thin hours, levels can be traded through and fills can be worse than planned.
- No recommendation. Nothing here is an instruction to trade a specific instrument or level.