One Excel register for every corrective action you open, whatever the source: NCRs, customer complaints, audit findings or SCARs. The sheet works out days open, flags overdue actions against today’s date, sets the effectiveness-check date when an action closes, and summarises the whole log for management review.
Tip: Keep the log as an index, not the full record. The root cause analysis, evidence and approvals stay on the CAPA or 8D form; the log points to them by number.
Header
Company, log owner, as-of date (TODAY()) and the effectiveness-check interval in days
Identification
CA number, date opened, source (NCR, complaint, audit, SCAR) and source reference
Problem and action
Problem statement, verified root cause, corrective action, owner and due date
Status
Date closed, with days open and Open / Overdue / Closed calculated
Effectiveness
Calculated check-due date, Effective? (Yes / No) and who verified it
Summary
Open, overdue and closed counts, average days to close, overdue effectiveness checks and actions found not effective
Example Log for Example Machining Co., a fictional job shop, as of 2026-10-15, with effectiveness checked 60 days after closure. The actions, dates and causes are invented for illustration.
| CA | Opened | Source | Problem | Due | Closed | Days open | Status | Check due | Effective? |
|---|---|---|---|---|---|---|---|---|---|
| CA-01 | 2026-06-02 | NCR-311 | Bore oversize on 14 housings | 2026-07-15 | 2026-07-14 | 42 | Closed | 2026-09-12 | Yes |
| CA-02 | 2026-07-20 | Complaint | Wrong label on one shipment | 2026-08-31 | 2026-08-25 | 36 | Closed | 2026-10-24 | — |
| CA-03 | 2026-08-05 | Internal audit | Two gauges past calibration due date in use | 2026-09-30 | — | 71 | Overdue | — | — |
| CA-04 | 2026-09-14 | SCAR-07 | Supplier plating thickness below spec | 2026-11-15 | — | 31 | Open | — | — |
| CA-05 | 2026-05-11 | NCR-298 | Burrs on cross-drilled holes | 2026-06-30 | 2026-06-19 | 39 | Closed | 2026-08-18 | — |
| Open / Overdue / Closed | 1 / 1 / 3 |
|---|---|
| Average days to close | 39.0 |
| Effectiveness checks overdue | 1 (CA-05) |
| Found not effective | 0 |
| Field | What to enter | Example |
|---|---|---|
| CA no. | A unique number that never gets reused. It is the link between the log and the full CAPA or 8D record. | CA-03 |
| Date opened | The day the decision to take corrective action was made, not the day the problem first happened. | 2026-08-05 |
| Source / reference | Where it came from and that record’s number, so you can trend actions by source. | Internal audit, finding IA-26-04 |
| Problem | One line: what was wrong, how much, where. Detail stays on the CAPA form. | Two gauges past calibration due date in use |
| Root cause | The verified cause, in one line. Leave it blank until it is verified rather than writing a guess. | Due-date report not reviewed when the calibration tech was absent |
| Action / owner / due date | The action that removes the cause, a named role and a real date. | Add backup reviewer to the calibration procedure / Quality Manager / 2026-09-30 |
| Date closed | When the action was fully implemented. Days open stops counting and the effectiveness-check date is set. | 2026-07-14 |
| Days open / Status | Calculated: days open up to the closed date or the as-of date; Overdue when the as-of date is past the due date and the action is not closed. | 71 / Overdue |
| Check due / Effective? | Check due is calculated from the closed date and the header interval. Enter Yes or No once you have evidence the problem has not come back. | 2026-09-12 / Yes |
The CAPA form is the full record for one action: problem, containment, root cause, action and verification. The log is the index of all of them, one line each, used to track status and report on the process.
A line is Overdue when it has no closed date and the as-of date in the header is later than its due date. On the blank Template sheet the as-of date is TODAY(), so status updates each time you open the file.
Long enough for the problem to have come back if the action did not work. That depends on how often the process runs; 30 to 90 days is a common choice, and you can set it in the header. Pick a period that covers enough production to judge.
You can add them with their own source, such as risk review. ISO 9001:2015 handles prevention through risk-based thinking rather than a separate preventive action clause, so many shops track them in the risk register instead.
Open, overdue and closed counts, average days to close, how many actions were verified effective, and any repeat causes. The summary at the bottom of the sheet gives the first four.
COPLAIN AI PLATFORM
Upload a nonconformance report, customer complaint, or audit finding and Coplain AI drafts a structured root cause analysis, ready to link from this log.
Generate yours automatically with Coplain →Related Tools & Templates