How to stop revenge trading with a pre-trade checklist

A stop loss gets hit, and a few minutes later you are back in the market with a bigger position, a worse entry and no clear setup. You want to recover the loss quickly.

This is revenge trading. It usually starts when you stop treating your plan as a requirement, even if your strategy is sound.

This guide shows how a short written checklist can add a step between that moment and your next order.

Signs of revenge trading

You may not notice it while it is happening, so it helps to know the signs:

• A new trade within minutes of a loss.
• A bigger position than usual, taken to win the money back.
• An entry without the confirmation you normally wait for.
• Trading outside the sessions or pairs you planned.
• Moving or removing a stop loss because you expect price to turn.

One of these on its own may not cause much harm. The larger risk is a chain of emotional trades that turns a normal losing day into the worst day of the month.

1. Write your rules before the market opens

Rules are easier to follow under pressure when you wrote them in a calm moment.

Good checklist rules are short and checkable, so you can answer each one with yes or no:

• "H4 and H1 trends point the same way."
• "Entry is at a zone I marked before the session."
• "Stop loss and take profit are set, with at least 1:2 risk:reward."
• "No high-impact news in the next 30 minutes."
• "I feel calm, and this is not a revenge trade."

Avoid rules you can't check, such as "be patient" or "trade well".

Decide which rules are required and which are reminders. Five or six required rules are usually enough, because a much longer list is easy to skim.

2. Go through the checklist before every trade

In Red Candle, Log Trade always opens your pre-trade checklist first. You tick the rules your setup meets, then continue to the trade.

If a required rule isn't met, you can still log the trade, because the app doesn't control your broker. You must write an override reason, and the trade is marked Broken. Having to type a reason gives you a moment to reconsider.

You can also tick your rules on the Dashboard while you wait for a setup. The ticks carry over to Log Trade on the same day.

3. Set daily limits

A bad day can still get out of hand with a checklist, so decide your limits in advance:

• Max trades per day, for example 3.
• Max losses per day, for example 2.

In Red Candle, you set both in Checklist & Rules. If you turn on Lock logging when a limit is hit, logging stays locked until tomorrow.

Red Candle can't block MetaTrader, so treat the lock as your cue to close the platform and step away. Daily loss limits: keep a bad day small covers this in more detail.

4. Review what breaking the plan cost

Once a week, compare the trades that followed your plan with those marked Broken:

• Compare their win rates. In the Journal, filter by Plan → Followed or Broken.
• Check Most Broken Rules to see which rules you skipped on losing trades in the last 30 days.
• If you use AI, AI Review summarizes these numbers as strengths, weaknesses and what to work on.

If your broken trades win less often, seeing that number may make you think twice before the next override.

A short checklist to start with

If you don't have a checklist yet, start with this one and adjust it to your own trading:

1. The trend on my higher timeframe agrees with the trade.
2. Entry is at a level I marked before the session.
3. Stop loss and take profit are set, and risk:reward is at least 1:2.
4. There is no high-impact news in the next 30 minutes.
5. I'm calm, and I haven't hit my daily limit.

Use it for two weeks. Then review which rules you break most often and how those trades turned out.

Key takeaways

• Revenge trading often starts right after a loss, when the plan starts to feel optional.
• Write short, checkable rules before the market opens.
• Go through the checklist before every trade, and write a reason when you override it.
• Set your maximum trades and losses per day in advance.
• Compare Followed and Broken trades every week.