Don’t Be Fooled
🎯 Learning Objective: To defend against declarer’s own deception — using three diagnostic questions that turn a guess into a reasoned decision.
💡 Key Idea: Declarer can deceive you exactly as you can deceive him — with a card played out of its normal order, a suit attacked for reasons that are not what they seem, or a line of play that only makes sense if he holds something he does not. The defence against this is not suspicion for its own sake, but three concrete questions asked at the moment of doubt.
Question one: where is the missing small card?
If declarer’s play only makes sense with a specific low card in a specific hand, and that card has not appeared, ask where it actually is. A declarer trying to conceal his exact holding will often manage the honours convincingly but cannot make a small card materialise from nowhere — the count of the suit, done carefully, frequently exposes the deception even when the play itself looked natural.
Question two: what does declarer want me to do?
If a play seems designed to nudge you towards a particular defence — cash a suit, duck a trick, switch early — consider doing the opposite. A declarer who plays a hand to look natural is not deceiving you; one who plays it to look like it is asking for something specific usually is.
Question three: does his line make sense if he holds what he’s pretending to hold?
Test the story declarer’s play is telling against what you can actually see. If his line only makes sense assuming a particular card lies in a particular hand, and everything else you have seen makes that placement unlikely, trust the arithmetic over the impression his play creates.
The paired problem — same question, opposite answers. Two defensive problems can look identical on the surface — declarer ducked trick one, do you continue the suit? — and yet have opposite correct answers, decided purely by the count. There is no shortcut that covers both: the only way through is to count declarer’s tricks and shape before deciding whether the duck was genuine or a deception designed to make you switch away from a suit that was actually still working for your side.
Blocking play, and the hypothetical count
Two further tools belong here. First, blocking play in defence — sometimes the right answer to declarer’s deceptive line is not to work out the true position but simply to play a card that blocks the suit regardless of how it actually lies, removing the need to solve the puzzle at all. Second, the hypothetical count — when you cannot be sure of declarer’s shape, assume the layout that makes his story true and ask whether the rest of the hand still adds up. If it doesn’t, the story is false.
⚠️ Common Mistakes:
Assuming every unusual play is deceptive. Most unusual-looking plays are simply the natural result of an unusual hand. Reach for these three questions when something feels off, not on every trick.
Doing the opposite without checking the count. “Do the opposite of what declarer wants” is a starting instinct, not a rule to apply blindly — confirm it against the arithmetic before you act on it.
Treating both duck problems as the same problem. A duck at trick one is not automatically a signal to switch, and it is not automatically a signal to continue either. Count before you decide which one you are facing.
🧠 Memory Tip: Where’s the small card? What does he want? Does his story add up? Three questions, asked at the moment of doubt, turn a guess about declarer’s deception into a reasoned decision.
Summary
Declarer deceives you the same way you deceive him. Defend against it with three questions — where is the missing small card, what is declarer’s play asking you to do, and does his story survive contact with the arithmetic you can see. When two problems look identical on the surface, trust the count to tell them apart, not the resemblance. And remember that sometimes the simplest defence is not to solve the puzzle at all, but to play a card that blocks the suit whatever the truth turns out to be.
This completes Course 7 — Defence.