MANAGER OVERSIGHT · 4 min read
Missed operational checks: how to review overdue routines
A missing record tells you something needs attention. It does not tell you why. Here is a practical way to review missed routines without confusing a blank answer with a completed inspection.
By CheckControl · Published 5 September 2026 · Updated 6 October 2026 · How we write our guidesSeparate the three questions
Was the routine assigned? Was the work carried out? Was the result submitted? These are different questions. A missing submission may mean the task was missed, the person could not access it, or the work happened without being recorded. Keep the missing record visible while you find out which explanation applies.
Start with a clear schedule
A useful completion report needs an agreed expectation. Give each routine a name, an owner or relevant role, and a due window. “Morning checks” is less useful than a focused routine with a clear finish time. Review the schedule when staff or opening hours change so the report reflects the work you actually expect.
Review exceptions during the shift
Make a short review of overdue work part of the handover. Ask the assigned person what happened and record the explanation. If the work still needs doing, agree who will do it and when. Avoid entering a retrospective pass just to make the dashboard look tidy: it changes the meaning of the record.
Look for the pattern behind the gap
One missed routine and a recurring missed routine need different conversations. Compare the day, shift and checklist involved. Is the deadline unrealistic? Is the task assigned during another duty? Does a particular device or location make submitting difficult? A weekly review should help improve the process as well as identify individual follow-up.
Keep your completion number honest
Completed routines and failed answers measure different things. A staff member can complete a routine honestly and record a failure within it. Likewise, a routine with no submission is not evidence that every item passed. Read the definitions alongside the totals before using them to compare teams.
Try the example in CheckControl
Open the demonstration report and select 25 August to see a missed routine. Compare it with 27 August, where submitted routines include failed answers. The date, staff and answer views let a manager move from the headline number to the record that explains it. Use that same habit in your real weekly review: start with the exception, then inspect the context.
WORKED EXAMPLE · FICTIONAL HANDOVER
Investigate the gap before changing the record
A room-reset task is due at 07:00 and still has no submission at the manager’s review. Establish whether it was assigned to the right person, whether the room was accessible and whether the work was actually carried out.
- Wrong assignment
- Record the scheduling issue and agree the responsible person and next task. Do not invent evidence that the original assignment was completed.
- Task could not happen
- Keep the access or other exception, the person informed and the next action visible. Use the site’s process to decide the current arrangement.
- Work happened without a record
- Document the explanation and any permitted later evidence accurately. Do not backdate a pass to imply a contemporaneous submission.
At the next review, look for the cause and timing of repeated gaps. Improve the assignment, task window or instruction where the actual records support it.
Use the weekly review worksheet to keep decisions and next owners together, then read the shift handover guide.
Sources and further reading
These are CheckControl record-design and management examples. Refer to HSE’s managing health and safety guidance alongside the competent arrangements and approved procedures relevant to your workplace.