Manual captain workaround

How to manually add captains when your team generator cannot

Published: October 23, 2026

If your generator cannot keep a chosen captain on each team, draw only the other members. Save that result, then add each captain using a team-to-captain mapping fixed before the draw. Check that mapping after merging; correct headcounts alone cannot prove the right captain joined each team.

This is a manual workaround, not an automatic captain feature. Use it when captains are already chosen and you want to randomize everyone else. It does not choose leaders or balance ability.

Which captain belongs to each saved team?

Our synthetic roster has twelve people: captains C-A, C-B and C-C, plus nine other members, N01 through N09. The allocation below is a constructed reference, not a captured random result or a real event. Each code identifies one intended person.

Do not attach captains alphabetically. Our agreed mapping is Team 1 to C-B, Team 2 to C-C and Team 3 to C-A. Sorting these labels and joining them by row position would change the assignments.

Enter only N01 through N09 in the random team generator, choose three teams, and save the draw. Your actual teammates can differ from this table. Keep their generated team numbers unchanged when joining the saved groups to the captain map.

Add C-B to Team 1, C-C to Team 2 and C-A to Team 3 in a separate document. The reference table produces three completed teams of four. Compare each completed team against the saved mapping before sharing it.

Keep the original export and completed roster separate. The generator file contains nine members because its input excludes captains. Our merged-12.csv contains twelve Member rows. Its repeated Captain cells identify the assigned captain beside each member; they are not extra participants.

Choose a team count your remaining roster can support. This site needs at least one entered member per requested team; captain-only teams need a different method. Do not put a captain back into the random pool merely to make the requested count possible.

Can correct totals hide the wrong captains?

The first damaged copy passes the headcount checks. Exchange C-B and C-C between Teams 1 and 2: each group still has four people and one captain, and every code appears once. The saved mapping catches the error. Teams 1 and 2 have the wrong agreed captain; Team 3 remains correct.

In the second copy, leave C-C out of Team 2. The roster now contains eleven people, with group sizes four, three and four. C-C is the missing code and Team 2 has no captain. This is the result of forgetting a manual merge row, not evidence that the random generator omitted a person it never received.

In the third copy, replace N03 with N01 in Team 2. The roster still contains twelve rows and one captain per team. N01 now appears twice, while N03 is missing. Both affected labels are filler members, so checking only captains cannot catch this error. Compare the completed Member codes with the original twelve-person roster.

In the fourth copy, include C-B again among Team 3's fillers while also keeping C-B as Team 1's captain. There are thirteen rows instead of twelve. Team 3 now has both C-A and C-B, and C-B occurs twice across the roster. Keeping the captain list outside the filler input prevents this particular construction error.

These are four deliberately damaged copies of the same reference. A script checked their member identities and captain assignments against the saved map. They test the manual merge, not randomness or how well a team would work together.

Which record should participants follow?

Keep the captain map, original draw and checked final roster together. If you replace the draw, merge its actual groups again and replace the shared final file. A downloaded roster does not update when the browser result changes.

Use one different captain per team. For general identity and export questions, use the same-name guide or CSV checking guide; this check concerns the additional captain mapping.

Reference files are captain-map.csv, filler-roster.txt and merged-12.csv. The MrExcel discussion already describes arranging group-numbered names beneath captains. This guide does not claim that basic method is new. Its worked errors concern checking the completed manual merge against your original agreement.