Confirmation creates delay

A pivot high or low is a local extreme defined by bars on both sides. Increasing the left and right lengths usually produces fewer pivots and more delay; reducing them produces a more sensitive, noisier map. Neither setting is universally correct.

If a pivot needs bars to its right, it cannot be confirmed at the extreme itself. A chart may draw the label back on the pivot bar for readability, but evaluation should use the later bar on which confirmation became available.

Define structure events precisely

A break can require a close beyond the level, any wick through it, or a volatility buffer. A change in direction can refer to the latest minor pivot or a larger confirmed swing. Each choice changes event timing and frequency.

Zones add another judgment: fixed ticks, a percentage, or an ATR multiple. A wider zone may reduce visual precision while acknowledging normal movement; a narrow one may trigger more interactions. The setting should describe the intended use, not optimize an example after the fact.

Review availability, not just outcome

For each event, record the pivot time, confirmation time, break rule, and chart timeframe. Then ask whether the label improved orientation before the next move was known. This is more informative than grading only whether price later traveled in the labeled direction.

Structure is a map of past and current relationships. It does not determine execution, risk, or how far a move can continue.