Youth Sports Software · Coaches, team managers & sports parents · Early access · 2026

The team’s single source of truth — roster, family comms, and team photo day in one place for every coach and sports parent

Youth Sports Software is built around the roster: one import drives the family communication list, the season schedule, and the team photo-day coordination. Coaches reach every opted-in parent by email and in-app today. Game-day texted alerts and the parent photo-day ordering store are in early access. Minor player data is consent-gated, access-controlled, and never public. Facial recognition is off by default. No public roster lookup.

Book a conversation How it works

Roster-drivenone import → comms, schedule, photo day — all from the same team record

Consent-gatedfamilies opt in before any message; minor data never public, never sold

Comms engine builtmessage composition + opted-in recipient list built; delivery honest-off (queued, not sent)

Early accessgame-day texted alerts + photo-day parent store — in active development

The coaching challenge — a roster in a spreadsheet, comms in a group text, photo day somewhere else

One change to a game time — and three tools to update manually

A coach running a youth sports team typically has the roster in a spreadsheet, the season schedule in a calendar app, family contact in a group text thread, and team photo day coordinated by email with a photographer. When the Friday game moves to Saturday, the coach updates the calendar, sends a group text, edits the email chain, and hopes everyone saw it. Two families miss the change. One parent shows up at the wrong field.

Youth Sports Software replaces the scatter with one roster. Import the team list once: every downstream surface — family comms, schedule, photo-day coordination — draws from the same record. A game change updates the schedule, queues an alert to every opted-in parent, and keeps the family-facing view current — in one step, not four. Coaches spend less time playing information-routing coordinator and more time coaching.

The roster engine and the family communications engine are built; message delivery is honest-off (queued, not sent). The season schedule, game-day alerts, and the parent photo-day store are in development or honest-off: the logic is present, but delivery, the schedule editor, and parent checkout are not enabled. We say so directly — because coaches deserve to know what the platform does today.

Book a conversation Full platform

How it works

The team year in four stages

Youth Sports Software runs on a season rhythm: roster import and family opt-in before the season, communications composed and the schedule set up at the opener, game nights and photo day through mid-season, and a clean year-end data handoff. Every stage is described as it is built today — including what is queued-not-sent and what is still in development.

Step 1 · Pre-season — roster import and family opt-in

A coach or team manager imports the team roster: player names, grade or age group, and family contacts. The platform creates one family record per household — a family with two children on the same team sees one opt-in, not two. Each family is invited to opt in to communications from the team before any message is sent. Consent is collected before the season begins, not assumed. Minor player data is never public without a released consent, and is never shared with outside companies. The team owns its roster and its family communication list from the first import.

Step 2 · Season opener — schedule set up, families in the loop

The season-opening message is composed and queued to every opted-in family — message delivery (email and in-app) is honest-off today, so it is queued, not dispatched, until the delivery channel is provisioned. The season schedule editor and the family-facing view are in active development; the scheduling logic that will populate the alert list from the opted-in roster is present in the shared library. Photo-day slots attach to a date on the schedule, ready for the photo-day coordination layer when the team’s session is scheduled.

Step 3 · Mid-season — game nights, comms, and photo day

The team drafts its mid-season communications through the platform: game reminders, last-minute location changes, cancellations, and announcements are composed and queued to opted-in families. Message delivery is honest-off — queued, not dispatched, until the delivery channel is provisioned; texted alerts are honest-off as well. The team photo day runs on the platform’s coordination layer: slot scheduling and photographer handoff. The parent ordering store is honest-off — not available today.

Step 4 · Year-end — season close and data ownership

At season’s end the team record is complete: the full schedule, every communication sent, and the photo-day record. The team’s data export is available in writing — if the organisation ever leaves, every record leaves with it: roster history, schedule, communication logs, and family consent status. The roster is archived, not deleted, so returning families can opt in again next season without re-entering their information. The organisation owns its data from the first import to the last export.

The full platform

Five engines — honest about what is built and what is coming

Every feature is labelled honestly: Built means the underlying engine is built and present in the platform (delivery and enablement may still be honest-off; we say which). Early access means the surface or carrier integration is in active development. We do not claim otherwise.

Team roster — one import, every family contact matched, consent-gated

