Pivot High Low Strategy: Confirmed Levels and Testable Rules
A pivot high-low strategy uses detected local extremes as reference levels. Those extremes require later bars for confirmation, so a valid strategy must separate the turning-point time from the first time the level could be traded. The method differs from daily pivot formulas based on the previous session's high, low, and close.
Use the right definition of pivot
A swing pivot high is a local high identified by comparison with surrounding bars; a swing pivot low is the corresponding local low. Neither requires price to touch the same level twice. Two touches can form a different pattern, such as a double top or bottom.
A period-based central pivot averages selected OHLC data and generates support and resistance bands. Those formulas are covered in the pivot points trading strategy article. Do not use daily S1/R1 formulas as if they calculated swing highs and lows.
TradingView explicitly notes the right-bar delay in its Pivot Extension Strategy description. A level plotted over an old turning point was not necessarily available for a trade on that old bar.
Define the level's lifecycle
Before specifying an entry, decide when a level becomes active, how long it remains valid, and what replaces it. An illustrative rule set could use three left bars and three right bars, activate the pivot only after the detection bar closes, and keep the latest confirmed high and low.
That specification still needs three decisions:
- Does a new pivot immediately replace the previous one, even if the old level has never been tested?
- Does a level expire after a defined number of bars or at a session boundary?
- Does one successful breakout consume the level, or can later crossings create repeated entries?
These are strategy choices, not properties automatically supplied by a pivot marker. Save the active level and its detection time with each simulated trade so the test can be audited.
Breakout and rejection are separate hypotheses
| Hypothesis | Illustrative entry condition | Important ambiguity to resolve |
|---|---|---|
| Break above resistance | A closed bar crosses above the latest active pivot high | Crossing once versus remaining above it |
| Break below support | A closed bar crosses below the latest active pivot low | Whether a gap beyond the level is eligible |
| Reject support | Price enters a defined zone near an active low and closes back above it | Zone width and the exact rejection condition |
| Reject resistance | Price enters a defined zone near an active high and closes back below it | Whether an earlier close above the level invalidates it |
These conditions are research examples, not established profitable rules. A rejection cannot be inferred simply because the final chart later shows a bounce. Likewise, requiring higher volume may change trade frequency without improving net results.
Work through a timing example
Assume a hypothetical high of 105 occurs on bar 100. With a right length of three, that high cannot become a confirmed pivot until bar 103 closes, if the intervening bars satisfy the definition. A breakout after activation might occur on bar 108 when the close moves from 104.80 to 105.20.
A close-based rule can recognize that breakout at bar 108's close. Under TradingView's usual next-tick market-order model, the resulting historical fill is commonly at the next bar's open. A test that assigns the entry to 105 on bar 100 would be a different, hindsight-driven calculation. The strategy documentation explains the broker emulator and order timing.
Keep the signal timestamp, submitted order, and simulated fill distinct. If both stop and target are reached within one historical bar, the assumed intrabar sequence can change the outcome. Review bar magnifier availability and the test's fill settings before treating a result as precise.
Size the trade from the actual proposed stop
For a simple cash-share example, assume an entry of 105.50, a stop at 103.50, and a planned price-risk budget of 100. The distance is 2 per share, so 50 shares represent 100 of planned price risk before costs. This is arithmetic, not a recommended account allocation. Contract multipliers, currency conversion, minimum lot sizes, and leverage require additional treatment.
Do not widen the stop after entry merely because a newer pivot appears. If a trailing rule uses newly confirmed pivots, specify when it updates and whether it may ever loosen the stop. Gaps and slippage can make a realized loss exceed the planned amount.
Test the rule without selecting the answer afterward
Use standard price bars, fixed sessions, and recorded costs. Choose the setup and parameter search on one period, then evaluate it on a separate period without retuning. Count all eligible signals, including ones that fail before a visually attractive swing develops.
Compare net expectancy, trade count, drawdown, exposure, and dependence on a few large trades. A win rate alone does not describe risk. No universal 70% return-to-pivot frequency, 45% reversal win rate, or guaranteed benefit from RSI, MACD, or Fibonacci confluence is established here.
Pineify's Pivot Points High Low component supplies pivot outputs. A complete strategy must add the state, timing, entries, and exits described above. Check the generated source and actual TradingView behavior rather than assuming the visual marker is already a trading system.
Does a pivot high require two touches?
No. The swing-pivot calculation compares a candidate high with surrounding bars. Repeated tests of a level are a separate condition.
Can a strategy enter at the pivot turning point?
A strategy relying on that confirmed pivot cannot know it at the turning point. It must wait for the required right-side bars and any chosen close confirmation.
Is a bounce rule better than a breakout rule?
That depends on a specified market, period, costs, and rule set. Compare them as separate hypotheses and retain out-of-sample evaluation data.