A doubles point can turn on one quiet finger hidden behind a back. Your partner flashes a signal, the serve goes wide, the net player darts acrossโand suddenly your opponents are scrambling to hit a passing shot they never wanted to hit. Or the signal is misunderstood, both teammates move the same way, and the middle of the court opens like a front door.
Thatโs the thrill of doubles communication: tiny messages, big consequences. A clear system helps you coordinate poaches, serve locations, and return formations without a mid-point conversation. The trick isnโt inventing a complicated code. Itโs agreeing on a few simple signals, using them consistently, and talking through the plan before the ball is in play.
Start with the idea behind the signals
In most doubles teams, the net player gives a hand signal behind their back before the serve. The server sees it and either agrees to the plan or asks for a change. The message usually covers two things: where the serve is going and whether the net player plans to move across for a poach.
Thereโs no universal code. One teamโs signal for a poach might mean โholdโ to another, so never assume your partner knows your system. Agree on the meanings together, then keep the signals easy to see and easy to remember.
Think of the signal as a plan, not a promise. If the serve lands somewhere unexpected or the returner makes a brilliant play, adjust. A good team follows the strategy; a smart team responds to the ball.
Build a simple serve-and-poach code
Begin with two questions: Where are we serving? And what is the net player doing after the serve? You can assign a signal to each answer, or use one signal for the serve location and another for the net playerโs movement.
For example, a team might use fingers to call the serve location and a closed fist to indicate that the net player will stay. A separate signal could mean the net player will poach. Thatโs only one possible code; the important thing is that both players know exactly what each sign means.
| Signal category | Example meaning | What the team should confirm |
|---|---|---|
| Serve target | Wide, body, or down the T | Which side of the court the target refers to |
| Net-player movement | Poach, fake, or hold position | Whether a fake includes a recovery step back |
| Combination plan | Serve wide, then poach | Who covers the open alley if the return goes there |
Make the serve target specific
โServe wideโ can mean different things to different players. Does it mean near the singles sideline, or just away from the receiverโs forehand? Choose a practical target, such as โwide enough to stretch them, but with margin,โ and discuss it before the match. The signal points to a zone, not a spot you have to hit by a millimeter.
Also decide what you mean by โbody.โ On the deuce side, a serve into the receiverโs body may jam a right-handed playerโs forehand. On the ad side, the same general target can create a different problem. Your plan should account for handedness, strengths, and the returnerโs positionโnot just the court markings.
Poach with a plan for the space you leave
A poach is not simply a dramatic dash across the middle. Itโs a coordinated move that makes the returner feel pressure and gives your team a coverage plan. If the net player crosses, the server usually shifts toward the open side. If the net player holds, both players need to be ready for the likely return direction.
That teamwork is what makes an aggressive net presence effective. The Bryan brothers became famous for their attacking doubles style, but the lesson for recreational teams isnโt to copy any one secret signal. Itโs to make movement look coordinated: the server commits to a target, the net player reads the return, and both partners understand who owns the next ball.
Use a โstay,โ โgo,โ and โfakeโ system
Many teams get plenty of mileage from three net-player options:
Stay: Hold the normal position and react to the return.
Go: Cross aggressively to intercept the return.
Fake: Show movement to make the returner hesitate or change direction, then recover to cover the likely shot.
Before using a fake, agree on what it looks like. A tiny shoulder twitch and a full sprint across the court are not the same message. The server also needs to know whether to shift behind the move or stay balanced. If youโre still learning the system, start with โstayโ and โgo.โ Add the fake once you can execute those calls without confusion.
Timing matters. The net player should give the signal where the server can see it, then get into a ready position. Donโt keep flashing a signal as the server begins the motion. The aim is a calm, clear agreement before the pointโnot a last-second puzzle.
Between-point communication: quick, useful, and calm
Hand signals canโt answer every question. Between points, use a short conversation to adjust your plan. Keep it practical: one observation, one decision, and a reminder about the next ball.
For example: โTheyโre driving the return crosscourt when I serve wide. Letโs show poach, but hold unless itโs short.โ That gives both players something specific to try. Compare it with โWe need to do better,โ which may be true but doesnโt tell anyone what to do.
Useful between-point topics include:
Which return the opponents keep favoring.
Whether a serve target is working or needs to change.
Who is covering the middle on a particular formation.
Whether to poach more, hold position, or use a fake.
A simple reset after an error: โSame plan; trust the call.โ
Keep your tone steady, especially after a missed poach or a return that gets past you. Blame turns the next point into a second argument. A calm โI went earlyโletโs hold next timeโ gives your partner information and helps you move on.
Also be mindful of event rules and pace-of-play requirements. Between-point discussion should stay brief enough that youโre ready to play when the next point begins. In some competitions, coaching and communication rules may differ, so check the regulations for your event rather than assuming every format works the same way.
Coordinate return formations, too
Communication matters just as much when youโre returning. Before the server starts, decide whether your net player will use a standard position, shade toward the middle, or show an unusual look. The returner should know what that movement means and which area they are expected to cover.
A simple return plan might sound like this: โIโll return crosscourt; you stay near the middle unless you see a weak second serve.โ That sets a default and leaves room to attack. If youโre planning to poach the return yourself, tell your partner so they donโt also move into the same space.
Teams can also agree on a specific formation for a particular point. For example, the net player might start closer to the alley to suggest a standard look, then shift toward the center before the serve. Or the pair might use an I-formation, with the net player near the center service line and a pre-agreed direction for the serve. These setups can disrupt a serverโs rhythm, but they need a clear plan for who covers each side.
| Return situation | Possible plan | Key coverage question |
|---|---|---|
| Strong first serve | Use a predictable return target and protect the middle | Who takes a ball hit directly between you? |
| Second serve you can attack | Return aggressively while the net player looks for a poach | Who covers the line if the net player crosses? |
| Opponent uses a sharp angle | Return crosscourt with enough height and margin | How far should the net player shade toward the center? |
Donโt change formations just to look clever. Use them to solve a problem: a server targeting one player, a returner who reads your usual pattern, or opponents who leave a predictable gap. If the new formation creates more confusion for you than for them, go back to your reliable setup.
Common communication mistakesโand easy fixes
Changing the code without telling your partner
If you want a new signal, explain it before the next point. A sign that suddenly means something different is worse than no sign at all. Keep the code consistent through a match unless both players clearly agree to change it.
Poaching without server support
The net player canโt cover every possible return. If you plan to cross, the server needs to know and shift accordingly. Talk through the uncovered alley before you use the signal in a tight moment.
Using too many signals
A sprawling code can sound impressive in practice and disappear under match pressure. Start with a few clear options. Add complexity only when both players can explain the system quickly and execute it reliably.
Sending mixed messages
Donโt flash โpoachโ and then stand frozen, or signal โstayโ while drifting into the middle. Your movement should match your message. If you change your mind because of the toss or the return, react naturally and tell your partner what happened afterward.
A quick practice routine for doubles teams
You donโt need a special drill to build better communication. Set aside ten minutes in a practice session and make the signals part of the point:
Agree on a small signal set and rehearse what each sign means.
Play several serve-and-volley points with the net player calling โstayโ or โgoโ silently.
After each point, take a few seconds to say whether the plan worked and what youโll change.
Switch serving sides and roles so both players understand the coverage.
Finish with a short set and keep the same system under pressure.
The goal isnโt to poach on every possible ball. Itโs to make your opponents respect the possibility. If they see a net player who sometimes holds, sometimes crosses, and communicates clearly with the server, they have to keep solving a fresh problem.
Frequently Asked Questions
What hand signals should a doubles team use?
Thereโs no universal code. Choose simple signs for serve location and the net playerโs planโsuch as stay, poach, or fakeโand agree on exactly what each one means. Keep the code small enough to remember under pressure.
Should the server always follow the net playerโs signal?
No. The signal is a proposal for a coordinated play. The server should agree to it only if the target and movement feel comfortable. If not, discuss a change before starting the point.
When should we talk between points?
Use the time to share one useful observation and decide on the next adjustment. Keep it brief, constructive, and within your competitionโs rules and pace-of-play expectations.
How do we stop leaving the alley open when we poach?
Agree before the serve on who shifts into the space the net player leaves. Then practice the move together: the poacher crosses, the server adjusts, and both players prepare for the next shot.
Final Thoughts
Good doubles communication isnโt a secret code or a nonstop stream of instructions. Itโs a clear plan your partner can trust: a serve target, a net-player decision, and a quick adjustment when the opponents show you something new. Keep the signals simple, talk with purpose between points, and back each other up when the plan doesnโt go perfectly. Once you do, those little gestures behind the back start carrying a lot more weightโand a lot more confidence.
