Pre-Trade Checklist Template for Discretionary Traders

A pre-trade checklist is a short decision check completed before placing an order. It compares the trade you are considering with the setup, timing, risk, and session rules you defined in advance. It does not tell you whether a market will move in your favor. Its job is narrower: make the standard for this decision visible before the outcome can influence your explanation.

That distinction matters for discretionary traders. Judgment may be part of the method, but judgment without a stable reference point is difficult to review. A checklist gives the trader a compact way to answer: Does this trade qualify under the process I intended to follow?

Copyable pre-trade checklist template

Copy this compact record and replace the placeholders with the terms from your own plan. A blank or unconfirmed answer is not a pass.

Checklist completed at: [YYYY-MM-DD HH:MM, timezone]
Instrument and direction: [instrument] / [long, short, or other permitted direction]
Setup identity: [planned setup name]
Setup eligibility: [PASS / FAIL / UNKNOWN] — [required conditions and brief evidence]
Trigger and timing: [PASS / FAIL / UNKNOWN] — [trigger] / [planned window]
Proposed entry: [price, level, or method-defined entry]
Invalidation and applicable exit method: [PASS / FAIL / UNKNOWN] — [condition] / [plan-defined exit method]
Risk and proposed size: [PASS / FAIL / UNKNOWN] — [planned exposure] / [quantity]
Session permission and active restrictions: [PASS / FAIL / UNKNOWN] — [current session state, boundaries, and restrictions]
Failed or unresolved condition: [condition, or none]
Final classification: [QUALIFIED, NOT QUALIFIED, or PENDING VERIFICATION]
Next action: [Eligible for separate order decision / Do not place / Verify before reconsideration / Reassess when permitted]
Exception, if applicable: [affected rule] / [pre-existing authorization] / [contemporaneous reason] / [no higher-priority conflict confirmed]

Use the record before the order decision and preserve it with the decision record. For review, compare the completion time with an independently identifiable order-decision or execution time. If that timing cannot be established, classify the record as timing-unverified; do not count an unverified timestamp as evidence that the checklist was completed before the decision. The template checks plan eligibility; it does not predict profitability or recommend entering a trade.

What should a pre-trade checklist do?

A useful pre-trade checklist should verify the few conditions that determine whether an order is eligible now. It should help the trader identify a missing condition, a change in planned risk, or a session boundary before those details become post-trade notes.

It should not become:

a complete trading plan;
a prediction score for the next trade;
a generic list copied from another trader;
a demand to feel calm or confident;
proof that the strategy has an edge; or
a guarantee that the written rules will be followed.

The checklist is a decision interface for an existing method. If the method does not define a setup, invalidation, or risk process, checking boxes cannot supply those definitions. Start with what a trading plan includes before compressing it into a live check. The boundary and response fields can then be operationalized through trading guardrails rather than left as reminders with no defined action.

If the plan contains many interacting rules, use the trading-rules hierarchy to decide which conditions the checklist should surface first.

Trading plan versus pre-trade checklist

A trading plan and a pre-trade checklist serve different moments.

Tool	Primary job	Typical detail	When it is used
Trading plan	Define the broader decision framework	Markets, setups, risk method, management, session rules, and review process	Before the session and during scheduled review
Pre-trade checklist	Test one proposed order against that framework	The few conditions that must be true for this trade now	Immediately before an order decision
Trade record	Capture what actually happened	Intended action, execution, result, context, and deviations	During or after the trade

The plan is the source. The checklist is a compressed view of the plan. The record shows whether the intended and observed decisions matched. Treating one tool as all three creates gaps: a long plan may be too slow to consult live, while a five-line checklist is too small to explain the entire method.

Why define the response before the trade?

Research on implementation intentions supports the broader self-regulation principle of deciding in advance when, where, or how a response should occur. Gollwitzer and Sheeran’s meta-analysis examined if-then planning across goal-pursuit settings.¹ This is cross-domain behavioral evidence for predefining a response—not evidence that a pre-trade checklist improves trading performance, profitability, or strategy quality.

