What are the rules of Support Resistance Reversal?
Support Resistance Reversal is a chart-based concept where a previously identified support level can behave like resistance later, and a previously identified resistance level can behave like support later. The idea is not that the level predicts the future reliably, but that levels may “flip” roles after price meaningfully breaks and then retests them.
In practice, you can treat Support Resistance Reversal as a testable set of chart-reading rules. The core is to define levels consistently, define what counts as a “break” and what counts as a “retest,” and then check whether the later behavior matches the role swap (support becomes resistance, or resistance becomes support).
A rule set that can be verified on historical charts should separate (1) stable mechanics of the method (your definitions and conditions) from (2) variable market conditions (volatility, range width, spreads, execution), and from (3) provider-specific details (chart settings, data source, and how costs are represented).
Mechanism and definitions you must lock down first
Before discussing implications, define the objects you will measure.
1) How to define support and resistance (the “level”)
Choose a repeatable way to mark a level, such as using recent swing highs/lows:
- Support level: a price area where downward moves previously stalled and price later moved up.
- Resistance level: a price area where upward moves previously stalled and price later moved down.
Because real charts are noisy, represent a level as an area, not a single tick. For example, you can use a tolerance band around the reference price:
- Assumption: you select a fixed tolerance based on the instrument’s recent range or on a percentage/ATR-like proxy.
- Test requirement: you must apply the same tolerance across all observations in your sample.
2) What “break” means
A role swap cannot happen without a break being present in your test. Define a break rule you can apply consistently:
- Example rule: a break occurs when price closes outside the level’s tolerance band.
- Alternative rule: a break occurs when price wicks beyond the level but closes back inside—however, if you do this, you must label that case separately because it often signals a failed break.
Assumption to state explicitly: you will use one definition of “break” for the entire test (e.g., close-based).
3) What “retest” means
The retest should occur after the break, not before. Define it as:
- A retest attempt is when price moves back toward the level’s tolerance band after the break.
- Retest confirmation is when, during the retest window, price reacts by moving away in the opposite direction.
To keep it testable, also define a retest window:
- Example assumption: retest happens within a fixed number of bars (time-based window) or within a fixed maximum distance (price-based window) after the breakout.
A testable rule set for detecting a Support Resistance Reversal
Below is one coherent approach you can verify. It is written as rules, not as a promise of profit.
Step A: Identify the initial level
- On a chart, mark a resistance level from a prior swing high (use a tolerance band).
- Mark a support level from a prior swing low (use the same style of tolerance).
- Record the timeframe and chart data source you used.
Step B: Apply the breakout rule
- For a resistance-to-support flip: wait until price breaks above the resistance level according to your break definition.
- For a support-to-resistance flip: wait until price breaks below the support level according to your break definition.
Material assumption: “meaningfully breaks” is defined only by your break rule (e.g., a close outside the tolerance band).
Step C: Apply the retest-and-reject rule
- After the break, observe the first meaningful return to the original level.
- Label a reversal as occurring if, on the retest, price reacts away from the level in a way consistent with the swap:
- Resistance-to-support: the level acts like support during the retest (price moves away upward after touching the band).
- Support-to-resistance: the level acts like resistance during the retest (price moves away downward after touching the band).
Step D: Separate “reversal” from “continued trend” cases
- Do not label every post-break touch as a reversal. Add a condition that the retest must show rejection:
- For example: the retest must produce a move back in the opposite direction that is larger than noise under your tolerance.
This is a major reason rules can become testable: without a rejection threshold, almost any retest can be interpreted as a flip.
Step E: Record outcomes as outcomes, not predictions
- For each instance, record whether your rules found a role swap within the retest window.
To keep it verification-friendly, also record “fail” cases:
- A false break: price breaks out but never properly retests with rejection.
- A re-entry into the original range: price returns and continues oscillating without a clear role swap.
- A level that becomes too ambiguous: price interacts with the band in many small touches, making direction hard to attribute.
Evidence and example logic (with explicit assumptions)
Because there is no real-time data here, the best way to understand the method is to run a chart-based thought test using fixed assumptions.
Example logic for a resistance-to-support flip
Assumptions:
- You use a 4% tolerance band around the level.
- You define break as a closing price above the band.
- You define retest as any move back into the band within the next 20 bars.
- You require a rejection threshold: the retest reaction must move at least 1% away from the band before the next bar close.
Procedure:
- Identify a resistance from a swing high and mark the band.
- Wait for a close above the band (break).
- After the break, watch for the next return into the band within 20 bars (retest).
- If price touches the band and then moves away upward by at least 1% (meeting the rejection threshold), record “role swap occurred.”
- If price returns but does not react upward enough, record “role swap failed.”
This structure turns the concept into a repeatable test. You are checking agreement between your label (role swap) and your measurable criteria (break, retest, reaction).
Limitations and failure modes you should expect
Support Resistance Reversal is sensitive to definition choices. Even with consistent rules, several failure modes are common.