School Timetable Software
School timetable software builds a weekly schedule by taking teacher availability, class lesson loads and room capacity into account simultaneously. Apakademia enforces three rules throughout: a teacher can be in one place at a time, a class can be in one lesson at a time, and a room can host one group at a time. Because these are hard constraints rather than post-hoc checks, clashes cannot occur.
What a timetable program has to solve
The difficulty of school scheduling comes from dependency, not from volume. In an institution running six days a week with twelve periods a day, each class has 72 slots. A school with twenty forms needs roughly 700 lesson placements per week — and every placement narrows the options for the rest.
Placing one lesson requires three simultaneous checks. Move that lesson later, and all three checks must run again for every directly or indirectly related lesson. Administrators describe this as "I moved one hour and five teachers' schedules broke."
Constraints the software handles
Teacher availability
Each teacher has a weekly grid of available days and periods. Unmarked slots are never used. Part-time staff, teachers who attend on fixed days and those shared with other institutions are all managed through this grid.
Class lesson loads
How many periods of each subject a form takes per week. Compulsory and elective subjects are entered separately, and subjects taught jointly by two teachers are supported.
Rooms and specialist facilities
Laboratories, sports halls, IT rooms and music rooms are limited resources. The software prevents the same room from being assigned to two groups in the same period, and runs a separate room verification pass after generation.
Double and triple periods
A subject can be set to run for two or three consecutive periods, and the days those blocks may fall on can be restricted. Block integrity is preserved — a block is never split across a lunch break or the end of the day.
Different period structures per day
Weekdays with eight periods and Saturdays with five can be defined separately. The difference is reflected consistently across screens, exports and shared links.
Cross-campus teacher clashes
In multi-campus institutions, a shared teacher's availability can be defined per campus, and cross-campus clashes are enforced as hard constraints.
Setting up
- Import your data. Teachers, classes and subjects from spreadsheet templates; an existing timetable can be imported as XML.
- Mark availability. The weekly grid for each teacher.
- Define your rules. Blocks, daily period limits, room assignments, preferred ordering.
- Generate. A conflict-free timetable in a single operation. Any lesson that could not be placed is listed with its reason rather than silently dropped.
- Review and share. Whole-school, per class and per teacher views; PDF, Excel or shareable link.
Beyond the lesson timetable
Supervision rotas and exam timetables are planned in the same system. Duties are balanced across staff and never assigned during a teacher's lesson. Exam planning covers sessions, rooms and invigilators, with a matrix view showing every form at once.
Manual timetable software versus automatic scheduling
| Aspect | By hand | Timetable software |
|---|---|---|
| Time to build | Days | Minutes |
| Clash risk | High, manual checking | Prevented by construction |
| Cost of a change | Cascading breakage | Pin and regenerate |
| Cross-campus teachers | Invisible | Enforced constraint |
| Distribution | Paper, manual | Link, PDF, spreadsheet |
| Version control | Unclear | Everyone sees the current one |
Who it is for
Primary, middle and secondary schools; private schools, colleges, tutoring and revision centres. The same system serves a single-site school and a multi-campus institution — the more constrained the setup, the more time automatic planning saves.
The platform is not fixed to any one country's school structure. The number of days in a week, periods per day, period length, break patterns and non-teaching days are all defined by the institution.