Define Support Resistance Breakout before assessing it
A support resistance breakout is the idea that price action interacts with a previously observed support (downward “floor”) or resistance (upward “ceiling”), and that a later move through that level may represent a change in market behavior. To assess it, you need to separate:
- the stable mechanics of the concept (how you define a level and a breakout), from
- variable conditions (market regime, volatility, spreads/fees, and how your data captures price). Because “breakout” is not a single universal rule, the first necessary data items are the exact definitions you will use for support, resistance, and what counts as “breaking through.”
Core inputs: price levels, timing, and measurement rules
To evaluate a support resistance breakout independently, gather data that lets someone else reproduce your level construction and breakout test.
1) Price history and timeframe choices
You need historical price series for the instrument you are evaluating, such as open-high-low-close candles or tick data (depending on your method). The key data you must record are:
- the timeframe (e.g., 1H vs 1D),
- the lookback window used to draw support/resistance,
- the exact date range for the breakout evaluation. A breakout assessment can change materially when you change timeframe or lookback, so you should state these assumptions explicitly.
2) How support and resistance levels are defined
Support/resistance levels can be created in multiple ways. The data required depends on your definition, for example:
- swing highs/lows from a specified lookback window,
- repeated touches within a tolerance band,
- a statistical level derived from recent candles (where you must state the method). At minimum, you need the numeric level values (or the rule that produces them) plus the tolerance/rounding used to decide whether price “tests” a level.
3) Breakout criteria and tolerance rules
Define what constitutes a breakout in measurable terms, such as:
- whether the breakout is based on candle close versus intrabar high/low,
- the minimum distance beyond the level,
- whether you require a retest or “hold” after crossing. These criteria are essential input data because they determine how many events qualify. If you do not state them, another analyst cannot verify your counts.
Evidence and example data to test the concept
To avoid treating the concept as a standalone pattern, you need evidence that shows how it behaves under your rules.
4) Outcome labeling data (without promising accuracy)
For assessment, create a reproducible labeling scheme tied to your breakout test. For example, after a qualifying breakout, you may record whether price:
- returns back below/above the level within a chosen horizon,
- reaches a defined distance move,
- shows volatility expansion or mean reversion. The required data are the post-event price series and the exact horizon you used. Historical relationships do not prove future results, so the goal is measurement, not prediction.
5) Provenance and completeness of the dataset
You also need provenance data so quality checks are possible:
- the data source (exchange, provider, platform export),
- whether the dataset has gaps, missing candles, or session breaks,
- corporate actions handling (where relevant) and time zone alignment. If you mix data feeds or fail to align timestamps, you can create false “breakouts” caused by data artifacts rather than market behavior.
6) Costs and execution assumptions (material for interpretation)
Even without using real-time data, your assessment should note execution-related assumptions that can change what “works.” You should record:
- assumed transaction costs (spreads/fees) if you model outcomes,
- whether your test assumes entry at close, at break, or at next open. If your method ignores costs, your historical evaluation can misrepresent the practical effect of breakouts.
Limitations and failure modes to include in your checklist
At least one material limitation should be part of your assessment framework.
False breaks and whipsaws
A common failure mode is a “false break,” where price crosses a level briefly and then reverses. Another is whipsaw, where multiple crossings occur due to volatility noise around the level.
Regime changes and non-stationarity
Support/resistance behavior can change when volatility, liquidity, or market regime shifts. Historical relationships do not establish future results, so you must treat any observed performance as conditional.