Start with a checked list
Paste one person per line. Identical names are separate entries, so use initials or identifiers to tell people apart. Remove anyone who is not taking part.
Choose the right group setting
Select the number of teams when you have a fixed number of stations. Select people per team when group size matters more. The generator calculates a team count and distributes people as evenly as possible.
Generate and review
The generator shuffles the list with a Fisher–Yates shuffle, then distributes people across the teams. It balances the number of members, not skills, accessibility needs, or social dynamics.
Copy the teams
Copy the result to your clipboard for your own meeting notes. Regenerate if needed, but explain any changes transparently to participants.
Worked example: fourteen participants
With fourteen names and four requested teams, two groups contain four people and two contain three. The size difference is one. Choosing People per team with a target of four calculates four teams and gives the same size pattern. Membership changes when you generate again, but the counts remain balanced. Team size mode therefore acts as a maximum target followed by balancing; it does not create three full groups and an isolated two-person remainder.
Check duplicate names and missing participants
If Alex appears twice, the generator treats the two lines as separate participants and can place both in teams. That is useful only if they represent two different people. Use initials or another suitable identifier and count the entries against your attendance list. A person missing from the input cannot appear in the result. The algorithm's even distribution cannot correct an inaccurate roster.
Plan for constraints before the draw
Random teams are appropriate when many groupings are acceptable. They do not automatically enforce fixed partners, prohibited pairings, ability levels, or access needs. If an activity requires these constraints, plan them separately and explain any manual changes to the group. Avoid regenerating repeatedly until a hidden preferred arrangement appears; choose a clear rule for when a redraw is justified.
Keep a usable copy of the final teams
Review the generated teams and use Copy teams to transfer the result to your own notes. Check the pasted text before distributing it. A local wheel save retains the input list and wheel settings, but it is not a saved archive of that specific team arrangement. Generate once more if attendance changes, and copy the updated groups. If you only need one person rather than a complete allocation, use Random Name Picker instead.