School cover reports are most useful when they distinguish absence requests, affected sessions and confirmed allocations. Use daily views to resolve outstanding work, then review comparable periods to understand workload and recurring gaps. Recorded allocations describe scheduled cover; they do not by themselves prove attendance or explain an individual's circumstances.
Which counts answer which questions?
A request count tells you how many records exist. A session count tells you how many teaching periods are affected. An allocation count describes confirmed assignments. Those measures cannot be substituted for each other: one request can affect several periods, and some may still be unallocated.
| Measure | Useful question | What it does not establish |
|---|---|---|
| Pending requests | Which decisions still need an approver? | How many lessons will eventually need cover |
| Unallocated sessions | Which approved requirements remain open? | Why staff are unavailable |
| Allocated cover | What has been assigned? | Whether the cover was carried out |
| Absence by reason | What categories appear in the selected records? | An explanation of individual circumstances |
How should periods and staff groups be compared?
Use consistent dates, filters and definitions before comparing results. A short teaching week and a full week do not offer the same number of possible sessions. Changes in recording practice can also change the totals without an equivalent change in school activity.
Compare like responsibilities where possible. A raw staff cover count does not account for every difference in role, working pattern or session length. Use the report to identify a question for the responsible school team, not to produce an automatic judgement about a person.
- Record the date range and filters used for each review.
- Separate pending, approved and denied requests where relevant.
- Check whether sessions or requests are being counted.
- Consider timetable changes and incomplete historical data.
- Explain unusual periods before treating them as a trend.
What can Cover Manager show?
Cover Manager provides dashboard counts and reporting views for absence activity, approval status, sessions needing cover and cover workload. The reports include filters and CSV exports so school teams can examine a defined set of records.
Keep the daily dashboard and longer-term reporting questions separate. An operational alert helps identify current work, while a historical report can include past records that no longer need action. Clear date labels help avoid confusing those two purposes.
How can reports improve the next week's process?
Turn each recurring pattern into a specific review. Repeated approval delays suggest checking routes and responsibility. Persistent unallocated periods suggest reviewing availability, workload rules and when decisions are made. Recurring duty gaps call for a rota review as well as a lesson-cover review.
An illustrative review might find that late changes are consistently missed after the first cover sheet is printed. The useful action is to assign responsibility for revised briefings and check whether that change helps, rather than simply adding another total to the dashboard.
Read next: Running the morning cover workflow
What should be checked before exporting or sharing?
Check the purpose and audience of the report before exporting. Share the fields needed for that purpose, confirm the date range and keep identifiable absence information within the school's agreed handling process. An export is a separate copy and will not update when the live record changes.
If the school needs evidence of attendance, costs or other outcomes, confirm what is actually recorded before making a claim from the report. Do not infer those measures from scheduled assignments alone.