01
Create the Estate
The guardian signs in once and names the household. READYPLAY keeps authority over membership and permissions.
Family READYPLAY Studio · Nephew CMS Network
One roof.Every player kept distinct.
The Family Hub Estate gives guardians one workspace without turning a household into shared credentials or duplicate player records.
Guardian flow
A Studio for the whole family game day.
02
Add each player once
Every dependent receives a distinct player identity and athletic record—even without an Apple ID or separate account.
03
Confirm the protection boundary
Choose Under 18 or 18 and older. Minor consent is recorded only after an explicit guardian attestation.
04
Run the Studio
Choose Score as, start a game, open Family Coach, and review Cards, Stats, Training, and Schedule.
Authority map
Estate underneath. Studio on top.
READYPLAY API + PostgreSQL
Canonical identity, household roles, consent state, games, and stats.
Nephew CMS Network
Editable guidance and reversible projections—never private household storage.
Swift, Player Web, and Electron
Parallel working surfaces over the same guarded contracts.
Admin
Privacy-safe relationship health without guardian contact details or birthdays.
CMS-authored family guide
Run the Family Hub Estate
A guardian-first guide to the family network: canonical member identities, one READYPLAY Studio, and a protected record for every dependent.
One family network
The Family Hub Estate is the durable root for a household’s READYPLAY world. Each family member appears as a node in that network and keeps one canonical player or member identity. Joining the Family Hub Estate never creates a duplicate person.
Work from the READYPLAY Studio
The Studio is the operating surface inside the Estate:
- Add or manage the household roster.
- Choose Score as and confirm the right player.
- Start a game or Quick Pickup.
- Open Family Coach for courtside prompts and development notes.
- Review each member’s Card, Stats, and Training.
Protect the household
Never share guardian credentials. Keep phone numbers, birth dates, consent details, and other private family information out of public Player Cards and CMS content. Removing a member node from the household must not erase that person’s athletic history.
Built with Nephew CMS Network
Nephew CMS Network supplies the Estate and child-node projection grammar plus editable guidance. Player Web is the signed-in browser Studio, Electron securely projects that Studio on desktop, and Swift Native provides the courtside experience. READYPLAY API and PostgreSQL remain authoritative for identity, roster, permission, game, and stat data.
Product boundary: “Estate” is READYPLAY game-world language. Creating an account or household does not automatically form a legal estate, trust, or other juridical entity.
Guardian safety receipt
New managed players are classified as under 18 or 18 and older. If an older client does not provide an age choice, READYPLAY uses protected_unknown and applies the safer minor boundary. A minor is never marked guardian-verified without an explicit guardian attestation.
Linked members who own their READYPLAY account keep authority over their player profile. A household manager may organize the Estate relationship, but cannot silently rewrite that member’s sport identity.