Timetable.

A timetable is a promise the whole school has to keep at once.

• Bell schedules & periods

  Define the school day once — period numbers, start and end times, breaks, lunch, assembly — then attach it to the classes that run on it. The bell schedule is the spine every timetable hangs from.

• Auto-scheduler

  Set when school ends, how often to break and whether to keep lunch, and the day fills itself — teaching periods, breaks and lunch laid out end to end. You fine-tune; you don't draw a grid by hand.

• Class timetables

  Drop a subject, teacher and room into each cell of the weekly grid. Track completion per class, view every section at once, and run parallel optional subjects in the same period through optional blocks.

• Per-teacher view

  Pick a teacher and see their week the way they live it — periods, days and classes across the grid, with a count of the load they carry, ready to export and hand over.

• Rooms & buildings

  Model the campus as buildings, floors and rooms — each with a capacity — then allocate a room to every period. Conflict checks catch the double-booked lab before it ever reaches the wall.

• Non-academic periods

  Assembly, PT, library and the rest aren't afterthoughts. Define non-academic components with their own colour and staff, then place them on the grid alongside the teaching periods they share the day with.

• Day-to-day adjustments

  A teacher is out; the day still has to run. Pick the date, see who's absent and which periods are covered, and assign a substitute with work instructions — covered and uncovered counted in plain sight.

• Resolved by the day

  Schedules carry effective dates and target days, so the grid that shows on the eighth Monday is the one that actually applies — resolved by branch, session, class, section and date, not by a stale default.

• 01 / 04

  Resolved by the moment, not a default. Every grid is worked out for one tenant, branch, session, class and section on a given date — so the timetable a class sees is the one that actually applies that day, week eight included.

• 02 / 04

  Kept separate by campus and year. Bell schedules, rooms and timetables live inside the same branch-and-session walls as the rest of the platform — a multi-campus trust keeps each campus's clock its own, and last year's grid stays last year's.

• 03 / 04

  On the same web, iOS and Android apps. An administrator builds the week from a desk; a teacher checks their next period — or who's covering it — from a phone. No separate timetable login, no second copy to keep in step.

• 04 / 04

  Within reach of Sol, the AI agent. The same assistant that answers questions across the school sits over the timetable too — a quiet way to ask who's free fourth period or what changed today, not a fourth tool to learn.

Why it matters

Every school runs on a bell. Ours keeps the whole building on the same one.