The roster import is the platform’s single source of truth. A coach or team manager runs one roster import — player names, grade, family contact — and every downstream surface draws from the same record: the family communications list, the season schedule, photo-day slot assignment, and the alert subscription list. Roster entries are consent-gated: a family opts in before a child’s data is added to any list. Roster deduplication handles the family with two children on the same team: one family record, one opt-in, one parent-facing view. Family contact matching is exact-name against the imported record — facial recognition is off by default, not used for family contact matching, and there is no public roster. The team roster engine and family contact matching are built and production-ready.

Roster engine built

Family communications — email and in-app channels, opt-in only, roster-driven

The family communications engine composes a message and routes it to the opted-in family list for a team. No message reaches a family who has not opted in. Consent is collected at the roster-import stage — each family is invited to opt in to communications from the team before any message is queued. A coach composes a message through the platform; it is queued against the opted-in family list for that team. The composition engine and the opted-in recipient list are built. Message delivery (email and in-app) is honest-off: a message is queued, not dispatched, until the delivery channel is provisioned — no message is delivered today. Texted (SMS) delivery is honest-off as well: carrier integration is not wired. We say so directly rather than imply live delivery.

Comms engine built · delivery honest-off

Season schedule — game calendar and event dates, the spine for every alert and photo day

The season schedule is designed to hold every game, practice, and event for a team: date, time, location, and opponent — the spine to which alerts and photo-day slots attach. The scheduling logic lives in the platform’s shared library today; the manager-facing schedule editor, the stored season calendar, and the family-facing event view are in active development and not yet available. The design is team-scoped: the schedule belongs to the team roster, not to a shared league calendar the team cannot control. We describe it as in development because that is the accurate status.

Scheduling logic present · editor + family view in development

Game-day texted alerts — reach every sports parent fast, in early access

The game-day alert is designed to reach opted-in family contacts when a game or event is approaching, cancelled, or relocated, roster-scoped so only that team’s families receive it. The scheduling logic that decides which families to alert and when lives in the platform’s shared library today; the alert delivery engine and its queue are in active development, not yet built. SMS carrier delivery is honest-off — carrier integration is not wired. Email and in-app delivery are honest-off as well: a message is queued, not dispatched, until the delivery channel is provisioned. No alert is delivered today. A conversation is the honest next step to understand the timeline.

Scheduling logic present · delivery in development

Team photo-day store — parent ordering and print delivery, in early access

The team photo-day store connects the team’s picture day to a parent-facing ordering surface: team photos, individual portraits, and digital downloads, all scoped to the roster. The photo-day coordination layer — slot scheduling, photographer assignment, and order catalog management — is built on the platform’s commerce layer. The parent-facing photo-day ordering interface is in early access: a family browses portraits and places an order there once it goes live. The money rail that accepts payment from a parent is honest-off: it exists in the platform but is not enabled for live transactions. No live parent store is available today. Minor student photos are consent-gated and access-controlled, and are never public without a released consent. A conversation is the honest next step to understand the photo-day early-access timeline.

Photo-day coordination built · parent ordering early access

Who uses it

Built for the coach, the team manager, and the sports parent — all running on one roster

Coaches

A coach imports the roster at the start of the season and the platform does the rest: family contacts matched, opt-in invitations sent, schedule up, and the first communication going to every opted-in family the same day. When a game moves, one schedule edit triggers the alert queue. A coach writes one message, not a group text to a contact list that gets stale. Photo day is coordinated through the same platform — no separate photographer email chain.

Team managers and club directors

A club director with five teams on the same platform sees each team’s roster, schedule, and communication log in one place. Each team’s family list is separate: a message to the U10 soccer team does not reach U14 baseball families. Photo day is coordinated per team within the same club session — one photographer booking, multiple team slots. Consent records are per-family, not per-team: a family with children on two teams opts in once. Data exports are available at any time: the club owns its roster history.

Sports parents

A sports parent opts in once and stays informed: the season schedule is visible in their family-facing view, communications come from the team through the platform, and game-day alerts (in early access) will fire as game time approaches. Photo day ordering — team portraits and individual prints — will be available through the platform’s parent ordering store when it goes live. A parent with two children on different teams sees both schedules in one family view. Consent can be withdrawn at any time: an opted-out family is removed from all lists immediately.

