Clashes caught while you build
Because Msomi already knows teacher-to-subject-to-stream allocation, it can tell you that you have just put the same teacher in two rooms at once — at the moment you do it, not on Monday morning.
Academics
Timetables
Build it once, and everyone sees their own version of it.
Standard plan and above
Why it matters
Everyone gets their own view
One timetable, seen four ways: the master grid for the deputy, a personal teaching schedule for each teacher, a daily list for each stream, and their child's day for a parent.
Load you can actually see
Teaching load per teacher and per department is visible as you build, so an unbalanced allocation shows up during planning rather than in a grievance six weeks later.
Timetabling is the piece of school administration most likely to be done on a wall chart with sticky notes, and the piece where a single mistake is discovered by forty learners sitting in an empty room.
Msomi builds the timetable on top of information the system already holds. It knows which teachers exist, which subjects they teach, and which streams they teach them to, so it can check every placement against every other placement as you make it.
Four views of one thing
The value of a timetable in a system rather than on a wall is that it can be sliced. The deputy sees the master grid. A teacher sees only their own week. A stream sees its own day. A parent, in their app, sees what their child is doing this afternoon. All four are the same underlying data, so a change made once is a change made everywhere.
Teaching load is summarised while you build. Balancing allocation across a department becomes a matter of reading a column rather than counting sticky notes.
Works with
Next step
See Timetables working on your school data
A demo runs about forty minutes and uses your own class lists, frameworks and grading — so you are looking at your school rather than a sample database.
Or try it first — the Trial tier gives you a full term, free, with every module unlocked.