Poaching Is Destroying Your Doubles Game

Played a rec doubles session last week where the same thing happened four times in ten minutes. Partner cuts in front of me for a poach, doesn’t get it, I’ve already moved to cover their side, nobody’s home on mine, easy put-away for the other team. Look of frustration directed at me. “You should’ve stayed.”

I did stay. You left. This is the unspoken conversation happening on rec courts everywhere.

Poaching is supposed to be a weapon. At the right level, used the right way, it is — a well-timed cross-court intercept that catches the opponent off guard, wins you a point you had no business winning, and shifts momentum. But at the recreational level, “poaching” has quietly become shorthand for “I’m going to cut across and take that ball without telling you, and if it doesn’t work out, that’s a positioning problem you’ll need to sort out.”

It isn’t. It’s a communication problem. And it’s costing rec teams far more than they realize.

What good poaching actually looks like

Before the argument: poaching is real, legal, and genuinely useful. The best doubles teams poach constantly. The difference is they’re doing it with their partner, not to them.

Good poaching is either communicated in advance — “I’m going to try to jump the middle on their return, cover my line” — or it’s a pre-agreed pattern, like always taking middle balls above the tape when the score is tight. Some teams develop signals. Some just play together enough that the reads are shared. The point is that both players know what’s happening, so when one person moves, the other moves with them instead of standing there wondering where their partner went.

The poach that works is a two-player coordinated shift. One cuts, one covers. The space created by the moving player is filled by the staying player before the ball arrives. The other team sees one thing but finds another. It’s genuinely effective and a lot of fun to pull off.

That is not what’s happening at most open play sessions.

What rec poaching actually looks like

What’s happening at open play is usually a unilateral decision made mid-point, telegraphed to no one, leaving the poaching player’s side briefly uncovered and their partner frozen between “should I cover their side?” and “are they actually going for that?”

The freeze is the killer. A half-step in the wrong direction loses more points than the poach attempt wins. Even if the poach is successful — ball goes in, point won — the partner has to recover their position for the next shot, which takes time and attention they should be using for something else.

And when the poach doesn’t work? The ball gets through, or the poacher pops it up, or — most commonly — they don’t quite reach it and deflect it into a worse position than if nobody had moved. Then there’s a scramble, or a point lost, and sometimes a look that says: “You didn’t cover.”

This is what creates the real damage. Not the missed shot — the erosion of trust. When you can’t predict what your partner’s going to do, you start hesitating on your own decisions. You’re playing your game and their game simultaneously, doing defensive planning that should be split between two people. It’s exhausting, and it shows in the score.

The blame transfer problem

Here’s what makes this pattern particularly durable: the person poaching doesn’t usually experience it as a mistake. The narrative in their head is “I saw an opportunity and went for it.” If it works, that’s validated. If it doesn’t, “my partner wasn’t in position.” The accountability lands on the partner who had no information and was never part of the decision.

The partner who got left behind has the opposite experience — they did everything right based on what they knew, which was nothing, and now they’re in the wrong. If they say something they’re being sensitive. If they don’t say something it happens again.

Nobody’s a villain here. This is just what happens when a coordinated two-person skill gets attempted as a solo one, by players who’ve seen it work at higher levels without seeing the communication infrastructure underneath it.

When to actually poach (and how)

The technical side: a poach makes sense when you read that the incoming ball is going to a specific spot — usually a predictable cross-court dink from a player who always goes cross-court — and you have time to move and still make good contact. It does not make sense on a hard drive you’re hoping to intercept, or on a ball you haven’t actually seen yet, or when you’re already stretched on your own side.

Before you go: say something. “Mine if it’s middle” during the rally is too late. Set it up between points. A simple “I’m going to cheat middle next rally, cover my line” takes three seconds and turns a chaotic individual move into an actual play. Your partner knows, covers accordingly, and either you win the point cleanly or you miss and there’s someone home on your side.

The doubles positioning fundamentals matter here: you’re a unit, not two singles players sharing a court. When one person moves, the other adjusts. That only works if both people are aware the move is happening.

The honest version

The rec players who handle poaching best aren’t the ones who do it most — they’re the ones who communicate before they do it. A team that calls one coordinated poach per game and executes it cleanly is scarier than a team where one player is freelancing constantly and their partner is guessing.

If you’re the one poaching: your partner isn’t slow, they’re uninformed. Tell them what you’re going to do. If they’re a good partner, they’ll cover. If you can’t tell them in time, don’t go.

If you’re the one getting left behind: it’s not your fault, but it is your conversation to have. Between points, not during them.

How does your regular doubles partner handle this? And if you’re the one poaching — honest question — do you call it before you go?