Team Challenge Generator

Almost every team game breaks in the same two places: somebody has to remember the score, and somebody has to remember which challenges have already been used. Both fail about four rounds in, and the argument that follows is longer than the game. This does both — teams drawn so the sizes differ by at most one, a challenge pool that cannot repeat until it is exhausted, and a scoreboard that is added up from the rounds themselves, so it can never disagree with what actually happened.

Everybody playing

One name per line. Names stay in your browser and are never uploaded.

Challenges to draw from

One per line. Edit these freely — the game draws without repeating.

How many teams

Sizes come out within one player of each other.

Rounds to play

The game stops here so somebody has actually won.

Set the game up, then press start.

What this generator does

Runs a team game rather than suggesting one. The random team generator here splits a list and stops; the party game session generator deals prompts in rounds without teams or a score. This holds all of it at once: who is on which team, which challenges have been used, what each team has scored, and how many rounds are left. The score is recomputed from the round record every time it is shown, which is the design decision that makes a running total impossible to get out of step.

How to use this tool

Type everybody's name, one per line, and choose how many teams.
Edit the challenge list if you want your own — one per line.
Press start to draw the teams, then next challenge for each round.
Tap the points buttons to score. Undo steps back if you get it wrong.

Understanding the controls

Everybody playing: One name per line. Names are dealt round-robin into the teams rather than sliced into chunks — with seven people and three teams that gives 3/2/2, where slicing would give 3/3/1.
How many teams: Two to twelve. Sizes always come out within one player of each other, and every name lands on exactly one team.
Challenges to draw from: The starting list is editable and replaceable. Challenges are drawn without replacement, so one cannot come round again until every other has been used; when the pool empties it reshuffles and carries on.
Rounds to play: The game stops here so somebody has actually won. Without an end point a party game just tails off.
The points buttons: +1, +2, +3 and −1, applied to the round just dealt. Pressing twice adds twice rather than replacing, so a team can be awarded points for two things in the same round. −1 exists because forfeits are a real scoring rule.

Worked examples

7 players, 3 teams: Teams of 3, 2 and 2 — the remainder is spread, not dumped on one team.
12 challenges, 10 rounds: Ten different challenges. Nothing repeats, because the pool shrinks as it is used.
Scoring a round twice: +2 then +1 on the same team gives that team 3 for the round, not 1.
Pressing undo: Steps back exactly one action — a score, a round, or an elimination.

Common use cases

A works Christmas party where nobody wants to run a quiz
A birthday party for a mixed group who do not all know each other
A youth group or club night that needs structure without equipment
A family gathering where the teams should not be the obvious ones
Any evening where the score is going to be argued about

How this generator works

Starting the game shuffles the challenge pool once and deals the players into teams round-robin from a shuffled order. Each round takes the next challenge off the front of the pool, which is what guarantees no repeats. Points are recorded against the round they were awarded in, and the scoreboard is derived by adding those rounds up whenever it is displayed — it is never stored separately, so there is nothing that can drift. Every action returns a fresh copy of the game rather than editing one, which is why undo is simply restoring the previous value.

Randomness and fairness

Randomness decides two things: the order of the challenge pool and which team each person lands on. Everything after that is yours — the score, the rounds and the pace. There is no seeded mode here, because reproducing a party game's team draw is not something anybody wants.

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

Assumptions this tool makes

Everybody listed is present and playing, and one device is shared by the group.

Limitations and good to know

It keeps the score; it does not judge the challenges. Somebody still has to decide who won a round.
Everything is visible on one screen, so it suits a group gathered round a phone, laptop or TV rather than players in different rooms.
Nothing is saved between visits — closing the page ends the game.
Undo steps back through this session only, and there is no redo.

Common mistakes

Adding fewer challenges than rounds: The pool reshuffles and repeats once it is exhausted, which is fine but noticeable. Give it at least as many challenges as rounds if repeats would spoil it.
Scoring before dealing the round: The points buttons only work once a challenge has been dealt, because points are recorded against a round.
Re-drawing the teams because one looks stronger: Sizes are always balanced; strength is not, and cannot be. If ability matters, set the teams yourself and use this for the scoring.

Practical tips

Agree what a round is worth before the first one, not during the third.
Paste in your own challenge list — the built-in one is a starting point, and challenges written for your group are always better.
Copy the round record at the end; it makes a surprisingly good summary of the evening.

Privacy and your data

The names you type, your challenge list and the score stay in your browser. Nothing is uploaded, nothing is saved between visits, and none of it is written into the page address. Analytics records that the tool ran and how many people were playing — never a name, never a challenge, never a score.

Frequently asked questions

How is this different from the party game session generator?: That one deals prompts in rounds and remembers what it has used. This adds teams and a score — the two things a competitive party game needs and that page deliberately does not have.
Can teams have different numbers of players?: They will differ by at most one, and only when the numbers do not divide evenly. Eleven people in three teams is 4/4/3; there is no way to do better than that.
Can I use my own challenges?: Yes — replace the whole list. That is the intended use. The tool holds no content of its own, so anything you paste in is what the game plays with.
Does the score survive if I refresh the page?: No. Nothing is stored, which is the same reason nothing you type can leak. Copy the record before you close the tab if you want to keep it.