TEMPLATESCA LOGFree Excel (.xlsx) download

Corrective Action Log Template

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.

Who this template is for

When to use it

Standards it supports

How to use this template

  1. Set the header — enter the company and log owner, and the number of days after closure to check effectiveness. The as-of date uses TODAY() on the blank sheet.
  2. Log each action when it opens — give it a number, the date opened, the source and its reference, and a one-line problem statement.
  3. Add cause, action, owner and due date — fill these in once the root cause is verified. Status shows Overdue as soon as the as-of date passes the due date.
  4. Close it — enter the date closed when the action is done. Days open stops counting and the effectiveness-check date is set.
  5. Verify effectiveness — on or after the check date, record Yes or No and who verified it. A No means the problem came back: reopen or raise a new action.

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.

What's inside the template

1

Header

Company, log owner, as-of date (TODAY()) and the effectiveness-check interval in days

2

Identification

CA number, date opened, source (NCR, complaint, audit, SCAR) and source reference

3

Problem and action

Problem statement, verified root cause, corrective action, owner and due date

4

Status

Date closed, with days open and Open / Overdue / Closed calculated

5

Effectiveness

Calculated check-due date, Effective? (Yes / No) and who verified it

6

Summary

Open, overdue and closed counts, average days to close, overdue effectiveness checks and actions found not effective

Example: a completed template

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.

Log

CAOpenedSourceProblemDueClosedDays openStatusCheck dueEffective?
CA-012026-06-02NCR-311Bore oversize on 14 housings2026-07-152026-07-1442Closed2026-09-12Yes
CA-022026-07-20ComplaintWrong label on one shipment2026-08-312026-08-2536Closed2026-10-24—
CA-032026-08-05Internal auditTwo gauges past calibration due date in use2026-09-30—71Overdue——
CA-042026-09-14SCAR-07Supplier plating thickness below spec2026-11-15—31Open——
CA-052026-05-11NCR-298Burrs on cross-drilled holes2026-06-302026-06-1939Closed2026-08-18—

Summary

Open / Overdue / Closed1 / 1 / 3
Average days to close39.0
Effectiveness checks overdue1 (CA-05)
Found not effective0

The math in this Example

How to fill in each field

FieldWhat to enterExample
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 openedThe day the decision to take corrective action was made, not the day the problem first happened.2026-08-05
Source / referenceWhere it came from and that record’s number, so you can trend actions by source.Internal audit, finding IA-26-04
ProblemOne line: what was wrong, how much, where. Detail stays on the CAPA form.Two gauges past calibration due date in use
Root causeThe 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 dateThe 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 closedWhen the action was fully implemented. Days open stops counting and the effectiveness-check date is set.2026-07-14
Days open / StatusCalculated: 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

Common mistakes

Frequently asked questions

What is the difference between a corrective action log and a CAPA form?

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.

How is Overdue calculated?

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.

How long after closing should effectiveness be checked?

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.

Should preventive actions go in the same log?

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.

What should I report from the log at management review?

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.

See also

COPLAIN AI PLATFORM

Generate yours automatically from your existing docs

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