Direct answer: a worked example (with every assumption)
A range breakout is often described as a price move that goes outside a previously identified trading range (for example, above a recent high or below a recent low). “Worked example” means you can reproduce the logic with the same inputs and calculations, without needing live prices.
Scenario setup (all assumptions stated)
Assume you are analyzing a chart where you define a range using these fixed, pre-chosen levels:
- Range high (Rhigh) = 1.2000
- Range low (Rlow) = 1.1900
- Range width = Rhigh − Rlow = 0.0100 (100 pips if pip is 0.0001)
- You choose a breakout level that is strictly the range boundary:
- Breakout above = price closing above 1.2000
- You choose a confirmation horizon measured in bars, not time:
- You will inspect the next bar close after the breakout bar.
- You assume no transaction costs for the primary arithmetic example (spread and slippage treated as a later limitation).
- You assume the instrument’s “price” is represented consistently on your chart (same decimal places/pip size).
The worked price path
Suppose your chart shows:
- Bar A close: 1.1980 (inside the range)
- Bar B close: 1.2012 (breakout close above 1.2000)
- Bar C close: 1.2004 (re-enters the range because 1.2004 is still above 1.2000, but close-to-boundary behavior is considered a risk in practice)
- Bar D close: 1.1978 (fails because it is back below 1.2000)
What this example illustrates numerically
- The breakout condition you set is: close > 1.2000.
- Bar B satisfies it because 1.2012 > 1.2000.
- However, the later closes show the move can reverse back inside the range:
- Bar D close 1.1978 is below the breakout boundary, so the breakout did not hold.
So, in this scenario, the “range breakout event” occurs at Bar B, but the “range breakout outcome” is uncertain because the price later returns below the breakout boundary. That is the core idea behind breakout vs. false breakout.
How it works: mechanics you can apply and verify
A practical way to apply range breakout logic is to separate three steps:
-
Define the range boundaries
- Pick a lookback window (for example, N bars) and decide which highs/lows define Rhigh and Rlow.
- Stable input: in this worked example, Rhigh and Rlow are fixed numbers chosen before looking at the breakout outcome.
-
Define the breakout trigger
- Your trigger is not “touching” the boundary; it is typically defined as a close beyond the boundary (as assumed above).
- This choice matters: an intrabar spike that does not close beyond the level may not qualify.
-
Define what “holds” means
- You can use a later close staying beyond the boundary, or require a minimum distance move.
- In the worked example, Bar D close provides an explicit “does not hold” illustration.
Material limitation: the definition changes the result
Even with the same underlying price behavior, different analysts can define:
- range boundaries differently (how many bars, which highs/lows),
- breakout trigger differently (close vs. touch),
- hold/confirmation differently (one bar vs. multiple bars).
Because of this, the term “range breakout” is meaningful only together with a specific, checkable definition.
Limitations and risks (what can fail, even in a clean example)
This worked scenario deliberately ignores costs, but real outcomes vary.
1) False breakouts
A false breakout is when price moves beyond the boundary to satisfy the trigger and then returns back into the original range. In the example, Bar D close back below 1.2000 demonstrates that possibility.
2) Execution friction (spread and slippage)
If you trade in real conditions, the effective entry/exit can differ from chart prices due to spread and slippage. This can turn a “holds on paper” move into a loss in execution, even when your breakout definition is consistent.
3) Volatility spikes and boundary noise
Currencies can make sharp moves around well-known levels. If volatility is high, brief excursions beyond the boundary can be more common.
4) Lookback and selection bias
If you choose the range after seeing the move, your range can “fit” the outcome. Independent verification requires you to predefine the range selection rule.