Setter hand signals: volleyball attack codes explained

Your setter glances over his shoulder just before the serve, puts up a finger, and nobody reacts. Two rallies later your middle is hanging in the air for a ball that never came. A signal system that half works is worse than no signal system at all: it makes your attack slower instead of faster, because players start waiting for information that never arrives. This is the build-up that does run after three sessions.

A signal is not a call

Two things get thrown onto one pile almost every time. A call is out loud and happens during the rally: your hitter calls for the ball while the pass is still in the air, so the setter knows who is available without looking. A signal is silent and happens before the rally: the setter uses his hand to tell a hitter which set he gets if the pass lands well. The first costs nothing and always works; the second costs agreements and discipline and only works off serve receive. Most teams badly need the first and think they need the second.

What a signal buys you is exactly one thing, and that is enough: the hitter knows which set is coming before the serve, so he starts his approach on the pass instead of on the set. On a quick middle attack that is the difference between existing and not existing: a hitter who only leaves once the ball has left the setter's hands is late by definition. Which tempos exist and what each one asks of your pass is in attack tempos from high ball to first tempo.

One more boundary: this article is about the signals you give on purpose. How a blocker reads a setter's unintended signals — shoulder line, hands, distance to the net — is in reading the setter. Same coin, other side.

Does it pay off at your level? Three conditions

Before you introduce a system that will occupy your team for months: signals only start paying off once three conditions are met.

1. Your pass reaches the setter zone in roughly half your rallies. Any lower and the signal usually gets cancelled anyway (see further down), so you are training something you rarely play.
2. You have one fixed setter. Someone who takes the second ball every rally and therefore uses the codes daily. If that role rotates, you double the number of people who have to know it flawlessly.
3. You have at least one hitter who can handle a fast set. Without a difference in tempo there is nothing to encode: every signal is then a roundabout way of saying "high ball outside".

If one of them is missing, calling gives you more than signalling. Calling costs no preparation, works during the rally as well and forces your hitter to commit. In recreational and youth teams that is nearly always the right answer: start with calling, and only add signals once the opponent is good enough to react to that calling. That is precisely when signals gain their value. What else is expected of your setter is in the setter's role.

The moment, the order and the nod

A signal has only one usable window: the five to eight seconds between the end of the previous rally and the whistle for the serve. The order inside it is fixed: everyone walks to their spot in the reception formation first, then the setter gives his signals, then the referee whistles. Turn it around and give signals while your team is still walking, and you are giving them to people who are looking at their feet.

Three agreements make that window workable:

• Hand low. At hip height or lower, against your thigh or just behind your back, with your side or your back to the net. A hand at chest height while you face the net square on is not a signal but an announcement to the opponent.
• One hitter at a time, in a fixed order. Middle first, then the outside hitter, then the hitter on the right. That way nobody has to guess whether the signal was for him, and you notice immediately if you skipped someone.
• Always a confirmation. The hitter only looks once he is standing in his spot, and confirms with a short nod or a tap on his thigh. No confirmation means no signal — that rule saves you more rallies than the system itself.

One situation deserves extra attention, and it is also the first place where signals quietly get skipped. If your setter is in the front row — in a 5-1 system that is half your rotations — he has his back to his outside hitter on the left. Agree that he gives the signal before he moves across to the net, or that the hitter takes one step towards him.

Build up to four signals, and start with two

The classic mistake is introducing a complete system: eight codes, an A through D for the middle and a separate code for the back-row attack, all explained in one evening. Two weeks later the team is still setting high balls outside, only now with a guilty conscience. Build it up in stages, and hold each stage long enough that it starts running by itself.

1. Stage 1 — two signals. One raised index finger is "quick middle", a flat hand is "high outside". Nothing more. Those two are furthest apart in tempo, so confusion is nearly impossible, and together they cover the vast majority of your attacks off a good pass.
2. Stage 2 — the third signal. Pick one: the fast flat set outside, or the pipe through middle back. Not both at once, however tempting.
3. Stage 3 — the fourth signal. The back set to the hitter on the right, or a deliberately agreed setter attack.

The test before you add a signal has to be measurable, otherwise you are adding on feel. Use this one: three sessions in a row without a single misunderstanding, and two matches in which every signal given actually got an approach. "It's going pretty well" is not a test.

Stop at four, and there is arithmetic behind that. A team might play thirty attacks out of reception on a training evening. Split those over two codes and each code gets fifteen repetitions; split them over six codes and it is five — and five repetitions a week makes nothing automatic. Four signals that run blind beat eight signals you have to look up.

What a signal says — and what it never says

A signal contains one thing: which set, meaning the combination of place along the net and tempo. It never contains the direction the hitter should hit. That depends on the block, and the block is only there once the ball has been served — your hitter sees it from closer and later than you do. Prescribe the direction as well and you take away from him the one decision he can make better.

On top of that, choose gestures that clearly differ from five metres away in a poorly lit hall: one finger, a fist, a flat hand, a thumb. Two fingers next to three fingers is asking for trouble. And consider the reverse version, which often works better in small teams: let the hitters ask for their set and let the setter only nod or shake his head.