Minor player data & family consent — the non-negotiable layer

Minor player data is consent-gated, access-controlled, and never public — from the first roster import

Every player on a youth sports roster is a minor. Their data — name, age group, family contact, and photo — is not public. It is not shared with outside companies or advertisers. It is not visible to other families on the team. A family must opt in before their child’s information is used for any communication. Consent is collected at roster-import, not assumed after sign-up. Consent can be withdrawn at any time: an opted-out family is removed from the active list immediately.

Team photo day adds a second consent layer: minor player photos are consent-gated and access-controlled. A family’s photo is never public and never visible to another family. Facial recognition is off by default and is not used to match or identify a player in this flow. There is no public roster lookup that returns a player’s photo. The consent record is part of the onboarding agreement, not a footnote. If the organisation ever leaves the platform, every consent record and data record leaves with it — a full export in a portable format.

What is built and what is coming — plainly

The roster and comms engine are built; delivery is honest-off. Schedule, alerts, and the photo store are in development.

Built today: the team roster engine and family contact matching; the family communications engine (message composition and the opted-in recipient list); and the photo-day coordination layer with slot scheduling and catalog management. Honest-off: message delivery (email and in-app) — queued, not dispatched, until the delivery channel is provisioned. In active development: the season schedule editor and family-facing event view, and the game-day alert delivery engine.

In early access — built but not yet live for all teams: SMS carrier delivery for game-day texted alerts (the alert logic and foundation are built; the carrier integration is in active development); the parent-facing photo-day ordering interface (the coordination layer is built; the ordering store and checkout are not yet enabled); and the money rail that accepts payment from a parent at the photo-day store (honest-off — present in the platform, not enabled for live transactions). There is no live parent checkout today. No pricing commitment. No subscription.

Connected to the school platform

The team platform connects to the school platform — boosters, recognition, and the moment captured.

Youth Sports Software manages the team: roster, family comms, schedule, and photo day. School Booster Network is the sibling platform for the booster club behind the same athletes: gate-scan, concessions POS, and exact-cent fundraising for game night and show night. A team platform and a booster platform for the same program are a natural pair. Seen is the recognition layer: the programme that ensures every student athlete lands on a real page in the yearbook or the sports programme — adviser-approved and consent-verified. Assembly is the moment layer: live school events captured, ticketed, and archived — the Friday night game, the championship final, the senior night. For the broader school publishing platform, homeroom.software is the full picture.

schoolbooster.network seen.school assembly.school homeroom.software

Early access · Coaches, team managers, and club directors

Book a conversation to see the current state honestly

Youth Sports Software is in active development. We do conversations that show the current state honestly: how the roster import works, how the family opt-in consent is collected, how the season schedule drives the alert queue, and what the photo-day coordination layer looks like for a team. There is no pricing commitment and no signup. If it looks right for your team or club, we discuss what early access looks like.

To book: email [email protected].

FAQ

Common questions

What does “single source of truth” mean for a team?

A team typically lives across three or four tools: the roster in a spreadsheet, the schedule in a separate calendar app, family contact in a group text thread, photo day with a different service entirely. “Single source of truth” means the roster import feeds all of those surfaces on one platform: family comms draw from the same contact list as the schedule, the schedule drives the alert queue, and photo-day coordination is scoped to the same team record. A coach changes a game location once and it flows to the family-facing schedule and the alert queue. That is what a single source of truth means in practice — one import, everything downstream consistent.

Is the roster import live now? Can our team use it today?

The team roster engine and family contact matching are built: a coach or team manager can import the team list and invite families to opt in. The family communications engine composes a message and queues it against the opted-in list — but message delivery (email and in-app) is honest-off today: a message is queued, not dispatched, until the delivery channel is provisioned. The season schedule is in active development — the scheduling logic is present, the editor and family-facing view are not yet built. SMS carrier delivery and the parent-facing photo-day ordering store are honest-off. A conversation is the honest next step to understand the current state for your team.

Are game-day texted alerts live?

