How youth sports age cutoffs work

Calendar year

Everybody born in the same calendar year plays together. A child born in January 2015 and one born in December 2015 are in the same group.

Simplest to explain and simplest to administer, which is why most national governing bodies use it. The cost is that the January child is nearly a year older than the December one, which matters a great deal at six and very little at sixteen.

School year

Groups follow grades, so the league matches the school day. Popular with recreational leagues because children play with their classmates and parents already know which group they are in.

The cost is that it does not travel. The moment you play another league or enter a tournament, your grade-based groups have to be translated into their age-based ones, and somebody is always ineligible.

Season year, with a fixed cutoff date

A specific date, often the start of the season or a date set by the governing body, and age is measured on that date. "Age as of August 31."

More precise and more portable than the other two, at the cost of a rule nobody can compute in their head. Expect to answer the same question many times.

Three reasons, and knowing them in advance helps.

• Relative age is real. Within a single year group the oldest children are measurably bigger and more coordinated than the youngest, and coaches select them more often, which compounds. It is well documented across youth sport and it is not a parent imagining things.
• Every parent has a story. A child who is small for their group, or large, or who has played with the same friends for three years. All of these are genuine and none of them can be accommodated without breaking the rule for everybody.
• The exception is the precedent. The first time you play somebody up or down, you have created the policy, whether or not you meant to. The second family will hear about it.

You will get requests to play up, and occasionally to play down. Decide in advance and write it down, because deciding in the moment means deciding about a specific child in front of their parent.

A workable policy usually says: playing up is considered on request and decided by named people; playing down is not allowed; safety and the governing body's rules override preference; and the decision is final for the season. You may disagree with those defaults, which is fine. The point is having them in writing before August.

Put the cutoff on the registration announcement itself, in the form "born on or after X and on or before Y", not "U10". Nobody outside your league knows what your U10 means, and half the people inside it are guessing.

A parent who can check their child's eligibility before filling anything in does not email you. That is the whole return on one extra sentence.

Age limits are set as a birthday window on the program: Earliest Birthday Eligible, which is the oldest child allowed, and Latest Birthday Eligible, the youngest.

Dates rather than ages is the right way round, and worth understanding. An age drifts as the season runs, so a child who is nine in September is ten by November and a rule written in ages quietly changes meaning. A birthday window means exactly the same thing all season.

Whichever of the three systems above you use, it converts into a birthday window. Calendar year 2015 is January 1 2015 to December 31 2015. Age as of August 31 is arithmetic you do once, at setup, instead of every time somebody asks.

A child outside the window still appears in their parent's list but cannot be selected, so the family finds out before filling the form in rather than after paying. The window is editable at any point, though changing it mid season does not remove anybody already registered.

See creating a registration program for where the fields are, and what you can change after registration opens.