Colleges and schools
Timetable
Timetable
Building it is the easy half. The hard half is the Tuesday a teacher is absent, which is the half this is built around.
What it does
The work it actually takes off you.
Built with the clashes visible
Slots are edited directly, moved in batches, and checked for conflicts as you go, against period profiles and your bell schedule rather than a generic grid.
Generated, for colleges
A college timetable can be generated automatically with lecture, tutorial, and practical loads respected, then reviewed as proposals you accept or reject rather than a result you are stuck with.
Substitutions with an approver
A substitution is requested, the covering teacher responds, and the HOD approves. It is scoped to a date, can be done in bulk for a longer absence, and keeps a history of who covered what.
Every teacher has their own view
Faculty see their own timetable on the web and in the mobile app, including the substitutions they have been given.
Draft, then publish
School timetables sit in draft with clash and workload warnings until you publish them, so a half-built grid is never what a parent sees.
Checked against the catalogue
Colleges can see the published semester’s coverage against what the curriculum requires, which is where a missing practical shows up.
Who touches it
By role.
Timetable in-charge
Builds, generates, resolves clashes, and publishes.
HOD
Approves or rejects substitution requests for the department.
Faculty
Sees their own week and requests a substitution.
Straight answers
What it does not do.
Every ERP demo looks complete. These are the edges of this one, stated here rather than found in month three.
- Automatic generation is a college feature. School timetables are built by hand and then maintained through substitutions.
- The machine-learning optimiser is optional; without it, generation uses built-in heuristics.
See timetable on your data
A demo runs this module against your own structure — your programs, your grades, your formats — rather than a sample dataset.