Real-time label
State how many bars confirm a swing, when a break becomes valid, and whether later displacement may relabel an earlier zone.
Editorially reviewed 24 August 2026
Turn visual labels into timestamped rules
FIELD 07ICT and SMC labels can be useful shorthand, but terms such as order block, liquidity sweep, displacement, and market-structure shift often become obvious only after later candles appear. A valid test defines the level, confirmation, invalidation, and decision timestamp using information already closed at that moment.
Run an inter-rater exercise before measuring profit. Give two reviewers the same hidden-future chart segments and a written dictionary, then compare setup eligibility, entry time, stop, and reason codes. Low agreement indicates a specification problem that a larger backtest will only repeat faster.
State how many bars confirm a swing, when a break becomes valid, and whether later displacement may relabel an earlier zone.
A wick seen after the candle closes is not automatically an available limit fill. Model order placement time, quote side, and same-bar sequence.
Report agreement on opportunity detection as well as outcomes. Deleting disagreements hides discretion instead of measuring it.
A visual trading concept becomes testable when another reviewer can reproduce the same decision before the outcome appears.
ICT concepts — Fair Value Gaps, Order Blocks, Breaker Blocks, liquidity sweeps — are structural patterns. You mark them after price has already moved through the area. In a backtest where you can see the full chart, you naturally mark the FVG that price actually bounced from — and ignore the three other FVGs on the same chart that price blew right through.
What this looks like in practice: You see a Bearish FVG form at 1.0850. Price taps it and reverses +40 pips. You mark it as a valid setup and count the win. But if you had been trading in real time, there were two other FVGs at 1.0840 and 1.0860 that also formed — both of which would have been valid entries by the same rules, and both of which failed. You are not counting the failures because your brain automatically filters them out after seeing the outcome.
The fix: Bar-by-bar replay. Advance one candle at a time. When a FVG or OB forms, write "FVG at X, potential entry" before advancing. If it works, count it. If it fails, count that too. Your win rate will drop — but it will be honest.
ICT entries are precise: "enter at the 50% level of the FVG with a 10 pip stop." In backtesting, you look at a completed candle, see the exact low, and mark your entry there. But in real time, you do not know where the wick ends. You place a limit order, price wicks through it by 2 pips, stops you out, then reverses. That trade was a winner in your backtest and a loser in reality.
A common r/Forex trader reported: "ICT Judas Swing Model — profitable in backtesting. Whenever I trade it live, only SLs." That trader was entering at the theoretical perfect wick level that only exists in hindsight.
The fix: Add a 2-3 pip buffer to your entries during backtesting. If the setup requires price to wick exactly to 1.0850 to work, and it wicks to 1.0852 instead, that setup fails. Model the imprecision of real execution. If the strategy cannot survive a 2-pip margin of error, it was never a real edge.
The ICT 2022 Mentorship teaches concepts using selected examples that already worked. Every FVG entry video shows the one that bounced perfectly. Every liquidity-sweep-and-reverse video shows the one that reversed. You are learning from a curated dataset of winners.
When you then go backtest these concepts, your brain naturally seeks out the same patterns — the ones that match the highlight reel. But the market produces 5-10x more setups that almost match the pattern but fail. You do not notice those because they do not look as "clean" as the example you memorized.
This is selection bias reinforcing selection bias: you learned from winners, so you spot winners, so your backtest shows winners, so you think the strategy works. But you are only seeing 20% of the actual setups that the same rules would have produced in real time.
ICT teaches: "Wait for price to sweep liquidity below a swing low, then look for a reversal entry." In a backtest with the full chart visible, you can clearly see the swing low. Price sweeps below it by 5 pips, reverses, +40 pips. Win.
In real time, the swing low is not obvious. There are three recent lows within 15 pips of each other. Which one is "the" liquidity level? Price sweeps below the first one, keeps going, sweeps the second, keeps going, sweeps the third, and finally reverses. You entered at the first sweep and got stopped out three times before the move you were waiting for.
The fix: Pre-define your liquidity levels before you see the outcome. If you cannot clearly mark "this is the level" before advancing to the next candle, the setup is not tradeable. If multiple levels are ambiguous, the backtest must count all of them as potential entries — and the failures must be logged.
FXAbsolute hides the next candle so you cannot see what happens. Mark every FVG, OB, and liquidity sweep. Record the ones that fail. Get a win rate you can actually trust.
▶ Start Free Backtesting →One reproducible testing idea, with its rules, limitations, and review questions made explicit. In your inbox every week.
Measured from 28 million candles
Beginner exploration
Open each answer for a plain-language way to read Why ICT/SMC Strategies Pass Backtests But Fail Live, test it carefully and decide what to explore next.
This page focuses on “Why ICT/SMC Strategies Pass Backtests But Fail Live”.Test ICT and SMC concepts with timestamped definitions, hidden future data, executable prices, ambiguity logs and inter-rater agreement.For “Why ICT/SMC Strategies Pass Backtests But Fail Live”, a beginner should identify what the backtesting guide measures, assumes or teaches before acting on its conclusion.Treat this page's account of “Why ICT/SMC Strategies Pass Backtests But Fail Live” as a learning reference rather than a prediction, signal or promise of future performance.
For “Why ICT/SMC Strategies Pass Backtests But Fail Live”, write one objective entry rule, one exit rule and one risk rule before revealing future candles.While exploring “Why ICT/SMC Strategies Pass Backtests But Fail Live”, start with one instrument and timeframe so practice errors are easier to diagnose.Keep your “Why ICT/SMC Strategies Pass Backtests But Fail Live” record honest: record every eligible signal, including skips and ambiguous cases, with the same cost assumptions.Before leaving “Why ICT/SMC Strategies Pass Backtests But Fail Live”, freeze the rule for a useful sample before changing one variable and testing again.
Turn one idea from “Why ICT/SMC Strategies Pass Backtests But Fail Live” into a rule with explicit inputs, dates, costs and pass-or-fail conditions.Ask AI to expose missing assumptions in that “Why ICT/SMC Strategies Pass Backtests But Fail Live” test, not to guess the next market move.Use the FXAbsolute AI Backtesting Lab to inspect calculations connected to “Why ICT/SMC Strategies Pass Backtests But Fail Live” and the assumptions behind them.Reproduce any important “Why ICT/SMC Strategies Pass Backtests But Fail Live” result and reserve unseen data before deciding that an apparent pattern is useful.
Continue your exploration of Why ICT/SMC Strategies Pass Backtests But Fail Live with the beginner AI prompt guide, or inspect public calculations in the AI Backtesting Lab.