Market screening and the trade checklist — from pair selection to clicking Buy
Screening is the initial market review that identifies instruments and situations worth examining. The trade checklist then tests whether a specific entry meets the rules already written in the plan. Together they connect observation with a decision to trade or reject an opportunity. This lesson shows how to narrow the watch universe, account for volatility, releases and relationships between positions, and evaluate a particular setup. Its 15-point checklist records evidence for each condition and permits “unknown” when information is missing. That creates a decision record you can later audit for consistent application of the plan.

Ask which instruments failed, not just how many
A screening report says four instruments fail one filter and five fail another. It is tempting to subtract both counts from the starting universe. That works only if the rejected groups do not overlap. Otherwise the same instrument disappears from the arithmetic more than once.
Consider a hypothetical universe of twelve instruments labelled A through L. These letters are worksheet identifiers, not recommendations or actual symbols. Two predeclared eligibility filters are applied to every instrument using one consistent snapshot and rule version. There are no unknown results in this small exercise. Both filters must pass to reach the shortlist.
Filter X rejects A, B, C and D. Filter Y rejects C, D, E, F and G. The filter definitions and these results are supplied inputs, not empirically validated trading rules. We are checking the construction of the shortlist, rather than claiming that either filter predicts a profitable trade.
Keep instrument identities in the filter record
| Group | Instrument identifiers | Count |
|---|---|---|
| Fails X only | A, B | 2 |
| Fails both X and Y | C, D | 2 |
| Fails Y only | E, F, G | 3 |
| Passes both | H, I, J, K, L | 5 |
The distinct rejected instruments are A, B, C, D, E, F and G: 7 in total. The two overlapping instruments, C and D, belong to both rejection lists but each occupies only one place in the universe. Counting them twice would overstate the number removed.
Write the reconciliation as 4 + 5 − 2 = 7 distinct rejections. The shortlist is 12 − 7 = 5 instruments. The shortcut 12 − 4 − 5 = 3 is wrong here because it subtracts the overlap twice. Keep the identifiers alongside the counts so a reviewer can reproduce the result instead of trusting a dashboard total.
Do not mix full-universe counts with sequential counts
Our two reported failure counts each refer to the entire starting universe. A sequential implementation would report something different at its second stage. If X first removes A, B, C and D, only E through L remain. Y then removes E, F and G from those survivors: three additional instruments, not five.
The sequential calculation is therefore 12 − 4 − 3 = 5, consistent with the full-universe method. Neither method is inherently better; their denominators and coverage must be stated. A report that labels a full-universe failure count as an additional removal produces an error even when every individual test result is correct.
If a real input is missing, retain an unknown state rather than silently treating it as a pass. If the rule version or snapshot changes, record that change and re-evaluate the relevant instruments. Our complete, simultaneous snapshot avoids those complications so that the overlap is visible on its own.
A shortlist hands work to the entry checklist
H, I, J, K and L have passed only the two supplied screening filters. We have not supplied a valid entry trigger, executable prices, current portfolio checks, a complete event check or a correctly sized order. The five-instrument shortlist is therefore an output for further examination, not five approved trades.
Preserve the starting universe, rule version, observation time, results by instrument and rejection reason. Record subsequent setup and admission decisions separately. An instrument can be eligible for observation yet fail a later hard condition; that does not mean the earlier screen was arithmetically wrong. Conversely, a profitable later price move does not retroactively change a recorded rejection.
The full lesson below provides the market context, indicator definitions, calendar exclusions and complete pre-trade card. Use its governing conditions when deciding whether an entry is permitted. This smaller example adds an audit question for any scanner: do the reported stage counts describe the full universe, the survivors, or distinct rejected instruments? A shortlist is easier to trust when those quantities reconcile.
Three exercises with worked answers
The exercise data are hypothetical. Choose an answer, then check the calculation.
From a reconciled shortlist to the full entry checklist
Carry the exact instrument-level screen forward to the market, calendar, portfolio and execution checks in the detailed lesson.
1. Screening versus unstructured watchlist browsing
A watchlist without a selection process might contain 18 currency pairs plus gold, oil, the S&P 500, Bitcoin, several shares and DAX. The trader clicks through charts for 15–40 seconds apiece and repeats the tour. After an hour, the market review is a collection of impressions without a measurable output. Entries follow whichever dramatic candle suggests that something is happening, producing the scenario's four to eight daily trades across unrelated setups. These are illustrative habits, not a measured description of every watchlist user.
Screening is a systematic filter. Start with a defined universe, illustrated as 28 major and cross currency pairs combined, plus five to ten additional instruments, for 33–38 in total. Reject instruments that fail the specified conditions, applying appropriately calibrated second-layer filters to the extras as well as FX pairs. The output is a shortlist of two to five instruments on which to look for valid setups. Depending on starting and ending counts, 28–36 are excluded before detailed candle analysis.
Watchlist and screening mechanics
| Dimension | Unstructured watchlist scenario | Systematic screening scenario |
|---|---|---|
| Starting point | 18–25 favorite pairs. | A defined universe of 28 or more instruments. |
| Filter | None; inspect everything. | 3–5 filtering layers covering macro context, ATR, ADX, calendar and correlations |
| Output | “Something is moving in GBP/JPY.” | 2–5 instruments eligible for specific setup checks, not automatic entries |
| Decision/review time | Variable, illustrated from 15 seconds to 40 minutes per idea. | A budget of 10–28 minutes for the complete scan. |
| Daily trades | 4–8 scattered entries | 0–3 concentrated candidates that may qualify |
| Logical consistency | Ad hoc setups. | A defined playbook applied to selected pairs. |
| Evaluating an edge | Difficult when many unrecorded variables change together. | More interpretable setup, pair and journal records, without guaranteeing an edge or adequate precision. |
How an unfiltered watchlist can contribute to losses
Three behavioral mechanisms can appear across 18 unfiltered charts:
- Availability bias: recently dramatic pairs look like opportunities even after the move, encouraging late entry near an extreme. Tversky and Kahneman's 1973 work provides general background on availability[4], not a measured FX-trader result.
- Portfolio-level FOMO: 18 charts provide many chances for one to look exciting. Entering four unrelated ideas can follow emotional salience rather than one coherent plan.
- Ad hoc confirmation: searching long enough can uncover an apparent justification on almost any chart. Without fixed criteria, the trader both advocates for and grades the idea.
Screening addresses those mechanisms by eliminating many instruments before attachment to a pattern develops, requiring explicit contextual evidence and focusing attention on two to five candidates. Your journal must establish how effective that process is for you; a small shortlist is not proof that its opportunities are profitable.
2. Top-down screening: macro → pair → setup
Top-down specifies the order of review. Starting with an attractive pattern can leave the trader searching afterward for a macro justification. The three layers below first establish permitted context, then instrument eligibility, then the actual setup. Context is not a deterministic price forecast, and its role as a hard condition or auxiliary ranking criterion must match the written checklist.
Layer 1: macro regime — illustrative five to eight minutes for the market
Before focusing on one pair, review the broader environment through six to eight indicators:
- DXY, the Dollar Index: USD against its six-currency basket. This example's illustrative intraday change above +0.3% flags stronger USD and less favorable context for EUR/USD or GBP/USD longs; below −0.3% flags weaker USD and less favorable context for shorts. Specify the session reference for the change; this is not an automatic trading signal.
- VIX, S&P 500 implied volatility: a risk-on/risk-off proxy. This working classification uses below 18 for risk-on, 18–25 for neutral/cautious and above 25 for risk-off. AUD, NZD and emerging-market currencies may respond differently from safe-haven JPY, CHF and USD, but relationships are conditional, not guaranteed.
- US, German and Japanese ten-year yields: relative yield changes can influence currency pairs. Rising US yields with stable German yields may support USD versus EUR; inspect the reason for the move rather than assuming one fixed response.
- S&P 500 futures before the cash open: an indication of equity sentiment and anticipated opening conditions.
- Gold, XAU/USD: a rise can accompany USD weakness or risk aversion; distinguish those possible explanations using the other evidence.
- WTI/Brent oil: relevant context for CAD, NOK and MXN. A strong rise can support a CAD-long thesis in some regimes, not an unconditional rule.
- Bitcoin/crypto, optional: an additional sentiment proxy outside cash-equity hours, with its own market-specific drivers.
- News services: this example lists Reuters, Bloomberg and Forexlive as examples. Check for current events capable of disrupting ordinary relationships; names are retained as examples, not verified service recommendations.
Produce one brief statement, for example “risk-on, weak USD, positive equities”, “risk-off, strong USD and JPY”, or “mixed/neutral: selective candidates or no exposure”. Record contradictory or unavailable evidence rather than forcing agreement. Complete this context record before moving to pair selection.
Layer 2: instrument selection — illustrative three to five minutes
Apply the next checks to the defined universe of 28 FX pairs and additional instruments. The numbers are illustrative thresholds, not market standards. Section 3 explains calibration; retain the hierarchy of hard and auxiliary criteria rather than turning every macro observation into a veto.
- Completed-day ATR(14) at least 0.9 times its 90-observation average: a minimum-volatility eligibility hypothesis. Passing does not itself prove that the setup's move will exceed costs.
- Completed-day ADX(14) at least 25 for trend or below 20 for range: match the instrument's measured regime to the strategy card.
- Calendar review over ±2 hours on both currencies: the mandatory exclusion in hard checklist item 11. No high-impact event may fall within two hours before or after the decision time for either currency. Shorter subwindows in section 4 do not override it.
- Absolute correlation below 0.7 with open positions: apply the declared return-series timeframe, lookback and account-exposure review. Position direction and shared events remain relevant.
This example's illustrative funnel reduces 33–38 instruments to three to eight technically eligible candidates and then two to five contextually preferred ones. Strong USD can deprioritize EUR/USD and GBP/USD longs because their quote direction opposes that context. Under the final checklist, however, a macro-regime conflict is an auxiliary downgrade, not a hard veto by itself; remove the idea only under the applicable full class rule or an explicitly stricter playbook. The resulting shortlist goes to Layer 3.
Layer 3: setup — one to three minutes per shortlisted pair
Now inspect the two to five shortlisted charts on D1/H4/H1 for an existing playbook setup. If one is present, proceed to Section 6's pre-trade checklist. Otherwise set the appropriate price alerts and keep the instrument under passive observation rather than manufacturing an entry.
The illustrative final output is zero to three potentially executable setups. Total scan time is 10–28 minutes: five to eight for macro, three to five for selection and one to three per shortlisted pair. Minimum 5 + 3 + 2 × 1 = 10; maximum 8 + 5 + 5 × 3 = 28. This example schedules this before London trading, with an optional second review before New York; convert those activity windows to your own available hours.
Why not start from the pattern?
Bottom-up review starts with an attractive formation and checks macro context afterward. It can encourage retrospective rationalization: once attached to the setup, the trader explains away opposing evidence as a special case or already priced in. The problem is that reasoning order, not a claim that every bottom-up method must lose.
Top-down first defines which setup contexts fit today's plan, then looks for those setups. Apply the recorded criteria consistently: a mandatory conflict rejects the trade; an auxiliary macro conflict affects its class as Section 6 specifies. Do not change that distinction to justify a preferred chart.
3. Mechanical filters: ATR, ADX, VIX, correlations and time of day
A mechanical filter is a condition that can be coded and checked consistently, rather than “looks good” or “interesting market”. Specify the value, threshold, data source and YES/NO decision, with unknown recorded when evidence is missing. The five categories below cover common screening needs; their numeric settings remain hypotheses to validate.
ATR: is the available movement sufficient for the setup?
Average True Range, ATR measures average true range in price units, converted to pips for these FX examples. Low volatility, illustrated by quiet EUR/CHF periods, can leave limited movement relative to costs. The working thresholds are illustrative, not market standards:
- Completed-day ATR(14) ≥0.9 times the mean of the 90 earlier completed-day ATR(14) observations, excluding the observation being compared: the example's minimum activity filter.
- ATR ratio above 1.5: elevated volatility; consider only the plan's calibrated stop-distance and reduced-volume variant within the risk budget. Do not widen a live stop ad hoc.
- ATR ratio above 2.0: the example excludes standard setups because conditions may be outside their model. The ratio is a stress signal, not proof of a particular shock.
In TradingView or your analysis tool, calculate ATR(14) on D1 and then the simple average of the 90 earlier completed values in that ATR(14) series, excluding the comparison value, or export the values to a spreadsheet. ATR with its own parameter set to 90 is a different quantity: a longer-smoothed true-range calculation, not the average of 90 ATR(14) observations. Substituting it silently changes the filter. Use completed-bar values consistently as described below.
ADX: trend strength versus a ranging regime
Average Directional Index, ADX measures trend strength rather than direction. This article's working bands are:
- Below 20: a consolidation candidate; the example's trend strategy is excluded and its range strategy may qualify. This does not prove mean reversion will be profitable.
- At least 20 but below 25: ambiguous; skip under this filter. Exact 25 belongs to the trend-eligible band.
- 25–40: stronger measured trend; eligible for the tested trend strategy if its other conditions pass.
- Above 40: strong measured trend. Review extension and reversal risk; ADX alone does not identify a late phase or predict a correction.
Use D1 ADX to classify daily trend strength and H1 for the intraday condition; direction comes from the defined price/structure or directional-indicator rule, not ADX itself. D1 ADX 28 with H1 ADX 12 describes a stronger daily regime alongside intraday consolidation. The example waits for the appropriate breakout in the separately established daily direction.
VIX: a broad risk-context indicator
VIX reflects the S&P 500's option-implied volatility over a 30-day horizon; Cboe publishes its methodology[5]. It is an equity-based proxy that can inform FX sentiment, not a direct FX-volatility or entry measure. Combine it with DXY, equity futures, yields and JPY/CHF behavior:
| VIX working band | Illustrative context | FX considerations, not automatic trades |
|---|---|---|
| Below 14 | Compressed volatility / strong risk-on interpretation | Carry and AUD/JPY or NZD/JPY long hypotheses may be considered; sudden reversal risk remains. |
| 14 to below 18 | Ordinary risk-on interpretation | No class is excluded by this observation alone. The journal establishes whether the particular setup performs in the regime. |
| 18–25 | Neutral or increased caution | Review carry exposure and JPY-cross execution conditions. |
| Above 25 through 35 | Risk-off interpretation | Possible strength in JPY/CHF/USD and weakness in AUD/NZD/ZAR/MXN; investigate widening spreads and exceptions to those relationships. |
| Above 35 | Severe stress | The example proposes only the strongest candidates, substantial size reduction and no new overnight positions. Any stricter no-entry rule must be explicit in the plan. |
This example's review trigger is a VIX increase above 30% in one session, for example 14 to 19, a rise of about 35.7%. Reassess existing candidate context. Under the 15-point checklist, VIX affects the auxiliary macro-regime item; it is not silently promoted into a mandatory veto.
Portfolio-correlation filter
Long EUR/USD and long GBP/USD can concentrate a common short-USD exposure. Correlation does not reduce the sum of stop-loss budgets. Two positions each risking one percent can both lose two percent in total before gaps/slippage, even if a volatility formula gives a smaller number. Positive loss dependence can increase the chance of simultaneous losses. For two components with equal standard deviation, √(2 + 2ρ) describes the standard deviation of their sum in units of one component's standard deviation: 1.84 at ρ = 0.7 and 1.87 at 0.75. It is not a stop-loss cash amount. The following second-position rules are illustrative:
- |ρ| below 0.4: weak linear association in the declared historical window. That does not establish independence, capture nonlinear/tail dependence or account for the directions and shared-event exposure of your positions.
- 0.4 ≤ |ρ| < 0.7: the example reduces second-position size by 25–40%. This is the only stated band where a size reduction is the admission rule; it does not bypass the next hard threshold.
- |ρ| ≥0.7: mandatory checklist item 10 fails: NO → SKIP. Half-size is not an exception. A smaller order does not make the required correlation condition true.
Use a provider's documented matrix or calculate correlations from aligned return series, for example with spreadsheet CORREL. Record return frequency, lookback, timestamps and data source together with the coefficient. “Correlation 0.73” without those definitions is not reproducible. The absolute-correlation screen is deliberately conservative; separately inspect position direction and common currency exposure.
Time-of-day filter: active trading windows
Liquidity and execution vary by instrument and session. The example proposes the following Polish-local-time strategy windows; they are not proof of universally best returns or exact exchange-session hours:
| Pair | Illustrative active window, Poland | Window to avoid under this plan |
|---|---|---|
| EUR/USD, GBP/USD | 09:00–17:00, covering London activity; New York overlap begins around 14:00 under the usual offset. | 22:00–08:00, the example's quieter overnight window. |
| USD/JPY, EUR/JPY | Tokyo 01:00–10:00 Polish winter time or 02:00–11:00 summer time; also 09:00–17:00 European/overlap activity. | 17:30–22:00 under the example's strategy restriction, rather than a claim that all European trading has ended |
| AUD/USD, NZD/USD | 00:00–09:00 as a simplified Sydney/Tokyo-oriented review window; check seasonal offsets. | 20:00–24:00 under this example. |
| USD/CAD | 14:30–21:00, focused on North American activity and US/Canadian releases. | 00:00–09:00. |
| All | Apply the instrument's verified schedule. | 23:00–00:30 around the assumed rollover, and Friday after 20:00 Polish time in this plan. |
This example's time note is dated 6 September 2026. Europe/Warsaw changes between CET and CEST; Japan does not change clocks, and US–EU transition dates differ for several spring weeks and roughly one autumn week. Australian/New Zealand transitions introduce their own offsets. Convert actual dated sessions/releases rather than treating PL times as fixed UTC values. 15.5 provides the full session/fixing context; here the table serves as a strategy time filter.
If a setup appears outside its permitted window, skip or wait for a valid new trigger inside it. Quiet periods can carry wider spreads and worse slippage, but measure the magnitude from your broker's tick/execution data. No public retail-account sample that establishes a universal difference.
Validating the ATR threshold instead of copying it
The 0.9 ratio is a starting hypothesis, not a market law. Evaluate it in your own records:
- Export closed trades of the same setup/version. More relevant observations can improve precision, but count alone establishes nothing and dependence reduces effective information.
- Attach the completed-D1 ATR(14) value actually available at entry and its ratio to the matching 90-observation mean, not the later completed value of the entry day.
- Calculate expectancy in R for non-overlapping bands: below 0.8; 0.8 to below 0.9; 0.9 through 1.5; above 1.5.
- State n and an appropriate interval for each mean. E ±1.96×std(R)/√n is an approximation for suitable independent observations; sparse or dependent groups need a suitable alternative. Four bins create smaller samples. Overlap between separate intervals is neither a test of their difference nor evidence of equivalence.
- Consider adopting0.9 only after a predeclared comparison estimates the net-result difference between below-0.9 and0.9–1.5 conditions with appropriate uncertainty, and genuinely held-out data confirms the proposed filter. Separate intervals need not be non-overlapping for a valid difference analysis. Account for the number of variants tried. Selecting and confirming on the same data fits noise; see15.4.
Without that work, the 0.9 rule remains someone else's hypothesis in your process. It may or may not help your setup.
Filter audit: one row before a rule enters the checklist
A checklist rule needs a concise operational definition. The last column records what a discretionary exception can expose the account to, rather than assuming a favorable outcome will justify it.
| Filter | Purpose | Condition | Evidence source | Decision | Risk of an ad hoc exception |
|---|---|---|---|---|---|
| Daily ATR(14) | Check movement relative to costs. | At least 0.9× the mean of the 90 earlier completed ATR(14) observations, excluding the comparison value; validate the threshold | Completed D1 values from the platform. | Below the mandatory threshold: exclude. | A target large relative to available movement and costs consuming much of it. |
| Daily ADX(14) | Match strategy to regime. | At least 25 for trend; below 20 for range. | Completed-bar calculation. | 20 to below 25: skip. | Trend entries repeatedly whipsawed in consolidation despite correct sizing. |
| VIX | Risk-context ranking. | Below 25 for the example's ordinary context; stricter exclusions must be defined in the selected card | Cboe methodology/quotes[5] or a documented feed. | Auxiliary macro criterion in this checklist. A separate above-35 no-entry policy must be explicitly adopted, not silently substituted. | Carry/JPY-cross exposure during severe spread and gap stress. |
| Correlation with open positions | Limit concentrated exposure. | |ρ| below 0.7 using a declared return frequency/lookback. | Documented matrix or aligned-return CORREL calculation. | At least 0.7: item 10 NO → SKIP. | Both stops hit in one common-currency move. |
| Calendar | Exclude events outside the model. | No high-impact release within ±2 hours for either currency in the pair | Calendar and, when uncertain, the publisher such as BLS, Fed or ECB. | A release within the defined exclusion window, or an unavailable calendar, means SKIP; the shorter periods discussed below do not waive it | Execution beyond planned 1R as spreads widen or prices gap. |
| Instrument time window | Control entry liquidity/cost. | Setup-card session and acceptable current spread. | Account quotes and own tick records. | Outside the window: alert rather than entry. | Fills and slippage absent from an unrealistic backtest. |
| Data quality | Establish whether a decision is supported. | Live feed, required completed bar and adequate history. | Connection logs and independent comparison feed. | No evidence: unknown → SKIP for a mandatory condition. | Stale or provisional input changes the classification; historical misuse of a final value can create look-ahead. |