Defining the response before the trade also protects the distinction between process and result. Baron and Hershey found that people judged decision quality differently once they knew the outcome, even when the information available at the time of the decision was otherwise the same.² Their finding supports the claim that outcome knowledge can affect decision evaluation. Separately, this article proposes completing and preserving a contemporaneous checklist as a reference for later process review; that workflow is not a direct validation of pre-trade checklists, recordkeeping effectiveness, or trading returns. A record reconstructed afterward cannot by itself show what standard applied at the decision point.

The five parts of a practical pre-trade checklist

The exact conditions must come from your own tested method and risk decisions. The following structure identifies the categories a checklist may need without prescribing a strategy.

1. Setup eligibility

Name the setup being considered and confirm that its required conditions are present. “The chart looks good” is difficult to classify later. A better prompt points to the method’s actual definition:

Which planned setup is this, and which required condition confirms that it is eligible?

For a discretionary setup, not every condition needs to be binary. The checklist can include a brief reason field when judgment is legitimate. What matters is recording the standard used before entry instead of reconstructing it after seeing the result.

2. Timing and invalidation

Confirm that the opportunity remains inside the method’s time window and that the condition which would invalidate the idea is known. This catches a common difference between recognizing a setup and chasing a setup that was present earlier.

Useful prompts include:

Is the entry still inside the planned timing window?
Is the required trigger present now?
Does the plan require checking scheduled events or market conditions before this setup is eligible?
What observable condition invalidates the trade idea?

The checklist should not ask whether the trade “feels late.” It should refer to the timing rule already defined by the trader.

3. Planned risk and size

Verify the planned risk decision before calculating or submitting size. The checklist does not determine an appropriate risk level. It checks whether the proposed exposure follows the trader’s existing process.

Ask:

What is the planned risk for this trade under the current session state?
Does the proposed size follow that risk and the defined invalidation?
Has any result earlier in the session changed what I want to risk without changing what the plan permits?
What are the proposed entry, method-defined invalidation, and applicable exit method?
Do existing exposure, costs, and slippage assumptions change the permitted exposure or size?

Keep risk checks separate from confidence. A setup feeling unusually strong is not, by itself, a documented sizing rule. For the broader distinction between exposure design and execution, read trading risk management.

The position-sizing workflow owns the detailed calculation; this checklist records whether its inputs and resulting size match the active plan. A known invalidation is an assumption used in the plan, not a guarantee that an executable stop will fill there or that realized loss will be capped at the planned amount. Keep the planned amount and the realized result as separate records.

4. Session state and boundaries

The same setup may not be eligible in every session state. A cutoff time, a predefined exposure state, an attempt rule, or a re-entry condition may change whether another order belongs to the plan.

Check the current state rather than relying on memory:

Is a new entry permitted at this point in the session?
Does a prior exit or loss activate a re-entry rule?
Is the trade inside the planned market and session scope?
Has a predefined boundary already been reached?

These questions are especially important when the proposed trade would be reasonable in isolation but conflicts with what occurred earlier in the session.

5. Decision and exception

End with one of three classifications. The classification is about eligibility under the plan, not expected profitability or a recommendation to enter:

QUALIFIED: all mandatory conditions are verified, applicable restrictions permit the action, and any discretionary judgment follows the pre-existing plan.
NOT QUALIFIED: a mandatory condition fails or a higher-priority restriction prohibits the proposed action.
PENDING VERIFICATION: a required condition cannot currently be confirmed. This is an intermediate verification status, not permission to trade.

Apply the classification in this order: first evaluate confirmed hard constraints and applicable higher-priority restrictions; any disqualifying failure makes the proposal NOT QUALIFIED, even if another condition is UNKNOWN. Next evaluate any pre-authorized exception against the exact affected rule, its authorization, its reason, and confirmation that no higher-priority restriction conflicts with it. If no disqualifying failure remains but a mandatory condition is UNKNOWN, classify the proposal as PENDING VERIFICATION. Classify the proposal as QUALIFIED only when every mandatory condition is verified, all applicable restrictions permit the action, and discretionary judgments comply with the existing plan.

