One person, one record
"Swimmer", "coach" and "guardian" are things a person does, never separate records. The coach whose own child swims is one person with two roles, not two rows that drift apart. Moving house updates one address.
What you can do today
Roster (needs read_roster, which nearly every staff role carries) gives you:
- A search by name across the club's people
- A person page with their details, household, roles and status
This is the screen you use to answer "who is this and are they ours".
What a person record holds
| Name, date of birth, gate photo | The identity the desk works from |
| Household | The family they belong to, and which one is primary |
| Roles | What they do in the club, dated |
| Emergency contacts | Who to call |
| Medical summary | A short line a deck coach can act on |
| Medical record | The full detail — needs read_medical, audited on every read |
The medical split is deliberate. A deck coach gets the summary they need to keep a child breathing. Nobody on deck needs a policy number, and every read of the full record writes an audit row naming who looked.
Archiving
A person can be archived rather than deleted. An archived person is red at the gate and the fix is to restore the record, not to wave them through — that refusal is one the front desk cannot override.
What is not built yet
- Editing a person from this screen — the reader is live; the registrar's write surface is still landing
- Bulk import from a spreadsheet — see Importing your club
- A do-not-release badge on the person and family cards — the underlying record is kept, the badge is not drawn yet