Closing an Action Is Not the Same as Solving a Problem
What meaningful verification of effectiveness can look like.
An internal audit finds that contractors sometimes start maintenance before responsibilities at the permit handover are clear. The action owner revises the handover form and briefs the supervisors. The tracker turns green. On the next weekend shift, a contractor arrives early and the same uncertainty returns.
The form and briefing are evidence that the action was implemented. To judge effectiveness, someone needs to check whether the new process works under the conditions that produced the problem.
Separate the immediate response from the corrective action
First resolve the immediate issue and control its consequences. In the example, the responsible manager pauses the affected job until responsibilities and controls are confirmed. Then investigate why the handover was unreliable. If the process assumes that two named supervisors are present, but weekend coverage works differently, the revised process needs to address that gap. Check for similar conditions at other shifts or sites where appropriate.
Decide how you will verify effectiveness before the work is finished
Agree a test with the action owner while defining the corrective action. For this example, the team could sample contractor starts across normal and weekend operations, including an early arrival or a shift change if one occurs. For each job, verify that the responsible people were identified and the handover was confirmed before work began. Compare the records with accounts from supervisors and contractors or with direct observation.
Choose the sample and timing to match the risk and frequency of the task. If the relevant work has yet to occur, record implementation as complete and set a follow-up trigger for the next representative job.
Keep the result with the action record
An effectiveness record can be short. Capture what was checked, the sample and date, the result against the agreed criterion, and the next decision. For example:
Over two weeks, the reviewer checked four contractor starts, including two weekend jobs. One weekend job started before the handover was confirmed. The corrective action was reopened, and the weekend cover arrangement was assigned to the maintenance manager for review.
A period without another incident may support the assessment. For an infrequent event, checking the underlying control usually gives you an earlier and more direct signal. At your next action review, take one recently closed item and ask, “What work did we sample, and what did it show about the cause we set out to address?”
Related ISO 45001 clause · 10.2 Incident, nonconformity and corrective action
