In most Nepali schools, the timetable lives in one place: a large sheet of paper taped to the staff room wall, a whiteboard that gets wiped and redrawn by hand every term, or a spreadsheet on one admin's laptop that nobody else quite knows how to edit. It works, until it doesn't. A teacher calls in sick at seven in the morning. Two sections turn out to share the same teacher during the same period, an error nobody notices until both classrooms are waiting. A substitute walks in fifteen minutes late because it took that long to figure out who was even supposed to cover the class. None of this is really a technology problem. It is an operations problem that technology happens to be reasonably good at solving.
Where the timetable actually lives
Building a whole-school timetable by hand is tedious in a specific way that is easy to underestimate from the outside. Every section has its own set of subjects. Every teacher has a limited number of periods they can realistically take, and preferences about which ones. Every classroom, if the school is short on rooms, has to be shared. Getting all of that to fit into a single week, without contradictions, usually falls on one person — a vice principal, a senior teacher, or whoever in the office has the patience for it. That person builds the routine once, then spends the rest of the year quietly patching it whenever something changes: a new teacher joins, a section grows too large and splits in two, someone's schedule needs adjusting mid-term. Each patch is a small opportunity for something to slip.
Starting from the bell schedule, not a blank grid
We built the Class Routine planner to start from something the school has already decided: its period template. Every school sets its own bell schedule — how many periods make up a day, what time each one starts and ends, where the breaks sit. That template is the frame the whole routine hangs on. From there, the class teacher or an admin fills in a weekly grid, days across the top and periods down the side, and for each cell assigns a subject and the teacher who takes it. There is nothing exotic about the grid itself; it looks like the timetable a school already keeps, just digitised. The difference is what happens once it exists as structured data rather than ink on a whiteboard.
The check nobody has time to do by hand
Once every section's routine is entered, the system can do something that is genuinely difficult to do by hand across an entire school: check whether the same teacher has been scheduled in two different sections at the same period. On paper, this kind of double-booking is easy to miss. A school with fifteen sections and eight periods a day has well over a hundred teacher assignments to track every week, and a senior teacher building the master timetable is not going to catch every collision by eye, especially when the routine gets revised mid-year. The planner flags these conflicts automatically, at the moment they are created, rather than on the morning a teacher is expected in two rooms at once.
The value here has nothing to do with anything clever. It is one overworked person no longer having to hold an entire school's timetable in their head at once.
A teacher's own week, not the whole school's
A whole-school routine, once it is built, is genuinely useful to almost nobody in its raw form — it is too large for any one teacher to read at a glance. A teacher who takes Science for three different sections does not want to scan a master timetable looking for their own name in each column. So every teacher gets a "My Teaching" view: just their periods, their sections, their subjects, pulled automatically from the whole-school routine as it changes. It sounds like a small convenience, and it is, but it removes a piece of friction that used to repeat itself every single day — checking a shared, cluttered document to answer a question that is really only about one person's own week.
When a teacher is absent
The harder problem is what happens when a teacher cannot come in. This is where a paper timetable stops helping entirely — a whiteboard has no memory of who is free during a given period, only of who is normally supposed to be there. Our substitution workflow tracks teacher availability and absence, so when someone is marked out for the day, the system can show which of their periods need covering and which other teachers are actually free at that time, rather than leaving the question to whoever happens to be standing in the staff room when the problem comes up. An admin or the class teacher assigns a substitute for each affected period, and that assignment shows up in the substitute's own "My Teaching" view for the day, so there is no ambiguity about who is walking into which classroom.
This does not make the decision of who should substitute for what. A teacher covering a subject well outside their own is still a real trade-off a school has to weigh, and the system does not pretend otherwise — it simply makes the free periods and the gap visible quickly, instead of everyone finding out by trial and error over the first ten minutes of a lesson.
A quieter kind of software
Schools around the world have been moving timetabling off paper and whiteboards and into dedicated software for a couple of decades now, for reasons that have very little to do with any particular new technology and a lot to do with plain reliability — a shared system that everyone can check, that updates in one place rather than several, and that does not depend on one person's memory of every recent change. We built the Class Routine planner in that spirit rather than as an AI feature, because it isn't one, and forcing that framing onto a scheduling tool would not make it more useful. The one place where light automation genuinely earns its keep is exactly the double-booking check described above: a small, mechanical comparison that a computer can run instantly across an entire school's routine, and that a person, doing the same check by hand at the end of a long day, is fairly likely to get wrong at least once a term.
What this is, and what it isn't
None of this replaces the judgement a school already exercises about who teaches what, who is a fair fit to substitute for a colleague, or how a timetable should balance a teacher's morning against their afternoon. What it removes is the manual overhead around those decisions — the redrawing, the cross-referencing, the last-minute scramble in the staff room when someone doesn't show up. For the admin who used to own the whiteboard, that is not a small thing. It is one fewer piece of the school that lives entirely in someone's head, and one fewer morning where a class sits waiting because nobody was quite sure whose turn it was to walk in.