Ready for daily operations
Students, classes, lessons, attendance, leave, makeup, POS records, receipts and parent views.
Start with the operational foundations that are ready now, then add assisted or provider-dependent capabilities when your centre is ready for them.
Students, classes, lessons, attendance, leave, makeup, POS records, receipts and parent views.
Capacity, duplicate bookings, permissions, tenant ownership and audit history are checked on the server.
Payment providers, messaging automation and assisted migration are shown as setup work—not hidden promises.
Switch between the views your team uses every day. These are illustrative screens, not live centre data.
The team sees the same lesson-level decision in admin, teacher and parent views—not three versions of a timetable.
Saturday · 10:00 · Room A
A small operational decision can move from the front desk to a teacher, then to a parent—without rebuilding the story.
The lesson decision is recorded once.
Attendance and makeup context stay attached.
The parent view reflects the confirmed record.
This is not a wish list. Each capability is labelled so a centre can judge fit before starting a trial.
A family submits once; the centre can keep working from the same record.
One student record connects enrolment, lessons and payments.
Manage what really happens in each lesson, not only a repeating timetable.
From amount due to settled, every payment keeps a traceable history.
Return high-frequency questions to a clear parent self-service view.
Each role sees its work, and each centre keeps its own records.
30 days to test your real workflow. No credit card required.
Start free trial