Rotating Judge Generator

What this generator does

Produces a schedule saying who holds each job in each round, built so that nobody takes a job twice before everybody has taken it once, and so nobody ever holds two jobs at the same time. That is a guarantee about the whole schedule rather than a property of any one round, which is exactly why drawing at random cannot provide it — a draw has no memory of who has already done the job.

How to use this tool

1. Add the players, one per line.
2. Add the jobs your game needs — judge, reader, scorer, timekeeper.
3. Set how many rounds you are playing.
4. Generate, and read off who is doing what each round.

Understanding the controls

Players

One per line. You need at least as many players as jobs, since nobody can hold two at once — the tool will not produce a schedule that pretends otherwise.

Jobs

Whatever your game needs. Judge alone is the common case; quiz nights often want a reader and a scorer as well. Each job rotates independently, so a player can judge in one round and score three rounds later.

Rounds

How many rounds you are playing. Setting more rounds than players means the cycle repeats, which is fine and expected — the guarantee is that each full cycle is even.

Worked examples

One job, four players

Rounds 1 to 4: each player judges exactly once. Round 5 starts the cycle again.

Three jobs, five players

Each round has a different judge, reader and scorer, and no player holds two at once.

Over a full cycle

With four players and eight rounds, everybody judges exactly twice — not three times for one and none for another.

Why a draw fails

Four players, four rounds, drawn independently: somebody is left out about 68% of the time.

Common use cases

• Judged party games, where somebody has to pick a winner each round
• Quiz nights where the question-reader rotates so everybody gets to play
• Family game nights, where fairness about the boring jobs is a live issue
• Classroom games with a scorer, timekeeper and reader
• Any long session where one person otherwise ends up running the whole thing

How this generator works

The player list is shuffled once and then offset by one each round, which is the same construction the site's station-rotation tools use. Offsetting rather than redrawing is what produces the guarantee: after n rounds with n players, every player has held every job exactly once, and nobody can hold two jobs in the same round because the offsets are distinct. The initial shuffle is what stops the same person always going first.

Randomness and fairness

Only the starting order is random — the browser's cryptographic random number generator shuffles the player list once, and every round after that is a deterministic offset from it. That is the whole design: the fairness guarantee comes from the rotation rather than from the randomness, and a tool that redrew each round could not make the same promise. A seed reproduces a schedule using a deterministic generator that is not cryptographically secure.

For how randomness is produced across the whole site, see how Generate Random works.

Assumptions this tool makes

• Nobody can hold two jobs in the same round.
• Every player is available for every round.

Limitations and good to know

• It cannot know that one player would rather always judge, or never. Swap by hand where somebody has a preference — the schedule is a starting point, not an instruction.
• There is no notion of a job being harder than another, so a player who draws scorer and timekeeper in adjacent rounds simply has a busier evening.
• It does not run the game, keep score or time anything. It says who is doing what.
• With fewer players than jobs no valid schedule exists, and the tool says so rather than doubling somebody up.
• Late arrivals and early departures are not handled. Regenerate with the new list, which takes ten seconds.

Common mistakes

Drawing a judge at random each round instead

It feels fair and is not. With four players over four rounds, a random draw leaves somebody out about two-thirds of the time, and that person notices.

Regenerating mid-game because somebody complained

Regenerating restarts the cycle and undoes the fairness. Follow the schedule to the end of a cycle — that is the point at which it is even.

Adding more jobs than the game needs

Every job you add takes a player out of the round. In a group of five, three jobs means only two people are actually playing.

Practical tips

• Print the schedule or leave it on a screen everybody can see. A rotation nobody can check is a rotation somebody will dispute.
• Put the least popular job first in your list. It rotates the same way, but seeing it at the top makes clear it is being shared rather than dumped.
• For a long evening, generate one cycle rather than twenty rounds. Regenerating between cycles reshuffles the starting order, which keeps it from being predictable.

Troubleshooting

The same person is judging twice in a row

That should not happen within a cycle. It can look that way across a cycle boundary — the last round of one cycle and the first of the next — which is a real limit of a repeating rotation rather than a fault.

I have more jobs than players

No valid schedule exists, because somebody would have to hold two jobs at once. Combine jobs or add a player.

Privacy and your data

Player names stay in this browser. Nothing is uploaded, nothing goes into the page address, and the site has no endpoint that could receive them. Analytics records only that the tool was used along with the number of players and jobs — never a name.

Frequently asked questions

Why not just draw a judge each round?

Because a draw has no memory. Over four rounds with four players, an independent draw leaves at least one person out roughly two-thirds of the time and gives somebody the job twice. A rotation guarantees each player gets it exactly once per cycle, which is what people mean by taking turns.

How is this different from the judging allocation generator?

That one solves a constrained problem: assigning competition entries to a panel of judges with capacities and conflicts of interest. This rotates jobs among the people playing a game, round by round, and its guarantee is about turn-taking rather than constraint satisfaction. Different problems that happen to share a word.

What if somebody arrives late?

Regenerate with the new list. It restarts the cycle, which is slightly unfair to whoever has already judged, and it is still better than the alternatives — most groups simply slot the newcomer into the next free slot by hand.

Can one person do two jobs?

Not in the same round, by design — the schedule would not be a schedule. If your group is small enough that it has to happen, combine the two jobs into one entry in the list and rotate that.