ReadySetPick creates size-balanced teams: it securely shuffles the participant list, then deals names across the requested number of groups one at a time. Team sizes differ by no more than one person.
Size balance and skill balance are different
A random generator can make groups of nearly equal size without knowing anything about experience, role, availability, language, or accessibility. That is often exactly what you want for casual games and short activities. It is not the same as constructing teams with equal skill.
Say “random teams with balanced sizes,” not “perfectly balanced teams,” unless you separately evaluated the factors that matter for the activity.
Choose the team count before generating
Start with the activity's practical needs: space, equipment, time, and the number of people who can participate meaningfully at once. Then check the expected sizes.
| Participants | Teams | Resulting sizes | Useful for |
|---|---|---|---|
| 8 | 2 | 4 and 4 | Debates or two-sided games |
| 10 | 3 | 4, 3, and 3 | Stations or project groups |
| 17 | 4 | 5, 4, 4, and 4 | Workshop tables |
| 23 | 6 | 4, 4, 4, 4, 4, and 3 | Short small-group tasks |
If the larger teams would receive a meaningful advantage, adjust the activity rather than repeatedly regenerating until you like the names. For example, rotate the extra participant, give smaller teams an extra resource, or choose a team count that divides the roster more evenly.
A fair workflow for ordinary groups
- Confirm the roster. Remove absent participants and add late arrivals before generating.
- Choose the number of teams. Base it on the task, not on preferred social groupings.
- Explain the rule. Tell participants that names will be shuffled and dealt into size-balanced groups.
- Generate once. Avoid reshuffling just because the first result is socially inconvenient.
- Make only necessary adjustments. State the reason openly when safety, access, supervision, or role coverage requires a swap.
When constraints genuinely matter
Some activities need one trained facilitator per team, must separate people with a conflict, or must keep a support person with a participant. A purely random list cannot know these constraints. Handle them before or after the draw using a written rule that applies consistently.
- Anchored roles: place one qualified leader in each team, then randomly distribute everyone else.
- Paired participants: treat an inseparable pair as one unit only if the group-size effect is acceptable.
- Separation requirement: generate teams, make the minimum transparent swap, and record why.
- Skill bands: shuffle within each band and distribute one band at a time when actual skill balance is required.
A worked example with 17 participants
A workshop has 17 participants, four tables, and one trained facilitator for each table. Generating all 17 names at once would balance sizes but could place two facilitators together. Instead, assign one facilitator to each team first. Randomize the remaining 13 participants, then distribute them in order across the four anchored teams. The final sizes will be 5, 4, 4, and 4 while every team retains the required role.
If two participants must remain together for interpretation or support, explain that constraint before the draw. Place the pair as one anchored unit, then check whether the size difference remains workable. Transparency matters more than pretending the final arrangement was purely random.
Handling late arrivals and withdrawals
When someone arrives before the activity begins, add them and regenerate with the group's knowledge. After work has started, moving everyone may waste more time than it saves. Place the late arrival into a smallest team using a stated rule. If someone leaves, continue unless the resulting size difference prevents the activity; then make the minimum necessary move.
Avoid hidden rerolls
Repeatedly selecting “Generate teams” until a preferred arrangement appears turns a random process into an undisclosed choice by the organizer. If rerolls are part of the activity, announce the rule first—for example, “we will generate three options and vote” or “we reroll only if a required role is missing.”
Privacy on shared screens
Use first names, initials, nicknames, or participant numbers. Do not paste email addresses, employee numbers, medical information, grades, or private performance labels into a projected tool. Lists are processed locally in the browser, but anyone who can see the screen can see the labels.
When another tool fits better
Use the pair generator for partners or person-to-task assignments. Use the seating chart maker when positions matter. Use the bracket generator when groups should advance through a single-elimination competition.