A practical pre-trade checklist for swing traders

A completed checklist records the review. It does not confirm a trade, turn unknown evidence into a pass, or make the decision for you.

A practical pre-trade checklist for swing traders separates the facts on the chart from the decisions that only the trader can make. It should confirm the setup definition, reveal missing or time-sensitive information, and leave room to skip the trade. A completed checklist is a record of review, not confirmation that the trade will work.

The useful version is not a score. It is a sequence that makes each item answerable as met, not met, unknown, or not applicable, with a written reason when the answer is not met or unknown.

Use it before the order, not after the move

Consider a hypothetical daily closing-breakout candidate. A stock closes above a level the trader has already defined, and the relative-volume context is available. The chart may be worth opening. It is still too early to call it a trade.

Before entering, the trader needs to distinguish at least four different things:

  • Setup facts: what price, volume, trend, and level data actually show at the chosen evaluation time.
  • Event and trading conditions: whether an earnings date, corporate action, halt, thin trading, or other relevant fact changes the plan.
  • Personal risk and execution choices: invalidation, quantity, existing exposure, order type, and whether the idea fits the trader's own rules.
  • Decision: take, wait, skip, or collect more information.

Combining them into one green tick hides the decision. A setup can match the written rule while the earnings date remains unknown. In that case, the honest result is “setup matched; event check unknown; do not force a verdict.”

The reusable checklist

Fill this in at the same point in the process every time. For a daily swing process, that might mean after the regular-session close and before placing an order for a later session. It is a template, not a recommended strategy, threshold, holding period, or allocation.

CheckRecord before decidingPossible result
1. Exact setupRule name and version; instrument eligibility; timeframe; trigger; whether the relevant bar is finalMet, not met, or unknown
2. Broader contextThe market and instrument context your written process requires, plus the source and evaluation timeMet, not met, unknown, or not applicable
3. Level and roomThe reference level, nearby support or resistance, and what “room” means in your own ruleRecord facts, then apply your rule
4. Volume and volatilityThe selected baseline, completed/live status, and whether the data is comparableMet, not met, or unknown
5. Scheduled eventsThe issuer source checked, event date/time if known, and your written treatment of uncertaintyClear, blocked, or unknown
6. Entry and invalidationThe conditions that would permit entry and the fact that would invalidate the ideaDefined, undefined, or changed
7. Risk and correlationPlanned loss model, quantity, open positions with related exposure, costs, and gap riskWithin your limit, outside it, or unknown
8. Order detailsBroker-supported order type, price instructions, duration, market session, and expected liquidityReady, revise, or do not place
9. Personal readinessWhether the decision follows the written process rather than urgency, revenge, or a need to actProceed, wait, or skip
10. RecordTimestamp, screenshots, facts used, unknowns, decision, and later outcome kept separateComplete or incomplete

“Not applicable” should be reserved for a check that genuinely cannot apply under the written strategy. It is not a softer version of missing data. “Unknown” means the evidence required for the check was unavailable, stale, contradictory, or not yet assessed.

Work through one hypothetical candidate

Assume a trader's written process watches a daily closing breakout. At 4:15 pm New York time, an eligible stock has a finalized regular-session close of 51.20. The pre-defined prior level is 50.00. The trader's 20-session baseline volume is 1.8 million shares and the completed session volume is 3.6 million shares.

The transparent arithmetic is:

close beyond level = 51.20 > 50.00
relative volume = 3.6 million / 1.8 million = 2.0×

Those facts may satisfy this hypothetical setup's price and volume conditions. They do not provide an entry price, a quantity, a stop execution price, or a forecast.

The next item is the event check. The trader searches the issuer's investor-relations calendar and the information is unavailable at the time of review. The correct row is:

CheckEvidenceResultDecision impact
Exact setupFinalized close of 51.20 above 50.00MetContinue the review
Volume context2.0× the stated 20-session baselineMetContinue the review
Earnings dateNo current issuer-calendar confirmation foundUnknownFollow the written unknown-data rule; do not relabel it clear
InvalidationNo level or condition written downUndefinedDo not turn the chart into a trade plan after entering
Existing exposureOne related position has not been reviewedUnknownCheck it before choosing quantity

This example stops there. A trader whose rules block unknown earnings information skips or waits. Another trader may have a different, pre-written treatment. Neither outcome is supplied by the breakout itself.

Keep the chart review separate from the trade decision

The first five checks describe the candidate. The next four describe a proposed action. That boundary matters because a good-looking chart can create pressure to retrofit risk and execution choices around it.

Write the invalidation condition before entry. It could be a price level, a time-based condition, a change in the setup state, or a combination. The article does not prescribe one. What matters is that the condition is clear enough to be recorded and reviewed later.

Quantity is a separate calculation. A fixed percentage or quantity is not universally suitable. Position sizing: separating risk from conviction shows why a planned loss model, costs, liquidity, correlation, rounding, and gaps can produce a different result from a simple price-distance calculation.

Order choice also needs its own line. A limit order can provide price control but may not execute. A stop order can become a market order after its stop price is reached, which can mean execution at a different price in a fast-moving market. FINRA's order-type guidance describes these distinctions. Record the broker's actual supported order type and session rules instead of assuming that a label means the same thing everywhere.

What the checklist does not tell you

A checklist cannot turn a setup into a probability score or a trade recommendation. Ten completed rows do not outweigh a material unknown, and a single failed rule can be enough to skip an otherwise attractive chart if that is how the process is defined.

It also cannot remove overnight gaps, partial fills, changed liquidity, data corrections, a missed order, or a different result from the one imagined at review time. A stop level is a planned response condition, not proof of an exit price.

The checklist is most useful when it makes a reason to skip visible. “No trade today” can be the complete output of a sound process. Recording that decision prevents a later outcome from rewriting what was known at the time.

Common ways a checklist becomes decoration

  • Checking it from memory: record the facts and timestamp. A vague recollection is difficult to review.
  • Turning unknown into pass: no confirmed event date is not the same as no upcoming event.
  • Changing definitions after a chart appears: preserve the original rule version. A new exception is a changed rule, not proof that the old one passed.
  • Using an after-hours price with a regular-session rule: state the session and bar finality before comparing prices or volume.
  • Counting the same exposure twice: review positions, pending orders, and related instruments before treating a new idea as independent.
  • Using a stop as a loss guarantee: market conditions and order mechanics can produce a different fill from the intended level.
  • Reviewing only winners: keep skipped candidates, rule deviations, and incomplete records alongside outcomes. Otherwise the checklist can become a story told after the fact.

Where HeraldGoat fits

Checking one chart manually is manageable. Repeating the same setup, context, freshness, and unknown-data checks across a watchlist is the repetitive part.

HeraldGoat is pre-launch. It is being built to monitor named playbooks, follow their changing state, and make selected market-context facts inspectable before a trader opens a chart. Initial testing is focused on opening-range break/retest and VWAP reclaim playbooks. It does not assess account risk, personal readiness, position size, order choice, or whether a trader should act. The trader keeps those decisions.

Use the checklist alongside these guides

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

Sources

  • FINRA: Order types: the distinction between market, limit, stop, and stop-limit orders, including execution and fill uncertainty.

Method note: the checklist is a reusable educational template. The stock, prices, volume, time, and results in the example are hypothetical. They are not a backtest, a recommended strategy, or evidence of an expected return.

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.