GroupMixer
Back to guides
Partner and peer-work guideUpdated July 22, 20263 min read

How to make random pairs from a list of names

Pairing is simple until the list is odd, the activity has several rounds, or two people should not be matched. Make those decisions explicitly before generating the first roster.

A facilitator turns a tangled pile of colorful pairing ribbons into neat partner pairs, with one odd card waiting nearby.

Guide visual

Pair rotations

Partner work with fewer repeated pairs.

pairsodd countsrepeat control

Choose an odd-count policy

PolicyUse it whenWatch for
One triadEveryone should participate in every round.Rotate who works in the triad so the same people do not repeatedly receive a different format.
One byeThe activity is tiring or observation is useful.Publish the bye rotation in advance and distribute it fairly.
Facilitator joinsA trained facilitator can participate without distorting the task.Do not make one participant dependent on staff every round.

Create a partner rotation

  1. Clean the list

    Remove duplicates and confirm attendance. A duplicate name can create an impossible-looking self-match or a missing participant.

  2. Choose pairs or an explicit group count

    For an odd list, choose whether the remainder becomes a triad or a bye. The preloaded example uses eight groups so seventeen people produce seven pairs and one triad.

  3. Set every round together

    For repeated peer work, set the full number of rounds and enable repeat minimization before generating.

  4. Add only necessary exclusions

    Use an apart rule for a real conflict, assessment-integrity issue, or safeguarding need—not because a previous conversation was merely awkward.

  5. Review partner history

    Check that each person receives the intended number of assignments and that the triad or bye burden rotates.

  6. Replan after absences

    One absence changes an odd list into an even one. Regenerate the remaining rounds rather than carrying forward an unnecessary triad.

Read pair history without losing the odd-person policy

  • The session rosters under Your groups show whether each round actually followed the chosen pair, triad, or bye structure.
  • The Pair Meeting Histogram counts pair contacts, including the three pair contacts created by a triad. Its repeated total therefore answers how many distinct pairs met again—not who repeatedly received the triad.
  • The Pair Meeting Matrix identifies repeated partners and the exact sessions they shared.
  • Triad and bye burden must be read from the session rosters because it is a group-format question, not a pair-count metric.
  • A required apart pair has no shared session in the matrix and “No violations” in its card in a valid result. Any other result is a solver defect.

Worked example: seventeen people, three rounds

The preloaded example uses eight groups: seven pairs and one triad in each of three rounds. Everyone participates, and the review should verify that triad membership and repeated partners are distributed rather than concentrated.

Setup facts

  • 17 participants
  • 7 pairs and 1 triad per round
  • 3 rounds
  • two prohibited pairings

Review the result

  • Confirm every participant appears exactly once per round.
  • Track who enters the triad and avoid giving the same people that format repeatedly.
  • Check both direct pair repeats and repeated contacts inside the triad.

Try this setup in GroupMixer

This tool is preloaded with the example from this guide. You can edit the participants, constraints, sessions, and balance settings before generating groups.

Enter one person per line in the first column. Optionally, add attribute columns such as gender, role, or skill-level on the right. Those attributes can then be used to balance groups and set additional rules.
Name
Use 1 session for a single round of groups. Increase sessions when you want multiple rounds with new group assignments for the same people.
People
17
Groups
8
Approx size
3
Force specific people into the same group in every session. Write one "clique" per line, with names separated by commas. Example: "Alex, Sam" keeps Alex and Sam together.
Prevent selected people from being placed in the same group. Write one set per line; everyone on a line is kept mutually apart. Example: "Alex, Sam, Jordan" keeps all three separated.
Pin specific people to a specific group across all sessions. Enter one name and one group number per row. This is useful for leaders, presenters, or anyone who must stay in a known group.
Name
Group
Set target counts for each attribute value inside each group. Keep auto distribute enabled for fair automatic targets, or edit the counts manually when you need exact control.
Add an attribute in the participants list to use this section.
Need even more control?
  • Partial attendanceSet which participants attend which sessions instead of assuming everyone is present every round.
  • Custom group capacitiesGive each group its own capacity and override those capacities for specific sessions when room sizes or staffing change.
  • Session-specific constraintsApply scoped rules only where they matter, then use global objectives such as Avoid Repeats for whole-schedule quality.
  • Weighted preferencesAdd preferences that can be violated when needed, then tune their weights relative to other goals.
  • Encounter targetsTarget how often selected people should all meet across the schedule, including exact, minimum, or maximum encounter counts.
  • Group visit targetsControl how often selected people visit selected groups across sessions for station rotations, task exposure, or visit caps.
  • Advanced constraint tuningFine-tune repeat limits, attribute-balance modes, penalties, and other constraint details beyond the landing-page controls.
  • Solver settingsAdjust runtime limits, deterministic seeds, solver family, and other optimization settings.
  • Result analysisInspect score breakdowns, constraint compliance, penalties, and saved results in more detail.
Quick Setup and the scenario editor use the same saved scenario. Settings hidden here remain intact.

Related guides

Run speed networking rounds

Add timing, transitions, and live-event operations.

Round robin groups

Move from pair rotations to complete contact coverage.

Split a class into fair groups

Choose a broader classroom grouping process.