Random Pair Generator

Create pairs from one active list, add any must-not-pair relationships, and decide how an odd person should be shown.

Presentation

1 · Add names

7 unique names

Excluded pairs

Add only the pairs that should not be matched. Each name is selected from the current list.

With an odd number of names, one participant receives a bye.

2 · Pairs

Add participants and generate pairs to see the result.

Ready to create random pairs.

What this tool does

A random pair generator shuffles eligible entries into groups of two, checks declared exclusions, and returns a visible Bye or other configured odd-person treatment when the count is uneven.

Partner matching

Practical ways to create random pairs

Make discussion partners

Pair participants for a short conversation or feedback round when attendance-specific history is not required.

Create practice opponents

Generate casual head-to-head pairs for drills, table games, or a non-bracket activity.

Set up peer checks

Use exclusions to prevent known conflicts or self-related pairings before copying the accepted list.

Instructions

How to generate pairs

Paste the active names

Enter one distinct person per line and remove anyone who is not participating in this pairing round.

Add necessary exclusions

Mark relationships that must not become a pair and keep the list limited to rules you can explain.

Choose the odd-person treatment

When the list is uneven, show a Bye or use another available option instead of silently dropping an entry.

Generate and review

Check every pair and exclusion, then copy, print, or generate another arrangement.

Troubleshooting

Pairing conflicts and odd counts

An exclusion set is impossible

When: One or more people are excluded from every possible partner.

Why: No complete pairing can satisfy all declared must-not-pair rules.

Try: Remove or revise an exclusion, add participants, or accept an explicit unpaired result.

The list has an odd count

When: An odd number of usable entries remains.

Why: Pairs consume two entries, so one person cannot be placed in a pair.

Try: Use the visible Bye, add another participant, or remove one entry.

Duplicate labels merge

When: Two people have the same normalized display name.

Why: The tool cannot distinguish identical labels when applying exclusions or showing results.

Try: Add initials or another identifier before generating pairs.

Trust

Pairing rules and private inputs

Exclusions constrain the random result

Without exclusions, the active list is paired randomly; each restriction removes possible arrangements and can make some outcomes unavailable.

  • Every usable entry appears once, either in a pair or as the explicit odd-person result.
  • The tool does not infer relationship history, compatibility, or social safety from names.
  • A constrained pairing is not uniform across arrangements that the exclusions have made impossible.

Names and exclusions are not saved

The list, must-not-pair relationships, and results are used for the active task and are not saved by Random 42.

  • Random 42 does not create permanent partner history, a share link, or an account.
  • Refreshing or closing the tool clears the current names, rules, and pairs.

Boundaries

What random pairing does not account for

Random pairs are not compatibility matches

The tool can apply explicit exclusions but cannot judge mentoring fit, language compatibility, safeguarding, or interpersonal risk.

Review before you use the result

  • Use a classroom-specific partner workflow when attendance and prior pair history matter.
  • Review consent, accessibility, power differences, and safety before announcing a pair.
  • Do not use the result for dating, clinical, employment, or other high-stakes matching.

FAQ

Frequently asked questions

What happens with an odd number of people?

The tool shows one explicit Bye or other selected odd-person outcome so nobody silently disappears from the result.

Can I stop two people from being paired?

Yes. Add a must-not-pair exclusion. If the complete exclusion set is impossible, the tool reports the conflict.

Does it avoid partners from earlier rounds?

Not automatically. This generic page uses only the exclusions in the current setup and does not save partner history between sessions.

Are names and exclusions uploaded?

No. They are used for the active task and are not saved by Random 42.

Keep exploring