The Team App reaches families

The platform stopped ending at the club office. Parents and guardians now have their own way in, and coaches have the roster and communication tools that go with it.

For parents and guardians

Sign in with Google, Microsoft, or simply the email address your club already holds — there is no account to create.
See every child you are a guardian for, with siblings together in one place.
Follow the team schedule, and subscribe to it from the calendar app you already use.
Read updates your coach posts to the team.
Answer season surveys from your coach, per child.
Respond to a roster offer — accept it, or mark it tentative and say why.
Reach another family through the team directory without their email address being disclosed.
Add a phone number so your club can reach you a faster way.

For coaches

A team workspace covering the roster, offers, updates and settings for one team at a time.
Build a roster from a spreadsheet, with siblings and duplicated guardians resolved to one person.
Send roster offer letters from a team template, resend to whoever has not replied, and skip families who have already accepted.
See where every offer stands, including the reason behind a tentative answer.
Post updates to the team, and add team events alongside the club’s master schedule.
Create season surveys and read the responses.
Set a team display name, and control which players appear on the team list.
Edit player and guardian details directly.

Also this month

Indoor joined grass and turf as a field surface type.
A recurring booking now carries a real series behind it, and a series can run longer.
Booking list filters — field, team, status, type and day — became multi-select.
Archiving and deactivating stopped behaving like the same switch.
One import file can now cover an entire club.
Carrying a season forward became a single flow with one clear starting point.

August 2026

LeagueHub learns where the games actually are

A league schedule is only useful if its venues resolve to somewhere you can drive to. Most of this month went into making league data land on the right field.

League data

Venues gained their own model, so a league venue can carry a real address independently of the games played there.
A shared park stopped being treated as a shared field.
League field aliases now match more reliably, and an alias that loses a match is reported rather than silently accepted.
New reporting on games arriving under names nothing can place, and on the several ways a game can miss a field it should have hit.

Imports and oversight

Imports leave an audit trail.
The import dialog remembers what it did last time.
Operations can review imports across every club.
Alerting stopped raising issues against configurations that were already correct.

What we've shipped lately