Rugby athlete monitoring: reading a pack without a GPS vest
I played rugby for a living for more than a decade, most of it with my head in rucks. Here is what almost nobody monitoring a rugby squad gets right: the load that breaks players down is not the load you can see them running. It is the collisions, the week-on-week ramp, and the forward who will never once tell you he is sore. You can track all three without a single GPS vest.
Rugby load is collision load
Most monitoring borrowed from running sports counts distance and top speed. Useful, but it misses the thing that makes rugby rugby: contact. Two players can cover identical distance in a session and finish in completely different states, because one spent eighty minutes hitting rucks and the other stood at fullback. Measure only movement and you are blind to half the load that actually costs you players.
You do not need accelerometers to catch it. Session-RPE — how hard it felt, times the minutes — quietly folds collision cost into one number, because a heavy contact day feels harder. Logged every session, it is a truer load signal than distance alone.
The ramp is the danger, not the total
The most dangerous week of a season is rarely the hardest one. It is the one that jumps. A squad rolling out of a holiday straight into a derby build-up — low base to high week in seven days — is where soft-tissue injuries cluster. Watch the week-on-week change against each player's own recent average, not the raw number. A player who trained hard all term can absorb a big week. The one who did nothing for three weeks cannot.
The forward who says nothing
Every honest forward will admit this: you learn not to mention things. A tight five that flags every stiff neck gets a reputation, so it stays quiet until something actually tears. That culture is real, and it is the enemy of monitoring. A sixty-second daily check-in, read privately by one coach, gets around it — not because the player suddenly volunteers the truth, but because a slow slide in his numbers shows up even when his mouth stays shut.
What to actually watch
- Session-RPE every session — it captures the collision load that distance misses.
- Week-on-week load change per player, against their own average — the ramp, not the total.
- Daily readiness, read privately — so the forward who will not speak up still shows up in the data.
- Body-map soreness over time — a niggle logged three days running is a conversation, whatever he says out loud.
The point
None of this predicts the hamstring or the stinger. What it does is hand you the week's warning you would otherwise only get in hindsight — the ramp that was too steep, the prop whose readiness has quietly slid for a fortnight. I spent a career being the data nobody was collecting. The coaches who could have caught it early were not short of expertise. They were short of the daily picture.
botthms.Ready gives a rugby coach that daily picture — collision-aware load and readiness, every player, no GPS required.
See how it works