SERVICE 01 · Academy operating system
Lessons, homework, make-ups, counselling —
joined per student.
Attendance apps exist. I build what comes after: records that accumulate per student and drive homework, make-ups and parent updates — the system I use while teaching.
IF THIS SOUNDS FAMILIAR
One of these is enough
- Parent calls mean digging through spreadsheets
- Every TA records differently
- Parent texts are retyped daily
- Scores stay, reasons vanish
- The director's judgement doesn't transfer
WHAT I DO
In this order
- Weeks 1–2
Diagnose the current records
Map where the same data is carried by hand.
- Weeks 3–4
Connect the most painful flow first
Usually lesson record → parent update, live first.
- Months 2–3
Converge on the student
Clinic, make-ups and counselling join the student record.
- Then
Turn judgement into rules
The system suggests the next action by your rules.
YOU RECEIVE
What stays with you
- Staff workspace
- Monthly parent viewer
- Per-student record and class analytics
- Auto-assembled parent texts
- Written rules and staff handover
CASE 01 · English academy
Academy lessons, attendance & homework
Enter once after class; counselling, texts and the parent view follow.
Read the case →SCOPE
Included and separate
- Current-workflow diagnosis
- Unified student records
- Lesson and clinic workflow
- Parent view
- Handover
Quoted separately
- Replacing billing apps
- Reusing client materials
- Material without clear rights
FAQ
Common questions
Do I drop my attendance app?
No — it stays; I connect what comes after.
Will staff adapt?
Screens follow your current sheet order; training in week one.
Who owns the data?
The academy's, in its own account.