Teachora.ai: Lecture & Substitution Management

The problem

Every school with a period-based timetable has the same morning: a teacher calls in, and someone has to work out who covers each of their lectures. Doing it by hand means checking timetables for who is free, remembering who already covered yesterday, and hoping nobody gets booked twice. The same reliable teachers end up carrying the load, and there is no record of why a decision was made.

How it works

Teachora turns leave approval into an automated substitution workflow:

1. An admin, or the teacher, creates a leave.
2. On approval, Teachora generates every lecture that leave affects that day.
3. Auto-assign ranks the eligible teachers: free that period, on that campus, and under their limits.
4. Workload caps keep it fair — one extra lecture a day, plus weekly and monthly limits the school sets (two and eight by default).
5. Admins can assign by hand, or override a limit in an emergency with a recorded reason.
6. Cancelling a leave or a substitution releases the workload and clears the board.

Built for multi-campus schools

Each campus is isolated: its own timetable, staff and cover board, switched from one place, so a deployment with a Main and a Junior campus never mixes the two. Around the substitution engine sits the rest of the day-to-day operation:

• A leaves list and a substitutions board for admins
• Weekly timetables with conflict checks
• Roles for Super Admin, Admin, Editor and Teacher, with staff login accounts
• Settings, data import, reports, and login history for platform admins
• An installable PWA with web push, so cover decisions don't wait for a desktop

Teachers apply for leave and see their own timetable; admins see everything for their campus.

Engineering

Built on Next.js 16 and React 19 with route handlers validated by Zod, Auth.js credentials sign-in, and PostgreSQL on Neon through Prisma 7. Web Push uses VAPID keys, and the scheduling rules are covered by Vitest.