Random list generator

How it works

You supply the list. The generator permutes it. The output is the same items, a different sequence. Nothing is invented, and nothing in the list is dropped unless you asked for a subset. If a name was missing at the start, it cannot appear at the end. If a name was pasted twice, it has two tickets.

Most on-screen tools are pseudorandom: a computer algorithm that is hard to guess by eye. That is enough for a classroom order, a chore rota, a playlist, or a friendly split into teams. It is the wrong instrument when the draw must be audited as a lottery. For that job you need a process built and recorded for that job, not a shuffle widget.

Decide the replacement rule before the first click. A full shuffle uses each item once in the new order. Drawing one item at a time with replacement can repeat. People argue after the fact because they never said which rule they were using. Write it on the board. Then click.

From a shuffled list to teams

A random lists team generator is the shuffle plus a cut. You choose how many teams, or how many people per team. The generator walks the shuffled order and deals items into buckets. Team A gets the first, Team B the second, and so on, or it fills one team then the next. Both dealing patterns are fine if you name them. They are not the same pattern. One spreads early list order across groups. The other keeps clumps of the shuffled sequence together.

Uneven counts happen when the list length does not divide the team count. Someone will have a short team. That is arithmetic, not bias, as long as the leftover seats were not assigned by hand after seeing the names. If you need equal sizes, trim the list or add a spare role before you shuffle, not after you see who landed where.

Paste every eligible name once, unless you intend extra weight. Choose team count or team size before you generate. Say whether leftovers form a smaller team or sit out. Show the full input list with the output so the room can check.

Do not reshuffle because you dislike a pairing. Captains, skill tiers, and “no two siblings together” are extra rules. A plain random list team generator does not know siblings. If you need constraints, apply them as a stated method: shuffle inside a tier, then deal, or swap only to fix a named constraint. Silent swaps after the reveal are how a fair tool becomes a delayed appointment.

If you keep regenerating until your friends share a team, you do not have a generator. You have a seating chart with extra clicks.

What fairness is here

Fairness means each permitted assignment had a chance, not that every session looks “spread out.” Clumps happen. Three names from the same row of the classroom can land together in an honest deal. A generator that secretly avoids recent neighbours is no longer a uniform shuffle. It is a mixer with a memory. Use that mixer only if you asked for it.

Publish the input. A screenshot of teams without the original list cannot be checked. Spelling mistakes become extra people. Blank lines become extra seats. Trim the list in the open. Then generate once for the record you will actually use.

Order of speakers, order of chores, and order of play are the same machine without the team cut: one shuffled column. Teams are that column folded. Do not switch from a fold to a “pick me a captain” click mid-process unless you said that captains are a separate draw.