No-Trade Rules
Learn how no-trade rules prohibit new risk during defined market, portfolio, operational or trader states and how objective re-entry criteria prevent avoidance.
Reading progress — saved on this device
No-trade rules define conditions under which new risk is prohibited even if an individual setup appears valid. They protect the portfolio when the environment, infrastructure or trader state falls outside planned operating conditions.
Learning objectives
- Separate market, portfolio, operational and trader-state no-trade conditions.
- Define hard triggers and re-entry criteria in advance.
- Use no-trade rules without converting caution into permanent avoidance.
What it is
No-trade rules sit above setup selection. They answer whether the trading system is permitted to take new exposure at all. A valid signal cannot override a hard portfolio loss limit or a venue failure.
Market-state rules can prohibit particular strategies in unsuitable volatility or liquidity regimes. Portfolio-state rules can stop new risk after drawdown, aggregate exposure or leverage thresholds are reached.
Operational-state rules cover exchange outages, suspended withdrawals, unreliable price feeds, wallet incidents or connectivity failure. Trader-state rules can cover severe fatigue, repeated checklist breaches or other predefined conditions that make reliable execution unlikely.
How to design the rules
Triggers should be observable: session P&L below -2R, spread above a threshold, exchange withdrawals suspended, or a checklist that cannot be completed reliably. Vague language such as "do not trade when uncomfortable" is difficult to enforce consistently.
Re-entry criteria are equally important. If trading stops because the exchange has suspended withdrawals, the rule might require restoration plus a verification period. If trading stops after a loss limit, the next permitted session can be defined in advance.
Some conditions justify smaller size rather than zero risk. The plan should distinguish reduced-risk mode from no-trade mode so the trader does not improvise during stress.
The rule accepts opportunity cost. A stopped trader may miss a winner. That is not proof that the rule failed; its purpose is to limit exposure during states where expected process quality or infrastructure reliability is below standard.
No-trade categories
| State | Example trigger | Re-entry condition |
|---|---|---|
| Market | Liquidity/spread outside strategy limits | Metrics return inside predefined range. |
| Portfolio | Session loss reaches -2R or exposure cap | Next authorised session or risk reset under plan. |
| Operational | Venue outage, withdrawal suspension, bad price feed | Service restored and independently verified. |
| Trader process | Checklist cannot be completed reliably or repeated breach threshold | Defined cooldown/review and process reset completed. |
Worked example and thought exercise
A momentum signal qualifies perfectly, but the trader is already down -2R for the session and the plan defines -2R as a hard stop. The trade is rejected. Whether the signal later wins is irrelevant to whether the no-trade rule was followed.
Separately, an exchange suspends withdrawals while spot prices remain normal. The operational rule prohibits new exposure on that venue because counterparty and exit risk changed even though the chart did not.
Thought exercise: why should a no-trade rule specify how trading resumes as carefully as it specifies when trading stops?
Common mistakes and practical workflow
- Creating rules only after a stressful event occurs.
- Using subjective discomfort as an unlimited veto.
- Ignoring operational failures because the market setup still looks good.
- Judging the rule by the profit of trades that were deliberately skipped.
Practical workflow
- List market, portfolio, operational and process states that materially reduce expected quality.
- Give each state a measurable stop trigger.
- Decide whether it requires reduced risk or zero new risk.
- Define explicit re-entry conditions.
- Review missed opportunities and avoided losses across a sample rather than overriding rules ad hoc.
Knowledge checkpoint
- Why can a valid setup still be rejected?
- What distinguishes reduced-risk mode from a no-trade state?
- Why are operational events valid trading stops?
- What prevents a no-trade rule from becoming permanent avoidance?
FAQs
❓ Can no-trade rules reduce returns?
Yes. They can skip profitable trades; the purpose is risk/process control, not maximum market participation.
❓ Should I always stop before major news?
No. Event restrictions depend on the strategy and should be defined in the plan rather than assumed universally.
❓ Why not just trade smaller?
Some conditions suit reduced risk, while infrastructure failure or a hard loss limit may justify zero new exposure.
❓ Can no-trade rules become avoidance?
Yes, if triggers and re-entry criteria are vague. Objective rules reduce that risk.
Summary
No-trade rules protect the trading process when conditions fall outside its authorised operating range. Clear triggers, reduced-risk distinctions and explicit re-entry criteria make the rules enforceable rather than emotional.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →