How to Review a Losing Trade Without Making Excuses

In short. To review a losing trade without making excuses, separate the facts from the explanation and the explanation from the result. First write down what was planned and what actually happened, using numbers from the journal. Then sort the loss into one bucket: a good loss, an execution error, an analysis error, or a rule violation. Finish with one concrete change, or with a clear note that nothing needs to change. A loss on a well-followed plan is not a mistake.

Why losing-trade reviews slide into excuses

Most traders do review their losses. The problem is the way the review usually goes. It starts with the P&L, jumps to a story about why the market did what it did, and ends with a conclusion that cannot be checked: "stop hunt", "bad luck", "news came out of nowhere". None of these is always wrong. They are excuses when they replace the review instead of being tested by it.

There is also a pull in the opposite direction. A trader who takes reviews seriously can overcorrect and treat every loss as proof of a flaw, then change the rules after each red trade. Both habits come from the same source: judging the decision by the outcome.

Psychologists call this outcome bias. In a classic set of studies, Baron and Hershey showed that people rate the same decision as better when it leads to a good result and worse when it leads to a bad one, even when they have the same information the decision maker had. A pre-registered replication with 692 participants found the same effect, including among people who said outcomes should not affect how a decision is judged (Feldman et al., replication of Baron and Hershey 1988, International Review of Social Psychology, via PMC). Knowing about the bias is not enough to avoid it. A review needs a structure that keeps the result out of the first steps.

This article is about that structure for a single trade. Tagging emotional states across many trades is a separate habit, covered in using a trading journal as a psychology tool.

Facts first, then causes, then one change

A useful model comes from outside trading. The US Army's after action review, as defined in its leader's guide, is a professional discussion that lets participants find out for themselves what happened, why it happened, and how to sustain strengths and improve weaknesses. The facts are agreed on first, and only then does the discussion move to causes and fixes. Research for the Army also contrasts this with the older "performance critique", which was based mostly on subjective opinion and was often resented rather than used (Morrison and Meliza, "Foundations of the After Action Review Process", US Army Research Institute, 1999).

Applied to one losing trade, the order looks like this:

The point of the order is that the P&L does not enter the review until step 3, and even there it is only a number to be explained.

Sort the loss into one of four buckets

Once the gap is clear, every losing trade fits into one main bucket. Picking one is what turns a vague review into a record that can be counted later.

Some losses mix two buckets. In that case, record the main one and note the second. A useful tie-breaker: if the trade would have been taken again with the same information, it was not a rule violation. If the plan was followed and the loss stayed near 1R, it was a good loss, however frustrating it felt.

Rule violations usually have a pattern behind them, and the reasons traders break their own rules are covered in why traders break their own rules.

A worked example: splitting one loss into its parts

Numbers make the buckets concrete. Here is an illustrative EUR/USD long, with position size set from the planned stop so that 1R equals $100.

• Plan: entry 1.0850, stop 1.0830 (20 pips), target 1.0890. Size: $5 per pip, so 1R = $100.
• Facts: entry at 1.0856 after chasing the move, stop moved to 1.0822 as price approached it, stopped out at 1.0822.
• Result: 34 pips against the position, a loss of $170, or -1.7R.

The review now has something specific to say. If the trade had been executed as planned, it would have been a good loss of -1R. The extra -0.7R is execution cost, and it came from two separate habits. The story "price hunted my stop" does not survive this breakdown, because the stop that was hit was not the planned one. Measuring losses in R rather than dollars is what makes this split possible, as explained in what an R-multiple is.

Turn excuses into questions that can be checked

Excuses are not banned from a review. They are turned into questions that the journal can answer.

Important. One loss, or even a short run of losses, says very little about whether a setup works. With an illustrative 45% win rate, the chance of losing the next four trades in a row is about 9%. Over 100 trades, the chance of at least one run of five or more losses is about 92% (our own calculation, assuming independent trades). Changing the rules after a good loss usually swaps a tested plan for an untested one. Keep the single-trade review for execution and rules, and leave strategy changes to a review of the whole sample.

When the losses do come in clusters, the protocol in how to handle a losing streak without spiraling helps limit the damage while the cause is still unclear.

When and how long to review

Timing matters for honesty. Right after the stop is hit, the explanation tends to be emotional. A week later, the details are gone and only the story is left. A practical window is the same day, after the session ends and before the next one starts.

The review itself can be short. For most trades, ten minutes is enough to fill in the plan, the facts, the gap, the bucket, and one line on what changes. Longer reviews are worth it only for unusual losses: much larger than 1R, or a rule violation.

Two habits help keep the review clean:

1. Write the plan and the facts before looking at what price did after the exit. If price later went to the target, that is not evidence that the exit was wrong. It is one data point for a review of exits across many trades.
2. Limit the output to one change. A review that produces five new rules usually produces none that stick. If nothing needs to change, write that down too. "Good loss, no change" is a valid result.

Journal fields that make the review possible

A review without excuses depends on what was recorded before the outcome was known. The minimum set:

• Planned entry, stop, target, and size: written before the order is placed.
• Actual entry, exit, size, and fees: so the gap can be measured.
• Changes made during the trade: a moved stop or partial exit, with the time.
• Screenshot at entry: to check what was visible at the time, not afterwards.
• Plan-followed flag and loss bucket: one tag per losing trade.
• One-line change: or "no change".

Once the bucket tag is in place, the single-trade reviews add up to something bigger. In a monthly trading review, the split between good losses, execution errors, analysis errors, and rule violations shows where the money actually goes. A month where most losses are good losses calls for patience. A month where execution errors cost more than the planned risk calls for work on execution, not on the strategy.

This article is for educational purposes only and is not financial or investment advice. Reviewing trades does not guarantee better results, and trading, especially with leverage, can lead to the loss of your entire deposit.

Record planned and actual prices for every trade in the BitStat trading journal, and tag each setup in Strategies & Setups so losing trades can be reviewed against the right sample.