The GotSport Seasonal Year Switch: What Every Club Must Change Manually for 2026-27

Most clubs find out about this the same way. A registrar tries to add a player to a 2026-27 roster, GotSport refuses, and nothing on the screen explains why. The player is registered. The team exists. The roster spot is open. GotSport still says no.

The cause is almost always the GotSport seasonal year setting, which nobody was told to change. On August 1, 2026, US Youth Soccer, US Club Soccer and AYSO moved age groups from a birth-year cycle to a school-year cycle running August 1 to July 31 (US Youth Soccer). GotSport updated part of your account automatically. The rest it left for you.

This guide covers what GotSport changed on its own, the four places you still have to change something, the order to do it in, and what to check when a roster will not validate.

What actually changed on August 1

Age groups used to be formed by birth year: everyone born in 2015 played together, January through December. From the 2026-27 season they are formed by school year instead, August 1 through July 31, so a team holds players from two birth years.

The three largest youth organisations made the decision jointly, which is why it applies whether your club registers through US Youth Soccer, US Club Soccer or AYSO. It was first announced with a September 1 cut-off and revised to August 1 in June 2025 (US Club Soccer), so if you have a memo from early 2025 in a folder somewhere, check its date before you follow it.

One thing worth setting expectations on: none of the three organisations publishes a table of birth-date ranges per age group. All of them point to a calculator instead. If someone sends you a homemade grid, treat it as a working note rather than a rule.

Automatic versus manual

This is the distinction the whole task turns on. GotSport did some of the work on August 1 and left the rest.

Those four GotSport seasonal year settings are the whole manual job, and they come from GotSport's own documentation (GotSport support). In Florida the same setting appears in FYSA guidance under the label "school year", which is what GotSport shows in the interface, so the two match even though the wording differs.

GotSport does not document what happens if you leave one of them on Calendar Year, and it does not say whether objects you created before August 1 keep the old setting. Assume they do, and check them. That assumption costs you five minutes; the alternative costs you a rostering weekend.

The order to work in

GotSport documents the four settings but not a sequence. This order is Centro's recommendation, not GotSport's instruction, and it exists because each step makes the next one easier to verify.

1. Teams first. They are the thing rosters attach to, and they are the fastest to check visually. Open a team and look at the Seasonal Year control. If it offers "Switch to Calendar Year", the team is already on School Year and you are done with it. That is confirmation, not a prompt. If it offers "Switch to School Year", change it.
2. Internal Rostering Events next. These are where roster validation actually runs. A correct team inside an event still set to Calendar Year will still fight you.
3. Programs. These drive what families see and which age group a registration lands in.
4. Forms. Last, because a form built against corrected programs and teams inherits the right options.

Work through your list once, all the way, before you test a roster. Fixing one setting and immediately retesting is how people conclude the setting "did not work" when the real blocker was the next one down.

Free resourceSeason plannerMap out a season week by weekGet it →

What roster validation now catches

GotSport validates against the school-year age band when a player is added, and blocks players who are too old for the band without anyone checking manually. That is a genuine improvement: the error surfaces at the point of the mistake rather than at a state association's desk in October.

It also means a blocked player is a signal, not an obstacle. Three things it usually indicates, in order of likelihood:

• The team or the rostering event is still on Calendar Year, so GotSport is comparing the player against last season's band.
• The team is on the right cycle but the wrong age band, which is easy to produce if the team was created before August 1 and its name still says U11.
• The player genuinely is outside the band, which is now the least common cause but the one that actually needs a conversation with a family.

Work them in that order. Check the settings before you check the player, because the settings are faster to rule out and are wrong far more often.

Team names, and why the U-number is a trap

Now that a band spans two birth years, a team named for one of them is misleading to half its own roster. GotSport recommends naming teams for both years covered, so "2013/14 Boys" rather than "2013 Boys".

It also recommends leaving the U-number out of the name entirely, on the grounds that the designation changes every season and forces an edit every year. That is a small piece of advice with a large downstream effect: a club with sixty teams named U9 through U19 has sixty edits every August, forever, and every one of them is a chance to introduce a mismatch between a name and a band.

Who gained a year, and who lost one

A transition like this moves the boundary, and players sitting on the old boundary move with it. Some pick up an extra season of eligibility and some run out early.

Florida is the clearest published example. FYSA's 2026-27 pre-season checklist states that players born August through December 2007 gain an additional year of eligibility because of the change, and that players born August through December 2020 lose eligibility to be placed on a team in the youngest competitive division. It also states that no exception will be granted for July-born players to play down except under Rule 203.4. That document is published as a draft, so confirm the detail with FYSA before you tell a family anything.

The general point holds outside Florida: your state association, not GotSport, decides who is eligible and who may play up or down. GotSport enforces the band. It does not grant the exception.

If a parent asks which group their child is in for 2026-27, the fastest honest answer is to run the birth date through a calculator rather than a memory of last season. Ours is here: soccer age group calculator.

The registrar's checklist

Work through this with GotSport open in another tab. It assumes you are setting up or repairing 2026-27.

Settings

• Every active team checked for Seasonal Year, and set to School Year
• Every Internal Rostering Event for 2026-27 set to School Year
• Every Program families can register into set to School Year
• Every live registration Form set to School Year
• Anything created before August 1, 2026 checked rather than assumed

Teams

• Team names show both birth years where a band spans two
• No U-number left in a team name that will need editing next August
• Age band on each team matches the group it is actually fielding

Rosters

• One test roster built end to end before you open the process to coaches
• Any blocked player triaged settings first, band second, player third
• Players on the transition boundary confirmed against your state association, not against last season

People

• Every rostered adult holds current SafeSport, concussion training and a background check
• Florida clubs: Level 2 fingerprint screening in place, which has been required of coaches since July 1, 2026

The last two are not part of the age-group change, but they fail at the same moment for the same reason, which is that rosters get verified all at once and any missing piece stops the whole team.

Where this leaves the rest of your season

GotSport is the system your state association requires, and for rostering, player cards and sanctioned competition it is the system of record. That is not in question here, and nothing in this guide is a reason to work around it.

What it does not do is run your club's own side of the season: the registration form families actually fill in, the money, the reminders when paperwork is missing, and the communication that follows. Plenty of clubs run that in spreadsheets and a group chat alongside GotSport, which works until the volume changes.

Centro handles that club-side workflow next to GotSport rather than instead of it. One registration link that collects the form, the waiver and the payment together, the roster built from what families actually submitted, and the chase list for whoever has not finished. If that is the part of your season that hurts, see how registration works in Centro.

For the wider picture of the 2026-27 transition beyond GotSport itself, our 2026-27 age group transition guide covers the club-side and parent-side consequences, and the FYSA registration guide covers what Florida clubs owe their state association each year.

This guide describes the 2026-27 season. GotSport's documentation and FYSA's checklist should both be reverified before the 2027-28 registration cycle opens. Centro is not affiliated with or endorsed by GotSport.