Who this is for — Readers who want to distinguish a verifiable operating deviation from a normal market loss and record it without personal judgment.
A trading mistake is an observable difference between a rule defined before the trade and what the trader actually decided, submitted, or executed. The rule may concern side, quantity, order type, entry condition, risk limit, or a control procedure.
A loss does not establish that a mistake occurred; a profit does not establish that the process was correct. This separation limits outcome bias: in Baron and Hershey's experiments, knowing whether an outcome was favorable or unfavorable changed evaluations of decision quality even when the information available to the decision maker was the same.
In plain terms — Compare the rule with the evidence first; read the financial result only afterward. The classification concerns the process, not the trader's personal worth.
Process and outcome are separate axes
What can be classified
| Observed case | Cautious classification | Minimum evidence |
|---|---|---|
| Quantity, side, or order type differs from the rule in force | Process deviation | Dated rule, order ticket, and confirmation |
| Compliant trade closes at a loss | No mistake established by outcome alone | Consistent plan, orders, and fills |
| Execution price differs from the trigger because of liquidity or venue rules | Execution event to verify | Order type, trigger, fills, and intermediary specifications |
| Ambiguous rule or insufficient record | Not assessable | Improve the documentation system without inventing a violation |
This scheme is a Cyclepedia editorial operationalization, not a universal taxonomy imposed by a regulator. A deviation may be intentional, accidental, or caused by a technical constraint; motive should not be inferred unless it was documented.
Verification procedure
- Identify the version of the rule that was valid before the trade.
- Gather the ticket, confirmation, fills, timestamps, quantity, costs, and contemporaneous notes. FINRA recommends reviewing confirmations, which report details such as executed price and quantity.
- Compare one field at a time: condition, side, quantity, order, risk, and subsequent management.
- Classify the case as adhered to, deviation, external event, or not assessable; do not use profit or loss as a shortcut.
- Record the deviation descriptively and connect it to a verifiable lesson.
- Look for recurrence only across comparable cases, without assigning causation from a single trade.
Illustrative example — The rule authorized no more than 20 units, while the confirmation shows 25. The five-unit difference is a verifiable deviation whether the trade gains or loses. If quantity and orders instead match the plan and the market reaches the planned stop, the loss does not establish a process mistake.
Limits of the label
Following a rule does not make it valid or profitable; a defective rule can be applied perfectly. Likewise, a mistake count alone does not measure skill, strategy quality, or future risk. Plan adherence, outcome, and rule quality are separate dimensions.
Limit — This classification supports process review; it provides neither trading signals nor performance guarantees. When no prior rule or reliable evidence exists, the correct answer is “not assessable.”
Sources
- CFTC — Forex Frauds — recommends defining risk capital, risk per trade, and a plan before trading (accessed 11 August 2026).
- FINRA — Are You Checking Your Trade Confirmations? — describes price, quantity, date, and other confirmation data used to verify what was executed (accessed 11 August 2026).
- Baron and Hershey (1988), Outcome bias in decision evaluation — five peer-reviewed studies on how outcomes influence retrospective evaluations of decisions.
Links
- trade-lesson — turn a review into a controllable action.
- plan-adherence — measure conformity with predefined rules.
- risk-per-trade — budget assigned before the trade.
- trading-journal — preserve evidence and decisions over time.