A teacher calls in sick at 7:10 a.m. By 7:30 the coordinator has made four phone calls, the first period has started, and one class is sitting unsupervised while a message goes out asking for volunteers. Nobody decided anything. The morning simply absorbed the problem.

That is how ad-hoc cover starts, and if nothing changes, it becomes the default. Absence is not an exception in a school — it is a routine operational event, and it deserves a routine process rather than a daily emergency. The difference between a school that copes and one that lurches is rarely software. It is deciding in advance who decides, what counts as covered, and where the record lives.

Put the decision rights in writing

Most cover chaos is an ownership problem wearing a scheduling costume.

Name three distinct roles. The reporter — whoever learns first that a teacher will be away — raises it in one agreed place and does not try to solve it alone. The coordinator — the academic owner — decides what each affected period becomes. The approver, usually a principal or vice-principal, sets the limits of that authority rather than reviewing every decision.

Write the limits down too. How many periods a teacher may be asked to cover in a week, whether a scheduled free period is available for cover at all, when a class may be combined with another, when a period may be swapped rather than substituted, and when the coordinator must escalate before acting. Without stated limits, the same three willing teachers absorb every absence, and the process quietly depends on their goodwill rather than on a decision.

Separate the master timetable from the day’s plan

The single most useful discipline is that a substitution never overwrites the timetable.

The weekly timetable is the permanent model of who teaches what. Today’s cover is a dated overlay applied on top of it: this teacher, this class, this period, this date, this reason. Treat them as one artefact and two things go wrong. The timetable slowly corrupts as weeks of temporary changes accumulate, and a month later nobody can tell a planned allocation from a favour. Keeping them separate costs nothing and answers the question every coordinator eventually faces: who is actually supposed to be teaching this class?

Make the daily cover decision take minutes

A workable cover process has five steps and should fit on one screen.

Absence recorded. Teacher, dates and periods affected, marked as reported or approved. Keep the confidential reason out of the operational view — the coordinator needs impact, not medical detail.

Affected periods listed, not remembered. The affected week should surface itself, so nobody reconstructs it from a diary.

Candidate pool by capability. Teachers who can teach the subject, are genuinely free in that period, are not already committed, and are inside the workload limits. Capability first; familiarity and convenience second.

Assignment recorded against the date, with the name of whoever decided it.

People notified through official channels — the substitute, the class, and where it matters, the department head and the parent — rather than a personal message thread that disappears.

A connected staff attendance and substitution workflow helps here mainly because the absence, the affected periods and the eligible teachers sit in one place instead of three. The point is that the coordinator sees the options without a spreadsheet hunt. The decision stays human.

Record cover as an assignment, not an edit

Every cover arrangement should leave a dated record: which teacher covered which class, on which date, in place of whom, and at whose direction.

That record answers four questions that otherwise become arguments — whether the class was actually taught, how the additional load was distributed, how often a subject lost teaching time to cover, and what the arrangement cost the school.

Do not erase the record when the original teacher returns. Absence history is how a school notices that one department carries a disproportionate share of disruption, or that one subject is consistently the first to be dropped when the day goes wrong.

Protect fairness, because it is what quietly breaks

The usual failure is not a shortage of teachers. It is the depletion of a handful of helpful ones.

Watch three patterns. Repeat load — the same people covering repeatedly while others are never asked. Cover by convenience — the free periods of the same easy-to-find specialists always used first. Unrecorded generosity — staff rearranging their own teaching informally, which solves today and distorts everything downstream, including next month’s workload review.

How cover is treated for pay and workload is an institutional policy question. Schools should set that policy deliberately and confirm it against the applicable local requirements with qualified advice rather than assume a default. What the system must do is make the practice visible and countable, so the school applies its own policy consistently and can explain it if a member of staff asks.

What turns cover back into chaos

Five specific degradations are worth guarding against.

  • The morning group chat. Asking for volunteers in a message thread means the fastest responder decides, not the most suitable teacher. Keep the request inside the process.
  • The silent swap. Two teachers privately agree to exchange periods. The arrangement may be perfectly sensible; the problem is that the day’s plan and the official record now disagree, and a week later no one can reconstruct what happened.
  • The unclosed exception. A colleague covers for twenty minutes, then the class is combined with another. If nobody marks how the period was resolved, the school believes the original teacher taught that class.
  • Cover by attrition. The class is “covered” by setting written work with no teacher present. As an occasional fallback that may be acceptable; as the routine answer for one subject or one class group it is a teaching-hours leak.
  • The unreported absence. An absence that never enters the system cannot create a substitution need, so a colleague absorbs it informally and the pattern stays invisible.

Escalate causes, not just classes

Cover records are most useful when they are read as a signal about the school rather than a report on individuals.

A recurring pattern usually points at something structural: a subject with too few qualified teachers, a department whose timetable has no slack, a cluster of absences inside one team, or a room constraint that makes certain periods almost impossible to cover. Review those patterns on a regular cycle — monthly is usually enough — and treat the output as staffing and timetable input rather than a reason to audit people. Aggregate is the right level for reporting; individual cover history belongs to the roles that need it for legitimate operational reasons.

A coordinator’s daily cover checklist

  • One agreed place where an absence is reported, with a named owner.
  • Recorded absences generate substitution needs without a phone tree.
  • Affected periods and eligible teachers are visible together.
  • Candidate selection checks subject capability, availability and workload limits.
  • Every cover assignment is dated, attributed, and kept separate from the master timetable.
  • The substitute, the class and the department head are notified through official channels.
  • Informal swaps are allowed only when they are recorded.
  • Unresolved periods stay visible until someone closes them.
  • Workload patterns are reviewed as a fairness measure, not a disciplinary one.
  • Recurring patterns feed back into staffing and timetable planning.

No school can prevent absence. What it can do is make cover a decision with a name, a rule, a date and a record — and that alone removes most of the improvisation from an ordinary school morning.

Related reading: School HR software: connecting attendance, leave, payroll inputs and substitutions and How to build a conflict-free school timetable.