Assign Mixed Ability Teams and Document Exceptions

To balance mixed ability teams for a community tournament, do four things in order. Collect comparable ability estimates and role preferences for every player. Lock in the roster constraints you have agreed to honor. Distribute the remaining players with an alternating snake order. Then review the result and write down every manual change and the reason for it. This works whether you are running a casual Mobile Legends night, a League of Legends scrim series or a mixed-skill rec league. The method produces a defensible starting lineup. It does not guarantee that matches will feel even, so the exception log matters as much as the math.

The steps below are organizer choices, not rules from any game publisher or governing body. If your event runs under a league ruleset, a venue policy or a sanctioned format, check those requirements first. They take priority over anything here.

Step 1: Build a roster worksheet with comparable information

Balancing only works if every player is described the same way. Before anyone is placed on a team, give each participant a row with the same fields. Use a participant ID rather than a name so the sheet can be shared and audited without exposing personal details.

participant_id | available | ability_estimate | estimate_basis | estimate_date | preferred_roles | allowed_alt_roles | grouping_constraint
P01            | yes       | 8                | organizer review | 2026-10-28  | jungle          | mid               | none
P02            | yes       | unknown          | new player       | -           | roam            | any               | with P07
P03            | no        | 6                | prior season     | 2026-09-15  | gold lane       | exp lane          | none

The rows above are an illustrative example, not real players. Use the role names your community already uses for your game. The fields that matter most are the ones below.

• Ability estimate: one number on a single agreed scale for everyone. MatchBalancer's League of Legends balancer, for example, uses a 1–20 rating. Any scale works if every estimate uses it the same way.
• Estimate basis and date: where the number came from and when. This lets you spot stale or inconsistent estimates before they skew a team.
• Preferred and permitted alternative roles: what the player wants to do and what they are willing to do. These are separate fields so you know how much flexibility you have.
• Team-size requirement: how many players each team needs for your format.
• Grouping constraints: declared requests such as a parent and child on the same team, or two siblings kept apart. Record only constraints you have agreed to honor.
• Unknowns: if you have no estimate for someone, write unknown. Never enter zero. A zero quietly treats a newcomer as the weakest player and drags their team's total down.

Agree with your co-organizers how estimates will be set, who can challenge them and which constraints count as mandatory. Settle this before you see any lineups. Deciding the rules after seeing results is how balance disputes start.

Step 2: Resolve mandatory constraints first

Take the players with mandatory constraints and place them before anyone else. If two players must be together, put them on the same team now and count both of their estimates toward that team's total. If two must be apart, assign them to different teams. Players you cannot place are not available for this round, so mark them as unavailable and remove them from the pool.

Step 3: Distribute everyone else in snake order

Sort the unconstrained players from highest to lowest estimate. Then deal them out to teams in a forward order, then a reverse order, and repeat. With three teams the order is A, B, C, C, B, A, A, B, C and so on. Each team that gets an early high pick also takes the last pick of the next pass, which evens out the totals.

Here is a hypothetical calculation for two teams of four, with estimates 8, 7, 6, 5, 4, 3, 2 and 1:

Pick order	Estimate	Team
1	8	A
2	7	B
3	6	B
4	5	A
5	4	A
6	3	B
7	2	B
8	1	A
Total		A = 8+5+4+1 = 18; B = 7+6+3+2 = 18

Equal totals mean only that this worksheet adds up evenly. They do not show that the teams will play evenly. Role coverage, communication and how accurate the estimates are all affect the result.

Step 4: Review the proposed teams

Check every proposed team against the same list before you publish anything.

• Team size: every team meets the format's requirement.
• Rating totals: note the gap between the highest and lowest team totals.
• Role coverage: each team has someone in a preferred or permitted role for every position your format needs.
• Unknown estimates: check whether unknown players are clustered on one team. If they are, spread them out.
• Constraint compliance: every mandatory grouping you agreed to is still intact.

Step 5: Make swaps only for a stated reason

If the review turns up a problem, look for a swap between players with similar estimates that fixes it. Typical problems are a team with no one who can play a needed role, or a team holding most of the unknowns. Before you make the swap, write down which constraint or numerical difference it addresses. If you cannot say what a swap fixes, don't make it. Unexplained swaps look like favoritism, even when they are not.

Step 6: Document every exception

An exception is any assignment that departs from the snake result or leaves a known issue unresolved. Log each one in a single place, using the same fields every time.

revision | participant_ids | reason                                         | reviewer | remaining_issue
r2       | P04, P11        | Swapped so Team B has a player able to roam  | Co-lead  | Team B total now 1 higher
r2       | P02, P07        | Mandatory grouping: parent and child together | Lead     | none
r3       | P09             | Estimate unknown; moved to spread unknowns    | Co-lead  | P09 playing alternate role

The log above is illustrative. Number each revision of the lineup so the final published teams can be traced back to the snake result and to every change made since. Record any role mismatch that remains after your swaps. That way, if a player says they were stuck in the wrong role, you can show it was a known tradeoff and not an oversight.

Step 7: Share assignments and record results

Publish the final teams together with a short note on how they were built: the shared scale, the snake method and the fact that exceptions were logged. Then record match results against each lineup revision. After a few events, those results show you where your estimates were off, so you can update the estimate basis and date before the next round of assignments.

Using a team balancer tool

If you would rather not run the worksheet by hand, team balancer tools automate the same flow. MatchBalancer describes its workflow this way: enter player ratings and role preferences, select who is available, review suggested lineups, share the assignments and record results. Its League of Legends example uses a 1–20 rating scale with named game roles. A tool speeds up the arithmetic, but it does not replace the rules you set. You still have to agree on the rating scale, honor your constraints and keep your own exception log for any lineup you change after the tool suggests it.