How to make a school timetable, step by step
Whether you build it in a register, in a spreadsheet or in software, a timetable comes together in a fixed order — and almost every rebuild happens because a decision was taken out of that order. Here is the sequence, what each step actually decides, and where weeks get lost.
The seven steps, in the order they have to happen
- Fix the shape of the day before anything elseHow many teaching periods, how long each one is, where assembly, breaks and lunch fall, and whether the day is different for primary and senior school. Every later decision is measured in these squares, so changing the bell schedule after you have placed lessons means placing them again.
- Decide the working week, including SaturdayFive days or six, and if six, whether Saturday is a full day, a half day or off — and whether that answer is the same for every grade. A per-grade Saturday is normal in India and is the single most common reason a timetable built for "the school" has to be redone per section.
- List classes and sections, not just gradesGrade 8 with three sections is three timetables that compete for the same Maths teacher. The competition is the problem you are actually solving, so it has to be visible from the start.
- Set the curriculum: periods per week, per subject, per gradeThis is where a board’s scheme of studies comes in, and it is the step most often done by memory. Get the weekly allocation right per grade before anyone thinks about which square anything goes in.
- Map teachers to subjects and sections, with load capsWho can teach what, and how many periods a week each person may carry. This is the step that decides whether a solution exists at all: if the periods demanded by the curriculum exceed what your staff can supply, no arrangement of squares will fix it, and finding that out in week three is a wasted week.
- Write down the rules you actually care aboutMaths in the morning. No teacher takes more than two periods back to back. Science gets a double for labs. Games is never the period before lunch. These are the rules that make a timetable feel good to teach rather than merely legal, and they must be stated before generation, not enforced by hand afterwards.
- Only now place the periods — then check by teacher, not by classA grid that reads perfectly class by class can still give one teacher seven periods on Monday and none on Friday. Every class timetable has a teacher timetable hiding behind it, and the teacher view is the one that tells you whether the week is humane.
The three mistakes that cost a week
- Placing lessons before checking staff capacity — if the curriculum needs 41 periods of Maths across the school and your Maths teachers can supply 34, the timetable is not late — it is impossible. Compare demand against supply before placing anything.
- Treating doubles as two periods that happen to be adjacent — they will drift apart the first time anything moves. A double is one block, and it has to be scheduled as one.
- Checking only the class view — clashes show up there, but exhaustion does not. Read every teacher’s week before you publish, or you will hear about it in the staff room in the first fortnight.
Doing it by hand versus generating it
Steps one to six are the school’s decisions and no software can take them for you — they are what your school is. Step seven is arithmetic: several thousand constraints checked against each other until nothing contradicts. That is the step that takes a coordinator two or three weeks, and the only step a machine is genuinely better at.
WeekWise is built around exactly that division of labour. It asks you steps one to six as plain questions, and does step seven in one pass — a clash-free, board-aligned week for every class and every teacher. After that you edit it all year, with a live clash check on every change. Open the live demo to see a solved school before deciding.