Chapter 35: CAR Template Design: The 12 Fields Every ISO 9001 CAR Must Include

Whether you're designing a spreadsheet, choosing a QMS platform, or filling out a printed form, these 12 fields are non-negotiable for audit compliance and actual effectiveness.
- CAR Number (Unique Identifier)
Format: YYYY-CAR-001, YYYY-CAR-002, etc., or Site-YYYY-001 if multi-site. This number is your legal reference point for traceability.
- Date Raised
When the nonconformance was first identified. Not when you got around to writing the CAR. This date is critical for audit proof of responsiveness.
- Source or Trigger
How was the nonconformance found? Customer complaint, internal audit, inspection, management review, employee observation, supplier finding? This field feeds your trending analysis.
- Nonconformance Description
What was wrong? Be specific: "Widget batch 2026-0347 failed hardness test (required 48–52 HRC; result 44 HRC)" not "quality issue found." A clear description prevents rework later and helps auditors understand your control rigor.
- Immediate Containment Action
What did you do right now to prevent a nonconforming product from reaching the customer or next process? "Quarantined batch 2026-0347; initiated 100% re-test" is auditor gold. "Will investigate" is not containment.
- Root Cause Analysis (RCA) Method
Did you use 5-Why, Fishbone, FMEA, fault tree, or another technique? Document the method. This signals to auditors that you're systematic, not just guessing.
- Root Cause Statement
The actual finding. Example: "Hardness test calibration procedure (Rev 3) required quarterly calibration; last completed March 2025; equipment was due for recalibration in June 2026 but was not scheduled." Link to evidence (calibration log, procedure review, schedule record).
- Corrective Action (What Will Change?)
The specific action to eliminate the root cause. "Implement automated calibration schedule in maintenance software" is a corrective action. "Improve quality" is not. The action must directly address the root cause, not just the symptom.
- Implementation Date
When the corrective action was/will be completed. For ongoing actions (e.g., new training program rolling out over three months), use the final completion date or break the CAR into stages with sub-dates.
- Verification Method
How will you confirm the corrective action actually worked? "Run next calibration on schedule and verify it was recorded" or "Review audit logs for missed calibrations; confirm zero missed calibrations in the next 90 days." Vague verification (e.g., "spot checks") fails audits.
- Verification Results
The objective evidence that the corrective action eliminated the problem. "Calibration performed 2026-09-15, certificate attached. Hardness test results for next 50 parts: all within range. No nonconformances detected in audit of batch 2026-0400 onward."
- Closure Date
When you officially closed the CAR. This is your auditor's proof that you followed up, not just filed and forgot.
Optional but Auditor-Impressive Fields:
- Escape Point Analysis: At what point in your system should this nonconformance have been caught? (Incoming inspection? In-process control? Final test?) Why wasn't it? This demonstrates systems thinking.
- Affected Documents List: Which work instructions, control plans, or inspection procedures needed updating as a result? Link to the document change request.
- Lessons Learned: What will you tell other teams or sites to prevent this happening elsewhere?
- Risk Register Update: If this nonconformance exposed a new risk or risk mitigation failure, how does your risk register change?
Did You Know? ISO 14001 (environmental) and ISO 45001 (safety) auditors expect the same 12-field rigor as ISO 9001 auditors. If you're running multiple management systems, use one unified CAR template. Trying to maintain separate correction processes is a common audit finding.
Chapter 34: Paper vs. Spreadsheet vs. QMS Software: A Decision Framework for Your Plant Size
If your plant has fewer than 50 employees, ISO 9001 does not require enterprise software. A properly designed Excel corrective action register—with clear naming
Chapter 36: Integrating Corrective Actions with Your Existing QMS Documents
A corrective action that doesn't update your procedure, work instruction, or control plan is incomplete. It's also a red flag to auditors: "You fixed this insta
Request a Consultation
Fill in your details and we'll get back to you.

