One Family, Several Players, Without Duplicate Admin
One parent brings two children to the club. The quickest administrative shortcut is to put everybody under the parent’s name or email and “sort it out later.”
Later arrives quickly. Ratings attach to the wrong person. Event registrations become ambiguous. A junior gets their own login but still has a duplicate profile. Club emails go to an address that was never theirs.
Family-friendly administration needs one convenient workflow without collapsing several people into one identity. For a club, the practical outcome is simple: register the right people, contact the right adult and avoid creating duplicate players.
Set up the people before the activity
A guardian may do the typing, but each player still needs their own profile.
That profile should hold the player’s name, membership, registrations, rating and competition history. A managed dependant without an email address is still a distinct person. Sharing the guardian’s profile may save one minute during setup and create years of data repair.
Before opening an event or league registration, check that each participant has one person record and that the adult who will handle administration is linked appropriately. Do not encode family structure by copying an email address across records or guessing that two people with the same surname are the same household.
ServeLeague’s household model gives one signed-in account a My family view across relevant clubs while preserving separate member and player profiles. The current capability focuses on household visibility, consent and managed profiles. It does not claim to cover every possible family arrangement.
Check who can act for whom
Families are not all the same. A useful model supports at least three situations:
- A dependant has no account, so the guardian manages the profile.
- A dependant later receives their own login but remains visible in the household.
- Another adult has their own account and must consent before a household link is created.
The words shown to users should make the distinction clear. The platform uses labels such as Child · you manage this profile and Child · has own login. Supported relationships also include partner and other family member, so “child” should never be the universal label.
Consent rules protect adults and account holders. A request to link somebody who has an account requires that person’s approval. A request involving an accountless member requires club-admin approval.
Clubs should verify relationships rather than infer them from attendance patterns. Arriving with a junior does not automatically make somebody their authorised guardian, and a shared surname proves little. Use the approval path and keep the relationship label accurate.
A guardian can act only for people they manage. They should not be able to edit an independent account holder merely because both people appear in the same household. The deeper permission and consent model is covered in Family Access Without Shared Accounts or Shared Identities.
Run registration around “who is playing?”
Once identity is sound, the practical benefit appears at registration.
The account holder signs in once, then chooses which household members are participating. Each selected player receives a separate registration. The system can apply that person’s membership, eligibility and payment state rather than treating the household as one entrant.
This is a better question than repeatedly asking for contact details: Who is playing?
The registration and waitlists tutorial covers the activity workflow. For membership administration, see managing memberships and payments.
Capacity rules should also remain person-based. Dependants count as separate members for family-plan capacity because they consume distinct membership and participation records. Convenience for the guardian should not make participants disappear from club counts.
Payment remains person-specific even when one adult pays for several entries. Each registration should stay attached to the correct participant so a sibling’s payment status or eligibility is not transferred by accident.
Email needs similar care. Do not invent an address for a dependant or copy the guardian’s address into every player record. Use the authorised adult as the practical contact while preserving the fact that the message concerns a different person.
Make family administration a repeatable club routine
Household administration is easier when the club uses the same checklist every time:
- Search before creating a new person.
- Confirm which household member is participating.
- Confirm who is authorised to manage that person.
- Keep membership, eligibility and registration attached to the participant.
- Use the adult’s contact route without pretending it belongs to the dependant.
- Review the relationship when a junior gains their own login.
Children grow up, partners join independently and guardianship changes. When a managed dependant gains a login, connect it to the existing person instead of creating a fresh player and abandoning the old rating. Confirm identity, test access and review the guardian’s remaining permissions.
The membership feature page explains the wider member context. Existing articles on member experience and membership management explore the difference between a useful member record and a billing row.
The test for a family workflow is simple: can a guardian do the necessary administration once, while every player keeps a correct identity and can become independent later?
If the answer is yes, the club has reduced repeated form filling without creating duplicate people. That is the organiser’s measure of success: the family can act together where convenient, while every entry, result and membership still belongs to the person who participated.