Module 6 · Lesson 5 of 17 · Risk, process, and mindset · About 5 minutes
A Pre-Trade Checklist: Slowing Down Before Acting
On this page
Before you read: Building a Trading Plan Document
What you will learn
- What a pre-trade checklist is and why fields such as aviation and medicine use checklists.
- Example items for data, events, size and plan fit.
- Why a checklist reduces avoidable errors but cannot predict outcomes.
Why use a checklist?
Can a short list prevent mistakes that knowledge alone does not?
Checklists are used in aviation and medicine because skilled people still skip steps under time pressure. In trading, a checklist is a short list read before placing an order. It slows the moment of action and catches simple errors, such as the wrong instrument, the wrong size or a forgotten event.
What might a checklist include?
What could go wrong before the order is even placed?
A fictional example:
- The symbol, contract month and session settings are the ones in my plan.
- I checked the economic calendar for scheduled releases in the next hour.
- The position size matches my per-trade risk using the arithmetic in my plan.
- My daily loss limit has not been reached.
- This trade matches conditions written in my plan, in my own words.
- I know where I will exit if I am wrong, and the order type I will use.
- I am not trading to make back a recent loss.
Each item is a yes or no question. A “no” means stop and check, not “find a reason to continue”.
Checklist diagram
Illustrative diagram constructed for teaching. Not real market data.
The diagram shows a fictional checklist with seven yes or no items covering symbol and session, events, size, daily limit, plan match, exit and emotion, with a note that any “no” means stop and check. All values are made up.
What can a checklist not do?
If every box is ticked, will the trade work out?
No. A checklist reduces avoidable errors, not market risk. Trades that pass every item can still lose. A checklist that grows too long gets skipped, so keeping it short and reviewing it with your journal helps. Recording whether each item was checked lets a later review see where steps were missed.
What this does not tell you about checklists
- Which items your own checklist should include.
- Whether passing a checklist makes a trade likely to gain.
- Any conditions for entering or exiting trades.
- Nothing here suggests any trade.
Method in Practice: filled in on Replay A's morning
Fictional example. John, Harbor Index futures, the prices, times, costs and results are all invented for teaching. This shows how a written plan can be built and tested. It is not a recommendation, and nothing here says how often this idea works.
Try it on a real chart. Test this idea yourself on past sessions with bar replay. Keep your own count, including the days with no trade.
The idea. A checklist is a list of yes-or-no questions read just before the order. A "no" means stop and check. This is the lesson's own example checklist, filled in by John on three mornings.
Three outcomes
-
Replay A's morning: seven yeses, so the order went in
-
A morning with a "no": a release was due at 10:00 and the setup came at 09:30. Item 2 was no, so no order
-
Replay C's morning: item 5 was no (only one close above), so no order. The checklist confirmed the plan
Show the filled-in checklists
| Item (this lesson's example) | Replay A, 10:00 | Release morning, 09:30 | Replay C, 09:30 |
|---|---|---|---|
| 1. Symbol, contract month and session settings match my plan | Yes | Yes | Yes |
| 2. I checked the calendar for scheduled releases in the next hour | Yes, none | No: release at 10:00 | Yes, none |
| 3. Position size matches my per-trade risk arithmetic | Yes, 2 contracts | — | — |
| 4. My daily loss limit has not been reached | Yes | Yes | Yes |
| 5. This trade matches the written conditions, in my words | Yes, two closes above 101.20 | — | No: one close above |
| 6. I know where I'll exit if I'm wrong, and the order type | Yes, close below 101.20, market | — | — |
| 7. I'm not trading to make back a recent loss | Yes | Yes | Yes |
| Result | Order placed | Stop: no order | Stop: no order |
Journal, release morning: "The setup looked good at 09:30, and item 2 said no. I didn't look for a way around it."
Test it yourself
- Read your checklist out loud before the next ten orders, practice or live.
- Log every "no", and what happened afterwards.
- If an item is always "yes" without thought, rewrite it so it makes you check something.
Where it breaks
- A full row of yeses doesn't mean the trade works (Replay B also had seven yeses).
- A checklist only catches what's on it.
- Under pressure, people tick boxes without reading them.
Reflection question: What on your checklist would have stopped your last avoidable mistake?
Check yourself
- Why do skilled people still use checklists? Hint: time pressure.
- What should a “no” answer lead to? Hint: stop and check.
- Why keep a checklist short? Hint: long lists get skipped.
Reflect on your own process
- Which items on your own checklist come from mistakes you have actually recorded, and which are guesses?
- How does your journal show whether each checklist item was answered before the order was placed?
- When a checklist item is answered no, what does your written process say happens next?
- What on your checklist would have stopped your last avoidable mistake?