4. Calendar filters: NFP, FOMC, ECB, BoE and BoJ — what disqualifies a setup
Alongside an unsuitable market regime, an unchecked economic calendar can invalidate an otherwise well-selected setup. You enter a technically attractive pattern: ATR and ADX pass, correlations are acceptable — then CPI is released at 14:30 Polish time, an event you never checked. The stop is hit within 90 seconds. In this example, the loss arose from an omitted calendar check, not from following the strategy. The ranking of calendar risk as the “second most common” cause is an editorial observation, not a measured retail-trading statistic.
High-impact releases to include in the filter
| Region | Release | Frequency | Potential impact |
|---|---|---|---|
| US | NFP (Non-Farm Payrolls) | Usually the first Friday of the month, normally 14:30 Polish time; check the BLS schedule for the actual year and daylight-saving differences | Extreme — all USD pairs |
| CPI / core CPI | Monthly under the BLS calendar, 08:30 New York time: normally 14:30 in Poland, or 13:30 during US–European daylight-saving mismatch weeks. Use the actual release date | Very high — USD pairs | |
| FOMC decision (projections and the “dot plot” do not accompany every meeting) | 8 scheduled meetings a year, decision normally at 20:00 Polish time (19:00 during US–European daylight-saving mismatch weeks). Economic projections and the dot plot accompany four of those meetings: March, June, September and December in the 2026 schedule | Extreme — global | |
| FOMC press conference (Fed chair) | After the decision, normally 20:30 Polish time (19:30 during the daylight-saving mismatch) | High — the press conference can produce a larger move than the decision itself; this is not a quantified frequency estimate | |
| Core PCE, closely watched by the Fed | Monthly, towards month-end | High — USD pairs | |
| ISM Manufacturing / Services PMI | Monthly, near the start of the month | Medium to high — USD pairs | |
| EU | ECB decision and press conference | 8 scheduled monetary-policy meetings a year; normally 14:15 and 14:45 Polish time | Very high — EUR pairs |
| EU inflation: flash and final releases | Monthly | High — EUR | |
| German ZEW, Ifo and PMI | Monthly | Medium — EUR | |
| UK | BoE decision and minutes | 8 scheduled meetings a year; normally 13:00 Polish time | Very high — GBP pairs |
| UK CPI | Monthly; normally 08:00 Polish time | High — GBP | |
| UK GDP and retail sales | Monthly / quarterly, depending on the release | Medium — GBP | |
| Japan | BoJ decision | 8 scheduled meetings a year; verify the actual release arrangements | High — JPY crosses; sensitivity varies with the prevailing BoJ policy regime |
| Tokyo CPI and BoJ minutes | Tokyo CPI monthly; minutes according to the meeting-publication schedule | Medium — JPY | |
| Australia / New Zealand | RBA / RBNZ decisions, Australian CPI and employment | RBA: 8 meetings a year, approximately every 6–7 weeks. Australian CPI: monthly — the ABS publishes the full index monthly from the October 2025 reference period; previously quarterly. Check the separate RBNZ and employment calendars | High — AUD / NZD pairs |
| Canada | BoC decision, Canadian CPI and employment | 8 scheduled BoC decisions a year; CPI and employment monthly | High — CAD pairs |
Clock times above retain this article's reference zone, Europe/Warsaw (CET/CEST); they are not UTC or your broker's server time. Convert the specific date to your location, including weeks when US and European daylight-saving changes differ. This article records verification of the Fed's projection meetings and Australian CPI frequency with the Federal Reserve and Australian Bureau of Statistics as of 7 September 2026; that is the example's dated verification, not a fresh verification performed for this translation. Check the actual year's BLS, Fed, ECB and other publishers' calendars for weekdays and exact dates. Schedules can change; an old table is not the operational calendar.
The calendar window: when not to enter
One governing rule applies to hard checklist item 11: no high-impact release within two hours before or after the current time, for either currency in the pair. The subwindows below explain what can happen inside that closed window; they are not exceptions to it. These are example policy thresholds, not an industry standard; assess them against your own spread records:
- The 30 minutes before the release: no new positions on directly affected pairs. Spreads may widen and liquidity may decline.
- The release and the first 15 minutes afterwards: a potentially disorderly period, with widened spreads, unusually large slippage and false breakouts. This example provides no public retail-account slippage sample with which to quantify the claimed multiple of normal slippage. Do not enter.
- Between 15 and 60 minutes after the release: direction is still developing, spreads normalize unevenly and early breakouts can reverse. This describes market behavior; it does not permit entry. Item 11's two-hour post-release exclusion remains active even if the spread has stabilized. A new entry is possible only after that window ends and the normal checklist passes.
A dedicated news-trading strategy, such as fading the initial NFP move, belongs to a separate playbook category with its own position-sizing and stop rules. It requires its own admission card; it is not a discretionary override of this checklist's calendar veto.
The currency hierarchy in the calendar
A US CPI release affects all USD pairs — EUR/USD, GBP/USD, USD/JPY, USD/CAD, AUD/USD, NZD/USD and USD/CHF — and can spill over indirectly into crosses such as EUR/JPY and GBP/JPY through broader risk sentiment and related currency moves. Those crosses do not literally contain USD or a DXY component. The operational rule is one release can block many pairs. Check both component currencies, together with any indirect event exposure specified in your playbook; checking only the currency that features in your trade narrative is insufficient.
The weekly rhythm: where the work belongs
Reviewing the whole week's calendar on Sunday and planning work windows belong to the workflow, covered in 15.5, section 2. Screening an individual opportunity uses the output of that review: a list of off-limits times for the coming days, which supplies checklist item 11.
5. Multi-timeframe context: D1 / H4 / H1 / M15
The multi-timeframe (MTF) rule in this playbook is that an M15 setup must align with the H1 bias, H1 structure with H4 structure, and H4 structure with the D1 bias. Setups that oppose a higher timeframe are often described as weaker, but the size of that difference has not been established in a public retail-trading sample. It depends on the strategy, instrument and period. Without out-of-sample validation, an observed anomaly can easily be mistaken for a market law. MTF is useful here as a coherent screening rule connecting directional bias, current structure and entry precision; calling it one of the “strongest” filters does not establish measured superiority.
The timeframe hierarchy: what each level provides
| Timeframe | What it provides | What to look for |
|---|---|---|
| D1 (daily) | Directional bias and longer-term structure | Trend, using SMA-50 versus SMA-200; ADX; key historical support and resistance over the last 60 candles; ATR as a regime proxy |
| H4 | Medium-term structure and market phase | Higher highs / lower lows, channels, range / wedge / triangle patterns, and the most recent extreme over roughly 10–20 candles |
| H1 | The setup and entry context | Pre-breakout consolidation, a level retest, or momentum divergence using RSI or MACD |
| M15 | The entry trigger and a precise stop level | A trigger candle, such as an engulfing pattern, pin bar or breakout candle; tick volume; the exact stop-loss level |
| M5 (optional) | Entry refinement and a micro-trigger | A pullback after the breakout or momentum immediately before entry |
Alignment: when timeframes disagree
Four typical situations:
- Full alignment: D1 ↑, H4 ↑, H1 ↑, M15 ↑ long trigger. An A+ configuration according to the playbook card, provided all other required conditions pass. The claim that it has the highest win rate remains a journal hypothesis to test.
- Minor conflict: D1 ↑, H4 ↑, H1 → consolidation, M15 ↑ long trigger out of consolidation. An A/B candidate according to the card. Entry may become eligible after confirmation from an H1 candle that has closed in agreement with the trigger; pending confirmation is not a completed condition.
- Moderate conflict: D1 ↑, H4 ↓ retest, H1 ↑, M15 ↑ long trigger. A B/C description in the card, with possible false-breakout risk. D1 and H4 context are auxiliary items 4 and 5 below, not standalone hard alignment vetoes. The actual card still determines whether this is an eligible B or an ineligible C, and a countertrend setup needs its own card.
- Major conflict: D1 ↑, H4 ↓, H1 ↓, M15 ↑ long trigger. Skip under this trend-following card. Treat it as a possible countertrend rebound, not an A+ setup.
An MTF workflow in 90 seconds per pair
- D1 — 15 seconds: up, down or neutral bias? SMA-50 above or below SMA-200? ADX above 25? Where is price relative to the latest key levels?
- H4 — 20 seconds: higher highs and higher lows for an uptrend, or lower highs and lower lows for a downtrend? Where is the latest extreme? Is price closer to resistance or support?
- H1 — 25 seconds: is a setup developing? Consolidation before a breakout, a level retest or a divergence?
- M15 — 20 seconds: is a potential trigger candle forming? What exactly is the stop level? What does tick volume show? A forming candle is only a candidate if the card requires a completed candle.
- Decision — 10 seconds: if the required levels align, move to the pre-trade checklist. If they conflict, skip or set an alert at the level that would resolve the conflict.
The “higher timeframe wins” rule
Use a predetermined priority rule when signals conflict: the H4 candle takes precedence over M15, and the D1 trend over H1 consolidation. This is a process rule, not a market law. The explanation that “more capital trades on higher timeframes” is a microstructure hypothesis, not a demonstrated mechanism here. Its operational value is that a rule set before the session removes negotiation with yourself precisely when you most want to enter.
In practice, an M15 long trigger while H4 remains in a clear downtrend is treated as a countertrend rebound, not proof of a trend change. Trading it is allowed only if countertrend trading is a separate setup with its own playbook card, required conditions, invalidation and position sizing. Without that card, the answer is NO; halving the volume does not make the original setup valid. Class definitions and sizing by class are covered in 15.2, section 2.
6. The 15-point pre-trade checklist: from screening to clicking Buy
After top-down screening and identification of an MTF candidate, run the pre-trade checklist. It contains fifteen criteria in five blocks and takes approximately 60–90 seconds to complete. Every criterion has three possible results — YES, NO and unknown — each with a consequence written down in advance.
How to read the columns
- Evidence available now: something concrete you can inspect at the decision time, such as a displayed number, a setup-card entry, a calendar event or the order ticket. Without that evidence, the criterion has not passed; it is unknown.
- Hard / auxiliary: a hard criterion is necessary for entry, regardless of the other answers. An auxiliary criterion ranks candidates and determines the setup class. See 15.2, section 2 for class definitions and sizing.
- Result: YES / NO / unknown. Unknown honestly means “I do not have the data”: the calendar is unavailable, the spread is invisible or the setup-card version is missing. For a hard criterion, unknown has the same blocking effect as NO.
- Consequence: what you do with that result. Write it before the session so it is not open to negotiation during the trade decision.
Governing rule: auxiliary criteria cannot compensate for a failed hard criterion. All three auxiliary answers being YES cannot turn one hard NO into an admissible entry. A smaller position does not make an unmet necessary condition true. That is the difference between this checklist and an additive score.
| No. | Criterion | Evidence available now | Type | Result | Consequence |
|---|---|---|---|---|---|
| A · SETUP | |||||
| 1 | The setup is in the playbook and I know the card version under which I am trading it | A setup card with an identifier and version, for example LON_short_EURUSD v3 | Hard | YES / NO / unknown | NO or unknown → SKIP. A setup invented during a price move has no version because it has no card |
| 2 | The trigger occurred on a closed candle | The platform's trigger candle: body, direction and tick volume | Hard | YES / NO / unknown | NO → wait for the candle to close or set an alert. “Almost closed” means NO. Unknown also blocks entry |
| 3 | Data quality: live feed, no gap in the required history, indicator inputs from completed candles | The terminal connection log and a quote comparison with a second source | Hard | YES / NO / unknown | NO or unknown → SKIP. A filter based on a forming candle can change before the close. That violates this card's completed-candle rule; see section 3 |
| B · CONTEXT | |||||
| 4 | D1 bias aligns with the entry direction | D1 moving-average arrangement, ADX and position relative to the latest extreme | Auxiliary | YES / NO / unknown | NO → downgrade the class. Countertrend trading requires a separate setup and its own card, evaluated from item 1; without that card, hard item 1 already blocks entry. Unknown does not earn a YES |
| 5 | H4 structure aligns: the setup is not in the middle of an opposing wave | H4 higher highs / higher lows or lower highs / lower lows, and position relative to the latest extreme | Auxiliary | YES / NO / unknown | NO → downgrade the class. Unknown supplies no positive confirmation; use the card's predetermined classification rule |
| 6 | The morning briefing's macro regime supports the direction | The one-sentence daily context from layer 1: DXY, VIX and yields | Auxiliary | YES / NO / unknown | NO → downgrade the class. An opposing macro regime plus a second conflict → SKIP. Unknown is not a supporting signal |
| C · SIZING AND EXIT | |||||
| 7 | Volume has been calculated from the stop distance and the plan's risk budget | The calculator output: lots rounded to the permitted volume step, and the cash amount of 1R in account currency | Hard | YES / NO / unknown | NO or unknown → SKIP. “I will use my usual size” is not a calculation |
| 8 | The invalidation level and exit target are recorded, with risk:reward of at least 1:1.5 | Specific SL and TP prices, plus any condition that invalidates the setup before the price stop is reached | Hard | YES / NO / unknown | No recorded invalidation, risk:reward below 1:1.5 or unknown → SKIP. The 1:1.5 threshold is an example from this setup card, not a market standard. The card determines the class — 15.2, section 2 — rather than this row alone |
| 9 | Total portfolio risk after the new entry remains within the plan's limits | Initial cash risk R0 for open positions plus this candidate, checked against portfolio headroom and the daily and weekly limits | Hard | YES / NO / unknown | An exceeded limit or unknown → SKIP. Count losses already incurred when calculating remaining loss-budget headroom. The limits belong to the plan: 15.2, section 3 |
| D · CORRELATION, CALENDAR AND TRADING WINDOW | |||||
| 10 | |ρ| with open positions is below 0.7 over the declared measurement window | A correlation matrix or your worksheet; record the window alongside the value in the journal | Hard | YES / NO / unknown | |ρ| ≥ 0.7, or unknown when there is relevant open exposure → SKIP. Size reduction belongs to the band 0.4 ≤ |ρ| < 0.7; it does not bypass the upper threshold |
| 11 | No high-impact event within ±2 hours for either currency in the pair | An economic calendar filtered by impact; consult the original publisher's schedule if uncertain | Hard | YES / NO / unknown | An event in the window or no calendar access → SKIP |
| 12 | The pair is in its active trading window and the spread is normal for that time | The live account spread and clock time checked against the setup card | Hard | YES / NO / unknown | Outside the window → a price alert instead of entry. An excessive or unknown spread also blocks entry |
| E · OPERATOR STATE AND ORDER TICKET | |||||
| 13 | Hard behavioral filters: sleep ≥6 hours; no alcohol in the previous 12 hours; drawdown over 48 hours shallower than 2 R (DD over 48 hours >−2 R); the daily loss limit not reached; no sequence of 3 consecutive losses | Five YES/NO answers under the selected operating policy; these are not medical fitness criteria or a guarantee of fitness above the thresholds | Hard | YES / NO / unknown | Any NO or unknown → SKIP. Operator-state rules: 15.5, section 7; loss limits: 15.2, section 3. These example thresholds do not establish medical fitness or recovery after drinking |
| 14 | SL and TP are entered in the ticket and submitted with the order, not “added in a moment” | Completed SL and TP fields before clicking Send, plus the card's prior verification that the execution provider maintains the stop server-side, tested on demo or minimum volume | Hard | YES / NO / unknown | An empty field or unknown → SKIP. Server acknowledgement is a separate post-submission step: only then can you inspect the accepted SL and TP attached to the position. The pre-trade checklist ends before the click, so do not mark future acknowledgement as already received. Verify the actual platform → state → action procedure |
| 15 | The order ticket matches the plan: symbol, live/demo account, Buy/Sell direction, volume in the platform's units, market/limit/stop order type, time in force (GTC/day/date), and SL/TP on the correct side of price | The order window before Send, read field by field rather than glanced at | Hard | YES / NO / unknown | Correct any mismatch and read the ticket again; an unresolved mismatch or unknown → SKIP. Wrong volume, direction, account and duplicate orders are operational errors: 15.8, section 4 |
Four decisions, not two
The checklist produces one of four decisions, each with its own journal entry:
- Qualify: every hard criterion is YES, and auxiliary criteria determine an eligible class. Enter according to that card.
- Reject: a hard criterion is NO. Record the item number and the specific value that determined the rejection.
- Wait: the condition may become satisfied at a predictable time: the candle has not closed, or the release exclusion expires in 40 minutes. Set an alert and restart the checklist at item 1 when it fires, rather than resuming at the interrupted item.
- No data: a hard criterion is unknown because the calendar, spread or card version is unavailable. Entry remains blocked, but record the different cause. Repeated “no data” decisions reveal a workstation or process fault rather than a market condition.
Do not rewrite the reason after seeing the outcome. Record the skip reason at the decision time, including the decisive value: for example, “item 10 = NO; |ρ| 0.73 with the open EUR/USD short; 30 daily-session window.” What price subsequently does cannot justify changing that entry, even if the skipped setup would have won.
The hard-veto rule
A hard NO or unknown means no entry: no discretionary exception, no argument that one item matters less, and no promise to obey it next time. Otherwise the checklist becomes a ritual of ticking fourteen boxes and entering because the setup looks good. Assess its actual effect in the journal: distinguish trades with complete checklist records, trades entered with a NO, and skipped setups with a consistently calculated hypothetical outcome. Estimate expectancy for each group with an uncertainty interval. Sample count alone does not settle the question; the interval's width relative to the decision threshold matters. See 15.9, section 4. The journal marker “15/15” denotes completion of all fifteen answers, not an additive admission score. Keep hard/auxiliary results and the class separately, so a completed record with an auxiliary NO is not mistaken for fifteen YES answers.
Two similar setups: one passes, the other fails a single item
The instrument, chart pattern and provisional class are the same. One hard criterion changes the decision. Illustrative example, not historical performance: prices and indicator values are synthetic, and each reason is recorded at the decision time.
| Element | Setup 1 — GBP/USD short | Setup 2 — GBP/USD short on another day |
|---|---|---|
| Technical picture | Resistance retest after a downward breakout; D1 downtrend; D1 ADX 27; ATR at 1.1× its reference mean | The same: resistance retest, D1 downtrend, D1 ADX 27, ATR at 1.1× its reference mean |
| Items 1–9 | YES: card v3, trigger on a completed M15 candle, complete live feed, calculator-derived volume and recorded invalidation | YES: the same answers and volume |
| Item 10 — correlation | No open positions, so there is no existing exposure against which to calculate |ρ| → YES, with that reason recorded | An open EUR/USD short; |ρ| 0.73 over 30 daily sessions → NO |
| Items 11–15 | YES | Not assessed: the hard NO ends the admission check |
| Decision | Qualify. Enter according to the card | Reject. Reconsider only after the conflicting EUR/USD exposure is confirmed closed, or another valid change removes the veto; an alert alone does not change correlation or portfolio state |
| Journal entry | checklist_15=15/15, all answers YES, class A+, card version v3 | skip_reason=“item 10 = NO; |ρ| 0.73 with EUR/USD short; 30 daily-session window; alert set” |
Notice what is absent: what price did afterwards. The decision ends with the recorded reason. A subsequent winner would not change setup 2's entry because this evaluates the process, not one random outcome. Conversely, one successfully avoided loss does not prove the filter works. Assess a series of skipped setups with hypothetical outcomes against admitted trades, using intervals rather than averages alone.
7. Quick setup-class validation and a complete trade example
During a session, you may have 30–90 seconds to decide whether a developing opportunity is A+, B or C. The playbook card defines the classes, required conditions and sizing — 15.2, section 2. Here you apply that existing definition to one opportunity. Provisional classification comes before the full checklist so you do not spend time on fifteen criteria for an ineligible C setup. This first decision is simply “start the pre-trade check” or “move on.”
Rapid recognition: the first filter
A practical recognition rule is that if identifying the class takes much longer than a few seconds, do not assume it is A+. A familiar A+ pattern can be recognized in three to five seconds because its definition was written before the session. Spending half a minute fitting pieces together and persuading yourself may indicate a B candidate awaiting higher-timeframe confirmation, or a C candidate to ignore. Recognition speed is a workflow heuristic, not evidence of positive expectancy. Fast recognition does not replace the full fifteen-point validation that follows.
Where the class comes from
The playbook card owns necessary conditions, quality criteria and sizing by class. Screening supplies MTF alignment, macro regime, ATR, correlation with open positions and the time window; it does not invent class thresholds or risk percentages. Resolve conflicting document thresholds against the declared card before the session and record which version applies. Do not choose the looser document during entry. The worked checklist here uses its stated ±2-hour calendar rule. Full class and sizing definitions are in 15.2, section 2; promotion, demotion and retirement decisions belong to the audit in 15.10, section 4.
The quick-validation algorithm
- First five seconds: do I recognize a setup from the playbook? YES → step 2. NO → SKIP.
- Next ten seconds: inspect MTF alignment. The example recognition shorthand is full alignment → provisional A+, one neutral timeframe → B, and material conflict → C. Apply the actual card's class rules, including its distinction between auxiliary context and necessary setup conditions.
- Next fifteen seconds: assess potential risk:reward, ATR and macro context. A potential 1:1 risk:reward, for example, fails this card's 1:1.5 minimum and makes the candidate ineligible regardless of the other positives.
- Class decision: eligible A+ or B candidates proceed to the fifteen-point checklist. C → SKIP and record “class C setup, skipped.”
The example timing is 30 seconds for classification, 60–90 seconds for the checklist and five seconds for order submission: 95–125 seconds, or approximately 1.6–2.1 minutes from trigger assessment to entry. Whether the setup remains valid that long depends on the instrument, time and execution provider. Test this against your own tick records. If it has already expired, inspect spread relative to stop distance, price movement and the liquidity window rather than automatically blaming a slow checklist. Never chase an entry whose original risk and reward no longer apply.
The B/C boundary: downgrade when uncertain
A clearly defined A+ versus B or B versus C distinction is straightforward; the difficult case is a “strong B” against a “weak C.” Use the working rule when uncertain, classify down rather than up. It counters the temptation to promote a setup because you want to enter. B versus C uncertainty means C → SKIP. A versus B uncertainty means B, with the B-class size taken from the playbook card in 15.2, section 2, not invented here.
Qualification: an extremely restrictive classification can leave too little data to evaluate. There is no universal adequate trade count: dispersion, setup frequency and the number of tested variants all matter. A large-sample approximate 95% interval for mean expectancy is E ± 1.96 × std(R)/√n, assuming sufficiently independent observations and a suitable approximation; clustered trades and shared events require a method that accounts for dependence. It estimates uncertainty around the process mean represented by the sample, not a prediction interval for the next trades or a guarantee the regime will persist. If the interval crosses the decision threshold, defer a class change until a later audit rather than acting because “thirty trades have accumulated.” A few trades per quarter may leave the question unresolved. Methods are in 15.4, section 6; the class-change decision belongs to 15.10, section 4.
A class is not an outcome: what to measure afterwards
Classification states a hypothesis: “this setup in this class has positive expectancy.” Test it using journaled R-multiples, not win rate alone. A 60% win rate with average wins of +0.6R and average losses of −1.5R gives 0.6 × 0.6 − 0.4 × 1.5 = −0.24R per trade despite the attractive win rate.[1] Expectancy, profit factor, the R distribution and uncertainty intervals are covered in 15.9, section 4. Screening contributes two fields that an execution import cannot reconstruct: the class assigned before entry and the contemporaneous reason for skipping opportunities that were never traded.
What screening cannot calculate: MAE and MFE
MAE and MFE describe the greatest adverse and favorable excursions while a position is open, expressed in R. They help investigate whether a stop is too tight or a target too close; definitions, a scatter plot and diagnostic guidance are in 15.9, section 7. If winners repeatedly approach a full 1R adverse excursion, investigate whether the volatility filter and stop-distance rule are mismatched. That observation alone does not establish whether an ATR threshold should rise or fall; compare the actual conditional data and test a proposed change. Specify the measurement model: entry fill to exit fill, one full exit, unchanged stop and target, executable price side and a stated cost convention. Under that model, a fill at the original stop gives about 1R adverse excursion, and worse slippage can exceed it. An exact target fill gives the target-distance MFE only if the observed path and execution agree with those assumptions. Favorable or adverse slippage, partial exits, a moved target, quote-versus-fill measurements or including prices after exit can change the relationship. Record the convention once and apply it consistently; otherwise the numbers are not comparable.
A complete trade: from screening to the journal
This composite teaching example follows one EUR/USD A+ setup from the morning scan to the post-exit journal. Illustrative example, not historical performance: prices, times and amounts are synthetic. This example uses a USD5,000 account, EUR/USD pip value of USD 10 per standard lot and a1% reference-price risk budget. The USD50 model excludes additional adverse-stop execution costs; a true all-in cap requires executable price-side inputs, a cost reserve and valid volume-step rounding. The account and pip-value currencies must agree throughout the calculation. Times remain in Europe/Warsaw and must be converted for another location.
| Stage | Specific data / decision |
|---|---|
| 1. Macro regime — 08:00 Polish time | DXY +0.15% intraday, VIX 16, SPX futures +0.3%, stable US ten-year yield. Context: mild risk-on, slightly firmer USD |
| 2. Pair selection — 08:08 | ATR ≥0.9× its defined reference mean leaves 6 instruments. ADX ≥25 and a clear calendar leave 3: EUR/USD, USD/JPY and AUD/USD. Auxiliary macro context ranks AUD/USD lower: an AUD short conflicts with mild risk-on, while an AUD long conflicts with the firmer USD. The shortlist contains 2 instruments: EUR/USD short and USD/JPY long; this ranking does not establish an edge |
| 3. MTF — 08:11 | USD/JPY has no active playbook setup: set a price alert, do not start the admission checklist or open a position. EUR/USD has D1 SMA-50 below SMA-200 and ADX 28; H4 is in a downward channel with a resistance retest. H1 is consolidating below resistance, so its direction is unresolved and the class is not yet assigned. There is no M15 trigger; set an alert at 1.0850 |
| 4. Classification — 10:35 observation | At 10:35, the alert prompts inspection of the M15 candle already completed at 10:30, with body >0.5× M15 ATR below the previously defined H1 consolidation boundary in the D1/H4 direction. The card treats that completed trigger as resolution of its H1 range; it does not import a future H1 close. Provisional A+ under LON_short_EURUSD v3: aligned setup conditions, supportive macro context and potential risk:reward 1:2.2. The card owns those class rules |
| 5. 15-point checklist — 10:35–10:36 Polish time | 1–3 YES: card v3, completed M15 trigger and intact live feed. 4–6 YES: D1, H4 and macro context support the setup. 7–9 YES: calculated 0.2 lots, recorded invalidation and target, risk:reward 1:2.2, reference-price portfolio risk 1% within this simplified model; an all-in order requires the cost reserve and volume-step check stated above. 10–12 YES: no open positions — USD/JPY was only a candidate — so record why the correlation check has no existing exposure; calendar ±2 hours clear for EUR and USD; active London window; spread 0.4 pips. 13 YES: 7 hours of sleep, no alcohol in the previous 12 hours, drawdown over 48 hours −0.3 R, daily limit not reached and no three-loss streak. 14 YES: SL 1.0875 and TP 1.0795 entered for submission with the order, with prior server-side-stop verification on the card. 15 YES: EUR/USD, live account, Sell, 0.2 lots, market order; read the time-in-force field only where it applies. 15/15 completed, all YES → qualify |
| 6. Execution — 10:36 | Sell 0.2 lots EUR/USD, planned entry 1.0850; SL 1.0875. The 25-pip initial distance represents 1 R = 25 × 0.2 × USD 10 = USD 50, or 1% of USD 5,000. TP 1.0795 is 55 pips away, or 2.2 R. After submission, verify both accepted levels attached to the confirmed position in the order view. This acknowledgement follows the checklist; separate realized fills are not supplied |
| 7. Outcome — 14:50 | The target is reached after 4 hours 14 minutes. The planned-price gross move is 55 pips × 0.2 lots × USD 10/pip = USD 110, or 2.2% of USD 5,000. The levels 1.0850 and 1.0795 are planned reference prices; actual round-trip fills are collectively 0.5 pips worse: 0.4 spread plus 0.1 slippage, counted once. With no additional commission or financing, net P&L is USD 109 ≈+2.18 R. Do not subtract spread again from fill-based P&L |
| 8. Journal — 15:00 | setup_id=LON_short_EURUSD_retest; class=A+; card_version=v3; planned_R=2.2; realized_R=+2.18 net, after 0.5 pips of cost; MAE_R=−0.3, representing 7.5 pips in the illustrative reference-price path; MFE_R=+2.2 on that same path; spread_pip=0.4; slippage_pip=0.1; session=LON; checklist_15=15/15; setup_tag=trend-following. No complete executable tick path or separate entry/exit fills are supplied, so these reference-price excursions do not establish fill-based MAE/MFE |
The scenario assigns approximately twenty minutes of active screening, checking and monitoring, distributed across the 6 hours 50 minutes from the 08:00 scan to the 14:50 exit. Its counterfactual trader would have entered four other moving pairs, two against the macro regime, without screening; without the checklist, the trader would have skipped calendar and ticket checks. These are parts of the synthetic story, not measured causal effects. Without journaled MAE/MFE and a series of comparable trades, the trader cannot investigate whether a 1R stop fits the setup. That assessment needs uncertainty estimates, not an arbitrary round number of entries.
The same sequence — three screening layers, checklist and recorded reason — can serve different trading styles. Window lengths, timeframes and scan frequency change. Scalping, day-trading, swing and position-trading workflows, and choosing a style that fits available time, are covered in 15.5, section 8.
8. Common screening mistakes
Mistake 1: no defined universe
The trader watches “whatever is moving”: GBP/JPY yesterday, AUD/CAD today, NZD/CHF next time. Without a stable observation universe, daily comparisons mix different instrument populations, and behavioral patterns disappear into selection noise. Define the universe and stay within it. Its size is a process choice based on style and available scanning time, not a universal standard. Ignore instruments outside it even when their charts look attractive.
Mistake 2: subjective thresholds instead of YES / NO
“The pair has good volatility” replaces “D1 ATR(14) ≥0.9× the mean of ninety earlier completed observations of that ATR series, excluding the compared observation.” “ADX looks strong” replaces “D1 ADX(14) ≥25.” Subjective judgments drift with mood; predetermined thresholds make the same input receive the same decision. Every filter needs an unambiguous numerical or qualitative binary rule. Without an operational YES / NO criterion, the filter is undefined. Missing evidence is recorded as unknown, not guessed into a YES.
Mistake 3: skipping the calendar
“The release is three hours away; I will be out by then.” That is an unverified exit assumption, and the position may remain open because you keep giving it more time. This checklist's entry veto is precise: a high-impact event within ±2 hours means no entry. An event three hours ahead does not itself fall inside that veto, but the card still needs a plan for managing exposure into it. Calendar planning precedes the trade; it is not improvised after entry.
Mistake 4: an unrevised watchlist
A watchlist created years ago can outlive the reasons for selecting its instruments. Currency behavior can change, as EUR/CHF did after the exchange-rate floor was abandoned, or as emerging-market currencies can after monetary-regime changes. Review the watchlist quarterly. Every three months ask whether each pair still meets the conditions that justified its inclusion.
Mistake 5: technical screening without macro context
The trader checks ATR, ADX and structure but ignores DXY, VIX and yields. A technically attractive setup may behave differently in an opposing macro environment, but any claimed win-rate disadvantage must be measured in the journal rather than copied from a guide. Macro context belongs to layer 1 of this process. Its auxiliary status in the checklist remains explicit; an unsupported performance claim cannot turn it into a new hard veto.
Mistake 6: treating the checklist as a ritual
The trader ticks fourteen of fifteen boxes and enters despite a NO because the chart looks good. Section 6's rule is unchanged: any hard NO or unknown means SKIP. An auxiliary NO affects the class and cannot compensate for a hard failure. Analyze fully completed records, records with a failed item and its reason, and skipped setups with hypothetical outcomes separately; keep hard and auxiliary failures distinct rather than treating “14/15” as one homogeneous score. An interval for the expectancy difference that excludes zero can support evidence of a difference under the analysis assumptions, but sample size alone cannot, and observational grouping does not establish causation. Without that measurement, “the checklist works” expresses confidence in the procedure rather than demonstrated performance.
Mistake 7: excessive screening detail
A new fear produces a new filter until there are forty-seven. The result can be zero or one setup a week, insufficient data, frustration and rule-breaking. This example's working suggestion is five to eight market-selection filters for a manageable process; this is a heuristic, not measured universal sufficiency, and it does not replace the fifteen operational checklist items. Require each additional filter to demonstrate incremental net benefit in testing, including held-out data and the cost of trying many variants. Remove unjustified complexity through the review process.
Mistake 8: screening after entry
The trader opens the platform, sees an interesting move, enters and then checks the filters. That is retrospective rationalization. Apply the market filters before committing to a setup: scan, eliminate ineligible instruments, then inspect the shortlisted candidates' trigger candles.
Mistake 9: no price alerts
Watching charts for eight hours because “I have to be ready” can produce fatigue, poor decisions and FOMO. After screening, set price alerts in the chosen platform — this example gives TradingView and MT4 as examples — at levels where a setup may become active. Return for candidate assessment when an alert fires, while maintaining any separately required monitoring of existing exposure. An alert reduces idle watching; it is not automatic entry permission.
Mistake 10: mixing screening with the post-mortem
Reviewing a losing trade to identify what went wrong is a post-mortem, covered by the end-of-day process in 15.5, section 5. It is not tomorrow's screening. Mixing the two can make the next scan an attempt to repair yesterday's result by selecting the same failed idea. Schedule screening and the post-mortem as separate activities.
Mistake 11: not recording what you skipped
A journal full of entries but empty of rejected opportunities measures only what already appears on the broker statement. Without skip_reason, you cannot investigate whether filters rejected losses or excluded winners. Every candidate that reaches the checklist but does not become an order needs an entry with the decisive criterion number and value. The journal field scheme is in 15.9, section 2.
Mistake 12: adding filters after every losing streak
First ADX, then RSI, then a Monday ban, then no entries after 15:00. After a quarter, the rules barely resemble the original, trades have fallen to a few per month and every new filter was selected to explain the streak that prompted it. That fits noise rather than calibrating a stable process. Adding a filter creates a new version whose results must be tracked separately. Whether it stays is decided in the audit — 15.10, section 4 — not on the day of a loss. The testing problems introduced by extra variables are explained in 15.4, sections 2 and 3.
Mistake 13: confusing execution failure with strategy failure
After a losing streak, first ask whether the data and execution are reliable: do trades reconcile to the execution provider's report, are costs represented consistently in net R against the declared R0 convention, and how many trades departed from the plan? Then examine the regime, and only afterwards the edge. Do not retroactively redefine R0 to hide costs or enlarge past risk. That decision order is covered in 15.10, section 8. Screening supplies one answer: did the setup satisfy the admission rules at the moment of the click?
9. Copyable templates: a laminated checklist card
Below are two practical templates and a threshold reference card. The first is the pre-trade checklist for an A6 card beside the keyboard — 105 ×148 mm, approximately 4.1 ×5.8 inches; use a larger readable printout if needed. The second is a morning top-down screening form for the journal. The threshold card is a memory aid, not a substitute for the versioned setup card.
Template 1: the laminated fifteen-point pre-trade checklist
==============================================
PRE-TRADE CHECKLIST — 15 CRITERIA
Result: YES / NO / UNKNOWN
[H] hard — NO or UNKNOWN = SKIP
[A] auxiliary — determines setup class
==============================================
A · SETUP
[H] 1. Playbook setup + card version? [ ]YES [ ]NO [ ]?
[H] 2. Trigger on a CLOSED candle? [ ]YES [ ]NO [ ]?
[H] 3. Live feed, complete required history? [ ]YES [ ]NO [ ]?
Indicator inputs from completed candles
B · CONTEXT
[A] 4. D1 bias aligns with direction? [ ]YES [ ]NO [ ]?
[A] 5. H4 structure aligns? [ ]YES [ ]NO [ ]?
[A] 6. Macro regime supports direction? [ ]YES [ ]NO [ ]?
C · SIZING AND EXIT
[H] 7. Volume calculated using the calculator? [ ]YES [ ]NO [ ]?
[H] 8. Invalidation recorded; R:R ≥ 1:1.5? [ ]YES [ ]NO [ ]?
[H] 9. Total risk within the plan's limits? [ ]YES [ ]NO [ ]?
D · CORRELATION, CALENDAR AND WINDOW
[H] 10. |ρ| with open positions < 0.7? [ ]YES [ ]NO [ ]?
Measurement window: __________________
[H] 11. Calendar clear ±2h for BOTH currencies? [ ]YES [ ]NO [ ]?
[H] 12. Active window and normal spread? [ ]YES [ ]NO [ ]?
E · OPERATOR STATE AND ORDER TICKET
[H] 13. All five behavioral checks YES? [ ]YES [ ]NO [ ]?
Sleep ≥6h / no alcohol in previous 12h
DD48h > −2R / daily loss limit not reached
No sequence of three consecutive losses
[H] 14. SL and TP in ticket before submission? [ ]YES [ ]NO [ ]?
Prior server-side verification on card
Server acknowledgement = AFTER submission
[H] 15. Ticket checked field by field? [ ]YES [ ]NO [ ]?
Symbol / live-demo account / direction
Volume in platform units
Order type / supported time in force
GTC-day-date where applicable
SL and TP on the correct side of price
==============================================
DECISION: [ ] QUALIFY [ ] REJECT
[ ] WAIT (alert) [ ] NO DATA
Hard NO or UNKNOWN = SKIP.
Auxiliary YES cannot offset a hard failure.
Smaller volume does not turn NO into YES.
Record the reason NOW, before the later move:
skip_reason: __________________________________
==============================================
Template 2: morning top-down screening for the journal
DATE: ____________ SCAN TIME / ZONE: ____________ FILTER-SET VERSION: __________ (A filter change creates a new version.) LAYER 1 — MACRO REGIME (5–8 minutes) DXY: ___________ (direction / intraday change) VIX: ___________ (level and change) US10Y: __________ DE10Y: __________ S&P futures: ___________ Gold: ___________ Oil: ___________ News wire — relevant news today: · ___________________________________ · ___________________________________ DAILY CONTEXT — ONE SENTENCE: ___________________________________________ ___________________________________________ LAYER 2 — PAIR SELECTION (3–5 minutes) Pairs remaining after ATR ≥0.9×, ADX, calendar and correlation checks: 1. ____________ Reason: __________________ 2. ____________ Reason: __________________ 3. ____________ Reason: __________________ 4. ____________ Reason: __________________ 5. ____________ Reason: __________________ LAYER 3 — SETUPS (1–3 minutes per pair) A+ setup: ____________________________________ B setup: ____________________________________ C setup (skip): ______________________________ DAILY PLAN: · Active sessions: ________________________ · Calendar exclusions: ___________________ · Maximum trades: ________________________ · Maximum portfolio risk: _________________
What these templates omit: the weekly plan
The Sunday review of upcoming releases and allocation of work windows belong to the workflow. Its template is in 15.5, section 2. The pre-trade checklist uses one output from it: the upcoming off-limits times that feed item 11.
Quick-reference card: numerical thresholds
==============================================
MECHANICAL THRESHOLDS — WORKING CARD
EXAMPLE THRESHOLDS, NOT INDUSTRY STANDARDS
Validate on your own data: section 3.
==============================================
ATR
· ≥0.9× the mean of the 90 earlier completed daily ATR(14) values, excluding the comparison value: minimum
· >1.5×: elevated volatility; card-based size reduction
· >2.0×: extreme; skip under the ordinary card
ADX
· <20: range; eligible mean-reversion card only
· 20 ≤ ADX <25: ambiguous; skip
· 25–40: trend; trend-following candidate
· >40: strong trend; assess late-entry risk
VIX — AUXILIARY MACRO CONTEXT
· <18: low-volatility / possible risk-on context
· 18–25: intermediate context
· >25: possible risk-off; review planned exposure
· >35: this selected card blocks new positions
· Not a standalone hard veto in this checklist.
A stricter policy needs its own declared card.
CORRELATION — ABSOLUTE |ρ| WITH OPEN EXPOSURE
Always record the calculation window.
· <0.4: weak association, not independence
· 0.4 ≤ |ρ| <0.7: reduce second-position size 25–40%
· ≥0.7: item 10 = NO → SKIP
Half size is not an exception to the veto.
CALENDAR — GOVERNING ITEM 11
· No high-impact release within ±2h, BOTH currencies.
· 30 min before: no new positions.
· 0–15 min after: no entry; possible high slippage.
· 15–60 min after: still NO ENTRY, even if spread
stabilizes; all these subwindows are inside ±2h.
· Recheck the complete card after exclusion expires.
MINIMUM RISK:REWARD — EXAMPLE CARD
· A+: ≥1:2, plus all other class conditions
· B: ≥1:1.5, plus all other class conditions
· Below 1:1.5: ineligible C → SKIP
· A ratio alone does not determine the class.
VALIDATION TIME — WORKFLOW TARGET
· Provisional A+ / B / C: approximately 30 seconds
· Fifteen-point checklist: 60–90 seconds
· Submission: approximately 5 seconds
· Total trigger assessment to entry: 1.6–2.1 minutes
==============================================
What these templates omit: the journal
The card and form end at the decision. Journal field definitions, MAE/MFE, reconciliation to the execution report, metrics and uncertainty intervals are a separate tool in 15.9, section 2. Screening supplies information no execution import can reconstruct: the setup-card identifier and version, the class assigned before entry, and skip_reason with the decisive checklist item and value.
FAQ — Frequently asked questions
How much time should daily screening take?
Can screening fit a full-time job and one hour a day for trading?
Should I use free screeners or paid tools?
What if screening finds no A+ or B setup?
How often should the pair universe change?
Is a fifteen-point checklist excessive for an experienced trader?
How does screening work with price alerts?
Should screening be automated with bots or scripts?
How do equity-screening thresholds differ from Forex?
What if conditions change after I have entered, for example when VIX jumps?
Sources and bibliography
- Tharp, V. K., Trade Your Way to Financial Freedom, McGraw-Hill, second edition, 2006/2007, and Definitive Guide to Position Sizing, IITM, 2008. Sources for the R-multiple and expectancy concepts used to evaluate setup classes. They are not this example of this article's A+/B/C grading scheme; this article describes that as trading-desk practice rather than Tharp's terminology.
- European Securities and Markets Authority, Decision (EU) 2018/796 of 22 May 2018, restricting the marketing, distribution or sale of contracts for differences to retail clients (ESMA). This was the original temporary measure, not a renewal as the Polish bibliography's English title states. Restrictions applied from 1 August 2018, were renewed at three-month intervals and were not renewed after 31 July 2019. They included standardized warnings with the percentage of losing retail accounts. This historical reference is not a statement that the expired EU measure remains the current legal basis everywhere.
- Polish Financial Supervision Authority (KNF), Decision DAS.456.2.2019 of 1 August 2019 on CFD product intervention, KNF Official Journal 2019, item 27. This article describes the national measure as indefinite and as the basis for the losing-account-percentage disclosure in Poland after the temporary ESMA measure expired; providers calculate their own percentage at least every three months. Check the current provider documentation. This Poland-specific example is retained for context, not generalized to other jurisdictions or represented as newly verified legal advice.
- Tversky, A., and Kahneman, D., Availability: A Heuristic for Judging Frequency and Probability, Cognitive Psychology 5, 1973. Foundational work on the availability heuristic. Its connection here to FOMO and an unfiltered watchlist is an application of that mechanism, not a direct trading-performance experiment in the paper.
- Cboe, Cboe Volatility Index (VIX) methodology, Cboe Global Markets (Cboe VIX information). Cboe publishes the index and its methodology. The filter values, including the threshold of 25, are this article's examples, not recommendations from the index publisher. Polish regulatory context.