How to assign participants to random teams of balanced size

Prepare one entry per person

Start with a final list containing one person per line. Assign participants rather than tasks or roles: someone doing two activities remains one person. Blank lines are ignored and spaces at the beginning and end of each name are removed. Review the list before choosing how many teams to create.

Identical names are rejected to avoid ambiguous assignments. If two people are named Ana, distinguish Ana A and Ana B or use identifiers such as P01 and P02. Different spellings do not guarantee different people: Ana and ANA could still refer to the same participant. The generator does not verify identities or recognize every semantic duplicate. Two to one thousand participants are supported.

Choose how many teams you need

Choose an integer from two to the total number of participants. The form asks for the number of teams, not the number of people in each team. Eleven participants and three teams produce sizes 4, 4 and 3. Three groups of four would require adding someone who is absent from the list.

Sizes never differ by more than one person. Twelve participants and three teams give four people in each; eleven participants and eleven teams give one each. Decide whether these sizes suit the activity before drawing. If the task requires exactly four people per group, you may need to change the team count or decide how to handle remaining participants.

11 = 4 + 4 + 3

1. Copy the eleven identifiers from the sample file.
2. Paste them as participants and enter 3 teams.
3. Generate once to obtain the assignment.
4. Check sizes 4, 4 and 3 and all eleven assignments.

What balanced means in this assignment

The list is shuffled using Fisher–Yates and cryptographic random numbers from the browser. Participants are then distributed in turns among the teams. This balances headcounts and avoids repeated entries; it does not analyze experience, age, availability, sporting positions or personal preferences.

Keeping pairs together, separating particular people or balancing abilities requires another procedure. Do not describe teams as equally skilled merely because they have similar sizes. Each execution makes a new draw. Changing the team count after generating discards the old result and requires running the operation again; the page does not preserve a previous accepted assignment for you.

Distinguish teams, shuffling and picking

Shuffle list changes the order of every entry but does not organize entries into groups. Pick from list selects options or winners according to its controls. The team generator assigns every participant to exactly one team. Repeatedly picking names is a different procedure and can introduce repeated selections with the wrong settings.

Agree before drawing whether the first result will be accepted and what happens if attendance changes. Repeating until a preferred team appears changes the selection rule. Save the original list and accepted assignment, especially when someone else must check that the agreed participant list was used. This tool does not issue certification or create an independently verifiable draw history.

Review and share without losing participants

Count participant lines across all teams and check that they total eleven in the example. Compare identifiers with the input: P01 through P11 must each appear once. Do not count team headings as participants. Specific membership and order vary between runs; balanced sizes and unique assignment are the properties you can check.

Copy the result or select Download to save the text. Generating does not start an automatic download, and editing the list invalidates the output. Processing is local, but text copied or sent to another application contains the names you supplied. If identifiers are sufficient, share those codes and keep their mapping to people separately. Review the saved file rather than assuming it is the latest result visible on another tab.