Not yet. Texted alerts are honest-off. The scheduling logic that decides which families to alert and when lives in the platform’s shared library, but the alert delivery engine is in active development, and SMS carrier integration is not wired. Email and in-app delivery are honest-off as well — a message is queued, not dispatched, until the delivery channel is provisioned. There is no staged rollout underway; the platform is pre-launch. A conversation is the honest next step to understand the timeline.

How does the team photo-day store work?

The photo-day store connects the team’s picture day to a parent ordering surface. The coordination layer — slot scheduling, photographer handoff, and catalog management — is built on the platform’s commerce layer. A photo day can be scheduled, photographers assigned, and the order catalog configured. The parent-facing ordering interface — where a family browses portraits and places an order — is in early access. The money rail that accepts payment from a parent is honest-off: it exists in the platform but is not enabled for live transactions today. No live store. A conversation is the honest next step for understanding the photo-day timeline for your team.

What about minors’ data and consent? Is my child’s information safe?

Minor player data is consent-gated and access-controlled, and is never public without a released consent. A family must opt in before their child’s information is added to any communication list. Consent is not assumed — it is collected at roster-import. Consent can be withdrawn at any time: a family that opts out is removed from the communication list and their contact information is no longer used. Minor player photos from team photo day are never public without a released consent, and are never shared with outside companies or advertisers. Facial recognition is off by default and is not used to match or identify a player in this flow; there is no public lookup. The team owns its player data. The organisation can request a full data export at any time.

Can coaches send messages to families right now?

A coach can compose a message today and the platform queues it against the opted-in family list for that team — only families who have opted in are on the list, and a family with two children on the team is one recipient, not two. But message delivery is honest-off: the message is queued, not dispatched, until the delivery channel is provisioned — no email, in-app, or SMS message is delivered today. We describe the model plainly rather than imply live delivery.

How does opt-in consent work for family communications?

When a coach imports the roster, the platform generates an opt-in invitation for each family on the list. The family receives the invitation and chooses to opt in to communications from the team. No message is sent to any family before they opt in — not a welcome email, not a season opener, not a game reminder. Consent is recorded at the family level: if a family has two children on the team, one opt-in covers both. Consent can be withdrawn at any time. A family that opts out is removed from the active communication list immediately. The organisation never receives a communication list it did not build through this opt-in process.

What can a team use today versus what is still coming?

Built today: the team roster import and family contact matching, and the family communications engine (message composition + the opted-in recipient list). Honest-off: message delivery (email and in-app) — a message is queued, not dispatched, until the delivery channel is provisioned; SMS carrier delivery; and the money rail that accepts payment from a parent. In active development: the season schedule editor and family-facing event view (the scheduling logic is present), the game-day alert delivery engine, and the parent-facing photo-day ordering interface. These are the accurate statuses — we do not call queued delivery ‘live.’

How is this different from a general group-messaging app?

A group-messaging app holds contacts and sends messages. Youth Sports Software is built around the team roster: the family contact list comes from the roster import, not from manually entering phone numbers. The schedule is tied to the same record: a game change propagates to the alert queue automatically. Photo-day coordination is scoped to the team roster: every player on the import gets a slot, and the parent-ordering surface knows which family is ordering for which player. The consent layer is purpose-built for minor players: opt-in before any message, revocable at any time, with minor data never public. A general messaging app does not do any of that.

Can a club with multiple teams use the platform?

Yes. A club director or multi-team manager creates a team record for each team in the club. Each team has its own roster, its own family communication list, and its own schedule. Families on multiple teams see a unified family-facing view with all their children’s schedules and communications. Communications are always scoped to the team that sent them — a message from the U10 soccer coach does not go to the U14 baseball families. Photo day can be coordinated per team within the same club session. The opt-in consent is per-family per-club, not per-team: a family with children on two teams opts in once.

When will the full platform be live for every team?

The platform is pre-launch. The roster and the family communications engine are built; message delivery (email and in-app) is honest-off; the season schedule editor and family view are in active development; SMS carrier delivery is honest-off with no rollout underway. The parent-facing photo-day ordering store and the money rail that accepts payment are honest-off — the coordination layer is built, the ordering interface and checkout are not enabled for live transactions. A conversation is the honest next step — we walk through exactly what is built, what is queued-not-sent, and what is still in development.