What Data Is Needed to Assess Failed Breakout?

Direct answer

Assessing a failed breakout requires more than noticing that price “went past a level.” You need (1) a clear definition of what counts as a breakout and what counts as failure, (2) the chart inputs used to measure it, (3) the provenance and timeliness of the data, and (4) quality checks that expose redraws, mismatched levels, and execution/cost assumptions. This lets you explain the concept accurately and independently verify the same facts on other chart sources.

Mechanism or definition

A breakout is usually defined as price crossing and then holding relative to a predefined level (for example, a prior high/low, trendline, or range boundary). A failed breakout is when that breakout does not sustain and price later returns back into the prior range or below/above the level according to your stated rules.

To assess it with usable data, separate stable mechanics from variable conditions:

• Stable mechanics (conceptual rules): the level definition, the breakout confirmation rule, and the failure condition.
• Variable conditions (context and implementation): timeframe choice, market regime, data vendor or platform differences, and transaction costs/execution constraints.

Evidence or example (what inputs to collect)

Use a checklist of inputs, each with a short “why it matters” note:

1. Level specification (what boundary?)

• The exact method used to draw the level (manual swing high/low, automated pivot, range high/low).
• Whether the level is treated as a single price, a zone (band), or a dynamic indicator-derived boundary.

2. Breakout measurement rules (what counts as crossing and holding?)

• Crossing rule: close above/below vs. intrabar touch.
• Confirmation window: how many bars after the cross are required to qualify as “holding.”

3. Failure definition (what counts as failing?)

• Retest/return rule: for example, the first meaningful close back inside the level boundary.
• Failure horizon: how long after breakout you wait before calling it failed.

4. Chart inputs (what data are you measuring?)

• Timeframe(s): note that the same price move can look different on 1-minute versus daily charts.
• Session context (if relevant to your definition): whether your level is based on a specific trading session.
• Price fields: whether you use OHLC closes, highs/lows, or both.

5. Provenance and timeliness (where did it come from?)

• The data source (charting platform, broker feed, or public data) and any known transformations.
• Whether the chart is “fixed” historical bars or can later change due to provider adjustments.

6. Cost and execution assumptions (what could prevent “holding”?)

• Spreads, slippage, and latency are variable, so for assessment you must state your assumptions explicitly.
• If you cannot model those costs, record them as an unresolved factor that can turn a theoretical “hold” into an observable failure.

Material limitation or failure mode to watch

One common failure mode is rule mismatch: a person may label “failed breakout” based on intrabar penetration, while another requires a closing breakout and a later close back inside. Without aligned rules, two observers can both be “right” relative to different definitions.

Another limitation is historical non-transferability: even if you identify many past failed breakouts, the relationship between pattern behavior and future outcomes is not guaranteed. Outcomes vary with conditions, costs, execution, and even how the same level is drawn.

Limitations and risks

• Timeframe sensitivity: the failure can appear earlier or disappear when you change timeframe or level construction method.
• Provider and redraw effects: historical bars can be represented differently across platforms, especially around the exact moment of crossing.
• Unmodeled costs: transaction costs and execution constraints can materially affect “holding,” independent of the chart pattern.
• Ambiguous level zones: if you use a zone, you must define whether price “failing” means closing back inside the entire zone or only partially.

Verification or next question

To verify your assessment independently:

• Replicate the same breakout and failure rules on at least one other independent chart data source.
• Document disagreements as evidence of definitional sensitivity (for example, “breakout confirmed on closes but not on highs”).
• For any calculation-like decision (confirmation window, horizon, zone boundaries), state your assumption plainly so others can reproduce it.

A good next question to make the evaluation concrete is: *What exact breakout-confirmation and failure-return criteria are you using (close vs. touch, confirmation bars, and failure horizon)?