How should you divide players into teams?

Every method below is fair by some definition and unfair by another, so the useful first question is which kind of fairness your league is actually promising.

• Even competition. Every team should have roughly the same chance of winning.
• Even development. Every player should get roughly the same quality of coaching and playing time.
• Convenience. Families should be able to get their child to practice.
• Friendship. Children should be with people they know.

You cannot have all four. A league that balances for even competition will split up friends. A league that keeps friends together will produce one very strong team. Pick the one or two that matter most to the families you serve, say so out loud before registration opens, and the complaints mostly stop being about fairness and start being about logistics, which are much easier to answer.

The simplest method, and the right default for younger age groups. Sort by date of birth and cut.

Works when you have enough players to fill separate age brackets, and when the sport's governing body already defines them, which most do.

Costs you nothing in effort and a lot in balance. Within a single birth year the gap between a child who turned eight in January and one who turned eight in December is enormous, and at the youngest ages it is the biggest single predictor of who looks talented. This is well documented enough to have a name, the relative age effect, and it is worth knowing about before you conclude the January children are simply better.

Run a tryout or a skills session, rate each player, then draft teams in turn so the rated talent is spread evenly. A snake draft, where the order reverses each round, keeps the team picking first from taking every best available player.

Works when competitive balance genuinely matters, typically from about eleven upward, and when you have enough coaches willing to give up an evening.

Costs you a whole extra event, a rating system you have to defend, and the reality that evaluations at these ages measure confidence and coordination at least as much as ability. Keep the ratings private. A parent who learns their child was rated a 2 will remember it longer than you will.

Group players by where they live or where they go to school.

Works when your league covers a wide area, or when practice attendance is your real problem rather than balance. It is also the method that builds the most loyalty, because a team of children who see each other all week turns into a group that comes back next year.

Costs you balance, sometimes badly. One school will have a strong group and another will not, and everybody will know by week three. It can also concentrate families by income in a way that is worth thinking about before you commit to it.

Ask on the registration form who a family wants to be with, and honor what you can.

Works when you are running a recreational program for young children, where having a friend is most of the reason a child will want to come back.

Costs you control. Requests cluster: you will get eight families asking for the same coach and four children who were named by nobody, and the second group is the one that matters. If you ask the question, decide in advance how many requests you will honor and say so on the form.

A combination, and there is nothing wrong with that. The common shape is age brackets first, because they are usually not optional, then one other method inside each bracket.

• Under 8: age, then requests. Fun and attendance beat balance.
• 8 to 11: age, then a light evaluation or a coach draft.
• 12 and up: evaluation, because by now the players notice imbalance before the parents do.

Write the method down before registration opens. Put it on the registration page. A parent who knew the rule going in complains far less than one who learns it after the teams are posted.

Check the sizes before you announce. Teams of 11, 11, 11 and 8 will generate more complaints than any balance decision you made, because playing time is the thing families actually count.

Announce all the teams at once. Trickling them out gives the first families a week to compare and lobby, and you will spend that week moving children around.

Everyone who registers goes into one list until you place them, so no method is built in and none is ruled out. You assign players to teams from the Master Data Grid, where every registration is one row and the team is a dropdown on it.

What makes the methods above practical is that the grid holds your registration form answers as columns. Ask about school, or preferred practice night, or who a family wants to be with, and you can sort on the answer and work down the column. See drafting players onto teams, and building your registration form for asking the question in a way that sorts cleanly.