Building Netball Trial Rotations That Are Actually Fair

What "fair" really means in a rotation

When parents complain about trials, they almost never say "the rotations were biased." But they do say things like:

• "She only got to play her position once."
• "She was always on court when the strongest players were off."
• "The same selector watched her every game."

All three of those are rotation design problems. A fair rotation isn't just about court time — it's about giving every player a fair opportunity to be assessed.

The four properties of a fair rotation

A well-designed trial rotation should hit four targets:

1. Equal court time — every player gets the same total minutes (within a few minutes), so nobody is over- or under-assessed
2. Position coverage — every player gets meaningful time in their preferred position, plus at least one secondary
3. Selector coverage — every player is observed by every selector at least twice
4. Comparison balance — no player is consistently grouped with the same teammates or opponents

Hitting all four manually for 40+ players is hard. It is doable, but it usually takes someone several hours and a lot of patience with a spreadsheet.

How most clubs build rotations (and why it goes wrong)

The most common approach is: divide players into pools based on preferred position, then assign games. This works for simple trials but fails as soon as you have:

• Players who can play multiple positions
• Players who arrive late or leave early
• Position imbalances (e.g. nine GAs but only four WDs)
• Multiple courts running in parallel

Most clubs end up either accepting unfair coverage or burning hours rebuilding rotations on the morning of the trial.

A simpler approach: rotation generation tools

Tools like GameStats trials generate rotations automatically from your registered player list. You input the constraints — number of courts, game length, total games per player, minimum games in preferred position — and it produces a rotation that hits all four fairness properties.

The benefit isn't just time saved. It's that the rotation is genuinely better than what most clubs build by hand, because the algorithm doesn't get tired or take shortcuts.

Designing the structure

Before generating rotations, decide on the structural parameters:

• Game length: 8 minutes is standard for trials. Long enough to assess; short enough to fit several rotations.
• Games per player: aim for 4–6. Below 4 is too small a sample; above 6 burns players out.
• Courts in parallel: the more courts, the more selectors you need, but the more efficient the day.
• Rest gaps: every player should get at least one game off between games on. Players assessed while exhausted look worse than they are.

Honouring position preferences

The biggest single fairness improvement you can make is collecting position preferences in advance and building rotations around them. A player who only ever plays GS at her club but gets assessed at WA on trial day will rightly feel the process was unfair to her.

Aim for:

• At least 2 games in preferred position for every player
• At least 1 game in declared secondary position
• No more than 1 game in a position the player did not nominate (and ideally zero)

If your numbers don't allow this — for example, you have nine GAs and only four WDs — that's a recruitment problem to solve before trial day, not a rotation problem to solve on it.

Selector rotations matter too

Often-overlooked: the selectors should rotate around courts, not stay fixed on one. Otherwise selector A always rates court 1 and selector B always rates court 2, and you lose the multi-selector signal that makes the process defensible.

Rotate selectors every 2–3 games so every player ends up rated by every selector at least twice. This is harder to manage manually than it sounds; software handles it without thinking about it.

What to do when things go wrong on the day

Even a perfect rotation breaks the moment a player arrives late, gets injured, or has to leave early. Have a plan:

• Designate one person — not a selector — to handle rotation changes on the fly
• Keep substitution slots in the rotation for late arrivals
• If a player misses games, note it explicitly so the selection meeting can flag them as having limited data

GameStats trials handles late arrivals by recalculating the remainder of the rotation in real time, but even with paper systems, having a dedicated rotation manager prevents the chaos that otherwise spreads across the day.

The bottom line

Rotation design is invisible when it works and catastrophic when it doesn't. The targets are: equal time, real position coverage, multi-selector exposure, and balanced comparisons. Hit those four and your trial day will run smoother and your selection meeting will be defensible.

If you'd rather not spend Saturday night with a spreadsheet, GameStats trials is built for exactly this — and the resulting team data flows straight into the stats platform for the season.