Why Follow Up Is Where Audits Either Deliver or Fail
Corrective action follow up is the step that separates audits that drive real improvement from audits that generate paperwork and nothing else. You can write a perfectly worded nonconformity report, identify a genuine systemic failure, and conduct a thorough audit. But if nobody checks whether the corrective action actually worked, the whole exercise becomes a compliance ritual rather than a tool for improvement.
On this page
This is one of the most common gaps internal auditors face. The audit happens, findings are raised, management acknowledges them, and then six months later the same issues appear in the next audit cycle. The finding was real. The root cause analysis looked reasonable. But the corrective action was either not implemented, not effective, or quietly abandoned when nobody was watching.
This article walks through corrective action follow up in practical terms. What you are actually verifying, how to structure the process, common traps to avoid, and what good closure evidence looks like across different types of findings.
Understanding What Corrective Action Actually Requires
Before you can follow up effectively, you need to be clear about what the standard actually requires. Clause 10.2 of ISO 9001, ISO 14001, ISO 45001, and ISO 27001 all follow the same basic structure. When a nonconformity occurs, the organisation must react to it, evaluate the need for corrective action, determine root causes, implement appropriate action, and review the effectiveness of what was done.
That last part is the one most organisations treat as optional. It is not. Reviewing effectiveness is a specific requirement, not a nice to have. As an internal auditor, your follow up activity is the mechanism through which that requirement gets tested.
It is worth being clear on what corrective action is not. It is not a quick fix to make the finding go away. Replacing a missing record satisfies the immediate problem but does not address why the record was missing in the first place. Root cause analysis is the bridge between the symptom and the actual corrective action. If the root cause analysis is shallow, the corrective action will be shallow, and your follow up will almost certainly find the problem recurring.
Exemplar Global Certified Training ProviderRTP No. 310970The Structure of an Effective Follow Up Process
Setting Realistic Timeframes at the Closing Meeting
Follow up begins at the closing meeting, not weeks later when you return to check. One of the most practical things you can do as an internal auditor is agree on realistic timeframes for corrective action responses before you leave the room.
Minor nonconformities in a stable, well resourced process might reasonably be addressed within 30 days. Major nonconformities involving systemic failures, infrastructure changes, or training across multiple departments might need 60 to 90 days. The timeframe should reflect the nature of the finding, not what is convenient for the schedule.
Be specific. A due date of “end of quarter” is not a due date. Agree on a specific date, confirm who is responsible for the corrective action response, and document it in the audit report or a corrective action register. If you leave this ambiguous, you will spend the follow up period chasing people rather than reviewing evidence.
What a Corrective Action Response Should Contain
Before you can assess whether a corrective action is complete and effective, you need to know what a complete response looks like. A well structured corrective action response should contain four things.
- Immediate containment action: What was done right away to address the specific nonconformity found during the audit. This might be correcting the specific record, re training the specific person, or withdrawing the specific product.
- Root cause analysis: A genuine investigation into why the nonconformity occurred. Not a one line statement, but evidence of actual analysis. Common methods include 5 Whys, fishbone diagrams, or fault tree analysis depending on the complexity of the finding.
- Corrective action: The action taken to address the root cause, not just the symptom. This is where most organisations fall short. The corrective action should logically flow from the root cause. If the root cause is that no procedure exists, the corrective action is to create and implement one. If the root cause is that the procedure exists but nobody follows it, the corrective action needs to address why compliance is not happening.
- Effectiveness review: Evidence that the corrective action worked. This is often left out entirely, or filled in with a statement like “action has been implemented” with no supporting evidence.
When you receive a corrective action response, check whether all four elements are present before you even start evaluating the quality of each one. A response that jumps straight from the finding to a list of actions, with no root cause analysis, is incomplete regardless of how many actions are listed.
Evaluating Root Cause Analysis: The Most Critical Step
The quality of the root cause analysis determines everything that follows. A shallow root cause analysis produces a superficial corrective action that addresses the symptom. A genuine root cause analysis produces an action that prevents recurrence.
When reviewing a root cause analysis, ask yourself whether the identified cause actually explains the nonconformity. If the finding was that calibration records for three instruments were overdue, and the root cause is listed as “oversight by the maintenance team,” that is not a root cause. That is a description of what happened. Dig deeper. Why was there an oversight? Was there no system to track calibration due dates? Was there a system but no one was responsible for monitoring it? Was someone responsible but not aware of their responsibility? Was there awareness but no time allocated to the task?
Each of those answers points to a different corrective action. A tracking system issue requires a system fix. A responsibility gap requires a documented assignment of accountability. An awareness gap requires training or communication. A resource gap requires management intervention.
If the root cause analysis stops at “human error” or “oversight,” push back. Human error is almost never a root cause. It is usually the last step in a chain of contributing factors that created the conditions for the error to occur. Your job as the follow up auditor is to assess whether the root cause analysis went deep enough to produce a corrective action that will actually prevent recurrence.
Reviewing Evidence of Implementation
Once you are satisfied that the root cause analysis is credible and the proposed corrective action logically addresses it, the next question is whether the action was actually implemented. This is where you need evidence, not assertions.
Common types of implementation evidence include updated procedures or work instructions, training records showing that relevant staff have received and understood the updated requirements, revised forms or checklists, updated registers or tracking systems, photographs of physical changes, and records of management decisions or approvals.
Do not accept a statement that something has been done without seeing the evidence. This is not about distrust. It is about the same principle that underpins every other part of an audit: if it is not documented or observable, you cannot confirm it happened. Audit evidence needs to be verifiable, not just plausible.
Sampling Beyond the Specific Finding
One of the most important things you can do during follow up is sample beyond the specific instance that was raised in the original finding. If the nonconformity was that one employee had not completed their annual competency assessment, checking that the one employee has now completed it confirms the immediate containment action. It does not confirm that the systemic issue has been addressed.
Pull a broader sample. Check five or ten employees. Look at the process for scheduling and tracking assessments. Check whether there is a mechanism to flag overdue assessments before they become a problem. This broader sampling is what tells you whether the corrective action addressed the root cause or just the specific instance that was caught during the audit.
Assessing Effectiveness: The Step That Gets Skipped
Effectiveness review is the most underperformed part of corrective action management. Many organisations close a corrective action as soon as the action has been implemented, without waiting to see whether it worked. This is understandable from a workload perspective. It is not acceptable from a management system perspective.
Effectiveness can only be assessed after the corrective action has had time to operate. If the corrective action was to implement a new calibration tracking system, you cannot assess effectiveness the week after it was set up. You need to see it operating over a meaningful period, with evidence that due dates are being met, overdue items are being flagged, and the responsible person is acting on those flags.
As an internal auditor, you have two options for assessing effectiveness. You can build it into the follow up audit itself, provided enough time has passed since implementation. Or you can plan a specific effectiveness check as a separate activity within the audit programme, timed to coincide with when the corrective action has had time to demonstrate results.
The second approach is more rigorous and more honest. It acknowledges that some corrective actions need months to demonstrate effectiveness, and that closing them prematurely just because the action has been taken is not the same as confirming the problem is solved.
Common Follow Up Traps and How to Avoid Them
Accepting Promises Instead of Evidence
The most common trap is accepting a statement that an action will be taken rather than evidence that it has been taken. This happens when follow up is conducted too soon after the corrective action due date, or when the auditor accepts verbal assurances without requesting documentation. Be polite but firm. If the evidence is not available, the corrective action is not complete.
Closing Findings That Have Only Been Partially Addressed
Sometimes an organisation addresses the specific instance but not the systemic cause. The calibration record is now current, but there is still no process to prevent it happening again. Closing this finding as complete would be premature. The immediate containment is done. The corrective action is not.
Be clear in your documentation about the distinction. You can acknowledge that the immediate action has been taken while keeping the finding open pending evidence that the systemic issue has been addressed. Tracing nonconformities through to genuine closure is a discipline that separates effective audit programmes from tick box exercises.
Letting Timeframes Slip Without Escalation
If a corrective action response is overdue, that is itself a management system issue. It suggests either that the finding was not taken seriously, that the responsible person does not have the resources or authority to act, or that there is no effective system for tracking corrective actions. Any of these is worth raising.
Do not simply extend the due date without comment. Document the overdue status, communicate it to the management representative or relevant manager, and if the pattern repeats, consider whether it warrants a finding in its own right. Clause 10.2 requires corrective actions to be taken in a timely manner. Persistent overdue responses are evidence that this requirement is not being met.
Documenting Follow Up Outcomes
Your follow up activities need to be documented. This serves several purposes. It provides an audit trail that demonstrates the internal audit programme is functioning as required. It provides input to management review. It creates a record that external auditors can examine to confirm that nonconformities are being properly managed.
At a minimum, your follow up documentation should record the original finding reference, the corrective action response received, your assessment of the root cause analysis, the evidence reviewed to confirm implementation, your conclusion on whether the action is complete and effective, and the closure date if applicable.
If you are using a corrective action register or quality management system to track findings, make sure the status is kept current. A register full of findings that have been addressed but not formally closed is a common source of confusion during external audits, and it creates unnecessary work when the certification auditor asks for a status update. You can find practical guidance on writing nonconformity reports that set up clear closure criteria from the start.
Exemplar Global Certified Training ProviderRTP No. 310970Linking Follow Up to the Audit Programme and Management Review
Corrective action status should feed directly into two places: the ongoing audit programme and management review inputs.
For the audit programme, areas with a history of recurring nonconformities or slow corrective action responses should receive more frequent audit attention. This is the practical application of risk based audit scheduling. If a process has demonstrated it cannot sustain compliance without close monitoring, it warrants more audit coverage, not less.
For management review, corrective action status is a required input under Clause 9.3 of most ISO standards. Management needs to know how many nonconformities were raised, how many have been closed, how many are overdue, and whether there are patterns that suggest systemic issues. Your follow up documentation is the source of this information. If you are not capturing it systematically, management review will be based on impressions rather than data.
The audit lifecycle does not end at the closing meeting. Follow up is the final stage of every audit, and treating it as a genuine audit activity rather than an administrative chore is what makes an internal audit programme worth running.
Building Follow Up Into Your Auditor Habits
If you are an internal auditor managing your own programme, build follow up into your calendar at the time you issue the audit report. Do not wait until the due date arrives and then scramble to schedule a review. Set a reminder for the due date, and another one for an effectiveness check three to six months after implementation.
Develop a standard template for corrective action responses that makes it clear what is expected. When auditees know upfront that you will be looking for root cause analysis, implementation evidence, and an effectiveness review, they are more likely to provide a complete response rather than a one line fix.
Communicate consistently that follow up is part of the audit process, not an optional extra. Some auditees treat the audit as complete once the report is issued. Your follow up activity signals that the finding is not closed until the corrective action is verified as effective. That signal, repeated consistently, changes the culture around how findings are treated.
If you want to build these skills in a structured way, Audit Workshop offers practical internal auditor training across ISO 9001, ISO 14001, ISO 45001, ISO 27001, and more. The training covers the full audit cycle including corrective action follow up, root cause analysis evaluation, and effectiveness verification, with real scenarios drawn from actual audit practice. You can explore the available courses at auditworkshop.com.