For the codes themselves there are roughly three families in circulation, and they convert into one another:

• Zone and tempo (the number system). The net is divided into nine zones of about a metre, numbered from the antenna. The first digit names the zone, the second the tempo: 1 for first tempo, 2 for the in-between tempo, 3 for the high ball. Precise, and some players already know it; the drawback is that everyone has to be able to see the net in zones. The numbering differs by country and by coaching course — check which version is common in your region before you adopt it.
• Letters for the middle attack. A, B, C, D for the distance between middle and setter: right in front of him, a bit further forward, directly behind him, far behind him. Short, and it names what actually matters to a middle: distance, not zone. Drawback: it says nothing about your outside hitters. Here too the meaning of the letters differs by country and by federation.
• Home-made words. "Quick", "high", "pipe", "back". No translation step needed: a new player gets it within one session and a stand-in can join in straight away. Drawback: it only works inside your own team.

For most club and recreational teams the third variant is the right choice, for one reason: every translation step costs time, and time is exactly what you are trying to win with signals. Only pick the number system if your players move on to teams where it is already running. Either way, write your codes down — gesture, set and hitter on one card behind your lineup sheet. What is written down nowhere no longer exists after the winter break.

Off reception it works, in the rally it doesn't

Signals work off serve receive because everything a signal needs is in place there: there is a pause, everyone is standing still in their own spot, and the setter has his hands free and his eyes needed nowhere else. Those are precisely the things missing in the rally. After a block or a dig nobody is standing still and the setter is watching the ball coming at him. A signal you try to give there arrives too late and costs you the very look you need most at that moment. So in the rally you call — which words those are and how to train them is in communication drills.

From that follows the most important agreement in your whole system, and your players have to be able to say it out loud: if the setter has to run, the signal is off. The moment the pass lands far enough from the setter zone that your setter has to take steps for it, the code no longer applies and the team falls back on the default set. Without that rule your middle keeps making his quick approach on a ball lying four metres off the net — and then he is standing exactly in the way of his outside hitter, who was about to take his approach there. What should happen instead is in playing out of system.

How to keep your code secret for one match

An opponent who reads your signals does it in two steps: he sees the gesture, and he links that gesture to what happens next. Both steps can be blocked, but not equally easily.

The first is a matter of posture: hand low, side or back to the net, and all the signals within two seconds in the same order. But the real leak is the second step, and it is not in your hand: if signal X is always followed by the same thing, nobody needs to crack your code. The opponent simply watches your hitters and draws his conclusion after a set and a half.

There are two answers to that. The first is free: give signals you don't run. A middle who makes his approach without ever getting the ball keeps the middle blocker in the centre and makes your high ball outside easier. The second is cheaper still: swap the meaning, not the gestures. One sentence in the time-out — from now on the fist is the pipe — and your entire code is secret again, without anyone having to learn a new gesture. Do that once a match at most, and only if your players know the first meaning blind.

Stay level-headed about it, though. At club level the chance that the opponent reads your signals is smaller than the chance that your own middle misreads them. If you do run into a block that consistently leaves earlier than it should, that is your cue to switch.

When it goes wrong: the hitter who didn't look

Three things go wrong, and for all three there is one agreement that solves it.

• The hitter didn't look. No second signal, no hissing, no shouting his name: you set the default ball. A setter who plays the quick anyway to a middle who confirmed nothing is setting the ball to nobody — more expensive than a predictable high ball. The rule in one sentence: without confirmation, the default set applies.
• The setter doesn't run his own signal. This is the costliest mistake, because it is invisible. A middle who has jumped for nothing three times stops making his approach the fourth time — and with that your threat is gone without anything visible having happened. The agreement: off a good pass you run the signal you gave, even if something better seems to be appearing in the meantime. You vary with the signal, not with the execution. How to build that timing is in timing drills for setter and hitter.
• Two hitters think they are getting the same set. That almost always happens because someone was skipped in the rush — the fixed order solves it.

Then measure it for a full match, with three columns on your sheet: given, run, point. A signal that led to zero attacks in two matches is not a signal but a ritual — scrap it and go back to three. Log your points per player and per point type in Koach and you also see whether that fast set really does produce more than the high one, instead of just feeling like it.

Twenty minutes per session, three weeks long

You don't have to clear a training evening for this. Twenty minutes, three sessions in a row, and after that once a month as a refresher.

1. Five minutes dry, no ball. Team in reception formation, setter gives his signals, hitters confirm. You point at someone: what did you get? Two rounds per rotation, and pay particular attention to the rotations where the setter is in the front row.
2. Ten minutes reception and attack, good serves only. One condition: a rally that starts without a signal doesn't count, not even if it produces a point. That makes skipping more expensive than thinking.
3. Five minutes with one bad serve in three. Now you are not training the signal but its cancellation — the ball the setter has to run for and everyone automatically falls back on the default set. This is the part teams skip and pay for most dearly in a match.

If you notice in week two that the third block delivers the most, that is right: your system is not as good as your best set, but as good as the rally where it goes wrong.

Frequently asked questions