ICT IPDA Explained: Lookback Ranges as Testable References
Learn how ICT educators use IPDA lookback ranges as price references, then test whether pre-defined levels are reached without assuming one algorithm dictates market movement.
Framework note: ICT terms are interpretations of price action, not proof of institutional motives or a market algorithm’s intent. No setup is guaranteed. Test clearly defined rules, account for costs and slippage, and use risk limits before risking capital. Read our editorial policy.
The Interbank Price Delivery Algorithm (IPDA) is ICT's conceptual model for studying price across selected lookback ranges. It describes an interpretive framework for comparing price, time and reference levels; it is not independent evidence that one algorithm governs markets or that price must reach a particular level.
The IPDA Data Ranges
ICT explanations often describe IPDA using 20-, 40- and 60-day lookback ranges. Traders can mark those highs and lows as reference levels, but these ranges do not prove that one algorithm is using them or that price will reach them.
For a test, mark the 20-, 40- and 60-day highs and lows on a daily chart, then record whether price reaches them and in what order. Do not assume that all six levels will be reached or that any move was caused by an algorithm.
How IPDA Delivers Price
Some ICT traders combine IPDA with the AMD framework (accumulation, manipulation and distribution). The labels can structure analysis, but they should be applied using predefined rules and compared with sessions that do not fit the pattern.
A test sequence could be: identify the 20/40/60-day range, state a possible target using a written bias rule, then record which boundary—if any—price reaches and whether the hypothesized path holds. Price may instead reverse, consolidate or reach another level first.
IPDA and the Quarterly Shifts
Some ICT traders compare quarterly context with 20-, 40- and 60-day reference ranges. Treat the quarterly direction as a scenario to test, not an established cycle that determines where price will go.
- Mark the 20/40/60-day highs and lows on your daily chart every week.
- Identify the quarterly shift direction (which direction, if any, the price action appears to favor under your pre-defined rules).
- Treat the nearest unswept reference level as one possible scenario target, not a prediction that price must reach it.
- Use a selected reference level as one input to weekly and daily DOL hypotheses; it is not an anchor that overrides new price information.
- If multiple reference levels are swept, record what follows; a reversal is one possible outcome, not an expected or required result.
IPDA can serve as a higher-timeframe planning lens for traders who use it. Mark selected ranges, document the reason for each hypothesis, and record misses as well as hits. No reference level determines the path forward, and backtested results—not confidence alone—should guide whether a rule is useful.
Worked hypothetical example
Suppose a NAS100 trader marks the prior 20-, 40- and 60-session highs and lows before Monday opens. Under a written rule, the nearest level is only a scenario target. During the week, price instead turns at the range midpoint and never reaches the marked high. The journal entry should say the target was not reached—not that an algorithm changed its plan after the fact.
Failure case and what to test
A common failure is selecting the reference range after seeing the move, or counting a level as a target only when price later approaches it. To avoid hindsight bias, record the chosen boundary, timeframe, bias rule and invalidation before the test begins.
Test checklist
- Use the same completed-bar lookback method on every sample.
- Record whether price reaches the selected boundary before invalidation.
- Include reversals, untouched levels, costs and missed entries in the results.
RELATED READING
Continue with guides selected for overlapping concepts and practical context.