School timetable

How this works in a running school

A timetable is only useful to the rest of the platform if other modules read it. Period attendance registers, teacher workload views, substitute cover, and room allocation should all derive from the timetable rather than being maintained separately, because a timetable change that does not propagate is worse than no timetable at all: staff act on stale information with confidence.

Construction is a separate question from consumption. Many schools build the timetable outside the platform, in a specialist tool or a spreadsheet, and need to load the result. Whether that import is practical matters more than whether the platform has an automatic generator.

What to check when evaluating it

• Whether period attendance registers derive from the timetable automatically.
• How a mid-term timetable change propagates to registers and teacher views.
• Whether an externally built timetable can be imported without manual re-entry.
• How substitute cover is recorded and whether the covering teacher gets the register.
• Whether clashes for teachers and rooms are detected at entry.
• How the timetable relates to the academic calendar for holidays and shortened days.

What it costs to get wrong

A timetable that does not propagate is actively dangerous rather than merely unhelpful, because staff act on it with confidence. A covering teacher who opens the wrong register records attendance for a class they are not teaching, and the student who was actually absent is marked present. Errors of that kind are hard to detect and matter in exactly the situations where attendance records are later scrutinised. Checking that a mid-term change reaches the register is a five-minute test.

School timetable: common questions

What does timetable software do in a school platform?

It assigns subjects, teachers, periods, and rooms to sections for an academic year, and provides that structure to the modules that depend on it: period attendance, teacher workload, substitute cover, and room usage.

Its value is largely in what it feeds rather than in the grid itself.

Can we import a timetable built elsewhere?

Many schools need to, having built the timetable in a specialist scheduling tool.

Confirm the import format and whether changes can be re-imported, because a one-time import that cannot be updated leaves you re-entering every subsequent change.

How are substitutions handled?

By recording cover against the affected periods so the covering teacher receives the register and the workload view reflects reality.

If substitution is tracked on paper, period attendance for covered classes tends to go unrecorded.

Who should be able to change a published timetable?

A small set of roles, with changes visible to affected teachers.

Distributed editing produces conflicting versions and, because other modules read the timetable, an unnoticed change propagates into attendance registers before anyone reviews it.