Workplace safetyCorrective actions
Overdue actions: record the decision instead of silently moving the date
An overdue review should explain what remains unresolved, current arrangements, dependencies and the responsible decision on the next step. Repeatedly changing the due date without context can make an open issue look as though it was always on schedule.
At a glance
An overdue review should explain what remains unresolved, current arrangements, dependencies and the responsible decision on the next step. Repeatedly changing the due date without context can make an open issue look as though it was always on schedule.
Define the decision behind the record
Keep original and revised dates identifiable. A delay reason is useful only when it is tied to a responsible review and the condition still requiring attention. The system should preserve the issue rather than resetting it to a new task each week.
Review the current condition before revising a date
Identify the open action, original commitment and evidence of its current state. Record why the work is delayed and who reviews the implications under the site process. An overdue label should lead to an explicit decision rather than only a new calendar entry.
Keep any authorised interim arrangements, dependencies and next review visible. If a new date is agreed, preserve the old date and reason alongside the decision maker. Do not let rescheduling make historical delay or unresolved work disappear from the record.
Test a delayed action with incomplete work and one awaiting verification after implementation. They require different next steps even if both are past a displayed due date. Review the export to confirm a colleague can understand what remains unresolved and why the revised decision was made.
Worked example
An assigned action depends on a replacement item. The owner records the dependency and escalates under the site process. The reviewer documents the next step and any revised date, while the original deadline and unresolved status remain visible.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Action and original deadline
- Current condition and progress
- Dependency or delay reason
- Responsible review decision
- Revised date and communication
Example record and review decision
Fictional record example: ACT-08: original due date, current condition, reason for delay, interim decision and revised review point.
Preserve the original commitment and document who evaluated the implications of continued delay.
Changing the date without recording the decision removes the evidence needed to distinguish deliberate review from forgotten work.
Test the review, not just the form
Inspect a sample whose due date changed twice. Another manager should see the history and understand why the issue remains open. Test views that identify unresolved work without rewarding date edits as completed progress.
A few useful answers
Does changing the date resolve an overdue finding?
No. It records a scheduling decision; the underlying outcome still needs to be achieved and verified.
Does changing the due date resolve the action?
No. It records a timing decision. Keep the actual work, current condition, reasons and verification status separate from the revised commitment.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
