Direct answer
A worked example of support resistance zones means you pick a simple price history, define clear rules for turning old price swings into zones, and then walk through how a later price movement is interpreted relative to those zones—using explicit assumptions (for example: how many touches count, how wide the zone is, and how outcomes are measured).
Mechanism or definition
Support and resistance zones are ranges on a chart where price has previously shown some form of “reaction,” such as bouncing away from an area (support) or being rejected from an area (resistance). A zone is wider than a line because real markets rarely respect a single exact price; instead, multiple nearby prices may act similarly.
To make a worked example verifiable, separate stable mechanics from variable conditions:
- Stable mechanics: the definition of what counts as a “touch,” how a zone’s boundaries are calculated from earlier points, and how you decide whether later price “entered,” “tested,” or “held.”
- Variable conditions: the market’s volatility regime, bid–ask spread, execution quality, and how any provider platform computes candle highs/lows.
Evidence or example (fully worked scenario)
Assume a simplified chart using only candle extremes (no live data).
Assumptions (state everything)
- Time series: we consider only the following earlier candle lows around the future support zone: 99.8, 100.1, 100.0, 100.2.
- Zone rule: define the support zone as min(low points) to max(low points), so the zone boundaries are 99.8 to 100.2.
- Later observation window: we look at a single future candle with a low of 100.25 and a high of 101.10.
- Interpretation rule: “test of support” is counted if the future candle’s low is less than or equal to the zone’s upper boundary (100.2). “Hold” is counted only if the candle closes back above the zone’s upper boundary; since we do not have a close in this simplified example, we will treat this candle as a “test without hold confirmation.”
Step 1: Build the support zone
- Earlier touch lows: {99.8, 100.1, 100.0, 100.2}
- Support zone = [99.8, 100.2]
Step 2: Check a later candle relative to the zone
- Future candle low = 100.25
- Zone upper boundary = 100.2
- Because 100.25 > 100.2, the candle did not reach the zone. Under the interpretation rule, this is not a support test.
Optional additional candle to show a “test”
Now add a second future candle (still simplified, still no live data): low 100.15, high 100.90, and assume a close of 100.30.
- 100.15 ≤ 100.2 ⇒ this candle reaches the zone, so it is a test.
- Close 100.30 > 100.2 ⇒ the candle closes back above the zone ⇒ “hold” is confirmed under the stated rule.
How to record an outcome without promising performance
You can record outcomes as labels based on your rules, for example:
- Candle A: no test (low above zone)
- Candle B: test + hold confirmed
This is not a prediction; it is a consistent classification exercise that any reader can reproduce using the same inputs and rules.
Limitations and risks (material failure modes)
- Zone construction is rule-dependent. If you choose different boundaries (for example: using an average, using a fixed buffer in pips, or counting more/less touch points), the “same” historical area can become a different zone.
- “Reaction” can be ambiguous. A bounce near a zone might happen without the zone causing it; both could be driven by volatility, news, or broader market moves.
- Measurement differences matter. If one platform uses different candle calculations (or if you use wick highs/lows versus closes), your touch detection may change.
- Costs and execution can invalidate comparisons. Even if price appears to respect a zone, real trading involves spread and slippage, which are not reflected in a simplified candle-based example.
- Regime shifts reduce transferability. Historical zone behavior does not guarantee future zone behavior, especially when volatility changes.
Verification or next question
To independently verify the concept, you can:
- Recreate the zone boundaries from a chosen set of historical highs/lows using the exact rule stated.