School cover management is the process of identifying which lessons and duties need a replacement when staff are absent, approving planned leave, allocating suitable staff and communicating the final arrangements. A reliable workflow gives every outstanding requirement an owner and separates proposed cover from confirmed cover.
What should a school cover process include?
Start with the handoffs between people, rather than the screens in a system. Staff need a clear route for planned leave; approvers need enough information to decide; cover managers need the affected sessions; and covering staff need an accurate briefing.
Keep three states distinct: the absence has been requested, the absence has been approved, and cover has been confirmed. Approval alone does not mean every lesson has a replacement. Likewise, a suggested teacher has not yet been assigned.
- Name the person responsible for reviewing planned absence.
- Define who records an unexpected absence when a staff member cannot submit a request.
- Identify lesson requirements and supervision duties separately.
- Check availability, confirm allocations and issue one agreed briefing.
- Review changes during the day and make the current version clear.
How do lesson cover and duty rotas differ?
Lesson cover follows affected teaching sessions. A duty rota records supervision requirements by time, location and staffing level, such as a gate or playground. A staff member may have both responsibilities on the same day, so checking only their lessons can leave a supervision gap.
| Area | Lesson cover | Supervision duties |
|---|---|---|
| Requirement | Affected lesson or session | Location, time band and required headcount |
| Useful context | Subject, class, room and original teacher | Duty location and open positions |
| Completion | A suitable replacement is confirmed | Every required position is assigned |
Read next: Planning school duty rotas
When is a spreadsheet enough?
A spreadsheet can suit a simple timetable with a single coordinator and few changes. It is less effective when several people approve requests, different versions circulate, or cover and duty information live in separate places. The issue is whether staff can reliably tell what still needs action.
Before replacing a working process, list the steps that cause repeated checking or confusion. A system that displays the same spreadsheet without improving responsibility, allocation status or communication may add little value.
What should you test in a demonstration?
Use a small set of realistic school scenarios and follow each one through to the final briefing. Include exceptions as well as an uncomplicated all-day absence. Treat these as evaluation cases, not a claim that every product handles them identically.
- A planned request needing the headteacher's decision.
- An unexpected absence affecting only part of a day.
- An absent colleague with both teaching and playground duties.
- A candidate who is already teaching or covering elsewhere.
- A day with some sessions covered and others still open.
- A correction after the first daily briefing has been issued.
Where does Cover Manager fit?
Cover Manager brings absence requests, configurable approval routes, Morning Cover, manager-reviewed suggestions and duty rotas into one hosted platform. Wonde-connected timetable context depends on the school's permissions and available data. Duty Manager works independently of that MIS connection.
Start by agreeing your approval rules, staff eligibility and communication process. Software can make those decisions visible and repeatable, but the school still owns the decisions and the people carrying them out.
Read next: School onboarding checklist