Unknown must never be treated as PASS. Do not change plan requirements during a live decision to justify an order.

A documented exception is not a universal override. It is valid only when the plan contains a pre-existing authorization, the applicable condition is present, no higher-priority restriction conflicts with it, and the reason is recorded contemporaneously. A discretionary exception cannot override a hard stop, an account restriction, or another higher-priority prohibition. Record the exception reason alongside the classification; recording a reason alone does not make an exception valid.

What the template leaves to your method

The copyable template above is the single live-use template for this article. It deliberately avoids universal trade limits, risk percentages, indicators, and setup criteria. Those belong to the trader’s method, account constraints, and risk tolerance. A checklist copied from someone else can look precise while checking conditions that have no role in your process.

How to keep the checklist usable during a live session

Keep only decision-changing checks

Every item should be able to change or classify the current decision. “Follow my plan” adds no new information. “Entry remains inside the setup’s defined time window” can distinguish an eligible entry from a late one.

If an item never affects classification, move it to the plan or remove it. If a frequently missed rule is absent, add it only after review shows that making it visible would help.

Use the same language as the plan

Do not call a condition “confirmation” in the checklist if the plan uses several different confirmations. Shared language reduces interpretation and makes the later record easier to compare with the intended rule.

What should happen if a pre-trade check fails?

If a confirmed disqualifying check fails, the proposed order is NOT QUALIFIED, even when another required check is UNKNOWN. Only when no disqualifying failure exists does an unresolved mandatory condition produce PENDING VERIFICATION, and it remains ineligible until verification is complete. A pre-existing exception authorization may qualify a discretionary condition only when it applies, does not conflict with a higher-priority restriction, and is recorded before the decision.

The checklist cannot block an order or enforce a response. The trader remains responsible for acting on the result, and a QUALIFIED classification means only that the proposal is eligible under the plan—not that it is likely to be profitable or that the trader should enter.

How long should a pre-trade checklist be?

A pre-trade checklist should be short enough to complete immediately before an order decision while still capturing enough to reconstruct it: time, proposed setup, key checks, planned risk, classification, and any exception reason. Rewriting the complete plan before every order defeats the purpose of a compact check.

The correct length is not a universal number of questions. It is the shortest version that still exposes the rules which repeatedly matter to your execution.

What changes between checklist completion and order submission?

A material change between completing the checklist and the order decision invalidates the affected checks. Examples include trigger expiration, a material entry-price change, changed position size or exposure, or a newly activated session restriction. Reassess the affected conditions without unnecessarily repeating unchanged checks; the final classification must reflect the information applicable at the actual order-decision point.

Worked example: a valid setup blocked by a session restriction

Jordan is a fictional trader reviewing a fictional session. The proposed order in Instrument X is long. The planned setup identity, required conditions, trigger, proposed entry, invalidation, applicable exit method, planned exposure, and proposed size are all verified against Jordan’s existing method. The setup is eligible on its own terms.

Jordan’s session plan also contains a current mandatory restriction: no new exposure may be initiated during the plan-defined restricted interval. That restriction applies to this decision and does not have an authorized exception. The final classification is therefore NOT QUALIFIED, even though the setup itself is valid.

Jordan records the restriction and does not place the order. Reassessment requires the restricted interval to have ended, the setup trigger to remain valid, the risk and exposure checks to be current, and no other higher-priority restriction to apply. If the trigger expires before then, the proposal remains NOT QUALIFIED. Recognizing a valid setup does not override a separate prohibition on initiating new exposure.

State summary:

Setup: PASS
Session restriction: FAIL
Final classification: NOT QUALIFIED
Action: Do not place the proposed order.

How to review whether the checklist is helping

Do not judge the checklist by whether checked trades made money. A qualified trade can lose, and a skipped or overridden check can precede a profit. Review the checklist as a behavioral process.

