Club OS
Run a club's roster, schedule, packages and retention from one workspace. Built for the operator, not the coach — the line between the two surfaces is on purpose.
Club OS runs at os.avelok.com. One workspace per club, multiple admins per workspace, separate sign-in from Coach Studio (same account, different role).
What's on the home tab
A snapshot for the operator on a Monday morning:
Sessions scheduled, sessions taught (vs target), packages running out in the next 14 days, payment failures.
Who's attended < 50% of expected sessions in the last 4 weeks. Sortable by package value.
Cohort retention by intake month. Coloured red where this month's cohort underperforms the rolling average.
Hours per coach this week vs their working-hours setting. Flagged red if any coach is 80%+ utilised three weeks in a row.
The five tabs
Members
One row per member. Filterable by tier, package, coach, age band. Click for the member detail page — their packages, attendance, payment history. Not their AI conversations or session notes (that lives in Coach Studio, gated by player-level shares).
Common operations: bulk message a tier, run a make-up for a missed session, transfer a member between coaches.
Coaches
One row per coach. Their working hours, current roster size, lesson rate, hours taught this month, member retention. Click for the coach detail page — schedule, package usage, payouts.
Packages
Create a package: a number of lessons, an expiration window, a price, an attached coach (or "any coach"). Members consume the package as their coach logs sessions; consumption is automatic.
The package screen also shows the package P&L: sold this month, redeemed this month, ageing balance (lessons paid for and unused for > 90 days, which the club has a soft obligation to clear).
Schedule
Weekly multi-court grid, similar to Coach Studio's schedule but with all coaches and all courts at once. Drag-and-drop, conflict detection, public-holiday awareness.
Operations
A miscellaneous bucket for everything else: club settings, branding, ops automations (e.g. "if a member misses 3 sessions in a row, send a make-up offer"), exports, integrations.
Permissions inside the club
Two levels:
- Owner. Full access to everything, including financials and ops automations.
- Admin. All operational features, no ability to change billing, financials, or remove the owner.
Coaches working at the club do not get Club OS access by default. They see Coach Studio. If a head coach also helps run the club, they can be granted Admin in addition to their coach role — they then see both surfaces.
What clubs cannot see (worth re-stating)
Even an Owner can't read AI conversations, private session notes, or coach-player direct messages. The split between Club OS (member ops) and Coach Studio (memory + plans) is non-configurable by design.
Integrations
Today (limited, growing):
- Stripe — payments, refunds, payout reports
- WeChat Pay — payments, refunds (China region)
- CSV export — member roster, attendance, package consumption
- iCal feed — read-only schedule subscription
What's coming: see API roadmap.