Advanced trading strategies for inside bar breakouts

Define the mother bar and nested inside bars

This page uses strict containment: the inside-bar high must be below the previous high, and its low must be above the previous low. Equal highs or lows do not qualify. An inclusive variant is possible, but record it separately. Candle color is irrelevant. The first qualifying inside bar establishes the preceding candle as the mother bar; save that candle's full high-low range after the inside bar closes.

• A mother bar from 100 to 104 followed by a bar from 101 to 103 is an illustrative valid setup.
• A later bar from 101.5 to 102.5 is nested inside both bars. Retain 100 and 104 as the original breakout levels.
• A later bar from 100.5 to 103.5 remains inside the mother bar but is not nested inside the preceding bar. Decide whether your test accepts this broader consolidation.
• Breaking the latest inside bar while still inside the mother bar is an earlier-entry variant. Do not count it as a mother-bar breakout.

Compare first-touch and close-confirmed entries

TradingView documents both stop-entry and closing-price approaches. Select one before evaluating results. In a bidirectional setup, the upper and lower boundaries are alternative entry levels, not two independent trades. A trend-filtered version may enable only one side.

Specify false breaks, expiry and reset rules

For an illustrative test, label a false upside break when price exceeds the mother high but that bar closes back inside the mother range. Reverse the rule for a downside break. This label is available only at the close: a stop-entry strategy may already have traded. A close-confirmed entry can also fail if a later bar returns inside. Neither rule eliminates losses.

• Keep a setup active for three bars after the first confirmed inside bar. Cancel unfilled orders at the third bar's close; do not extend expiry when another inside bar appears.
• For this example, retire a setup after any boundary breach that fails the chosen close-confirmation rule. A later attempt needs a new mother bar.
• Allow only one active setup and one position. Ignore new patterns until the current setup expires or its trade closes.
• For intraday testing, separately decide whether session end cancels pending entries and closes positions. Setup expiry alone does not close an existing trade.

Calculate risk from the entry and stop, including buffers

Consider a hypothetical stock with a 0.01 tick, a mother high of 104 and a mother low of 100. A buy stop at 104.01 and protective stop at 99.99 imply 4.02 per share of planned price risk, assuming those exact fills. A target at twice that distance is 112.05. The four-point mother range alone understates risk because both buffers matter.

• With a hypothetical 200 risk budget, 49 whole shares imply 196.98 of planned price risk before fees and slippage.
• For a close-confirmed entry, recalculate risk from its actual fill. A higher entry with the same stop increases risk per share.
• A stop below the inside bar instead of the mother bar reduces the planned distance but changes which retracements exit the trade. Test it as a separate variant.
• Gaps, spread and slippage can increase realized losses beyond the planned stop distance. A 2R target is a test assumption, not an expected outcome.

Test trend and volatility filters one at a time

Start with an unfiltered baseline and keep entry, exit and cost settings identical while testing a filter. The following settings are illustrative candidates, not recommended optimal values. Measure each filter at the inside-bar close and freeze its decision for that setup so later price changes do not silently alter the rule.

• Trend candidate: permit longs when the close exceeds the 20-period SMA and that SMA exceeds its value five bars earlier. Reverse both conditions for shorts.
• Compression candidate: require the inside-bar range divided by the mother-bar range to be at most 0.5. Exclude a zero mother-bar range.
• Volatility candidate: compare mother-bar range with 14-period ATR, for example testing a maximum of 1.5 times ATR. Keep the ATR measurement time fixed.
• Report trade count, average result after costs, drawdown and separate long/short results. Reserve a later period for evaluation after parameter selection.
• Check nearby settings and different market periods. An isolated best result can reflect parameter selection rather than a repeatable effect.

Audit TradingView fills before comparing results

TradingView strategies simulate trades. Under default calculation and fill settings, a market order created at a bar close fills on the next available tick, usually the next bar open. Do not label that fill as the confirmation close. For opposing pending entries, an OCA cancel group can cancel the remaining order after the first fills. Inspect both entry IDs and the trade list.

• If one historical candle crosses both boundaries, its OHLC values do not establish which boundary traded first. Inspect available lower-timeframe data and flag unresolved sequencing.
• A live candle's high, low and close can change before it finishes. Confirm the inside bar only after its close, and match alert timing to the chosen entry rule.
• Record symbol, timeframe, session, date range, commission, slippage and order-processing settings. Compare variants on the same inputs.
• Check expired setups, gaps through entry levels, and bars that reach both a stop and target. A favorable-looking equity curve does not resolve fill ambiguity.

Turn the rules into a script you can inspect

Pineify's Pine Script AI Coding Agent can draft a strategy from these written rules. Specify fixed mother-bar levels, strict containment, the entry mode, one trade per setup, expiry and exit handling in the request. Review the generated code and trades in TradingView. Syntax checks address code errors; they do not establish correct fills or profitable behavior.

• Use the Visual Pine Script Editor for supported indicator and condition combinations. Confirm that its available controls express your intended state and cancellation rules.
• After the strategy behaves as specified, expose selected thresholds as inputs for Strategy Optimizer to compare. Keep the reserved evaluation period separate from parameter selection.