Volleyball scouting sheet: writing a rally on a single line
A tally sheet tells you how many points number 9 scored. What it does not tell you is what happened in those rallies: did the points come off a perfect pass or off scramble balls, and did they fall on the first swing or only on the third? There is one fix for that, and it fits on a single line per rally.
Tallying adds up, coding keeps the order
A tally sheet answers one kind of question: how many. How many kills number 9 got, how many errors sat behind number 4. That is useful, and for most teams it is enough. But there is a question a tally sheet cannot answer in principle: what happened in that rally? The moment you put down a tally mark, the order is gone. Eight marks next to number 9 say nothing about where those balls came from.
Coding does something else. You write one line per rally, left to right, in the order the ball went: who touched it, what they did, how good it was. At the end of the set you have no column of tally marks but a stack of lines, each one readable back as a small story.
That difference sounds academic until you want to know something you had not thought of in advance. For instance: after a bad pass, does the ball always end up with the same player? On a tally sheet there is no way to find out. In a stack of coded lines you look up the lines that start with a poor reception and see which number comes next. Same sheet, same afternoon, an answer to a question you only asked afterwards.
This is what scouting means: coding every action live instead of adding things up. Professionals do it on a laptop with software that turns it into percentages on the spot. The handwritten version below gives you less, but it costs nothing.
The block: number, action, rating
Every touch by your own team becomes one block of three positions, written together:
- The shirt number — who touched the ball.
- One letter for the action — what they did with it.
- One symbol for the rating — how good it was.
For the actions you need five letters, six at most: S for serve, R for reception, E for the set, A for attack, B for block and D for dig. Those are the letters the international scouting software uses too, and E for the set only looks odd until you remember that S was already taken by the serve. Write the list once at the top of the sheet. That feels pointless until somebody else has to read your sheet.
For the ratings, take over the symbols set out in volleyball stats on paper; that scale is not explained again here. Reception is the exception: it gets a number from 0 to 3, and what each number means is in tracking reception quality. Take both scales exactly as they are and invent nothing extra.
So 9A# becomes number 9 puts it away and 4R1 becomes number 4 barely gets the serve up. Three characters, and still readable a month later.
One convention is what makes the line genuinely usable: put a vertical stroke every time the ball crosses the net. You do not write down the opponent's actions, but that stroke keeps the timeline intact. It shows you how often the ball went back and forth and on which swing the rally ended.
The margin: where the line belongs
A line on its own without context is an anecdote. Three things in the left-hand margin make it findable again.
- Who is serving. One letter on the far left: W if we are serving, T if they are. Pick letters that clash with nothing else on your sheet — E is already doing duty for the set here. Without that mark you cannot tell afterwards whether a rally you won was a side-out or an extension of your own serving run.
- The rotation. Write down the number of your own player in position 1, the right-back spot the serve goes from. That single number pins down your whole line-up, because the rest stands around it in fixed order. As long as the rotation does not change you do not have to write it again: an arrow pointing down will do.
- Set changes and the score. Draw a line right across the sheet at every new set. Alongside it, put the score in the margin every five rallies — not admin but a checkpoint: miss a rally and you notice within five lines instead of after a whole set.
Substitutions go down the moment they happen, as an arrow from the old number to the new one — otherwise you will be crediting twenty lines of actions to somebody sitting on the bench.
Four rallies, written out
Four lines from the same set, with what they say in plain language underneath.
T · rot 5 · 4R2 1E 9A#
They serve, with our number 5 in the right-back corner. Number 4 takes the serve and delivers a usable pass, not a perfect one. The setter can still do something with it, sets outside, and 9 puts it away. Side-out in three touches, exactly what the system is for.
T · rot 5 · 11R1 1E 7A/
Same rotation, a few rallies later. This time the serve goes at 11, who only just gets to it: a scramble pass. The setter has to set on the run and can only reach the middle, where 7 hits it straight into the block. This was a side-out that fell apart on the third ball — and the cause sits two characters earlier, at that 1. On a tally sheet all that would have appeared here is an error behind number 7, and you would have spent the drive home thinking about 7's attacking instead of about the reception.
W · rot 9 · 9S+ | 5B- 6D+ 1E 4A- | 11D+ 1E 9A#
We serve, with number 9 in the right-back corner. He puts the opponent out of system, so their attack does not come in full. Our middle gets hands on it but does not hold it, 6 digs it up, 1 sets and 4 hits — but it comes back. Out of the counter-attack 11 digs well, the setter gets a second chance and 9 finishes it after all. On a tally sheet this is one mark next to 9; here you can see the point came not from the serve but from two digs.
W · rot 9 · 9S/
Service error. One block, done. A line like that feels too short to be worth writing, and that is exactly why it has to go in: five of these in the same rotation is not bad luck but a pattern — and you only see it if the miss is on the sheet just as reliably as the point.
In short: never write down a symbol you are not sure of. If you did not see who touched the ball, put a question mark and move on. A gap you can skip; an invented shirt number ruins the count without you noticing.
What a stack of lines tells you
It only gets interesting afterwards, and you need no calculator for it.
- Side-out per rotation. Take every line starting with T, sort them by rotation number and count, per rotation, how many of those rallies ended with a point for us. That is your side-out, the figure explained in what side-out means in volleyball. The rotation where it sags is usually also the rotation where the set turns.
- Where rallies end. Count the vertical strokes per line. A team that finishes almost everything on the first attack is playing a completely different game from a team that wins most of its points after a dig. That decides whether your practice time goes into attacking off a good pass or into the second and third ball.
- Which ball goes up after a bad pass. Find the lines starting with a 0 or a 1 behind the R and see which number comes after the E. It is often the same player every time, and often that player is also the one with the lowest efficiency. In that case you do not have an attacking problem but a distribution problem, and the conversation continues in playing out of system.
One warning about numbers. A set gives you roughly fifty lines spread over six rotations: about eight per rotation. You cannot build a single conclusion on eight rallies. Collect three or four matches before you change your line-up; until then every outlier is just as likely to be chance.
If you cannot do this alongside coaching
Coding takes both hands and your full attention. If you cannot do it while coaching, give it away: how to set up the sheet and the system around it is in volleyball stats on paper, and who to ask is in delegating live scoring.
There is a middle road that saves you the retyping afterwards. In Koach you tap, per rally, who scored the point and how — attack, block or serve — and on a point against, what went wrong: service error, attack error, poor pass, too late or a net touch. When the opponent serves, a reception card appears with the numbers 0 to 3, and after a tap the app asks who took the ball. Afterwards the side-out per rotation is already worked out for you, with the rally-by-rally run alongside it.
But be honest about what that is: an app like that records the decisive action of each rally plus the reception, not the whole sequence. Anyone who wants to see back which set sat between that pass and that attack still needs paper. The two do not fight each other either: let somebody keep the score and the receptions in the app while you code half a set per match on paper, aimed at one question.
Starting without ruining your first match
Four rules keep the first attempt upright.
- Start with three letters. Only R, E and A: reception, set, attack. That covers the side-out, and for most teams that is half the match. Add the rest only once those three reach the paper without you thinking about it.
- Practise on a recording. Put on a match you can pause and rewind, and code one set. That is when you discover which symbols you keep forgetting — rather than during a match that counts.
- Do one set, not a whole match. One full set coded is worth more than three sets that fell apart halfway. And choose which set: the first, while you are still fresh, or the one where things usually go wrong for you.
- Read it back the same evening. Go down the lines while you can still picture the match and write three sentences in plain language at the bottom. A sheet you rediscover months later is a sheet whose symbols you no longer trust.
To begin with, code only your own team; at least you can do something with what you find there at practice. Watching the opposition is a different craft with different priorities — those are in scouting the opponent.
Frequently asked questions
What is the difference between a scouting sheet and the official scoresheet?
The official scoresheet is the formal record of the match: score, line-ups, substitutions and signatures, filled in by an appointed scorer. A scouting sheet is yours and has no official status whatsoever; it exists purely so you can see afterwards how the rallies unfolded. They are separate documents and they are filled in by different people.
What do you do with a rally where you miss a ball?
Put a question mark where the block should go and carry on with the next touch. Never guess: an invented shirt number or rating disappears among the good lines and then ruins every count you run on them. Lines with a question mark in them you simply skip when counting.
Can two people code together?
Yes, and it is easier than doing it alone. One person reads out loud what happens — number, action, rating — and the other writes. Do agree that the reader has the final say and that there is no discussion during the rally, or you will end up with two half versions after a long one.
How many matches do you need before you can get anything out of it?
For an impression, one set is already enough, for instance to see where rallies end. For decisions about your line-up or your rotations you need three to four matches, because a single set gives you only a handful of rallies per rotation. In those first weeks, then, look mainly at patterns you recognise with your own eyes rather than at the numbers alone.
