ISO Corrective Action Plan Template: Blank Form, Timeline, Examples
11 min read ยท 2026-11-19
An iso corrective action plan template is a form that follows one nonconformity from the day it is found until it is closed. Several standards share the same clause. It is 10.2 "Nonconformity and corrective action" in ISO 9001:2015, ISO/IEC 27001:2022 and ISO 14001:2015, and "Incident, nonconformity and corrective action" in ISO 45001:2018. It asks you to keep records of three things: the nature of the nonconformity, the actions you took and the results of the corrective action.
The same clause asks you to react to the nonconformity, find its causes, act on them and check that the action worked. The form below records all of that. Some fields go beyond the minimum record: the root cause written out in full, a verifier who is not the action owner, and a closure signature. They are good practice, not wording from the clause, and auditors expect to see them. Below you get a blank form to copy, notes on what changes for each standard, a 90-day timeline, a tracker for a full internal audit and three filled examples.
The 90 days and the day ranges in the roadmap are an illustrative plan, not a requirement of any ISO standard. Your own audit procedure sets your deadlines. For an external audit finding, use the deadline your certification body gives you.
The roadmap at a glance
Goal: Close one ISO nonconformity with a verified root cause fix and records an auditor will accept. Duration: About 90 days
Log and contain (Days 1-5)
Record the finding and stop the damage before you look for causes.
- Give the finding an ID and note its source: internal audit, external audit, incident or customer complaint.
- Quote the clause or control it breaks and the objective evidence.
- Apply the correction, which is the immediate fix.
- Name one action owner.
Milestone: Finding logged, correction done, owner accepted the action.
Find the root cause (Days 3-15)
Find out why it happened, not only what happened.
- Collect data: records, logs, interviews, process documents.
- Run 5 Whys, or a fishbone diagram when several causes are possible.
- Check whether the same cause could hit other sites, teams or systems.
Milestone: Root cause written in one sentence and agreed by the process owner.
Plan the actions (Days 15-20)
Decide what will change and how you will prove it worked.
- Write one or more actions aimed at the root cause.
- Set a due date for each action.
- Define a success criterion you can measure.
- Get approval from the manager who owns the process.
Milestone: Plan approved and dates entered in the tracker.
Implement (Days 20-60)
Make the change and keep the evidence.
- Update the procedure, system setting or training.
- Tell the people affected.
- Save evidence of each completed action: new document version, screenshots, attendance list.
Milestone: All actions completed, with evidence attached.
Verify effectiveness (Days 60-90)
Check that the problem has not come back after enough time has passed.
- Sample records produced after the change.
- Compare the result with the success criterion.
- Reopen the action if the criterion is not met.
Milestone: Effectiveness confirmed by someone other than the action owner.
Close and report (Day 90 onward)
Close the record and feed what you learned back into the system.
- Sign off the closure.
- Update the risk register or aspects register if needed.
- Report the result at the next management review.
Milestone: Record closed and listed in the management review inputs.
Correction, corrective action and preventive action
Most forms mix these three words up, and auditors notice. A correction is the immediate fix. You remove a user account that should not exist, or you quarantine a damaged batch. A corrective action removes the root cause so the nonconformity does not happen again. You change the leaver process so accounts are disabled on the day someone leaves.
ISO 9001:2015 clause 10.2.1 puts them in this order. First, react to the nonconformity: control it, correct it and deal with the consequences. Then evaluate whether action is needed to remove its causes, which includes checking whether similar nonconformities exist or could occur elsewhere.
Preventive action targets a problem that has not happened yet. Older editions of ISO 9001 had a separate clause for it. The current standards handle prevention through risks and opportunities, so a preventive idea usually goes into the risk register, not the corrective action form. A form that only shows a correction is not a corrective action plan.
Blank ISO corrective action plan template
Copy this form into Word or your document system. Use one form per nonconformity. Keep the fields in this order, because it follows the sequence of clause 10.2.
Three roles keep the form honest. The action owner does the work. The verifier checks effectiveness and should not be the owner, usually the auditor or the quality or security lead. The approver closes the record, usually the manager who owns the process.
- Part 1. The finding: Finding ID; Source (internal audit, external audit, incident, complaint, management review); Standard and clause or control; Date raised; Raised by; Requirement; What was found; Objective evidence; Grade (major, minor, observation).
- Part 2. Reaction: Correction and containment; Done by; Date; Consequences dealt with.
- Part 3. Cause: Method used (5 Whys, fishbone, other); Root cause in one sentence; Extent check (other places where the same cause applies).
- Part 4. Actions: Action 1, owner, due date; Action 2, owner, due date; Action 3, owner, due date; Success criterion; Plan approved by, date.
- Part 5. Evidence and effectiveness: Evidence of completion (document, version, record reference); Effectiveness check date; Checked by; Result.
- Part 6. Closure: Risk register or other updates made; Closed by; Closure date; Status (open, in progress, awaiting verification, closed, reopened).
What changes between ISO 9001, 27001, 45001 and 14001
The form stays the same. What changes is the source of the finding, who has to be involved and what you update after the fix.
- ISO 9001:2015: findings often come from customer complaints, product or service failures and supplier issues. Clause 10.2.1 asks you to update risks and opportunities and change the quality management system if needed, so add those to Part 6.
- ISO/IEC 27001:2022: name the Annex A control in the "clause or control" field when the finding is about a control, not only the clause. Evidence is often technical, such as access reviews, logs, ticket exports and configuration screenshots. Write down where it is stored.
- ISO 45001:2018: clause 10.2 covers incidents as well as nonconformities. You evaluate the need for corrective action with the participation of workers, and you communicate the records to relevant workers. Add a "workers consulted" line to Part 3 and a "communicated to" line to Part 6. The clause also asks you to review existing assessments of OH&S risks where appropriate.
- ISO 14001:2015: in your reaction, clause 10.2 asks you to deal with the consequences, including mitigating adverse environmental impacts. Record that mitigation in Part 2. Corrective actions should match how significant the effects are, so link the finding to your aspects register.
ISO 27001 corrective action plan template: what changes
ISO/IEC 27001:2022 clause 10.2 asks for documented information as evidence of the nature of the nonconformities, the actions taken and the results of any corrective action. The standard does not require a written procedure for this, so in practice the form is your main evidence. A thin form is a weak spot in the audit.
Example 1 is an internal audit finding under ISO 27001. The three examples in this guide use made-up IDs (IA-2026-07, INC-2026-11, EA-2026-03) and illustrative deadlines. They show how to fill the form. They are not requirements of the standards.
- Finding ID: IA-2026-07, source internal audit under clause 9.2.
- Control: A.5.18 Access rights. The control says access rights should be provisioned, reviewed, modified and removed according to the organisation's access control policy and rules.
- Description: Three former employees still had active accounts in the finance system, found during a sample of ten leavers.
- Correction: Accounts disabled on the day of the audit by the IT lead.
- Root cause (5 Whys): The accounts stayed active because IT was not told. IT was not told because HR's leaver checklist did not include the finance system. The system was missing because it was added after the checklist was written, and nobody owns checklist updates.
- Actions: Add every business system to the leaver checklist (HR lead, day 30). Name an owner for checklist updates when a system is added (IT manager, day 30). Run a monthly access review on the finance system (finance lead, starts day 45).
- Success criterion: No active account for a leaver in the next two monthly reviews.
- Effectiveness check: Day 90, by the internal auditor.
Internal audit corrective action plan template: timeline and tracking
ISO/IEC 27001:2022 clause 9.2 and ISO 9001:2015 clause 9.2 ask you to keep evidence of the audit programme and the audit results. One audit usually gives you several findings, so run them in a single tracker next to the forms, with one line per finding.
Here is an illustrative tracker for an internal audit with four findings, three weeks after the audit. Each line shows the phase from the roadmap above, so you can see at a glance which finding is stuck. In this tracker, IA-2026-08 has not passed root cause analysis three weeks in. That is the line that needs a decision, not the others.
- IA-2026-05, minor, document control, owner quality lead, phase implement, next date day 45 (new procedure version issued), on time.
- IA-2026-06, observation, supplier review, owner purchasing manager, phase plan, next date day 20 (plan approval), on time.
- IA-2026-07, minor, A.5.18 access rights, owner IT manager, phase implement, next date day 30 (checklist updated), on time.
- IA-2026-08, major, backup testing, owner IT ops, phase root cause, next date day 10, overdue by 11 days, escalated.
Three habits that keep the tracker moving
A tracker only helps if someone looks at it and acts on what it shows. These three habits are enough for most audit programmes.
- A short weekly review. The quality or security lead goes through every line that changed phase or has a date in the next seven days. Nothing else.
- The effectiveness check gets its own date on day one. Set it after enough new records exist. A monthly control needs one or two cycles before you can judge it. A daily control can be checked sooner.
- A written escalation rule. For example: an action two weeks overdue goes to the process owner's manager, and an action still open at the next management review is reported there by name. The exact rule is yours to set. What matters is that it is written down and applied.
Incident corrective action plan template
An incident gives you less time and more pressure than an audit finding. Containment comes first and may take hours, not days. The root cause analysis follows the incident review, and lessons learned feed the corrective actions.
Example 2 is a security incident under ISO 27001.
- Finding ID: INC-2026-11, source incident.
- Description: A nightly backup of the customer database failed for six days without an alert.
- Correction: Manual backup run and restored to a test environment the same day.
- Root cause: The backup job sent alerts to a shared mailbox that was closed during an email migration.
- Actions: Send backup alerts to the monitoring tool instead of email (IT ops, day 14). Add an alert routing check to the migration checklist (IT manager, day 30). Run a restore test every quarter (IT ops, first test day 60).
- Success criterion: Every failed job raises an alert in the monitoring tool, proven by a deliberate failed run, and the quarterly restore test passes.
- Effectiveness check: Day 75, by the security lead.
Example 3: ISO 45001 audit finding
This last example comes from an external audit. Note the extra line ISO 45001 asks for: the workers consulted during the cause review.
- Finding ID: EA-2026-03, source external audit, minor.
- Clause: ISO 45001:2018 clause 7.2, competence, which asks you to keep documented information as evidence of competence.
- Description: Two forklift operators on the night shift had no refresher training on record.
- Correction: Both operators taken off forklift duty until trained.
- Root cause: The training matrix was only reviewed for the day shift, because the night supervisor had no access to it.
- Workers consulted: Night shift operators and their supervisor, during the cause review.
- Actions: Give both supervisors access to the matrix (HR, day 7). Add a monthly matrix review to the shift handover (operations manager, day 30).
- Success criterion: No operator with expired training at the next two monthly reviews.
- Effectiveness check: Day 90, by the safety lead.
Corrective action plan template in Microsoft Word, and presenting it
Word works well for the form itself. It prints cleanly, holds signatures and goes into an audit folder. Paste the blank form above, lock the field labels, and save one file per finding using the finding ID as the file name.
When you present the plan to management, an auditor or a client, show the timeline, not the forms. A single view with each finding as a line, its phases and its due dates answers the questions they ask: how many are open, which are late, and who owns them. Keep the forms ready as backup. Auditors will sample a few and check that the timeline matches the evidence. Here is what an auditor usually asks to see.
- The finding and its evidence.
- The correction and when it was done.
- The root cause analysis, not only its conclusion.
- Completed actions with evidence.
- The effectiveness check with a date and a result.
- Closure approval, and a link to management review.
Common mistakes to avoid
- Writing "human error" as the root cause, when you should keep asking why until you reach a process or system cause.
- Closing the record when the action is done, when it should only close after the effectiveness check passes.
- Proposing a complex solution such as a new system, when a simpler change to the existing process removes the cause.
- Letting the action owner verify their own work, when a separate verifier makes the check credible.
- Keeping records with no evidence references, when every completed action should point to a named document or record.
- Setting no follow-up date, when the effectiveness check needs its own date in the tracker from day one.
Frequently asked questions
Is a corrective action form required by ISO 27001 clause 10.2?
Clause 10.2 of ISO/IEC 27001:2022 requires documented information on the nature of nonconformities, the actions taken and the results of corrective actions. It does not name a form. Most organisations meet the requirement with one, because it keeps all three in one place.
How long do you have to close a nonconformity after an internal audit?
ISO standards do not set a fixed deadline. You set it in your own audit procedure, often based on the grade of the finding. For external audit findings, your certification body sets the deadline, and that one applies.
How do you verify that a corrective action was effective?
Define a measurable success criterion before you implement. Then check new records against it after enough time has passed. If the problem has come back, reopen the record and review the root cause. Ask someone other than the action owner to do the check.
Can one template be used for multiple nonconformities?
Use one form per nonconformity, so each has its own root cause, owner and evidence. If several findings share the same root cause, link them by ID and run one set of actions. A tracker gives you the overview across all findings.