A corrective action template is more than a form. It is the structure that forces every owner to document the same evidence in the same order, so an auditor or customer can read the record without asking questions. A well-designed template eliminates most of the rework that comes from incomplete CAPAs. See the broader corrective action process guide for context on where the template fits.
Why use a template at all
Teams that handle a few nonconformances a year can get away with ad-hoc memos. Teams that handle dozens or hundreds — anyone in automotive, aerospace, medical devices, or contract manufacturing — cannot. A template gives three things a freeform document never will: a consistent structure that every reviewer recognizes, a built-in checklist of required evidence, and a record that can be queried across the year for repeat-cause and effectiveness trending.
IATF 16949, AS9100, and ISO 13485 do not mandate a specific template format, but they all require the record to show the same information. A template that maps cleanly to those clauses cuts the time between intake and closure and reduces the chance of a finding during surveillance.
The required sections
A working corrective action template needs the following sections at minimum. Anything less and an auditor will write you up; anything more and owners stop filling it in.
- Header and traceability block
- Problem statement
- Containment actions
- Root cause analysis (occurrence and detection)
- Corrective action plan
- Verification of implementation
- Effectiveness check
- Read-across and closure
Header block
The header is the section auditors look at first. It needs the corrective action request number, the source (internal NCR, customer complaint, audit finding, supplier reject), the date the issue was identified, the date the record was opened, the part number or process, the customer or supplier name where applicable, the assigned owner, and the target closure date. If any of those are missing, the record cannot be trended and cannot be cross-referenced to the source data.
Problem statement
Write it for someone who has never seen the line. What is wrong, where it was found, when it occurred, how many units are affected, and how it was detected. Avoid causes in this section — they belong in the root cause block. A common failure mode is writing "operator did not follow the procedure" as the problem statement, which is both a cause and a conclusion at the same time.
Containment actions
Containment is not the fix. It is the dam. The template should ask for the specific containment actions, the scope (which lots, which locations, which work-in-process, which finished goods), the owner, the completion date, and the evidence — usually a sort report, a quarantine record, or a stop-ship confirmation. Containment that says "100% inspection" without naming the lots and locations is not auditable.
Root cause analysis
The template should name the method (5 Whys, Fishbone, 8D, FTA), show the analysis itself, and present the root cause in two parts: occurrence (why it happened) and detection (why the existing controls did not catch it). Treating only one of the two is the most common reason corrective actions fail the effectiveness check. See root cause analysis methods for the technique itself.
Corrective action plan
One row per action. Each row needs an action description, the root cause it addresses, an owner, a due date, and the evidence required to call the action complete. Actions should change the process, equipment, or controls. "Retrain operator" alone is not a corrective action — see the corrective action plan guide for the structure most customers expect.
Verification of implementation and effectiveness check
These are two separate sections in the template. Verification confirms the action was done — who confirmed, when, with what evidence (signed work instruction, training record, PFMEA revision). Effectiveness confirms the action worked — the acceptance criteria defined when the plan was written, the data collected over the verification period, and the disposition. The most common template weakness is collapsing both into a single signature line, which removes the audit trail for whether the action actually held.
Word vs PDF vs CAPA system
For a few CAPAs per month, a Word template stored alongside the source NCR is enough. PDF is useful for read-only customer submissions and audit packages. Beyond about a hundred records a year, a dedicated CAPA system pays for itself — the template structure is the same, but trending, due-date management, and read-across become impossible to do manually at volume. Whichever format you use, the underlying section structure should be identical so records remain comparable over time.
For a free Word and PDF template with every section described above, see the corrective action plan template download. For worked examples that show what each section should look like when filled in, see corrective action examples.
Download the Corrective Action Plan Template
Free Word and PDF. Every section described below is pre-built, with prompts and example text.
Get the template