Random Team Generator

Use pure random grouping when every participant should be treated equally; switch to Balanced Team Generator only when you deliberately provide ratings and accept a heuristic result.

Saved list / roster

Save current list as

Names / items — one per line

After generating, use the lock checkbox to keep a member in that team on the next reshuffle, or use the team menu beside a member to move them manually.

ReadyBalanced sizes differ by at most one member.

8People

2Teams

0Locked

Seating chart Student picker Classroom screen

Randomness & draw-integrity audit

Inspect the current pool, probability model, duplicate/replacement rules and result constraints with a separate browser-local verification layer. It does not choose or alter the primary result.

Set the random workflow above, then refresh this audit.

Audit ready. Browser-local capability evidence only.

Core random, wheel & group workflows

Use the broad picker, number, wheel, name, team or dice workflow first. Move to a specialist only when the probability model or output structure genuinely changes.

All 35 random tools

Random Number GeneratorSecure integer draws & unique mode Random PickerPick names or items from a list Spin the WheelVisual choice wheel & winner history Random Name GeneratorGenerate names in local batches Random Team GeneratorSplit a roster into teams Dice RollerCustom dice count & sides Yes or No WheelBinary decision with visible odds Weighted WheelCustom non-negative probability weights

Fairness and randomness boundaries

Random selection can make equal-probability choices from the entered pool, but it cannot prove that the input list itself is appropriate or unbiased. Visual wheel/dice animations are presentation only. Seeded tools remain reproducible pseudo-random workflows rather than cryptographic randomness, and rating-balanced teams use a transparent heuristic rather than an optimal or human-judgment model.

How to use the Random Team Generator

Choose either a target number of teams or members per team. After generation, lock people who should stay in place, move members manually, and reshuffle only the unlocked members.

Why use it

Use pure random grouping when every participant should be treated equally; switch to Balanced Team Generator only when you deliberately provide ratings and accept a heuristic result.

Randomness, privacy, and limits

Random balancing starts with sizes differing by at most one. Manual moves can intentionally make teams uneven; the result panel reports when that happens.

Pure random teams vs rating-aware teams

This tool treats every entered row equally and balances team sizes to within one member. It does not infer skill; use the separate Balanced Team Generator only when you deliberately provide ratings.

Practical guide and verification

Use the tool first, then apply these checks to verify inputs, interpret the result, and hand it off without displacing the primary workflow.

Use randomness for assignment, not as proof of equal skill

Random assignment can remove organizer choice and keep team sizes even, but it does not guarantee equal ability, experience, leadership, or role coverage. If those factors matter, decide whether the activity truly needs pure random teams or a separate balancing method. Keep that distinction explicit so a fair draw is not presented as a performance-balanced roster.

Freeze any constraints before generating

If certain participants must stay together, remain apart, or fill specific roles, decide those rules before the draw rather than editing an inconvenient result afterward. Post-hoc swaps can reintroduce organizer bias. For a classroom or event, write down the constraint, run the random split, and keep a copy of the final assignment so the process is explainable.

Reuse rosters without exposing personal data

Saved lists are convenient for recurring classes, teams, and workshops, but names can still be personal information. Prefer initials or non-sensitive labels when a full name is unnecessary, avoid placing confidential notes in the roster, and clear saved browser data on shared devices. Local storage improves privacy only if the device and browser profile are controlled.

Audit size balance after every reshuffle

When the participant count does not divide evenly, the expected result is that team sizes differ by at most one. After reshuffling, confirm every name appears exactly once, no one is missing, and the size spread matches the selected split mode. Copy or print the assignment only after those simple integrity checks pass.