Reading support and resistance for your plan
Every trading plan that uses technical signals eventually references levels — areas where price has previously reversed or paused. The problem is not finding lines on a chart; it is deciding which lines deserve a place in your written rules and which are noise.
Levels that belong in a plan
A level earns documentation when it meets at least two of these criteria on your chosen timeframe:
- Price tested the level at least twice with a visible reaction (bounce, rejection wick, range boundary)
- The level aligns with a prior swing high or swing low that remains unbroken
- A higher or lower timeframe shows the same price zone as significant
- Volume or range expansion occurred at the level (where volume data is available)
If you cannot point to two tests or a structural reason for the line, leave it off the plan until price proves it matters again.
How to write the level in plain language
Plans fail when levels are described vaguely. Compare these:
- Weak: "Buy near support on the daily chart."
- Usable: "Consider long entries when price retests the prior week low at 7,842 on the FTSE daily chart and the four-hour candle closes above that level."
The second version names the instrument, the timeframe, the exact level, and the confirmation candle. Another trader could mark the chart without asking you what you meant.
The retest test
Before adding a level to your plan, scroll back six months and mark every time price approached it. Count how many approaches produced a tradeable reaction versus a clean break. If more than half the approaches broke through without pause, the level is not support or resistance for your setup — it is a line that happened to exist.
Updating levels over time
Levels break. Your plan should include a review note: when a documented level is breached on a closing basis, remove it from the active list and add the new swing point that formed. Weekly review is enough for swing traders; intraday traders may update daily.
Support and resistance are the foundation of most signal-based plans. Get the level definition right and your entry and stop rules become easier to write — which is the subject of our next guide on entry rule wording.