Confirmation Candle Trading: Define the Close Before Entry

What is a confirmation candle in trading?

A level touch and a completed close beyond a level are different observations. Neither is automatically a better entry. Waiting may avoid a temporary intrabar signal, but it can also move the entry farther from the planned stop or miss a move altogether. Evaluate those tradeoffs with the same instrument, data period, exit logic and cost assumptions.

Turn candle characteristics into testable rules

There is no universal 60% or 70% body threshold, volume multiple or ATR cap that makes a candle reliable. Write candidate conditions as measurable inputs, then compare them against a baseline on unseen data. Avoid choosing thresholds after looking at only the successful examples. Volume also depends on the instrument and feed; a missing or tick-volume series is not interchangeable with consolidated traded volume.

• Body fraction: absolute open-to-close distance divided by high-to-low range; skip or explicitly classify zero-range bars instead of dividing by zero
• Reference break: specify whether the close must strictly exceed the previous high or fall below the previous low; decide how equality is handled
• Volume filter: state the averaging period and whether the current bar is included; define a missing-volume policy rather than silently treating missing as zero
• Size filter: express any range limit relative to a specified ATR calculation; test the effect on entry distance and rejected signals

Common confirmation candle setups and patterns

These are example rule definitions, not measured profitable patterns. Candle color and body size are separate conditions: a close can exceed a reference level even if the bar is red. The whole body need not be outside a range unless that is an additional rule you deliberately choose.

A hypothetical entry-price tradeoff

Suppose an initial support-entry plan uses 100, a stop at 98 and a target at 106: planned risk is 2 price units and reward is 6, or 3R before costs. If waiting for a confirmation close produces a fill at 102 while keeping the same stop and target, planned risk becomes 4 and reward 4, or 1R. These invented prices do not measure win rates. A gap can change the fill, and the stop is not a guarantee of the maximum loss.

Signal confirmation and execution in Pine Script

TradingView distinguishes bar confirmation from order execution. A confirmed-bar condition can prevent a current chart-bar signal from disappearing before that bar closes. It does not repair future-data leakage, delayed pivots or every higher-timeframe repainting problem. The default strategy calculation and broker-emulator fill timing also differ: a market order created after a bar closes normally fills at the next available tick, commonly the next bar open in a historical backtest.

• Use barstate.isconfirmed for the intended chart-bar condition; it is true on historical bars and on the realtime closing update, and does not work as a confirmation check inside request.security
• Keep the signal timestamp distinct from the fill price; processing orders on close or using intrabar recalculation changes assumptions and needs separate review
• Specify stop, target, position size and costs; an alert condition or indicator alone is not a strategy order or live broker execution
• Review generated logic and compare replay/forward observations; a syntax pass does not establish that the script never repaints