Academic office
- Today: classes without attendance, students at risk, overdue fees
- Classes, make-up lessons, transfers, pauses; room and teacher clashes are refused
- Take payments, send receipts, bulk fee reminders
Kitelab English has two branches in Hanoi, 12 classes and about 120 students, and runs on a real management system, in a trial environment. Open your own copy of the centre and try it in four roles.
Every visitor gets a private copy with two months of data, deleted after 7 days without use. Enter your email in the top bar to really receive the emails sent to parents.
Each centre copy is a Durable Object that handles one request at a time: checking the timetable and writing the session is one transaction. Opening a clashing class shows exactly which class and lesson it clashes with.
What a family owes is never stored on its own: it is invoices minus payments, so the debt list, the reports and the parent portal always show the same number.
Monthly reports are drafted from attendance, scores and teacher notes; every number is checked against the data, and nothing reaches a parent until the teacher approves and sends it.
Permissions are enforced on the server for every call; the parent assistant only has tools that read the signed-in family’s records.
Absence notices, fee reminders, receipts and monthly reports are really emailed (to the inbox you enter) and shown as a Zalo OA preview; the Zalo connection comes with a production rollout.
Before each model call the worst-case cost is reserved; if it would cross the daily cap, the call is not made and the question goes to the office.