Are repeated names removed?

No. Every non-empty input row receives its own internal ID. In constraints, the first occurrence uses the name and later occurrences use Name #2, Name #3, and so on.

What does reshuffle one team do?

It only randomizes the order of members already assigned to that team and redraws that team's representative. It never moves people between teams, and every other team stays unchanged.

What happens when the rules have no solution?

The tool reports an explicit error. It never drops a participant, merges a duplicate, exceeds capacity, or silently ignores a fixed, together, or apart rule.

← Home

Secure, constraint-aware browser tool

Advanced random team generator

Build size-balanced teams without losing repeated names, then add the real rules ordinary shufflers ignore. Tags are spread as evenly as the constraints allow; fixed assignments, together groups, and apart pairs are treated as hard requirements.

Editorial and interface reviewed in English.

Advanced team settings

Participants and balance tagsOne person per line. Add optional tags after |, separated by commas. Repeated names remain separate rows and are referenced as Name #2, Name #3, and so on.

Local roster handoff

Only names are transferred. Attendance, tags, constraints, weights, images and results are not transferred.

Saved in this browser only. Export JSON to move the roster to another device.

This tool accepts 2–100 names.

Import roster JSON

Number of teams

Optional constraintsFixed team assignmentsOne per line: Name -> team numberKeep togetherOne group per line: Name + Name + NameKeep apartOne pair per line: Name -> Name

Enter at least two participants, choose the team count, then generate.

How the advanced team generator works

Enter each participant on a separate line and add optional balancing tags such as experienced, new, design, or engineering.
Choose 2–20 teams, then add exact fixed-team, keep-together, or keep-apart rules using the visible row references.
The bounded solver validates every rule, searches for a size-balanced assignment, minimizes tag concentration, and draws one representative per team with Web Crypto.

Worked example

For eight people in two teams, four tagged experienced and four tagged new can normally become two experienced and two new per team. If Amina and Mateo must stay together while Amina is fixed to team 2, the whole together group goes to team 2; the remaining rows are solved around that hard rule.

Rules, limits, and interpretation

The tool accepts 2–100 participants, 2–20 teams, and up to eight distinct tags per person. Team sizes differ by at most one.
Together groups are merged when they overlap. A merged group cannot exceed the largest balanced team size or contain people fixed to different teams.
Keep-apart blocks two people from sharing a team. It does not promise distance, different sessions, or conflict resolution outside this grouping.
Tag balance is a best-effort optimization after hard rules and team capacity. It does not infer skill, identity, fairness needs, or tag importance.

Private by design

Entries and results stay in this tab by default. Only when you choose to save a roster are its names stored in this browser. Tags, constraints and results are not included in the roster handoff. Tool values are not sent to URLs, analytics or servers; export happens only when you choose it.

Frequently asked questions

Are repeated names removed?: No. Every non-empty input row receives its own internal ID. In constraints, the first occurrence uses the name and later occurrences use Name #2, Name #3, and so on.
What does reshuffle one team do?: It only randomizes the order of members already assigned to that team and redraws that team's representative. It never moves people between teams, and every other team stays unchanged.
What happens when the rules have no solution?: The tool reports an explicit error. It never drops a participant, merges a duplicate, exceeds capacity, or silently ignores a fixed, together, or apart rule.
Do the names and tags leave my device?: Entries and results stay in this tab by default. Only when you choose to save a roster are its names stored in this browser. Tags, constraints and results are not included in the roster handoff. Tool values are not sent to URLs, analytics or servers; export happens only when you choose it.