The scariest document at any kids' sports venue is a printed roster from last Tuesday.
It has 14 names, no allergy list, an emergency contact whose number changed in March, and no way to tell which of the two Jameses is the one with the inhaler. The coach on the pitch is running a session for children whose critical information they can't see — because the "master sheet" was updated after the printout, or never updated at all.
For camps and clubs working with children, the roster isn't admin. It's a safety document. Here's how to build one that deserves the name.
What a proper roster carries
For every child, the coach needs — at the session, on a phone, in seconds:
- Full name and age group (not "B. Smith")
- Medical flags that matter pitch-side: allergies (especially anaphylaxis), asthma, diabetes, epilepsy, injuries
- Emergency contact: name and relationship, current mobile number
- Pickup authorization: who is allowed to collect this child
- Attendance status: present, absent, expected-late
And it must be live. A roster that was accurate on Monday is a liability on Saturday if a parent updated medical info on Wednesday.
The three failure modes of paper rosters
1. The stale printout. Medical info changes mid-season; paper doesn't. The allergy list on the clipboard is a snapshot of whenever someone last reprinted.
2. The knowledge gap. "Oh, Sarah's mum knows about the EpiPen" — critical information living in one volunteer's memory. When that person isn't at the session, the information isn't either.
3. The privacy leak. Full medical details printed and left on a table, or a WhatsApp group where one parent's medical info is visible to twenty others. Medical data is sensitive data; the distribution method needs to respect that.
What good looks like
One source of truth per child. Medical info, emergency contacts, and pickup authorizations are entered once — at registration, by the parent — and flow to every session the child attends. No re-typing, no "can you send the allergy list again."
Live rosters on the coach's phone. The coach opens today's session and sees the current roster: who's booked, attendance marks, and medical flags. If a parent updates an allergy on Thursday, Saturday's coach sees it Saturday.
Attendance in three taps. Pitch-side marking — present, absent, late — from a phone, not a clipboard. Attendance data then feeds everything else: no-show follow-ups, invoice accuracy, safeguarding records.
Access control. Coaches see rosters for their sessions. Parents see their own children. Medical details aren't broadcast — they're served, scoped, and logged.
Setting this up (whether or not you use software)
If you're on paper/Excel today, the minimum viable version:
- Collect medical + emergency data at registration, in a structured form — not in email threads. Allergies, conditions, two emergency contacts with relationships, pickup authorizations.
- Timestamp it. A roster without a date is guesswork.
- Version-control the master. One file, one owner, changes dated. (This is the spreadsheet ceiling — it works until someone edits the wrong copy.)
- Brief coaches on changes weekly. Any medical-info change gets communicated to the session coach explicitly, not silently updated in a sheet.
- Review rosters before every session. 60 seconds per session: names, flags, contacts.
That process is exactly what Club Term automates: participants carry medical info and emergency contacts entered by parents; sessions generate live rosters; coaches mark attendance and see flags from their phone; access is scoped by role and family. The register stops being a document you maintain and becomes a view you trust.
The questions to ask of any system
Whether you're evaluating software or formalizing a paper process:
- Can a parent update medical info themselves, and does the change reach the next session's roster?
- Do coaches see rosters on their own phones, scoped to their sessions?
- Is attendance marked in seconds, and does it feed payment and no-show tracking?
- Is medical data visible only to those who need it?
If the answers are no, the roster is a liability wearing an admin costume.
Upgrade your rosters → — and if the money side of camp is the bigger headache, start with stopping payment chasing.