Choose a fixed review window, then ask:

Completion: Was the checklist completed before the decision rather than reconstructed afterward?
Classification: Could you determine why each proposed trade was qualified, rejected, or treated as an exception?
Adherence: When a required check failed, did the final action follow the predefined response?
Friction: Which items were ambiguous, duplicative, or too slow to use?
Coverage: Did repeated deviations involve an important rule the checklist never surfaced?

Change checklist wording during scheduled review, not while trying to justify a current order. Preserve the distinction between improving the interface and changing the trading method. If a setup rule itself needs revision, that is a strategy or plan decision requiring the trader’s own evidence—not a reason to silently change a checkbox.

What can the review metrics actually measure?

Keep three measures separate, state the review window and declared scope, and report only what the records can observe.

Record coverage: denominator = all recorded executed trades within the stated review window and declared scope; numerator = trades with a sufficiently complete, contemporaneous pre-trade record that can be assessed against the plan applicable at decision time. Report missing, retrospective, and otherwise unassessable records separately; do not remove them from the denominator.
Adherence among assessable trades: denominator = executed trades for which the contemporaneous record, relevant plan, and observed action allow an adherence determination; numerator = those assessable trades whose actual action complied with the applicable rules, including only valid, pre-authorized exceptions. Report the assessed and unassessable counts separately. A QUALIFIED label alone does not establish adherence, and a retrospectively completed checklist does not establish contemporaneous eligibility.
Opportunity-level completion: denominator = candidate opportunities actually recorded within the declared observation window; numerator = those recorded opportunities with a checklist completed before their respective decisions. Label this as completion among recorded opportunities. Unrecorded opportunities prevent a full opportunity-level rate, and Costante does not automatically capture rejected or skipped opportunities. If only executed trades are available, do not report this measure as a full opportunity-level completion rate.

Checklist completion is not strategy adherence, and improved completion does not prove improved trading returns. If a denominator or the timing of a record cannot be established, report the missing or unassessable data rather than inferring compliance.

Common pre-trade checklist mistakes

Checking feelings instead of decisions

“Am I confident?” and “Am I emotional?” do not show whether a trade follows the plan. A trader can feel uncertain and take a valid setup, or feel composed and enter outside the rules. Translate the concern into the decision it might alter: setup eligibility, timing, size, re-entry, or session boundaries.

Completing it after the order

A post-entry checklist is a record of explanation, not a pre-trade intervention. If completion regularly happens late, reduce friction and inspect what makes the check impractical rather than treating retrospective boxes as evidence of adherence.

Letting a profitable exception rewrite the rule

Outcome does not determine whether the process was followed. Keep the trade result and rule classification as separate fields. A profitable deviation may deserve investigation, but it does not become part of the method without deliberate review.

Adding more boxes after every loss

Losses are inherent to trading and do not automatically reveal a missing rule. Add or revise an item when the existing prompt is ambiguous or when repeated review shows that an important planned boundary is not visible at the decision point.

Where Costante fits

Costante supports the behavioral-performance process around a trader’s existing method: session planning, self-defined behavioral guardrails, pre-trade and in-session checks, low-friction logging, and structured review. That can make the comparison between intended rules and observed decisions easier to inspect before, during, and after a session.

This is an educational checklist and a way to make trader-defined behavioral guardrails reviewable; it is not a broker-level risk control. Costante does not create a checklist that determines whether a setup has an edge, provide trading signals, connect to a broker, execute or block orders, enforce account or strategy rules, automatically capture rejected opportunities, or guarantee discipline or profitability. The trader remains responsible for the method, the checklist conditions, risk, and every order.

A useful pre-trade checklist is not a longer promise to be disciplined. It is a short comparison between the decision in front of you and the process you already chose. Build it from your plan, keep only decision-changing checks, and review adherence separately from P&L.

Sources

Costante provides educational workflow tools, not financial advice. Trading involves risk.