The Soccer Age-Group Boundary Moved Back to August

If you run a youth soccer club, you are probably doing this in a spreadsheet right now.

US Club Soccer, US Youth Soccer and AYSO have moved the age-group year back to 1 August to 31 July, starting with the 2026-27 season. For the last several years age groups were formed by calendar year, January to December. They are not any more.

Every age group your club has on paper was computed on the old boundary. None of them was wrong. All of them now need doing again.

Why the federations changed it back

Their reasons, and both are about children rather than administration.

The first is what the federations call trapped players: a child born in the wrong part of the year who ends up permanently at the young end of their group, playing against children up to eleven months older, for their entire youth career. Calendar-year grouping produced that reliably and predictably.

The second is simpler. An August-to-July year lines up with the school year, so a child plays with the friends they already have. That sounds like a small thing until you watch a nine-year-old leave a team because everyone they knew moved up without them.

The part that actually costs you a weekend

Knowing the new date is not the hard part. The hard part is the edges.

Under the old boundary a child born in, say, September sat in one group. Under the new one they may sit in another. Multiply that by every child born in the five months between the two boundaries, across every team in your club, and the work is not a calculation. It is a list of individual children whose group changes, each of whom has a parent who will ask you why.

That is where the errors go. Not in the middle of a group, where everybody moves together, but at the edge, one child at a time, in a spreadsheet at eleven o’clock at night.

What we can honestly tell you about Rostered

This is somebody else’s calendar change and we are not going to pretend otherwise.

Rostered does not recompute your existing divisions. When a club sets up an age group, the boundary that applied is stored on it. Nothing goes back and re-derives it later, so if your divisions were built on the January boundary, they still carry it, and moving them is work somebody has to do. We would rather say that plainly than let you find out in March.

Two things are true and worth knowing anyway.

A new program generated in Rostered uses a 1 August boundary, which is the boundary the federations have just returned to. That helps a club setting up from scratch. It does nothing for one that already has structure.

Every cohort stores its eligibility window explicitly, a start date and an end date, rather than implying them from a rule somewhere. So a club can look at a cohort and see the window it actually covers, and look at a child and see which window they fall in. That does not do the recomputation. It does make the edges visible, which is where the errors are.

If you are doing this now

Work from the children outward rather than from the groups inward. The groups will take care of themselves once the children are placed; it is the placements near the boundary that need a human looking at them.

And write down the boundary you used. In four years, when somebody moves it again, the club that can answer “which rule was this group built on” will do this in an afternoon. The club that cannot will do it the way you are doing it tonight.

Rostered is free for every parent and athlete, and clubs start at $9 a month. See what’s free, look at the packages, or start your club.