TradingView chart patterns

Broadening wedge pattern: widening boundaries and failed breaks

A broadening wedge pattern has two boundaries that slope in the same direction while moving farther apart. In an ascending version, the upper line rises faster than the lower line. In a descending version, the lower line falls faster than the upper line. A widening wedge pattern describes expansion, while an ordinary rising or falling wedge narrows. The shape alone does not confirm a breakout direction.

See the decision guide

Broadening versus converging wedges

Let U(t) be the upper boundary and L(t) the lower boundary at bar t on a linear price scale. Their vertical separation is W(t) = U(t) - L(t). Require W(t) to remain positive over the formation. With straight boundaries, the width changes by the upper slope minus the lower slope each bar. The table is a geometric classification, not a forecast.

  • An expanding wedge pattern is another name used for a broadening wedge. A formation with an upward upper line and a downward lower line is a broadening formation, but does not meet the same-direction wedge definition used here.
  • TradingView describes its Falling Wedge pattern as a converging channel. Do not assume that its detector identifies a descending broadening wedge simply because both patterns point downward.
  • These equations use arithmetic prices and bar indices. Drawing straight lines in logarithmic price space changes the geometry; keep the scale and calculation convention consistent.
StructureSlope relationshipWidth over time
Ascending broadening wedgeBoth positive; upper slope is largerIncreases
Descending broadening wedgeBoth negative; lower slope is more negativeIncreases
Converging rising wedgeBoth positive; lower slope is largerDecreases
Converging falling wedgeBoth negative; upper slope is more negativeDecreases
Parallel channelEqual slopesStays constant

Define touches and a minimum expansion

A boundary needs separated swing points, not repeated candles sitting near one price. Bulkowski describes touches at minor highs and lows and excludes price cutting through a line. His published touch counts differ between ascending and descending wedges. For the custom detector below, use three confirmed highs and three confirmed lows in alternating order for either direction. This is a stricter chosen specification, not a universal minimum.

  • The 0.25 allowance is in price units, not percent or chart pixels. It belongs to this hypothetical example and needs a different interpretation on instruments with different prices or tick sizes.
  • When all checks pass, freeze the six pivots and two boundary equations for 20 completed bars starting at candidate confirmation. Evaluate no replacement candidate during that window.
  • An extra swing that fails the selection or touch rules is a rejection to record. Moving the line to fit that swing creates a different candidate and must not rewrite the earlier one.
DecisionIllustrative ruleReason
Swing confirmationThree bars on each side of an extreme; reject equal highs or lowsEach accepted point has a known confirmation time
Point selectionEvaluate the latest six alternating confirmed pivots, with adjacent pivots at least four bars apartAvoid selecting a different historical combination after seeing the outcome
Boundary anchorsJoin the first two selected highs for U and first two selected lows for LThird touches test lines that are already defined
Third-touch toleranceThe third high and low must each be within 0.25 price units of their own lineMake near-touch acceptance measurable
ExpansionW at the last pivot divided by W at the first pivot must be at least 1.5Reject near-parallel candidates; require a positive initial width
Formation containmentNo completed close from the first pivot through candidate confirmation may exceed either boundary by more than 0.25Reject a formation already interrupted by a qualifying break

Calculate a descending broadening wedge

Assume hypothetical swing highs at bars 10, 20 and 30 are 109, 108 and 107. The alternating swing lows at bars 15, 25 and 35 are 101.5, 98.5 and 95.5. These six points give U(t) = 110 - 0.1t and L(t) = 106 - 0.3t. Both lines fall, but the lower line falls faster. Assume the surrounding candles satisfy the stated pivot and containment rules.

  • The width ratio is 11 / 6, approximately 1.83, which passes the chosen 1.5 minimum. Each third pivot lies exactly on its boundary, so both touch errors are zero.
  • A different lower boundary of L(t) = 100 - 0.05t would narrow toward the same upper line: width falls from 9.5 at bar 10 to 8.25 at bar 35. Lower highs and lower lows can therefore occur in either expanding or contracting structures.
  • The final low at bar 35 is only confirmed at the close of bar 38 under the three-right-bar rule. A drawing placed at bar 35 does not make the complete candidate available three bars earlier.
BarUpper boundaryLower boundaryWidth
10109.0103.06.0
20108.0100.08.0
30107.097.010.0
35106.595.511.0

Keep repeated false breaks visible

Continue the same hypothetical candidate with its frozen equations. Define an upside event as a completed close above U(t) + 0.25 and a downside event as a close below L(t) - 0.25. Record the first eligible event, then wait for a close inside the raw boundaries before allowing another. For this audit, a return inside within the next three bars marks that event as failed. This failure label is a study rule, not a claim that price cannot resume the move.

  • A wick outside followed by an inside close would produce no event under this closing rule. A close outside can still fail, as the two events demonstrate.
  • Requiring two consecutive closes beyond the same buffered boundary would reject both one-bar breaks here. That filter also delays detection and can miss moves; the example does not establish that it improves results.
  • Preserve both failed events through the review window ending at bar 57. Do not widen the saved lines to absorb them or delete them when a later pattern looks clearer.
  • This log is not a trading strategy. Entries, exits, size, fees, slippage and gap handling would need separate rules before any performance test.
Bar and closeBoundary checkRecorded event
38: close 105.0U = 106.2; L = 94.6Candidate confirmed; price is inside
39: close 106.4106.4 exceeds U + 0.25 = 106.35Upside break
40: close 105.7Between L = 94.0 and U = 106.0Upside event failed; detector rearmed
42: close 93.193.1 is below L - 0.25 = 93.15Downside break, assuming bar 41 stayed inside
43: close 94.0Between L = 93.1 and U = 105.7Downside event failed; detector rearmed

Record identification stability before testing trades

TradingView documents how a pivot plotted on a past candle can become visible only after later bars confirm it. For a broadening-wedge detector, save the pivot bar, its confirmation bar, the six selected anchors, both slopes, the width ratio and every event time. Compare that log during bar-by-bar review with the history after reloading the chart.

  • Separate provisional candidates from confirmed candidates. Track how often provisional anchors change, rather than presenting the final drawing as if it had always been fixed.
  • Check that reloads preserve events produced from the same confirmed data and settings. Investigate changes in source data, selection rules or intrabar calculations when they do not.
  • Ask Pineify to draft the written rules with candidate IDs, frozen boundary values and separate confirmation markers. Inspect the generated code and validate its syntax before testing the detector on TradingView.
  • Start with ordinary price candles on one named symbol, timeframe and session. No recognition accuracy, preferred parameter set or trading edge is established by the illustrative prices on this page.
Where Pineify fits

Pine Script AI Coding Agent

Turn your pivot, width and breakout specification into a Pine Script draft for review. Request a log of anchor changes and confirmation times. This educational page does not scan symbols or provide a tested broadening-wedge indicator.

Draft broadening-wedge rules

Frequently asked questions

Educational information, not investment advice. All example prices, thresholds and event paths are hypothetical. No historical trading results or success rates are presented. A recognized shape or confirmed breakout does not guarantee direction or profit.

Sources and verification

Published by Pineify. Pineify is an independent product and is not affiliated with TradingView. Sources support the technical explanations; examples do not establish trading performance.