ADVANCED FOREX · ICT · LESSON 10
ICT Judas Swing: False Moves and Liquidity Sweeps
Study potential false moves around session liquidity and learn how to evaluate confirmation without treating any setup as certain.
What is a Judas Swing?
A Judas Swing is an ICT term for a deceptive early move that may draw traders into one direction before price moves the other way. It is a study framework, not a guaranteed pattern.
Session context
Observe the Asian range and the opening phases of London or New York. Session timing varies with daylight saving time. Do not assume that a reversal must happen at a fixed clock time.
Bullish example
Price trades below an obvious prior low, then reclaims that level with strong upward displacement. A trader may mark the swept low, subsequent market structure shift, and possible retracement area. The idea is invalidated if the setup fails its defined structure or risk conditions.
Bearish example
Price briefly trades above an obvious prior high, then moves lower with displacement. Mark the swept high, possible market structure shift, and a defined invalidation level rather than predicting a reversal solely from the sweep.
Confirmation checklist
Identify a clear liquidity pool; note the session and higher-timeframe context; wait for a sweep and meaningful displacement; assess structure; define invalidation before any simulated entry. A sweep alone is not a trade signal.
Risk management
Practice in a demo account first. Position size should be based on predefined risk and stop distance. Spreads, slippage and news volatility can invalidate a seemingly clear setup. Avoid promising returns.
Chart practice
On a historical 15-minute chart, mark the prior session high and low. Move to a lower timeframe only if useful. Record whether price swept a level, whether displacement occurred, and whether a structure shift followed. Log examples where the pattern failed too.
Knowledge check
- Does a liquidity sweep alone confirm a Judas Swing? No. Seek context and confirmation.
- Why do session times change during the year? Daylight saving time.
- What must be defined before a simulated entry? Invalidation and risk.
Judas Swing: deeper chart walkthrough
A Judas Swing is a proposed false directional move around a session transition, not a promise that price will reverse. Start with a clearly marked overnight or Asian-session range. Record its high, low, and midpoint before London activity begins. When price moves above the range high, ask whether the breakout holds or whether candles quickly close back inside the range. A wick above the high alone is not sufficient evidence: volatility and spread expansion can produce similar shapes without a reliable reversal.
For a hypothetical bearish case, suppose EUR/USD trades overnight between 1.0800 and 1.0830. London opens and briefly reaches 1.0840, then closes below 1.0830. This suggests that buy-side liquidity above the range may have been tested. A trader could wait for a lower-timeframe bearish market structure shift and a retracement into an imbalance before considering a simulated short. The invalidation level should be defined above the sweep extreme with a realistic buffer, not placed at an arbitrary fixed number of pips. A potential target might be the range midpoint or opposing sell-side liquidity, but the reward-to-risk ratio must be checked before entry.
For a hypothetical bullish case, price first sweeps below an established range low and then reclaims that level. A bullish structure shift can add confirmation, but the reclaim may still fail. The setup should be skipped if the range is poorly defined, if an important announcement is imminent, or if the entry is so late that the next liquidity target offers little room. Compare examples across multiple sessions rather than treating one chart as proof.
A disciplined review records the session date, timezone, daylight-saving adjustment, range boundaries, sweep candle, confirmation candle, spread, entry rationale, invalidation, target, and outcome. Include examples where price continued in the breakout direction. Those failures help reveal whether the setup is genuinely repeatable or merely attractive in hindsight. Practise first with historical charts and demo execution; leverage can magnify losses even when the chart interpretation appears reasonable.
Try a structured exercise: select twenty London sessions, mark the overnight high and low without looking at future candles, and label each sweep as reversal, continuation, or unclear. Record whether a displacement candle and market structure shift occurred before the proposed entry. Then compare the average outcome of confirmed and unconfirmed examples. This separates an observable trading process from a story constructed after price has already moved.
Applied analysis: testing the lesson in context
The following exercise develops the specific decisions involved in ict judas swing: false moves and liquidity sweeps. It is a hypothetical training workflow, not a prediction or an instruction to place a live trade. Keep the market, time zone, instrument, observation window and data source fixed before evaluating the idea. Separate what the chart shows from the interpretation assigned to it; two analysts can label the same sequence differently without either label being a verified market mechanism.
Case step 1: What is a Judas Swing?
Start with the lesson's what is a judas swing? component. Source observation: A Judas Swing is an ICT term for a deceptive early move that may draw traders into one direction before price moves the other way. It is a study framework, not a guaranteed pattern. Record the exact candle or pivot at which this information first became available. If confirmation depends on a later close, mark that later close as the earliest legitimate decision point. A visually compelling retrospective drawing is not sufficient evidence that the setup was identifiable in real time.
Now construct a counterexample for what is a judas swing?: imagine the price initially behaves as the lesson suggests but then fails to follow through. Write the invalidation condition as an observable price or time event, not as a vague change in confidence. Compare two annotated screenshots, one before the proposed confirmation and one after it. Explain what genuinely changed in the available evidence. For a trading-system study, record spread, slippage, position size, and whether the proposed stop could have been filled at the assumed price.
Case step 2: Session context
Start with the lesson's session context component. Source observation: Observe the Asian range and the opening phases of London or New York. Session timing varies with daylight saving time. Record the exact candle or pivot at which this information first became available. If confirmation depends on a later close, mark that later close as the earliest legitimate decision point. A visually compelling retrospective drawing is not sufficient evidence that the setup was identifiable in real time.
Now construct a counterexample for session context: imagine the price initially behaves as the lesson suggests but then fails to follow through. Write the invalidation condition as an observable price or time event, not as a vague change in confidence. Compare two annotated screenshots, one before the proposed confirmation and one after it. Explain what genuinely changed in the available evidence. For a trading-system study, record spread, slippage, position size, and whether the proposed stop could have been filled at the assumed price.
Case step 3: Bullish example
Start with the lesson's bullish example component. Source observation: Price trades below an obvious prior low, then reclaims that level with strong upward displacement. A trader may mark the swept low, subsequent market structure shift, and possible retracement area. Record the exact candle or pivot at which this information first became available. If confirmation depends on a later close, mark that later close as the earliest legitimate decision point. A visually compelling retrospective drawing is not sufficient evidence that the setup was identifiable in real time.
Now construct a counterexample for bullish example: imagine the price initially behaves as the lesson suggests but then fails to follow through. Write the invalidation condition as an observable price or time event, not as a vague change in confidence. Compare two annotated screenshots, one before the proposed confirmation and one after it. Explain what genuinely changed in the available evidence. For a trading-system study, record spread, slippage, position size, and whether the proposed stop could have been filled at the assumed price.
Evidence record and independent assessment
Create a small research log specifically labelled “ICT Judas Swing: False Moves and Liquidity Sweeps”. For each candidate observation, store its date, instrument, session, timeframe, setup definition, entry eligibility, invalidation level, expected costs, and actual subsequent path. Include candidates that never triggered, rather than selecting only attractive examples. Compare at least two market regimes and note whether the interpretation changes when a nearby swing anchor or session boundary is chosen. If it does, classify the result as sensitive to analyst discretion rather than robust evidence.
Finally, write a three-part conclusion about ict judas swing: false moves and liquidity sweeps: (1) which elements can be verified directly from historical prices, (2) which elements are hypotheses about participants or future behavior, and (3) what observation would cause you to reject the hypothesis. The exercise is complete only when a second reader could reproduce your markings using the written rules. Do not infer a profitable edge from a single worked example; that requires a separately designed, cost-aware and out-of-sample evaluation.