One platform runs the whole school.

• Fully remote from day one: families join from the Gulf, the UK, North America, South Asia and beyond, with class times that suit their time zone.
• Live and interactive: short 25–35 minute sessions with songs, storytelling, flashcards and teacher prompts, never long lectures.
• Parents as co-educators: planning manuals, activity guides and parent workshops turn the home into the classroom.
• Character at the centre: Learning, Character and Leadership, with ten core values woven into everyday stories, for Play Group to Prep-II (ages 2 to 6).

• Proxy guard: sends signed-out users to login, everyone else to their own dashboard, and blocks cross-role pages.
• Role checks on every API: each sensitive endpoint confirms the caller's role before acting.
• Business rules on top: coordinators can't exceed the discount cap; only unpaid or rejected vouchers accept new proof.
• One login, many roles: sign in with email, phone or username; staff with several roles choose one at login.
• Parents see their own children: the parent portal shows only their own children's lectures, homework, attendance and fees.
• Teachers stay in their portal: teachers work in the teacher portal only and cannot open parent or student portals.

One record carries a family from first enquiry to live class. Each step is enforced in code, logged to the audit trail and sent to the right people by email or WhatsApp.

1. 01EnquiryThe parent fills in the contact form. A lead is created and a coordinator is alerted.04 · Admissions ↓
2. 02InterviewThe parent interview is tracked before the admission form is sent.04 · Admissions ↓
3. 03Admission formA personal link arrives by email and WhatsApp. Reminders follow at 10, 20 and 30 days until it is submitted.04 · Admissions ↓
4. 04Fee voucherSubmitting the form creates the admission record and its voucher, with any discount or scholarship applied.05 · Finance engine ↓
5. 05PaymentThe parent uploads proof on the public payment page, with no login. A coordinator approves or rejects it.06 · Payment verification ↓
6. 06AccountsApproval creates the parent and student accounts, enrols the child in a class and emails the logins.06 · Payment verification ↓
7. 07Live classesThe child joins lectures on Google Meet. Verified lectures, recordings and homework appear in the parent and student portals.07 · Learning engine ↓
8. 08Every monthA new voucher is issued. Unpaid dues carry forward, and an overdue voucher pauses access until its payment is approved.05 · Finance engine ↓

• One formula, protected: total = (regular fee + admission fee) − discount − scholarship, never below zero, itemised line by line.
• A discount cap for coordinators: set in fee settings (20% by default); admins can go further.
• Monthly batches: one voucher per enrolled student per class, numbered LMS-YYYYMM-####, emailed with a payment link.
• Carry-forward and gating: remaining = carried-in dues + this month − paid; an overdue monthly voucher pauses LMS access.

• Scheduled once, created everywhere: recurring lectures across chosen weekdays, each with a Google Calendar event and Meet link.
• Four Google Workspace APIs: Calendar, Meet, Admin Reports and Drive together prove who attended and find the recording.
• Teacher reports, coordinator decides: approve, reject (disputed), mark missed, or reschedule, each with a full trail.
• Families see verified lectures: recordings, attendance and homework appear in the parent and student portals.

• It reuses existing data: lead signals, interview answers, Meet recordings, fee history and attendance already exist.
• It reuses existing infrastructure: pgvector on the current Postgres; recordings already land in Drive.
• Humans stay in the loop: payments, grades, admissions and messages are drafts or scores a person confirms.
• It degrades gracefully: if an AI service is down, the manual flow still works, just like the Google integrations.