Trader checklists and weekly review
A checklist is not just a tool for beginners — it is a tool for anyone who makes decisions under time and financial pressure, because under pressure people simply forget basics that seemed obvious when they were calm. You do not have to overlook the calendar often: a single entry fifteen minutes before a release can be enough for slippage and a widening spread to exceed the entire risk allowed in your plan. This toolkit article delivers the templates promised in articles 15.5 and 15.6: four checklists (pre-market, pre-trade, EOD, EOW) and two practical weekly schedules. You can tick off each card directly on this page — the checklist module saves your answers only locally in this browser (localStorage) and does not send them anywhere — or print it using its own button. The pre-trade card belongs beside your monitor at eye level; a file buried in a folder on your drive will not be opened in a moment of pressure.
- Four checklists and two schedules: pre-market (8 items, 5–10 min), pre-trade (10 questions, target: about 30 s), EOD (7 items, 10–15 min), EOW (7 items, 30–45 min), plus a weekly plan in Central European time (CET/CEST) for swing trading alongside a full-time job and for intraday trading
- Everything is binary: the answer is YES or NO; “almost yes” = NO. In pre-trade, one NO means no entry — with no exceptions negotiated at the chart
- This pre-trade card is designed around 10 questions and about 30 seconds to confirm conditions checked earlier. This is a working target, not a safety limit or a standard for every checklist. If data is missing, stop the check and return to your analysis; the other cards have their own completion times
- Interactive or on paper: checkboxes saved locally in your browser, a count of questions blocking entry, and a button beside each checklist to print a separate A4 card. Paper is the quickest to adopt; the on-page version also collects information about blocked entries
Four checklists and two schedules form a single system: the schedule tells you when to work; the checklists tell you exactly what to check in each block. The EOW audit closes the loop, producing at most one process adjustment for the following week — often none:
| Tool | When | Time | What it protects against |
|---|---|---|---|
| Pre-market (8 steps) | Before the first decision of the day | 5–10 min | Trading on a day when you should not be in the market |
| Pre-trade (10 questions) | Before every order | 30 s | Entries outside the playbook, no SL, news in 20 minutes |
| Post-trade and EOD (7 steps) | After a trade + end of day | 10–15 min | A journal full of gaps that cannot be audited |
| EOW (7 items) | End of the week, at a fixed time | 30–45 min | Process drift and tuning the system to weekly noise |
| Swing schedule | Week, ~6–7 h in total | — | Trading clashing with a full-time job and making decisions on your phone at work |
| Intraday schedule | Day, 08:00–17:20 | — | An unstructured session: running overtime, chasing losses, trading after EOD |
On READ-DO cards, a tick means “done”; an unticked box means the step has not been done or checked. Pre-trade has YES, NO and an unanswered state: NO or even one missing answer means no entry. An empty field is not a confirmed NO in the breakdown of reasons, but it does not give clearance either. In EOD/EOW, an unfinished step means an incomplete review; a discovered limit breach or critical failure stops new entries according to the plan, regardless of the card’s counter.
The first visit uses your device’s zone. Saved cards and checks retain their original zone and session date when this setting changes. Earlier records without zone fields belong to Europe/Warsaw. Weekly statistics include checks saved in the selected zone; CSV exports every zone with its original dated UTC offset and UTC timestamp. The schedules and their DST alert below remain the Europe/Warsaw regional case.
JavaScript will show the selected time zone here.
Why a checklist beats memory and intuition
Aviation provides a well-known example of the importance of checking routine actions: the crash of the B-17 prototype (Model 299) on 30 October 1935. The investigation identified locked controls; the report did not establish the pilot’s “working-memory limit”. The story is associated with the development of aviation checklists, but does not establish when all checklists were invented. In medicine, a checklist implementation programme was studied: after the WHO’s 19-item surgical checklist was introduced in eight hospitals, the complication rate fell from 11.0% to 7.0%, and mortality from 1.5% to 0.8% (Haynes et al., NEJM 2009). The study compared 3,733 patients before implementation with 3,955 afterwards; it was a before-and-after study, not a randomised test of ticking boxes alone. The result concerns the entire programme to improve communication and care; it does not demonstrate an identical effect in trading. One clarification about its scope: this is evidence concerning omissions in aviation and surgery, not a promise of profit. A checklist will not turn a system without an edge into a money-making machine — at most, it will make you execute a losing system systematically and according to procedure.
Trading meets all the conditions of an environment where memory fails: time pressure, real stakes, competing demands on attention and fatigue that grows with every hour of a session. A checklist moves the check out of your head: 10 questions verifying previously calculated values take about half a minute — provided those values actually have been calculated, as discussed below — and its purpose is to reduce omissions that the journal labels “outside the plan”. Ticking boxes does not verify that the answers are true. A checklist supports the execution of a plan with previously tested expectancy — not an improvised variation dreamt up on Tuesday after a losing Monday.
Intuition needs a separate qualification. As described by Kahneman and Klein (2009), developing accurate intuition requires sufficiently predictable cues and opportunities to learn from feedback — chess, firefighting, landing an aircraft. The currency market is the opposite kind of environment: feedback is delayed and noisy (a good decision regularly ends in a loss), and plays out across changing regimes. A tagged sample of several dozen comparable trades can begin to organise observations, but it is not universal proof of an edge or accurate intuition. The sample size needed depends, among other things, on the dispersion of results, dependencies between trades and the number of variants tested; set your assessment rules before the test in protocol N. A checklist does not eliminate intuition — it confines its authority to the one place where you have data for it: recognising a setup from the playbook. Everything else (sizing, limits, the calendar, spread) is arithmetic and procedure.
Pre-market checklist (5–10 minutes)
Complete this before the first decision of the day: intraday traders do it in the 08:00–08:45 block; swing traders with a full-time job do it the previous evening (see the schedules below). Eight steps, each with a binary completion criterion. The 08:00–08:45 block in the intraday schedule consists of about 35 minutes of analysis and marking levels, plus 5–10 minutes of binary verification on the card. Select the IANA time zone for your cards above, then explicitly choose the session date. New visitors start with the device time zone; the default session date is today in that selected zone. The Warsaw schedules below are a regional example, not a mandatory local routine. when preparing a plan in the evening, choose the correct next trading day and check holidays and your broker’s hours. After the date changes, the earlier card remains available to view but is marked out of date; you deliberately start a new one.
| ✓ | # | Step | YES criterion (binary) |
|---|---|---|---|
| 1 | Today’s macro calendar | High-impact releases listed with times; windows of ±30 min (or the width specified in your plan) marked as no-new-entry zones | |
| 2 | Identify the regime | Every pair on the watchlist has a label: trend / range / breakout — one word, not an essay | |
| 3 | D1/H4 levels | Marked on the chart before you look at the intraday price; no more than 2–3 levels per pair | |
| 4 | Account and position status | Balance and equity, risk of positions and pending orders in the account currency (PLN in the example), conversion to the plan’s common R base, and each position’s distance from SL/TP recorded in the daily note — numbers on paper, not just something you know | |
| 5 | Daily limit | Written as a number (e.g. −3R = end of day), together with the current status of the weekly limit (limit rules — chapter 9.3) | |
| 6 | Equipment, connection, backup | Platform logged in, backup LTE tested, the broker-supported emergency channel from the contact card (toolkit K), its hours and the scope of assistance — checked in a test no more than a quarter ago, without live orders; telephone support does not necessarily allow trading | |
| 7 | Watchlist spreads | Reading and time recorded, the plan’s limit known. Measure again in pre-trade before a new order; an evening reading does not confirm the spread when a pending order is triggered later | |
| 8 | Session plan | Written down: which playbook setups I will trade today in this regime — and which I will not |
Item 6 looks excessive right up to the moment your connection drops with an open position during a release — an unattended position whose protection depends entirely on the terminal (e.g. a local script instead of an SL accepted by the server) is uncontrolled risk in the worst possible window. Hence the checklist’s internal hierarchy: first, what can ruin the day (items 1, 5 and 6); then, what shapes the plan (2, 3, 7 and 8); item 4 determines whether you have any limit left for new positions today at all.
An example card for a hypothetical Tuesday with an assumed US CPI release at 14:30 — these are synthetic data, not a calendar or quotes for any particular day. BLS publishes times in Eastern Time; 08:30 ET usually means 14:30 in Europe/Warsaw, or 13:30 during DST divergence periods. Item 1 determines the content of item 8:
| # | Card entry (example of a completed card) |
|---|---|
| 1 | US CPI at 14:30 — no-new-entry window 14:00–15:00 marked in the daily plan |
| 2 | EUR/USD: downtrend · GBP/USD: range · USD/JPY: uptrend |
| 3 | EUR/USD: 1.0740 / 1.0800 · GBP/USD: 1.2650 / 1.2720 — marked before the first look at M15 |
| 4 | Balance PLN 48,200, equity PLN 48,000 · common daily base 1R = PLN 240 · open planned risk PLN 120 = 0.5R (short EUR/USD, price 32 pips from SL); no pending orders — recorded in the daily note |
| 5 | Daily limit −3R, weekly −6R; −1R of the weekly allowance used |
| 6 | Platform and LTE working; example broker-channel test: 14 April, scope of assistance confirmed — next test by 14 July (these dates belong to the example; they do not confirm a current test) |
| 7 | EUR/USD spread 0.6 pips ≤ the plan’s 1.0 limit — OK |
| 8 | Plan: manage the open position only until 14:00; new entry only on a EUR/USD breakout after 15:15 if the spread returns to ≤ 1.0. No USD/JPY trades today (BoJ overnight) |
Pre-trade checklist — target: 30 seconds before entry
Run this after identifying a setup, before submitting an order. Every question has the same polarity: YES = the condition has been checked for this specific order; you can move to the next question. The overriding rule: one NO = no entry, without exceptions. Start with an empty card before each subsequent order (“Clear without saving”, or save the previous check). Restored ticks do not confirm a new setup or the current spread. After refreshing the page, returning from another window or changing the stored data in another tab, saved YES answers require another check: untick and retick them after checking, or start an empty card. Answers remain visible but do not restore a green result on their own. YES and NO are mutually exclusive, and when you finish the check, click “Save check” — the result, time and numbers of the blocking questions go into a local log, whose breakdown you review in item 3 of the EOW audit and reset for a new week. This is a version of the 15-item checklist in article 15.6, reduced to the minimum needed for execution; that article adds screening filters.
| YES / NO | # | Question | Entry criterion (binary) |
|---|---|---|---|
| 1 | Is the setup in the playbook? | YES — and it has a grade the playbook allows you to trade (in 15.6: A+ or B); a setup “similar to one in the playbook” = NO | |
| 2 | Is the setup’s context rule met? | YES — the condition written in the playbook for this setup: for trend-following trades, direction does not fight the H4/D1 structure; a countertrend setup has its own written rule | |
| 3 | Outside the high-impact release window? | YES — the time until the next release and since the previous one exceeds the window set in the plan and pre-market (item 1; example: ±30 min). Both ends of the window checked; an unconfirmed release time = NO | |
| 4 | Spread ≤ the plan’s limit? | YES — read from the platform now, not “from memory” | |
| 5 | R:R ≥ the setup’s playbook minimum? | YES — calculated to the TP determined by the structure, after costs; the threshold comes from the setup’s grade (in 15.6: B from 1:1.5, A+ from 1:2), not from one universal number | |
| 6 | Position size calculated from risk? | YES — from the risk amount to the volume (calculator in toolkit C), and before clicking, the estimated loss at SL including costs is checked in the account currency (e.g. PLN); this is not a guaranteed maximum loss — not just “I calculated it” | |
| 7 | SL ready to submit? | YES — the order form has the correct level and volume, with a broker-supported SL attached to the order. After submission, you must check acceptance and protection on the server; an entry in the form does not confirm that. A “mental stop” = NO | |
| 8 | SL consistent with the setup’s rule? | YES — the SL follows a written, tested exit model (e.g. a structural invalidation level or volatility). “Exactly 30 pips” requires a rule in the plan; the amount you “can afford to lose” does not by itself determine the SL level | |
| 9 | Limits and total exposure respected? | YES — the daily and weekly limits have not been reached, and planned risk after adding the new position (including pending orders and correlated exposure) fits within the plan’s limits; add amounts on a common base, in accordance with 9.3 | |
| 10 | Pre-trade journal entry ready? | YES — setup, grade and planned R recorded before entry, not afterwards |
Of the ten questions, we single out three as particularly critical (the concept of killer items discussed by Gawande); this is the card author’s selection, not a ranking of omission or loss frequency: question 3 (a release — a gap can jump past the SL by dozens of pips), question 6 (risk-based sizing — one oversized position turns −1R into a −5R loss) and question 7 (preparing the SL and confirming it after submission — a lost connection with a “mental stop” leaves the position on its own). The other items can also block critical risks — particularly item 9 on limits. No YES guarantees stop execution at the specified price.
Post-trade and EOD checklist (10–15 minutes)
Complete steps 1–4 after every closed trade, and steps 5–7 once a day when you finish work. With the data to hand, post-trade takes 2–3 minutes — with one qualification: a standard MT4/MT5 report does not show MAE and MFE per trade, so obtain these two values using the procedure in article 15.9 (which also contains the complete journal column structure); the ready-to-use spreadsheet in toolkit F converts supplied MAE/MFE into the appropriate units and aggregates metrics, but does not retrieve historical price movements itself.
| ✓ | # | Step | “Done” criterion (binary) |
|---|---|---|---|
| 1 | Trade in the journal | R-multiple, MAE and MFE obtained using the procedure in 15.9, not reconstructed from memory | |
| 2 | Compliance classification | Status assigned: according to plan / violation — regardless of the financial outcome | |
| 3 | Chart screenshot | Saved with entry, SL and TP marked; filename: date + setup name | |
| 4 | Deviations from the plan | Listed with reasons, one line per deviation — no excuses | |
| 5 | Daily limit updated | Daily and weekly limit status recorded in R; limit reached = no new entries; manage open positions and pending orders according to the plan before finishing work | |
| 6 | Mental state | Score of 1–5 recorded (fatigue, tilt, FOMO) — raw material for correlations in the EOW audit | |
| 7 | Levels for tomorrow | D1/H4 marked in the evening; forex continues trading on weekdays, so state whether you are using a closed candle and which server time zone — not in a morning rush |
The classification in item 2 gives four possible trade outcomes; assess financial performance and process compliance separately:
| Outcome | According to plan | Violation |
|---|---|---|
| Profit | An outcome consistent with the process — one trade does not justify any changes | Misleading: the reward can reinforce breaking the procedure (see FAQ below) |
| Loss | The cost of running the system — not an error or a reason to adjust it | Financial loss and a process violation: investigate the cause and the safeguard; the pain of a loss alone does not guarantee a quick correction |
Weekly EOW audit (30–45 minutes, end of the week)
A fixed slot in the calendar, different for each approach: swing traders with a full-time job audit on Saturday, 10:00–10:45; intraday traders on Friday from 15:00, instead of the last trading hours (both slots appear in the schedules below). Inputs are EOD records from actual working days, including days without trades, plus the status of open positions and orders. A shorter week does not require five entries; explicitly mark missing data.
EOW is not a fresh analysis of every trade — EOD already did that as you went along. The audit starts with aggregates and patterns, returning to individual trades when an anomaly, data error or violation needs checking. Returning to candles makes sense when examining a specific event. Replaying the entire week without a question to investigate, however, encourages fitting the system to a remembered case rather than to the distribution of outcomes.
| ✓ | # | Audit item | Specific action |
|---|---|---|---|
| 1 | Weekly metrics | Trade count, win rate, sum of R, profit factor — entered in the weekly worksheet to see the 4–8-week trend, not just one week | |
| 2 | R distribution by setup | Which setup contributed to the result and which gave it back; minimum: a table of setup × trade count × sum of R | |
| 3 | Violations and blocks | How many violations, which ones, and do they recur: the same time? The same pair? The same mental state from EOD item 6? Also: which pre-trade question blocked entry most often this week (the check log above or tally marks on the paper card) — after reviewing it, copy the log to your archive; only then reset it, if you wish | |
| 4 | Compare with the playbook | Whether win rate and average R fall within the ranges from testing; five days rarely settle whether an edge exists; distinguish a small sample from a failure, data error or change in conditions. Fitting filters solely to one weaker week risks overfitting to noise, which destabilises the system | |
| 5 | Weekly limit | Breached or not; if so: one bad session or a sequence, and what mechanism took it past the limit | |
| 6 | Conclusions → 0–1 process adjustment | Usually at most one process change for next week; address a critical threat immediately, with several actions if needed. No change is also a valid audit outcome; record the change in the weekly plan so you can review it at the next EOW | |
| 7 | Next week’s macro calendar | High-impact releases listed with times, no-entry windows transferred to daily plans |
A week without closed trades: enter a trade count of 0 and a sum of realised R of 0; leave win rate and profit factor blank (or mark them “not applicable”). Do not enter 0% or PF=0 as an assessment of the system. If there are trades but no losses, PF likewise has no finite value — consistent with spreadsheet F , the field stays blank. Analyse open risk, unrealised P&L and violations separately; no closed trades does not mean no exposure.
Why at most one adjustment, not three? Attribution. If on Monday you change the pre-market time, the spread threshold and how you record mental state all at once, by Friday you do not know which change helped — and after a weak week, you do not know which hurt. One change at a time is still an observation on a noisy sample, not a controlled experiment — but at least you know which variable you are discussing. Do not change the procedure after one slip, or change anything simply because a week has passed: an adjustment is made when the same error has recurred in at least two consecutive EOW audits, or a single event has exposed a critical risk.
Weekly schedule — swing trading alongside a full-time job (CET/CEST)
Assumptions: a 09:00–17:00 job, decisions on D1/H4, execution through pending orders with server-side SL. The week is built around one decision-making block in the evening — in the morning, verify the prepared scenarios and take protective action if needed, without inventing a new setup. Times are CET/CEST; the US and Europe change clocks on different dates, so during the divergence periods (in 2026: 8–28 March and 25–31 October), US releases and the New York session occur one hour earlier than usual in this time zone. When such a period is in progress, an automatic warning appears above the tables.
| Day | Window (CET/CEST) | Block | Specific action |
|---|---|---|---|
| Mon–Fri | 07:30–08:00 | Morning review | Open positions and pending orders versus overnight developments; with no open positions, this takes 5 minutes, not 30 |
| Mon–Fri | after work, around 17:30–17:45 | EOD | Full record on days with a trade or event (fill, SL, TP); on other days, briefly confirm limits, open positions and no events, without creating a fictitious trade |
| Mon–Fri | 21:00–21:45 | Pre-market for the next session | 8-step checklist + pre-trade before submitting or changing an order’s parameters. Next session date: a Friday plan does not assume an ordinary Saturday session; check it again before trading resumes. Account for holidays and order validity |
| Saturday | 10:00–10:45 | EOW | Weekly audit, 7 items as above |
| Sunday | 21:30–22:00 | Gap-risk review | Weekend news versus open positions before the market opens — usually around 23:00 Europe/Warsaw time throughout the year (brokers open around 17:00 New York time), or around 22:00 during US–Europe clock-change divergence windows; check the exact time in your broker’s specifications. Decision plan: hold / intend to reduce once trading becomes available. Reducing exposure before the open may be impossible; decide weekend exposure before Friday’s close, without a guaranteed price when trading resumes |
| Total | — | for example, ~6–7 h/week | The maximum blocks in this table add up to 8 h 15 min (5×30 + 5×15 + 5×45 min + 45 + 30 min). The example’s core blocks total 6 h 10 min: morning 15 min × 5, full EOD 10 min × 2, analysis 40 min × 5, EOW 45 min and Sunday 30 min. Adding a brief 2-minute check on the other 3 days gives 6 h 16 min. This is a planning assumption, not a measurement of the typical workload; carry out the brief limits and events check even without a closed trade |
This approach rests on one principle: a pending order executes overnight a decision you made in the evening using the checklists — but it does not react to a change in context, a price gap or unscheduled news. That is why the evening block ends with orders set with server-side SL and TP, and the morning review checks one thing: whether overnight events invalidated the assumptions (gap, intervention, news from Asia). If so, cancel orders that are still active and check confirmation of cancellation; some may already have been filled by morning. For an open position, follow the management plan or emergency plan K. Unattended activation requires tested rules for validity, release windows, costs and available protection; an evening YES alone does not confirm conditions at the fill.
Schedule — intraday trading (London/NY session)
Assumptions: M5–H1 trading during the most liquid hours, with full availability during session blocks. The day has firm boundaries for one reason: without a written finishing time, a session ends when the daily limit runs out. During US–Europe clock-change divergence periods (in 2026: 8–28 March and 25–31 October), the NY activity block used here starts at 13:00 instead of 14:00. Not all data is released at that time: an 08:30 ET release then occurs at 13:30 instead of 14:30. Move the re-briefing, afternoon block and EOD one hour earlier, and shorten the break to 12:00–12:30; the morning block remains unchanged.
| Window (CET/CEST) | Block | Specific action |
|---|---|---|
| 08:00–08:45 | Pre-market | 8-step checklist: calendar, regime, levels, limits, equipment, spread, session plan |
| 09:00–12:00 | London session | Only setups from the session plan; 10-question pre-trade check before every order |
| 12:00–13:30 DST: 12:00–12:30 | Mandatory break | Away from the charts — step away from actively looking for entries; close the platform only if doing so does not cut off necessary monitoring or local automation. The three-hour block is an assumption of this plan, not a biological threshold. Before the break, protect open exposure and arrange monitoring; your own journal and EOD item 6 will help you choose the length of your work blocks |
| 13:30–14:00 DST: 12:30–13:00 | Pre-NY re-briefing | Afternoon calendar (US data), review of open positions and the session plan — no new orders until the block specified in this plan begins |
| 14:00–17:00 DST: 13:00–16:00 | London/NY overlap block | Second part of the session; the daily limit applies cumulatively from the morning, not “from scratch after the break”. During clock-change divergence: 13:00–16:00 |
| 17:00–17:20 DST: 16:00–16:20 | EOD | 7-step checklist; no more new entries. Before closing the platform, confirm protection and monitoring of remaining exposure and whether automation depends on the terminal |
| Friday from 15:00 DST: from 14:00 | EOW instead of trading | No new positions; weekly audit using fresh data + next week’s plan |
An honest count of the hours: pre-market 45 min + London 3 h + re-briefing 30 min + overlap 3 h + EOD 20 min = 7 h 35 min of work in blocks, spread across 08:00–17:20 (9 h 20 min), with the 12:00–13:30 break and 15 minutes between pre-market and London (1 h 45 min in total); exposure to trading decisions is two session blocks, 6 h. This is the sum of the chosen blocks, not a proven limit for maintaining quality. During DST divergence, working time stays the same, but the day ends at 16:20 and includes 45 min of breaks; Friday has a separate, shorter trading block replaced by EOW. “DST” in the table means only the divergence between US and European clock-change dates, not the entire summer. Adding the Asian session increases working time and may increase fatigue; assess availability, sleep and execution quality using your own data rather than treating the schedule as a standard for everyone.
Rules for using checklists
Five design principles. Match the time and number of questions to the particular stage; the 30 seconds below applies only to pre-trade:
- On this pre-trade card: 10 questions. This is a design choice, not a universal limit for checklists. Match the number of items to critical omissions and test use under pressure; a longer procedure can be split into stages instead of removing necessary safeguards.
- Target: about 30 seconds (pre-trade). The checklist calculates nothing — it verifies values calculated earlier, during pre-market or order preparation (calculators — toolkit C). If a required calculation takes longer than a working allowance of 5 seconds, return to order preparation; do not remove a check merely to meet the time target.
- Binary. YES or NO; “almost”, “probably”, “usually” = NO. A question you cannot answer in binary terms is poorly written — clarify the criterion and the data needed; do not remove a safeguard without assessing the consequences.
- One NO = no entry (pre-trade). No answer also means no entry. A checklist with negotiable exceptions does not fulfil its purpose. Exceptions are designed in the playbook, calmly and in writing — not beside a chart with a setup that is “getting away”.
- Review once a quarter, as part of an audit — not after a losing streak (emotion) or a winning one (pride). Routinely consider 1–2 questions per quarter and record the reason and version. Correct a critical error immediately; a quarterly review date does not justify leaving an unsafe procedure in place.
FAQ
How many checklists do I really need at the start?
At the start, you can focus on learning two cards: pre-trade and EOD. Pre-trade blocks the most expensive errors (an entry outside the playbook, no prepared SL protection, a release in 10 minutes), while EOD builds the data without which you cannot diagnose anything later. Preparing the calendar, limits and plan is nevertheless required from day one — without it, you cannot answer pre-trade reliably. You can introduce the full pre-market and EOW card formats gradually, e.g. in weeks 3–4; this is a suggested way to organise learning, not a finding from habit research. From the beginning, keep at least a record of violations and check limits every week.
Paper or an app?
Start with paper: a printed card beside the monitor, ticked with a pen — no extra windows, phone out of reach. A digital version is better only when it records answers without lengthening the procedure: the cards on this page do exactly that — checkboxes save their state locally in the browser, and the check log counts which pre-trade question most often receives a NO (the module sends nothing to the server). There is one deciding criterion: if operating the tool makes a brief pre-trade confirmation harder, compare it with paper; do not skip questions or data to achieve 30 seconds. EOD and EOW have longer time allowances.
What should I do if I broke the checklist and the trade made a profit?
Book the profit and mark the trade as a violation. Of the four possible outcomes (plan/violation × profit/loss), this one can be particularly misleading: a reward for breaking the procedure encourages repetition, although subsequent losses and their size are not predetermined. That is why the journal tracks two independent outcomes: financial and compliance with the plan — the complete logic of this classification is in article 15.7. A series of profitable violations is a signal to reduce position sizes, not to “update” the playbook to fit impulses.
How long does it take to establish a checklist habit?
Think in weeks rather than days of daily use before pre-trade no longer needs a reminder — no precise number can honestly be given because it depends on trading frequency. One difficult moment may be the first profitable trade “without it” — the intermittent reinforcement mechanism in the section “Why a checklist beats memory and intuition” may then weaken motivation to use the card; this is not a prediction of how quickly a habit will fade. There are two safeguards: a violation status in the journal regardless of outcome, and a checklist physically in view (a printout beside the monitor, not a file in a folder). If you still skip it after several weeks, check the reason: length, unclear criteria, missing data or an inconvenient point at which to check. The pre-trade target is a brief verification, about 30 seconds with data ready; do not shorten it by removing critical items.
Related course articles
- 15.5 Trader workflow — regime identification, pre-market and EOD — the full form templates whose shorter versions appear in this toolkit article
- 15.6 Market screening and trade checklist — a 15-item pre-trade checklist with screening filters and A+/B/C classification
- 15.7 Anatomy of a trade — two independent outcomes for every trade: financial and compliance with the plan, underpinning the matrix in the EOD section
- 15.9 Trading journal — R-multiple, expectancy, SQN and MAE/MFE — the column structure into which EOD records data, and the procedure for calculating MAE/MFE
- 15.10 Strategy audit — the decision procedure for when to improve the system and when to improve the process; expands on EOW item 6
- Tools section — risk calculators — position size, pip value and expectancy: numbers that pre-trade only confirms
- 10.7 Procedures as a substitute for self-control — why procedure beats willpower, and the evidence behind it
- 9.3 Risk per trade, total risk and loss limits — principles for setting limits; −3R and −6R in this card’s example are illustrative, not mandatory course thresholds
Sources
- Atul Gawande, The Checklist Manifesto, Metropolitan Books, 2009 — checklist effectiveness under pressure (medicine, aviation) and the “killer items” principle.
- Alex B. Haynes et al., A Surgical Safety Checklist to Reduce Morbidity and Mortality in a Global Population, New England Journal of Medicine 360, 2009 — the WHO’s 19-item checklist in eight hospitals: complications fell from 11.0% to 7.0%, mortality from 1.5% to 0.8%.
- Brett N. Steenbarger, The Daily Trading Coach, Wiley, 2009 — routines and procedures as external support for a trader’s self-control; checklists and journalling to improve execution quality.
- Mark Douglas, Trading in the Zone, Prentice Hall, 2000 — the mechanical phase of trader development: procedures as a prerequisite for consistent execution of a system before discretion is introduced.
- Internal: course articles 15.5 and 15.6 — full versions of the pre-market, EOD and weekly retrospective templates whose shortened versions are collected in this toolkit article.
- National Museum of the USAF — Model 299 Crash: the board’s statement of 15 November 1935 on locked controls.
- Kahneman and Klein (2009), Conditions for intuitive expertise: conditions for developing accurate intuition, not evidence that a particular forex setup works.
- BLS — 2026 release calendar (Eastern Time); NIST — US DST rules; GUM (Polish Central Office of Measures) — clock changes; NYSE — regular session hours. Dates and times verified on 20 September 2026; check the calendar before the session.
- MetaQuotes — MT5: SL/TP and trailing stop and order acceptance and execution. Documentation for a specific platform, not a guarantee of identical conditions at every broker; checked on 20 September 2026.
Seven candidates, nine checks: read the block log correctly
A repeated check is a new observation of the same candidate, not automatically another trading opportunity. This fictional desk exercise keeps both counts visible.
Give the candidate an identity before counting
Imagine seven candidates labelled C01 through C07. The first pre-trade pass approves four and blocks three: C02 has an excessive spread, C04 is inside the plan’s release window, and C07 lacks a confirmed risk calculation. These are invented records for practising the log, not results from a trading account.
Keep a small companion note linking the checklist’s check time and control_id to the candidate identifier. The existing module does not store your instrument or setup. A local export alone therefore cannot reconstruct that link afterwards. Do not put account credentials into the note.
Keep the first failure when conditions change
The plan’s assumed spread ceiling is 1.5 pips. C02 first shows 2.0 pips and later 1.4 pips; a fresh check can now pass if every other answer also remains valid. C04 is checked again while still inside the exclusion window and stays blocked. C07 has no second check.
| Candidate | First check | Later check |
|---|---|---|
| C02 | Blocked: 2.0 pips | Pass: 1.4 pips |
| C04 | Blocked: release window | Still blocked |
| C07 | Risk unconfirmed | No recheck |
Do not edit the earlier failure into a pass. Its timestamp explains why entry was unavailable then. Passing later does not retrospectively authorise an earlier order.
Choose the denominator that answers your question
The file contains nine checks: seven initial observations and two rechecks. Five checks pass and four block entry. The blocked-check share is 4 / 9 ≈ 44.4%. At candidate level, five eventually pass and two remain blocked: 2 / 7 ≈ 28.6% unresolved. Both calculations are valid, but they describe different things.
Neither percentage measures the profitability of blocked trades. You have recorded eligibility under a plan, not a comparable counterfactual fill, complete exit path and costs. Rechecking more often can change the check-level percentage without creating or removing a candidate.
Use the weekly review to ask a concrete question
First reconcile the export: retain the original file, identify exact duplicate control_id records across successive exports, and preserve genuinely distinct checks. Then ask whether a particular reason repeatedly blocks candidates at your available trading hours. Keep unresolved data separate from a confirmed failed condition.
For this exercise, the useful outcome is a traceable chain from candidate to check to decision. It does not demonstrate that more approvals would be desirable. Before resetting the browser log, download its backup and open the exported file to confirm it contains the expected records.
Three exercises with explanations
1. How many check records belong in this exercise?
Seven first checks are followed by one recheck for C02 and one for C04.
Show the answer and explanation
C. 7 + 2 = 9. Keep the candidate count alongside it rather than replacing one count with the other.
- A. Seven counts candidates but leaves out both later observations.
- B. Eight includes only one of the two documented rechecks.
- C. Nine retains seven initial checks and both later observations.
- D. Eleven invents two checks that the scenario does not contain.
3. What does C02’s later pass establish?
Its spread falls from 2.0 to 1.4 pips under the assumed 1.5-pip ceiling.
Show the answer and explanation
D. Preserve both observations. A new passing check is time-specific evidence, not permission to rewrite the past.
- A. A later quote does not alter the conditions at the earlier decision.
- B. No trading outcomes or expectancy estimate were supplied.
- C. Deleting the earlier observation removes evidence of the original block.
- D. The later measurement supports a new check, provided the remaining conditions are verified again.