A CAPA template — Corrective and Preventive Action — is the documented framework that turns a quality problem into a closed loop of root cause investigation, action, verification, and permanent prevention. An effective CAPA report template is not a form to fill out after a customer complaint; it is the operational discipline that prevents the same defect from recurring. This page gives manufacturing quality teams a complete CAPA report format covering every required element — from problem statement through 5-Why root cause analysis, corrective action, effectiveness verification, and CAPA closure — with guidance on each section.
Run Every CAPA on iFactory — From Problem to Verified Closure
iFactory's CAPA module replaces your corrective action template with a structured digital workflow — 5-Why root cause, action assignment, evidence upload, and effectiveness verification — with automatic escalation when deadlines are missed.
Problem Statement — What Happened and Where
The quality of a CAPA is determined almost entirely by the quality of the problem statement. A vague problem statement produces a vague root cause and a temporary corrective action. A precisely scoped problem statement — describing the specific defect, the part affected, the quantity, when it was first observed, and how it was detected — produces a targeted investigation that addresses the actual failure mode rather than a category of failure.
Problem Description
Specific, measurable description of the non-conformance. Include what failed, how it failed, and what the correct condition should be. Avoid vague language like 'quality issue'.
Part Number & Lot
Engineering part number, drawing revision, and the specific lot or serial numbers affected. Links the CAPA to the physical product and production records.
Detection Point
Where the problem was found — customer return, outgoing inspection, in-process check, or supplier audit. Indicates the escape point that the CAPA must also address.
Quantity Affected
Number of parts or units confirmed non-conforming. Containment scope — how far back the suspect population extends. Basis for the containment action.
Customer / Source
Customer name (if external), or internal department / process responsible for the non-conformance. Determines SCAR vs. internal CAPA workflow.
Date Detected & Owner
Date the non-conformance was first identified. CAPA owner — the individual responsible for driving the investigation and actions to closure.
Containment Action — Stop the Bleeding First
Containment must happen before root cause analysis begins. The purpose of containment is to prevent any additional non-conforming product from reaching the customer — and to define the boundaries of the suspect population so that the CAPA investigation has a clear scope. Containment is not a corrective action; it is a temporary measure that buys time for a permanent fix.
Physically quarantine all suspect product immediately. Apply hold tags. Update ERP status to prevent production use or shipment. Scope extends to all product produced since the last confirmed good inspection point.
If non-conforming product has reached the customer, notify immediately per your contract requirements. Initiate field containment if required. Document all communications in the CAPA record.
Determine how far back the non-conformance potentially extends. Review production records, process change logs, and tool change records to establish the earliest possible defect introduction point.
Inspect 100% of the suspect population. Document each unit's result. Accepted parts are re-tagged and released. Rejected parts are scrapped or returned with documented disposition.
Verify that no additional non-conforming product is escaping. If the customer continues to find defects after containment is declared complete, the containment scope was insufficient and must be expanded.
Root Cause Analysis — 5-Why and Ishikawa
Root cause analysis is the section where most CAPA reports fail. The most common errors are: identifying a symptom instead of a root cause, stopping the 5-Why too early, and failing to identify the escape cause separately from the production cause. Every CAPA must address two causes: why the defect was produced, and why it was not detected before reaching the next operation or the customer. Both require separate permanent corrective actions.
5-Why Root Cause Format
- Why 1: State the immediate symptom (e.g., "Hole diameter out of tolerance")
- Why 2: State the process cause (e.g., "Tool wear exceeded replacement interval")
- Why 3: State the system cause (e.g., "Tool change frequency was not in control plan")
- Why 4: State the management cause (e.g., "Control plan was not updated after process change")
- Why 5: State the root cause (e.g., "No change control process for control plan updates")
- Escape Why: Separately identify why the defect was not detected — requires its own Why chain
Common Root Cause Errors
- "Human error" accepted as a root cause without further analysis
- 5-Why stopped at the process level instead of the system level
- Production cause identified but escape cause not investigated
- Root cause stated as an assumption rather than a verified finding
- Corrective action addresses the symptom of Why 1, not the root of Why 5
- No evidence that the identified root cause actually caused the defect
Corrective & Preventive Actions
Corrective actions address the identified root cause of the current non-conformance. Preventive actions extend the learning to similar processes or products to prevent the same failure mode from occurring elsewhere. Both must be specific, measurable, assigned to an owner, and have a defined completion date. Vague actions — "retrain operators" or "improve inspection" — without specific descriptions of what will change are not acceptable CAPA actions.
| Action Type | Description | Owner | Due Date | Evidence Required |
|---|---|---|---|---|
| Corrective | Update control plan to include tool change frequency at Ops 30 | Process Engineer | +7 days | Updated control plan, Rev level change |
| Corrective | Add tool wear measurement to in-process IPQC checklist every 50 pcs | Quality Engineer | +10 days | Updated IPQC form, operator training record |
| Corrective | Update change control procedure to require control plan review for all process changes | Quality Manager | +14 days | Updated SOP, management approval |
| Preventive | Audit all other operations in routing for similar missing tool wear controls | Quality Engineer | +21 days | Audit report, findings log |
| Preventive | Review all control plans for processes changed in last 12 months — confirm change control was followed | Quality Manager | +30 days | Control plan review log, corrective actions for any gaps found |
Effectiveness Verification
Effectiveness verification is the evidence that the corrective actions actually eliminated the root cause — not just that the actions were completed. An action being "implemented" is not the same as the problem being solved. Effectiveness verification must be defined at the time the CAPA is created — not added as an afterthought when the team wants to close the file. The verification method must specify what data will be collected, over what time period, and what threshold constitutes confirmed effectiveness.
The effectiveness check must be documented in the CAPA at the time of action planning — what metric, how many units, over what time period, and what constitutes success. If the verification method is added later, it is typically designed to confirm success rather than to genuinely test it.
Effectiveness is demonstrated by subsequent production runs showing no recurrence of the same defect — not by inspecting the same lot that triggered the CAPA. Production data from the next three to five runs after implementation, covering at least the same process conditions, constitutes acceptable effectiveness evidence.
Any recurrence of the same or similar defect after CAPA closure — from any source — constitutes a CAPA failure and requires reopening the file. A CAPA that is closed and then a recurrence is opened as a new CAPA with a new number is a red flag in any customer or certification audit.
Track Every Corrective Action from Root Cause to Verified Closure
iFactory's CAPA module enforces the complete CAPA procedure — problem statement, 5-Why root cause, action assignment, evidence upload, and effectiveness verification — with automatic deadline tracking and escalation when actions are overdue.
CAPA Report Checklist — 25 Items
Use this checklist to verify completeness of every CAPA before submission or closure. Covers all five sections: problem statement, containment, root cause analysis, corrective and preventive actions, and effectiveness verification.
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 1 | Specific defect description — what failed, how it failed, and what correct condition should be | Text | High | — | ✓ | ✓ |
| 2 | Affected part number, drawing revision, and lot/serial numbers documented | Pass/Fail | High | — | ✓ | ✓ |
| 3 | Detection point recorded: customer return / OQC / IPQC / IQC / audit | Selection | High | — | ✓ | ✓ |
| 4 | Quantity confirmed non-conforming and suspect population scope defined | Pass/Fail | High | — | ✓ | ✓ |
| 5 | CAPA owner assigned with name, department, and acknowledgement date | Pass/Fail | High | — | ✓ | ✓ |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 6 | Suspect lot physically quarantined — ERP status updated to hold | Pass/Fail | High | ✓ | ✓ | ✓ |
| 7 | Customer notified within required timeframe — communication documented | Pass/Fail | High | — | ✓ | ✓ |
| 8 | 100% sort of suspect population completed — results recorded by unit/lot | Pass/Fail | High | ✓ | ✓ | ✓ |
| 9 | Field containment initiated if non-conforming product reached customer | Pass/Fail | High | — | ✓ | ✓ |
| 10 | Containment effectiveness verified — no additional escapes after containment declared | Pass/Fail | High | — | ✓ | ✓ |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 11 | 5-Why analysis completed for production root cause — Why chain reaches system level | Pass/Fail | High | — | ✓ | ✓ |
| 12 | Escape root cause separately identified — why defect was not detected | Pass/Fail | High | — | ✓ | ✓ |
| 13 | Root cause verified with evidence — not assumed or stated without data | Pass/Fail | High | — | ✓ | ✓ |
| 14 | "Human error" not accepted as root cause without further system analysis | Pass/Fail | High | — | ✓ | ✓ |
| 15 | Root cause directly linked to corrective actions in next section | Pass/Fail | High | — | ✓ | ✓ |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 16 | Corrective action addresses identified production root cause specifically | Pass/Fail | High | — | ✓ | ✓ |
| 17 | Separate corrective action addresses escape root cause | Pass/Fail | High | — | ✓ | ✓ |
| 18 | Each action has named owner, specific description, and due date | Pass/Fail | High | — | ✓ | ✓ |
| 19 | Preventive action extends learning to similar products/processes | Pass/Fail | Med | — | ✓ | — |
| 20 | Evidence of action completion attached — updated documents, training records, photos | Pass/Fail | High | ✓ | ✓ | ✓ |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 21 | Effectiveness verification method defined before actions were implemented | Pass/Fail | High | — | ✓ | ✓ |
| 22 | Verification based on production data — not re-inspection of original lot | Pass/Fail | High | — | ✓ | ✓ |
| 23 | Minimum 3 production runs post-implementation show no recurrence | Pass/Fail | High | — | ✓ | ✓ |
| 24 | CAPA closure signed by Quality Manager with date | Signature | High | — | ✓ | ✓ |
| 25 | CAPA record filed in QMS — linked to original NCR and lot records | Pass/Fail | Med | — | ✓ | — |
Frequently Asked Questions
What sections must a CAPA report template include?
A complete CAPA report format must include: a problem statement with specific defect description, affected part and lot numbers, and detection point; a containment action section documenting what was done to prevent further escape; a root cause analysis section using a structured methodology (5-Why, Ishikawa, or fault tree); corrective actions addressing the root cause with owner, due date, and required evidence; preventive actions extending the learning to similar products or processes; and an effectiveness verification section with a defined method, timeline, and success criteria. CAPAs that are closed without effectiveness verification are frequently rejected during ISO 9001 and IATF 16949 audits.
What is the difference between a corrective action and a preventive action?
A corrective action addresses the specific root cause of the current non-conformance — it fixes the problem that happened. A preventive action extends the learning to prevent the same failure mode from occurring in similar products, processes, or operations where the root cause could also exist but has not yet produced a defect. Preventive actions are often broader in scope — a corrective action might update one control plan, while the corresponding preventive action audits all control plans for similar gaps. Both are required in a complete CAPA report.
How long does a CAPA need to be open?
CAPA duration depends on the complexity of the root cause and the time required to implement and verify corrective actions. Most quality management systems specify a target response timeline — typically 30 days for an initial response and 90 days for verified closure. Customer-specific requirements (CSRs) for automotive OEMs may specify tighter deadlines. The CAPA should remain open until effectiveness verification is complete with objective evidence — not until the actions are implemented.
Can iFactory generate a CAPA report automatically?
Yes. iFactory generates a formatted CAPA report document from the data entered in the CAPA workflow — problem statement, root cause analysis, actions with completion dates and owner names, evidence attachments, and effectiveness verification results. The report can be exported as a PDF for customer submission or stored in iFactory's quality records with full audit trail. Book a Demo to see the CAPA module. Book a Demo
What is an 8D CAPA template and how does it differ from a standard CAPA?
An 8D CAPA template structures the corrective action process across eight disciplines (D0–D8): emergency response, team formation, problem description, interim containment, root cause identification, permanent corrective action, preventive action, and team recognition. The 8D format is specifically required by Ford, GM, Stellantis, and many other automotive OEMs for supplier corrective action responses. iFactory supports both standard CAPA and 8D formats from the same platform. Book a Demo
Replace Your CAPA Format Excel Sheet with a Digital CAPA System
iFactory's CAPA management module gives manufacturing quality teams a complete digital CAPA workflow — from problem statement through 5-Why root cause, action tracking, and effectiveness verification — with no spreadsheets and no missed deadlines.
