Direct answer
Support Resistance Range is built from inputs used to identify a support level and a resistance level, and then treat the area between them as a range. In most descriptions, the inputs are (1) historical price data, (2) a time window or lookback period, and (3) parameters that define how you compute levels from that data. It also depends on assumptions about data quality (timeframe, session handling, and whether you use close, high/low, or other derived values).
Because different implementations can vary, the practical goal is to separate stable mechanics (what kinds of data and parameters are needed) from variable conditions (how markets behave and how a provider or tool chooses to compute the levels).
Mechanism or definition
Support and resistance are levels derived from prior price behavior. A Support Resistance Range approach then uses two computed levels to define a band: support at the lower boundary and resistance at the upper boundary.
Typical inputs you must name to explain the method clearly are:
- Price history: usually OHLC data (open, high, low, close) over a specified period.
- Timeframe: the bar size (for example, minutes, hours, or days). Different timeframes can shift where levels appear.
- Lookback period: how many bars back the method examines when estimating levels.
- Level definition rule: how the method selects the support and resistance candidates. Examples of rule families include using local lows/highs, pivot-like swing points, or aggregations of extremes.
- Aggregation and sensitivity parameters: settings that control how strict or smooth the level selection is, such as tolerance width, smoothing, or the number of touches required.
- Outlier handling: whether one spike is allowed to redefine a level, or whether extremes are filtered.
A simple way to think about the inputs is: the method first transforms raw price bars into two level estimates, then converts those estimates into a range.
Evidence or example (with explicit assumptions)
Below is a concrete, checkable example of the type of inputs you should document. It is not tied to a specific platform implementation.
Assumptions for the example
- Data: OHLC candles.
- Time window: the most recent N candles (your lookback).
- Timeframe: fixed to a single bar size.
- Level rule:
- support = the minimum low observed among the N candles after filtering out extremes using a tolerance rule.
- resistance = the maximum high observed among the N candles after the same tolerance rule.
Inputs you would list
- The exact timeframe used.
- The exact lookback N.
- The exact tolerance/filter rule (for instance, excluding the top and bottom 1% of extremes, or requiring multiple touches).
- The source fields for the level computation (low for support, high for resistance).
What to verify independently
- If you repeat the same computations on the same historical segment, you should get the same support and resistance boundaries (up to rounding and implementation details).
- If you change only one input (like N or timeframe), the range should move in a way consistent with the method’s sensitivity.
Limitations and risks
Even with correct inputs, Support Resistance Range can fail or become misleading because:
- Regime changes: markets can shift from one type of behavior to another, making previously derived levels less relevant.
- Parameter sensitivity: small changes to lookback, smoothing, or tolerance can materially change the range.
- Outliers and illiquidity: rare spikes, news-driven moves, or low-liquidity periods can distort level estimation.
- Data and session effects: different sources may handle timestamps, trading sessions, and missing data differently; that can alter the input series.
- Overfitting: choosing parameters to match past price history can reduce usefulness on later periods.
A material failure mode to watch for is when the computed range becomes an artifact of the chosen filter rather than a stable feature of price behavior. Another is when the method implicitly assumes that the next segment will respect the same boundaries, which is not guaranteed.
Verification or next question
To independently verify what Support Resistance Range uses, you can do three checks:
- Identify the raw data fields it consumes (for example, close-only versus using high/low extremes).
- Confirm the lookback and timeframe settings that define the computation window.
- Document the level rule and tolerance/sensitivity parameters, including how it handles outliers.