Candidate Move Errors – “I Didn’t Even Consider It” (and How to Fix That)
Many “blunders” are not calculation failures. They happen because the correct move was never even on your radar. That’s a candidate move error — your candidate list was too narrow, biased, or missing forcing moves.
What Is a Candidate Move Error?
A candidate move error is when you choose from the wrong set of options. You calculated “well” — but only inside a tiny box.
Common signs:
- you say “I didn’t even consider that move” after the game
- you calculated one line deeply, but missed a simple refutation
- you played a “normal” move while a forcing move existed for either side
- your move ignores the opponent’s best defensive resource
Why Candidate Lists Break
Candidate selection is where psychology leaks into chess. Most errors happen because you were drawn toward one idea and stopped searching.
Typical causes:
- plan tunnel vision: you only looked for moves that support “your plan”
- greed bias: you only looked at pawn grabs / material wins
- fear bias: you only looked at passive defenses
- habit bias: you auto-played a “standard move” without scanning alternatives
- time pressure: you picked the first move that looked safe
The #1 Fix: Forcing Moves First (For Both Sides)
Candidate selection is not “list 10 moves”. It’s a simple priority rule: forcing moves first.
Candidate priority order:
- 1) Checks (yours and theirs)
- 2) Captures (especially with tempo or tactical purpose)
- 3) Threats (forks, pins, discovered attacks, mating threats)
- 4) Only then quiet improving moves
If you skip this step, you will repeatedly miss tactics and defenses.
How to Diagnose the Exact Candidate Error
When you review the game, don’t just write “missed tactic”. Identify which candidate stage failed.
Candidate error types:
- Type A: you didn’t consider the opponent’s forcing move (defensive blindness)
- Type B: you didn’t consider your own forcing move (missed opportunity)
- Type C: you considered the move briefly but dismissed it for a wrong reason
- Type D: you never generated a “boring” safety move that solves the position
The “2–3 Candidate Rule” (Stops Overthinking)
Good practical chess rarely needs 8 candidates. It needs 2–3 realistic options. More than that usually means you haven’t prioritized forcing moves properly.
Simple routine:
- generate forcing moves first
- choose 2–3 candidates total
- calculate only these (unless a new forcing move appears)
How the Engine Helps (Without Wasting Time)
Engines are great for revealing “invisible candidates” you didn’t list. But the improvement is not the engine move — it’s the reason the move belonged on your list.
Engine questions for candidate errors:
- What forcing move did I fail to consider for either side?
- What was the simplest “safety move” that solved the position?
- What was the hidden resource that refuted my plan?
One-Line Lesson Template (Use This in Your Notes)
Candidate errors improve fast when you write the right kind of lesson. Keep it short and reusable.
Good examples:
- “Before improving a piece, scan opponent checks and captures.”
- “When the king is exposed, forcing moves must be candidates.”
- “When defending, always include at least one move that removes the main threat.”
Where This Fits in the Analysis System
- critical moments tell you where to focus
- candidate errors explain how you chose the wrong move
- missed threats often happen because the opponent’s forcing move wasn’t a candidate