A parent is not simply a member who does not train. A child is not a small attachment to an adult profile. When software starts with the wrong model, every booking, payment and permission becomes harder to understand.
Give every person the correct role
The system should know who trains, who can make decisions for a child and who is responsible for payment. Those facts may point to the same adult, but they are not the same role.
Clear roles reduce mistakes and make the member experience easier to understand.
- Parent or guardian
- Child student
- Adult student
- Household payer
Keep the training record with the child
Bookings, attendance, curriculum exposure and progress belong to the child who trains. The parent needs permission to see and manage them, but the records should not move into the parent profile.
Let the household connect rather than merge people
A household creates the relationship between people. It allows the school to understand the family without turning several identities into one confusing account.
This becomes especially important when one parent pays, another parent manages bookings, and more than one child attends different programmes.
Skull OS arrives January 2027
Apply for early access