A family account should connect the adult responsible for administration with separate participant records for each child. One login can simplify the parent’s experience without combining the children’s classes, services or histories into a single record.
This distinction matters as soon as siblings join different groups. A question about one child’s membership should not require reception to reconstruct which schedule, payment or document belongs to whom.
Separate the guardian from the participant
The guardian is a person with contact details and an administrative relationship to a child. The child is the participant whose attendance, group and development the club records. Avoid putting the parent’s name in the class register simply because they completed the form.
Use a consistent participant identity as the child moves between levels or seasons. Recreating the child every time they join another group makes the training history harder to follow and creates extra work for the family.
Keep siblings’ services and histories distinct
Two children may train at different times, hold different plans and need different documents. The parent should be able to select the child concerned and review the relevant information. Staff should perform the same check before changing a booking or explaining a payment.
When reviewing family-account software, test this scenario directly. The presence of a parent phone-number field does not establish that the system supports separate child contexts within one account.
Connect documents with the right person and version
Identify which documents your organisation needs and whose acceptance is required for the workflow. Keep the relevant participant and document version associated with the record. Do not assume that one stored checkbox explains every later administrative question.
The software can organise records and acceptance history, while the organisation remains responsible for deciding which documents and procedures it needs. Review the actual setup during implementation instead of relying on a generic label such as “consents”.
Make messages clear about the child and class
A parent with two children should not have to guess which session a cancellation concerns. Include the relevant class and date, using the child’s context appropriately. Choose the recipient based on the administrative relationship and the communication rules.
Keep the result accessible to the staff who handle the family. A coach may need class context, while reception handles a membership question. Shared records should still respect those different access scopes.
Test the parent journey before launch
Create a representative family with two children in different groups. Review the timetable, available services, documents and a booking change for each child. Then ask reception to answer a question using the same records.
Klunivo’s members and families workflow supports connected guardian and participant records. For a broader teaching context, explore children’s activities and check how your actual group structure will be configured.
FAQ
Questions worth answering
Should siblings share one participant profile?
No. They can share a guardian relationship while keeping separate participant profiles and histories.
What should a family-account demo show?
A guardian switching between two children with different groups, services, attendance and document contexts.
Does one shared record mean every employee sees everything?
No. Staff access should match the person’s administrative, reception or coaching responsibilities.
