How to define a setup so you can actually repeat it

To define a repeatable trading setup, write down the eligible instruments, evaluation time, exact trigger, context checks, and conditions that end the setup. Another person using the same data should be able to reach the same result without guessing what “strong” or “good volume” means. Precision makes a rule repeatable, not profitable.

Start with the sentence you cannot test

Consider this hypothetical instruction: “Watch for a strong breakout with good volume.”

At noon, a stock trades above its previous 20-session high. By the regular-session close, it is back below that level. One trader records a breakout. Another records no setup. Neither has necessarily misread the chart. The instruction left the timing undefined.

“Good volume” leaves another choice open: full-day volume compared with previous days, or volume so far compared with the same elapsed time on previous days? Those are different calculations.

A useful definition resolves these choices before the next chart arrives. CME Group’s trade-plan lesson similarly distinguishes setups from trigger points and asks traders to write exact entry and exit conditions. This guide focuses on the earlier monitoring decision: when a setup deserves review.

Separate the trigger from the surrounding decisions

There are several jobs hiding inside that one sentence:

• Eligibility: which instruments and sessions the rule applies to, and whether the required data exists.
• Trigger: the observable event that creates a review candidate.
• Context: additional facts reported alongside the trigger, each with its own definition.
• Personal action: what the trader does after reviewing those facts.
• Invalidation and expiry: what ends the idea or makes the observation too old to use.

Decide whether each contextual check is required, informative, or a blocker. A volume check that is required to qualify a candidate is different from a volume reading displayed beside every price trigger. Changing that role changes which candidates qualify.

Neither arrangement supplies an entry order, a position size, or a probability of success.

Replace the description with a rule

Here is an educational daily-stock example, not a recommended strategy or a claim about a supported HeraldGoat playbook.

The volume threshold is illustrative. It is context in this definition, not a gate on the price trigger and not evidence that the breakout will continue.

For this example, all prices use one provider’s split-adjusted, non-dividend-adjusted series, with volume adjusted consistently for splits. Save the provider, adjustment convention, and data revision with the result. Do not compare an adjusted close with unadjusted historical highs. If the required series is unavailable, the calculation remains unresolved.

The rules in compact form are:

level = maximum high of the previous 20 sessions
price trigger = current finalized close > level
baseline volume = sum of previous 20 session volumes / 20
relative volume = current finalized volume / baseline volume
volume context met = relative volume >= 2.0

Use 20 consecutive trading sessions from the relevant exchange calendar, not 20 calendar days or the last 20 rows that happen to be available. Require valid prices and volumes for every included session and a positive volume denominator. A missing volume input leaves volume context unknown; it need not erase an independently evaluable price trigger.

This definition tests a closing condition. It does not require proof of an intraday crossing or that the stock opened below the level. An opening gap followed by a close above the level also meets it. If that is not the intended setup, the rule needs another explicit condition.

Work through the same session twice

Suppose the previous 20-session high is 100 and those sessions have total volume of 40 million shares. Their mean volume is 2 million shares. Today’s finalized volume is 5 million shares, so relative volume is 5 ÷ 2 = 2.5×.

Strong relative volume does not rescue a failed price trigger. A midday price of 101 does not satisfy a finalized-close rule if the close is 99.40.

Now keep the 100.80 close but remove one required historical volume observation. The price trigger still passes if its price history is complete. The volume check becomes unknown. Reporting “breakout; volume unknown” preserves the evidence. Reporting “breakout with good volume” invents it.

This is also why the evaluated session must be excluded from the prior-high window. Including its own high changes the comparison; a valid bar’s close cannot be strictly above that same bar’s high.

Define what happens after it fires

For this monitoring example, the response is “open the chart and review.” It is not “buy at the recorded close.” A rule evaluated only after a finalized close cannot assume a fill at that already-observed price.

Save the breakout level of 100 with the candidate. As a hypothetical lifecycle rule, mark the candidate invalidated if a later finalized daily close is at or below that saved level. Expire it after the next regular session closes, whether or not it invalidates. Evaluate invalidation before expiry if both apply at that close. These are explicit example choices, not generally suitable holding or exit rules.

A new qualifying session creates a new dated observation under this example. Rerunning the same symbol, session, and version does not create another alert. If the intended behavior is one alert until a setup resets, define the reset condition instead of quietly adding it later.

A provider correction should amend the record with a visible correction history. It should not pretend the revised value was known when the original review happened.

Setup invalidation also needs to stay separate from an actual exit instruction. A closing condition does not place a stop order. FINRA’s order-type guidance explains that a triggered stop becomes a market order, whose execution price can differ from the stop price; a limit order may not execute. Recording a level does not cap a possible loss.

A reusable definition sheet

Before testing a setup, fill in these fields:

1. Name and version: what this rule is called, when it became effective, and what changed from the previous version.
2. Universe and eligibility: instruments, exclusions, dated watchlist, and any measurable liquidity requirements.
3. Data and timing: provider, session calendar, timeframe, adjustment policy, completed or live bars, and evaluation time.
4. Trigger: exact inputs, lookback, operator, threshold, and treatment of equality and gaps.
5. Context: each calculation and whether it is required, informative, or a blocker; what happens when it is unknown.
6. Lifecycle: duplicate handling, reset, invalidation, expiry, and corrections.
7. Personal response: review or skip criteria; separately defined entry, exit, sizing, and execution assumptions if a trade is considered.
8. Review record: original inputs, timestamp, rule version, result, unknowns, screenshot, and action actually taken.

Try it on a passing case, a failing case, an exact-boundary case, and a missing-data case. If two readers disagree, locate the undefined choice before adding more indicators.

When a rule changes, preserve the previous version. Moving a threshold from 2.0× to 1.5×, making volume mandatory, or accepting intraday prices creates a different definition. Keep the resulting observations distinguishable in later review.

What repeatability still cannot tell you

A precise rule can repeatedly identify losing opportunities. This example includes no performance test and establishes no trading edge.

Avoid defining the rule around a few attractive historical screenshots, replacing the original data with later corrections without a record, or grouping discretionary exceptions with trades that followed the rules. Those choices make the evidence harder to interpret.

A complete strategy assessment still needs entry and exit rules, costs, fills, risk assumptions, and an appropriate evaluation of outcomes. The setup definition gives that work a stable starting point. It does not supply the answer.

Where HeraldGoat fits

HeraldGoat is pre-launch. It is being built to monitor named playbooks, track setups as they change, and show inspectable context before the trader opens a chart. Clear rules make it possible to explain what changed, which conditions were met, and what remains unknown.

Initial testing is focused on opening-range break/retest and volume-weighted average price (VWAP) reclaim playbooks. The daily example above is educational, not an available custom strategy builder. HeraldGoat does not establish an edge, size positions, or execute trades. The trader keeps the decision.

Continue with the surrounding checks

• Understand the 20-day breakout comparison
• Review what belongs beside a breakout trigger
• Give alerts a defined response and reduce duplication
• Browse all practical trading guides

If repeating that first pass across a watchlist would be useful, you can join the launch waitlist.

Sources

• CME Group: Trading strategies in your trade plan: explicit conditions, setups, trigger points, and the surrounding trade plan.
• FINRA: Order types: execution distinctions between market, limit, and stop orders.

Method note: the daily rule, thresholds, prices, volumes, and lifecycle choices are hypothetical examples written to demonstrate an unambiguous definition. They are not backtest results or recommended trading parameters.

This guide is for educational information only. It is not investment advice, a recommendation, or a promise of returns. Trading involves risk, and actual losses can exceed planned losses.