How to Stop Blundering: A Five-Second Checklist Before Every Move

Almost everyone who blunders says the same thing afterwards: "I saw it as soon as I moved." The knowledge was there. What was missing was a routine that made you look. Below is a short check you can run on every move, and the evidence for why it works.

By the RookSac teamSeptember 29, 20265 min read

Blunders are a process problem

Ask a 1200 and a 2000 player whether a knight left en prise is a bad idea and both will say yes. The difference between them is not that the stronger player knows more about hanging pieces. It is that they check, almost without thinking, before they play. Blundering is what happens when the check gets skipped: you are sure of the plan, the move looks natural, you are short of time, or the position is emotional.

That is good news, because a process can be trained in a way that knowledge cannot be crammed. The aim of this article is a routine that takes a few seconds and catches most of the blunders that a game review lists.

What blunders look like

When you go through blunders in your reviews, they fall into a handful of kinds:

• Loose pieces. A piece is attacked and nothing defends it, or a capture wins it outright.
• Overlooking the opponent's last move. It created a threat and you played on as if it hadn't.
• Moving a defender. The piece you moved was guarding something, and now it isn't.
• Walking into a tactic. A fork, pin, skewer or discovered attack (see six tactical patterns).
• Back-rank and king safety. A mate threat that only appears after a plausible-looking move.
• Time trouble. A move that was never really checked.

Nearly all of these are answered by looking at what your opponent can do next, in the forcing sense.

The evidence: check the forcing moves first

In the three RookSac sample reports (300 real games by strong players, described on the sample report page) the players made 71 moves that the review called blunders. In 33 of those 71 (46%) the engine's punishing reply began with a capture (25) or a check (11, some of which also capture). Nearly half of even the elite players' blunders were answered by the most forcing kind of move there is, and those are precisely the moves that a short check can find.

That is the origin of a classic rule taught to improving players: before you move, look at checks, captures and threats, first for you, then for your opponent. It works because forcing moves are few, easy to list and carry the biggest consequences.

The five-second checklist

Run this after you've decided on a move and before you touch the piece:

1. What did my opponent's last move do? Which squares does the moved piece now attack? What has it uncovered? Ask this even when the move looks pointless. If it looks pointless it was probably not.
2. After my move, what can they check, capture or threaten? Go through your opponent's checks first, then captures, then threats. If any of them is good for them, choose another move.
3. What does my move stop defending? Look at the piece you are moving and the squares it guards, and at any pawn or piece it was shielding from attack.
4. Are my pieces protected? Look at every piece of yours that's attacked, and every piece that's loose, meaning undefended.
5. Is my king safe? Look at back-rank mates and open lines to your king, especially if you have castled and pushed no pawn.

Steps 1 and 2 catch the majority. When the position is quiet, you can run through the list in under five seconds. When it isn't, you have found the moment where the game deserves real time.

An example: the loose piece

Here White wins a piece with 1.Bxd5. The knight on d5 is attacked by the bishop on g2 and no black piece defends it: it is loose. A player who checks the position from the loser's side will spot that before making a move that leaves it there.

The same thing happens to you when you leave a piece loose. Make the check a habit that asks, at the end of every move, "which of my pieces has nobody defending it?"

Building the habit

A checklist you have to remember will fail in the moments you most need it, so it has to be automatic. Three ways to get there:

• Start with slow games. In 15+10 or longer, force yourself to run all five steps every move for ten games. It will feel slow. In a month it will be a reflex you can use in blitz.
• Sit on your hands. When you spot an obviously good move, pause for a breath before playing it. Most blunders are played instantly.
• Keep a blunder log. After each game, note which step would have caught each blunder. After twenty games, the step you keep skipping is obvious, and it is the one to practise.

Tactics puzzles help too, as long as you solve them the same way you should play: list the forcing moves, calculate, then move. See training with puzzles.

When time is the problem

A checklist takes time you don't have if you've spent it early. Two adjustments help. Play the first ten moves quickly, on knowledge and principles, so you enter the middlegame with time in hand. And in a fast game, drop steps 3 to 5 and keep steps 1 and 2: the opponent's last move and their forcing replies. Even a two-second check is far better than none. For more, see time management in blitz and rapid.

Finding your own blunder pattern

The checklist is general. Your own blunders will have a specific shape: perhaps you overlook checks, or leave pieces loose late in the game, or blunder mostly after a big move. A single review tells you a little; the picture appears over dozens of games. That is the case for reviewing many games at once, and it is what a report's blunder list is for. Look at your last 30 blunders, ask which checklist step would have caught each, and practise that one.