If you’ve ever had that 7:15am feeling — “who’s in, who’s out, who’s covering, and who actually knows?” — you’ll know why this keeps coming up.
In the HeadteacherChat community, leaders keep returning to the same point: cover collapses fastest when the sickness reporting process is vague, inconsistent, or relies on assumptions.
This is not about being strict for the sake of it.
It is about safeguarding, fairness, and protecting the working day.
Why this matters (beyond “logistics”)
An unclear absence process creates four predictable risks:
- Safeguarding risk: you cannot be confident who is supervising which pupils, and whether ratios are secure.
- Operational risk: cover planning happens too late, and the day starts in firefighting mode.
- People risk: resentment grows when some staff follow the rules and others do not.
- Wellbeing risk: the head/deputy/office team absorb the stress spike at the worst possible time.
The tension the thread revealed: speed vs certainty
Leaders in the discussion tended to sit in two camps:
- Speed + paper trail Text/email is quick.
- It creates a written record.
- It helps cover planning early.
- Safeguarding + verification A repeated concern was: a message might not be from the staff member.
- Many therefore require voice contact to confirm identity and clarify likely duration.
The key insight is that both camps are trying to solve a real problem.
So the best solution is a process that gives you certainty and a record.
The simplest defensible approach: call first, written follow-up
Across replies, the most common “middle ground” process looked like this:
- Call a named person within a clear window (for example, 7:00–7:30am).
- If no answer, call the second named person (often the deputy).
- If still no answer, leave a voicemail and send a text/email follow-up.
- When the office opens, ensure the office is informed (so registers and systems match reality).
This gives you:
- a safeguarding-safe confirmation
- speed for cover decisions
- a record for HR and patterns
A practical script to make the call easier
Staff often avoid calling because it feels awkward.
A simple script removes the friction:
“Hi [name], it’s [name]. I’m unwell and I won’t be in today. I expect to be off for [1 day / until [date]]. I’ll send a quick email as confirmation. Thank you.”
No long explanation.
Just clarity.
What to put in writing (so nobody has to guess)
If you only document three things, document these:
- Who staff must contact (primary and back-up)
- By what time (and what happens if they cannot get through)
- What happens next (confirmation message, office update, expectations on cover handover)
Then add a short line for common scenarios that often get messy:
- “lost voice”
- emergency appointments
- dependants’ leave
- bereavement
The thread also flagged a real-world outcome: some leaders reported that requiring calls reduced casual absence, because it introduced accountability and clarity.
A deputy headteacher note: this is one of your highest-leverage fixes
Deputies often end up as the default “cover air traffic control”.
If cover is a recurring pain point in your school, a clear sickness reporting process is one of the quickest operational wins you can lead:
- it reduces morning stress
- it prevents conflict
- it protects safeguarding
- it makes staffing patterns visible early
Quick takeaway: your “sickness reporting” checklist
If you want a process that actually holds under pressure:
- One window (e.g. 7:00–7:30am)
- Two named contacts (head then deputy)
- Call first, then written follow-up
- Office informed when open
- Explicit policy wording shared in induction
This blog is based on a HeadteacherChat community discussion about staff sickness reporting: call vs text, safeguarding verification, and cover planning.