Timetabling
How a school builds a week and everyone else reads it — the days and hours you open, the rooms you have, who teaches what, the grid itself, and then the same fourteen lessons appearing as a teacher’s week, a pupil’s day and the register that gets taken in the lesson.
Built once by one person, read every day by six hundred
A timetable is the least glamorous thing a school owns and the most load-bearing. It decides where four hundred children are at ten past nine, which teacher is accountable for them, whether the laboratory is double-booked, and — quietly — what a register even is: you cannot mark a lesson that was never scheduled. EaseAcademia treats it that way. The grid is not a document the office publishes and everyone re-types; it is the record, and a teacher’s week, a pupil’s day and the subject register are all just different reads of it. This walkthrough follows one class — JSS 2A — from the constraints that shape its week to the moment a teacher marks a lesson that exists because somebody placed it.
On this page
What the week is allowed to look like
Nothing can be scheduled until three things are settled: when the school is open, what rooms it has, and who is qualified to stand in front of which class. None of these is timetabling software — they are the school describing itself — but every one of them is a constraint the grid will be checked against.
The days and hours you actually open
The operating schedule is the outer boundary of every timetable, register and attendance figure the platform will ever compute. A school running a half-day Saturday says so here, once, and no other screen has to be told.
The rooms you have to put lessons in
Rooms are records, not free text on a printout: each has a type, a capacity and a code. That is what lets the platform notice that the laboratory is booked twice at nine o’clock, or that a class of forty has been put in a room that seats thirty.
Who is allowed to teach what
The subject catalogue carries the teaching assignments the timetable will draw from. When the entry form offers a teacher for Mathematics, this is the list it is offering from — a teacher assigned here, not any employee on the payroll.
Ready to run your school on this?
Every screen in “What the week is allowed to look like” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Place the lessons
The grid is built one class at a time, and it can be built two ways — slot by slot when a school is adjusting something, or generated for a whole class in one pass when a term is being set up from scratch. Both write the same rows, which is the point: there is no “planner output” separate from the real timetable.
One class’s week
Every lesson JSS 2A sits, with its subject, its teacher and its room. Switching class switches the grid; filtering by day narrows it. This table is the timetable — not a view of one, not an export of one.
One lesson, placed
A slot is a subject, a teacher, a room, a day and a time — and the pickers are already narrowed to what this class can actually have. It is the screen where a timetable stops being a spreadsheet: the teacher list comes from the subject assignments, and the room list from the rooms the school owns.
Or generate the whole week
Placing thirty-five slots by hand at the start of a session is the work nobody has time for. The planner takes the class, the subjects and how many periods each needs, and lays out a week — which the office then adjusts on the same grid, because the output is ordinary timetable rows.
See this on your own school’s data.
Every screen in “Place the lessons” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
The same grid, sliced by who has to be there
A teacher never opens the school’s timetable. They open theirs — the lessons they are named on, across every class they teach, which for most secondary teachers is five or six different rooms in a day. Nobody assembled this; it is the same rows filtered by the teacher on them.
My week
Every lesson this teacher is named on, in day order, with the class and the room. The office scheduled JSS 2A; the teacher sees JSS 2A alongside every other class they hold, which is the view that actually gets them to the right door.
The register the timetable created
This is the payoff, and it is easy to miss: the lesson on this register exists because somebody placed it in step two. A subject register is per-lesson, and “which lesson” is a timetable row — which is why a school that timetables properly gets per-subject attendance for free, and one that does not cannot have it at all.
Set this up for your team.
Every screen in “The same grid, sliced by who has to be there” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
The end of “what have we got now?”
The last read, and the one the grid is really for. A pupil gets the same fourteen rows as their own week — on a phone, without a paper copy, and updated the moment the office changes something.
My week
The pupil’s own timetable: subject, teacher and room for every period, laid out by day. It is the office’s grid filtered to the class they are in — including the two electives they chose, because their subject list and their timetable are the same decision seen twice.
Today, and what is next
The pupil’s home screen answers the only timetable question anyone actually asks — what have I got now, and where. It is derived from the same rows, filtered to today and read against the clock.
Ready to run your school on this?
Every screen in “The end of “what have we got now?”” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Run your whole school on one connected platform
Start with the base package, switch on the modules you need, and give every parent, student and staff member a single place to log in.