Sub coverage that doesn't make Christina chase three people
Teacher raises a sub request. It fans out to front desk, owners, and qualified teachers. First-to-claim locks. The original teacher sees it happen.
The story
A teacher can't make a class. The current playbook: the teacher emails Christina. Christina emails Mike. Mike texts three other teachers. One of them says yes; the other two find out by accident two days later. Parents find out by accident too.
Pirouette: the teacher raises a sub request from their mobile app. The request lands in the sub-request inbox seen by Christina, Mike, Michelle, and qualified teachers. The first one to tap 'I'll cover it' locks the assignment. The lesson-plan handoff thread auto-opens between the original teacher and the sub. Parents get a notification only after the sub is confirmed.
What this looks like in practice
- Multi-stakeholder inbox: front desk, owners, qualified teachers see the request
- First-claim locks the assignment — no two people coordinating the same gap
- Lesson-plan handoff thread auto-opens between original teacher and sub
- Parents notified after confirmation, not at the moment of the original request
- Live status on the original teacher's app: 'Maria claimed at 9:42 AM'
Related
The whole year in one view. No joining across separate tables. Season at the top, sessions on the day.
Teacher opens the app, sees today's class roster, taps a kid, the kid is present. No drilling, no laptop, no end-of-day catch-up.
Want to see this running on your studio's data?
Walk through a demo with us. We'll show this feature in context against the day-to-day workflow your studio actually has.