Pre-Trade Checklist
Learn how a pre-trade checklist blocks setup, risk, execution and operational errors before an order is placed, using hard gates rather than vague caution.
Reading progress — saved on this device
A pre-trade checklist is a short decision gate used immediately before execution to confirm that a proposed trade satisfies strategy, risk and operational requirements.
Learning objectives
- Design a checklist around high-impact trading errors.
- Separate setup validation from portfolio and operational checks.
- Use binary gates and measured thresholds to prevent rationalisation.
What it is
Checklists are valuable when errors are predictable but easy to overlook under time pressure. In trading, common examples include incorrect size, entering before a known catalyst, excessive aggregate exposure, choosing the wrong contract or using an unsuitable order type.
The checklist should not repeat the entire trading plan. It should contain the small number of items whose omission can materially change the expected trade or create avoidable tail risk.
Some items can be binary, such as whether the setup is valid. Others need measured thresholds such as spread, funding, loss-at-stop, liquidity or portfolio risk. The key is that an answer has a defined consequence.
How to design useful gates
Sequence matters. Verify thesis and setup before spending time on execution details. Then confirm invalidation, size and portfolio exposure. Finally check venue, order type, liquidity and event risk.
A "no" on a hard gate should stop the trade. If the trader can override every answer because conviction feels strong, the checklist merely documents rationalisation.
For discretionary strategies, a confidence note can be captured after hard rules are passed, but confidence should never repair a failed risk gate.
Track checklist breaches in the journal. Repeated breaches reveal whether the checklist is badly designed or whether the trader is systematically bypassing a useful control.
Control framework
| Gate | Purpose | What to verify |
|---|---|---|
| Setup gate | Confirms edge | All required entry and regime conditions are present. |
| Risk gate | Caps loss | Invalidation, position size and aggregate exposure are inside limits. |
| Execution gate | Reduces avoidable cost | Correct instrument, venue, order type, spread and slippage plan. |
| Event gate | Controls surprise exposure | Known macro, unlock, funding or protocol events are understood. |
Worked example and thought exercise
A planned trade risks 300 at its stop and fits the setup, but adding it would raise aggregate correlated open risk from 1,700 to 2,000 while the portfolio limit is 1,800. The checklist rejects the trade even though the chart qualifies.
This is exactly the purpose of the control: prevent a compelling local setup from bypassing a portfolio-level constraint. The trader can reduce another position, reduce this trade if the plan permits, or do nothing.
Thought exercise: why should the checklist be completed before even a small starter position is opened?
Common mistakes and practical workflow
- Including dozens of low-value questions until completion becomes rote.
- Allowing subjective conviction to override hard risk limits.
- Completing the checklist after the trade.
- Failing to review which checklist items actually prevent errors.
Practical workflow
- Identify the highest-cost preventable errors in the strategy.
- Convert them into observable yes-no or threshold questions.
- Order the checklist from setup to risk to execution to event checks.
- Make hard-gate failures block execution.
- Review breach frequency and revise the checklist only from evidence.
Knowledge checkpoint
- Why should a checklist be shorter than the full trading plan?
- What makes a question a hard gate?
- Why does portfolio risk belong beside setup validation?
- What can repeated checklist breaches reveal?
FAQs
❓ How many items should a checklist contain?
There is no universal number. It should be short enough to use consistently and complete enough to catch high-impact errors.
❓ Can I override a checklist?
Only if the plan explicitly defines an exception process; routine ad-hoc overrides defeat the control.
❓ Should every strategy use the same checklist?
Core risk items can be shared, but setup and execution items should match the strategy.
❓ Why record checklist breaches?
They reveal recurring process failures that P&L alone may hide.
Summary
A pre-trade checklist is a compact control layer between analysis and execution. Its value comes from hard gates, measurable thresholds and consistent use before the order is placed.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →