Conflict-free timetable, and attendance in thirty seconds

A timetable engine that knows what it cannot do

Building a master timetable by hand is three days on a whiteboard, and the result still has a teacher in two rooms at once in period six on Thursday. The engine holds the constraints and refuses to break them, so a clash is impossible rather than merely unlikely:

• Teacher availability, maximum periods a day and weekly workload ceilings
• Lab and specialist-room capacity, so a practical cannot be scheduled into a full lab
• Subject period quotas per class per week, including doubles that must sit adjacent
• Period rotation across the cycle, so the same subject does not always land last period
• Reserved slots for assembly, games, library and house activity

Substitutions on the morning they are needed

A teacher calls in sick at 7:40am and somebody has to cover six periods before the first bell. The system already knows who is free, who is qualified for that subject, who has covered twice this week and who is on a half day, so the coordinator picks from a ranked list instead of ringing round the staffroom. The substitution reaches the covering teacher and updates the class timetable, so nobody is standing outside a locked room.

Attendance by exception, not by roll call

A teacher marking fifty students present one at a time is doing data entry for a database. Exception marking inverts it: everyone is present until touched, so a teacher taps only the absentees and the late arrivals. In a class of fifty with three absent, that is three taps and under thirty seconds. The register still records every student, because the data model has not changed — only the number of actions a human performs.

• Period-wise or day-wise marking, whichever your school actually runs
• Late arrivals and leaving-early recorded distinctly from a plain absence
• Bulk operations for a whole class on a trip or an exam day
• The parent sees the mark in their app the same morning, not in a monthly summary

Staff attendance without a biometric vendor

Geo-fenced mobile attendance for staff, so a teacher marks in from inside the school boundary and nowhere else. Leave requests, approvals and the balance that follows from them live in the same place, which means the leave approved on Tuesday is already reflected in Wednesday’s substitution list. No separate biometric device, no second vendor, no third database for HR to reconcile.

The front desk, offline

Visitor management is the piece every ERP forgets and every school needs daily: who came in, who they came to see, when they left, and the gate pass that proves it. It runs on the free desktop edition on the machine at the gate, with no internet connection, which is the only way a visitor register is reliable — a front desk that cannot log a visitor because the broadband is down falls straight back to a paper book.