A repeated rule breach deserves investigation, not an automatic diagnosis that emotion has defeated logic. The rule may be unclear, the interface may make mistakes easy, or the trader may be bypassing a known limit. Each problem calls for a different response.

Start with the exact action: what was intended, what happened and what evidence can explain the difference.

Check whether the rule can be applied

“Trade only strong momentum” is difficult to audit without a definition. An order-quantity check can be much more specific. Write observable conditions and include what happens when data is missing or conditions conflict.

A rule can also be clear but unsuitable. For example, demanding another trade after every loss may conflict with an account limit. A complete plan needs stop conditions and permission to take no new trade.

Avoid explaining the brain as two literal switches where one inevitably takes control by a particular time of day. That story does not identify the operational cause of a wrong order.

Reconstruct the breach from records

Compare intended and submitted quantity, account selection, timestamps, fills and cancellations. If a stop did not limit the loss as expected, check order type and execution before assuming it was moved deliberately.

Group specific failures, such as duplicate entries or unplanned size increases. Do not label every early exit a breach if the plan contained a valid condition for it.

Record a profitable breach too. The later result does not change whether a control was bypassed.

Put a check near the failure

If quantities are wrong, add a review of quantity and account before submission and practise it in simulation. A position-size calculator helps only if its inputs, contract values and rounding are correct.

If you trade after a limit, check what any available restriction actually enforces. A reminder, timer or local software feature may not block manual broker orders. It may also fail to cancel existing orders or flatten positions.

Bracket orders are not impossible to override and do not guarantee fills at their requested prices. Verify their broker-side or local behaviour, including partial fills and cancellation, before relying on them.

Track severity as well as frequency

A compliance percentage can be useful as a summary, but it should not make a critical account-limit breach acceptable within an eighty- or ninety-percent target. Record the consequence and investigate serious failures separately.

There is no universal two-week period of high compliance that makes a size increase appropriate. Operational competence, strategy evidence and financial suitability remain different questions.

If live exposure makes the issue harder to investigate, pause and use simulation for mechanics. Minimum live size is not automatically negligible or safe.

Review the proposed fix fairly

Define what improvement would look like before trying a new procedure. Check whether it solves the named problem and whether it creates another one, such as hiding a necessary alert.

Compare rule-following and rule-breaking trades without assuming the second group must always lose. A poor strategy can lose when followed perfectly. Do not selectively classify winners as disciplined after seeing their results.

Frequently asked questions

Should I punish myself for a breach? Focus on protecting the account, understanding the event and correcting the procedure. A financial penalty or extra live trade is not required to learn from it.

What if the rule is the problem? Review its purpose and evidence. Test alternatives away from the immediate live decision and preserve necessary account constraints.

What if the behaviour feels difficult to control? Consider pausing new exposure and seeking appropriate support. More confidence or a higher compliance target is not a substitute for addressing a persistent problem.

See our risk checklist for related pre-trade checks.

Risk Disclaimer: Trading involves substantial risk of loss. Past performance is not indicative of future results. See our full risk disclaimer.