Features
Everything a season needs, and not much else.
A youth-sport product succeeds on a small number of things done exactly right: a schedule that survives change, a headcount you can trust, and a message that reaches both parents. The rest is scaffolding around those three.
Schedule
Fourteen changes, and the answer stays correct
Nobody struggles to enter the first practice. The difficulty is the Wednesday in November when the pitch is unplayable, the away game moves an hour, and half the squad has already answered the old question.
- Repeat a practice weekly, fortnightly, or on the second and fourth Tuesday. Edit one occurrence, this one and the ones after it, or the whole series — always as an explicit choice.
- Every event stores an exact instant plus the IANA zone the organiser meant. A tournament two states over does not drift when daylight saving ends.
- Move an event and answers to the old time are cleared, so the number on screen is a headcount for the new time and not a stale one.
- Arrive-by time, kit colour, referee status and a field note live on the event itself.
- Conflicts are checked against every team the player is on, including teams in other clubs, on every plan.
Attendance
The useful list is the one nobody has filled in
A coach does not need to see fourteen names that said yes. They need the three that said nothing, and a way to ask them again without messaging the other seventeen.
- Going, maybe, out — each with an optional note, on every plan including free.
- Nudge only the families who have not answered, through the channels each of them has opted into.
- An optional cutoff freezes the count, so Saturday's plan is made against a number that has stopped moving.
- Either guardian can answer, and both see the answer. A player is never marked absent because the wrong parent got the message.
- Colour never carries the meaning alone: going, maybe and out each have a distinct glyph, and the three separate in greyscale as well as in hue.
Messaging
A message that arrives, and can be proven to have arrived
Weather cancellations are the reason messaging matters. At 7am on a Saturday, an email is not a channel — a text message is. Ours goes through a carrier messaging API with recorded consent, delivery receipts and real unsubscribe handling.
- Threaded channels per topic rather than one firehose, with read receipts and inline media.
- Target by role and by division at the same time — every coach in U12, with an attachment — and save it as a template for next time.
- SMS consent is recorded per contact with a timestamp, and an unsubscribe is honoured everywhere, permanently.
- Message history is permanent and searchable. Nothing expires out of the record at ninety days.
- A parent mutes chat mentions without muting a cancellation. Notification categories are separate, and the safety-critical ones are the last to go.
Households, guardians and money. Modelled the way a family actually works.
One invoice per household
Two children on two teams appear on one bill, paid with one card, incurring one transaction fee. Sibling discounts and early-bird pricing apply at checkout rather than being computed by hand in a spreadsheet.
Two guardians, equally
Both guardians receive every notification, can answer an RSVP, can pay, and can see the same threads. Neither is a secondary contact by default, which matters most in the households where it matters most.
Financial aid without a phone call
A family applies inside the product — need statement, supporting documents, an approval state — and an approved award applies itself at checkout. Nobody has to ask the treasurer for a favour in person.
Instalments that recover
A failed payment is retried on a schedule you set, and the dunning notice reaches every guardian on the household — not one address on a BCC line that nobody reads.
Refunds that behave
Refund a whole program in one action. Partial refunds return the processing fee proportionally, and the balance owed adjusts itself.
One dashboard per coach
Coaching three sides is normal. One screen shows the combined calendar, the unread messages and the outstanding RSVPs across all of them, rather than three logins and a guess.
Documents & consent
A signature that would survive being questioned
A tick box that says “I acknowledge” is not a signature, and a club that finds this out during an insurance claim finds it out at the worst possible moment.
- Each signature records the signing time, the signer's IP, and a hash of the exact document version that was on screen.
- Export every signed document for a season or a program in one action, for an audit or a renewal.
- Medical forms, physicals and birth certificates upload against a player and are readable only by the roles the schema names.
- Health check-ins keep the same split a good policy needs: the coach sees cleared or not cleared, and never the reason.
- Coach certifications carry expiry dates, send their own renewal reminders, and block a roster assignment when they lapse.
Game day
One scorer, on the web as well as the phone
A live score that anyone present can edit is not a score, it is a rumour. One person holds the official scorer role for a fixture, and the record shows who that was.
- Live score, clock and play-by-play, in a browser as well as the app, so the grandparent on a laptop is not excluded.
- A follow link for extended family that shows the score and nothing about the roster.
- Lineups and batting orders built before the game, sport-agnostic, not bolted to live scoring.
- Results roll into division standings, and a player's statistics follow the player across seasons and teams rather than resetting when a team is recreated.
API & webhooks
Your club's data, reachable by your club's tools
Clubs run on more than one system. Without an API, keeping them in step means a volunteer exporting a CSV every Sunday night — and forgetting one Sunday in four.
Webhooks for the events that matter
roster.changed, payment.failed, event.rescheduled, registration.completed — delivered with retries and a visible delivery log.
Read and write, with real keys
Scoped API keys per integration, revocable individually, with a request log so an admin can see what a key has actually done.
Calendar feeds that stay subscribed
One webcal feed per family covering every child and team, so a phone calendar is set up once and stays correct.
Export without asking
Roster, schedule, payments and signed documents export as CSV or PDF on demand. Leaving is a normal action, not a support ticket.