Knowella

Corrective Action Effectiveness Trend

This review asks one question of a quarter's corrective actions: did the same thing happen again. Its recurring failure is that it measures the CAPA process instead of the workplace. Closure rate, average days to close and backlog direction all improve while the same root cause recurs in the same area, because none of those figures counts recurrence, and a green quarter is reported to management review on the strength of administrative tidiness.

KnowComplyReviewCMP-05348 fields across 6 sectionsFull researchSee the form

Reviewed by Siddarth SinghCSPLast reviewed 16 August 2026

Basis
ISO 45001 cl.10.2
Workspace
KnowComply
Form type
Review
Review trigger
Quarterly, and after any repeat audit finding
Feeds
Management review, CAPA process change, objectives

The short version

  • Effectiveness has one honest measure: whether the same thing happened again. Closure rate, average days to close and backlog direction describe whether the process is busy, not whether it works.
  • ISO 45001 cl.10.2 and ISO 9001 cl.10.2 both require the effectiveness of corrective action to be reviewed, not merely its completion. This review is where that duty stops being per-record and becomes a judgement about the system.
  • The repeat rate is only as good as the rule that decides two events are the same. Most sites count a repeat as a reopened CAPA, which guarantees a near-zero rate because every recurrence is filed under a new number.
  • Weak actions percentage predicts next quarter's repeat rate better than any timeliness figure. Retraining, a toolbox talk and a reminder to be careful are the three actions most likely to sit against a cause nobody addressed.
  • Extent of condition is what separates a corrective action from a repair. If the same failure could exist on the other nine machines and nobody looked, the action was local and the recurrence will not be.
  • A trend review whose only output is a percentage has failed. The output that matters is a named systemic cause and a change to the CAPA process itself, which is why Main Systemic Cause and Process Change Required sit on the form.

What this is

What is a corrective action effectiveness trend?

What is a corrective action effectiveness trend?

It is a periodic review of a whole population of closed corrective actions, judging whether the process that produced them is preventing recurrence. Individual effectiveness verification asks whether one action worked against its own success criteria. The trend asks the harder question: across everything closed last quarter, how often did the event, the finding or the root cause come back.

How is effectiveness actually measured?

By recurrence, and by almost nothing else. An action is effective if the condition it was raised against stops happening, which can only be observed after the action has been in place long enough for the condition to have recurred. Closure, verification sign-off and days-to-close are all measures of activity, and a process can score perfectly on every one of them while the site keeps having the same accident.

Who should run the review?

Someone who does not own the corrective actions being reviewed. The compliance lead is the usual owner, and the reason is structural rather than hierarchical: the person who closed the actions cannot credibly judge whether their closure decisions were sound. Where the compliance function also raises and closes CAPAs, the review needs a second reader from audit or from another site.

Scope

When is a corrective action effectiveness trend required?

This review sits above the individual corrective action records and judges the process that produced them. It is a governance instrument rather than an investigation, and the two most common misuses are treating it as a status report on the CAPA backlog, or as somewhere to re-investigate one recurrence in detail.

Use this template when

  • The period has closed and a defined population of corrective actions is available to review
  • Repeat findings have appeared at an internal or certification audit and the CAPA process itself is in question
  • Management review needs an input on whether corrective action is working, rather than how much of it was done
  • A regulator or customer has questioned closure quality after an event that had a prior, similar precedent
  • Individual effectiveness verifications are consistently positive while events keep recurring, which is the signal that the verification criteria are too weak

Do not use it for

  • A single action's effectiveness, which belongs in the Effectiveness Verification record (FDN-016) judged against that action's own success criteria and observation window
  • Investigating one recurrence, which needs the incident or nonconformity investigation and a root cause method, not an aggregate percentage
  • Tracking action completion and dates, which is the Management Review Action Log (CMP-015) and the CAPA register itself
  • Reporting the numbers upward as a measured objective, which is the Performance Indicator Report (CMP-016)
  • Running the improvement this review calls for, which is the Continual Improvement Project Record (CMP-051) with its own problem statement and measurement

Compliance mapping

Which ISO 45001 cl.10.2 requirements does this satisfy?

Every management system standard requires corrective action to be effective, and almost none of them says how effectiveness is to be judged across a population. That gap is why this review exists: it is the instrument certification bodies and regulators reach for when the individual records all look complete and the same events keep occurring.

ClauseRequirementWhere it lands
ISO 45001 cl.10.2Action to control and correct, evaluation of the need to eliminate root causes so the event does not recur, and review of the effectiveness of the action takenQuality
ISO 9001 cl.10.2Review the effectiveness of corrective action taken, update risks and opportunities, and change the management system where neededQuality
ISO 45001 cl.9.1.1Monitoring, measurement and evaluation against defined criteria and methods, with results retained as documented informationVolume and timeliness
BRCGS Food Safety Issue 9 cl.3.7Corrective action completed to an agreed timescale with root cause identified and the effectiveness of the action confirmedVolume and timeliness
ISO 45001 cl.9.3Management review to consider incidents, nonconformities, corrective actions and continual improvement, with outputs including system changeOutcome
ISO 45001 cl.10.3Continual improvement of the suitability, adequacy and effectiveness of the management system, with results retainedOutcome
ISO 13485 cl.8.5.2Corrective action appropriate to the effects of the nonconformity, with review of the effectiveness of the action taken and records retainedRelated records
ISO 45001 cl.7.5.3Documented information controlled, retained and available where and when it is needed, including the period and population reviewedHeader

What it does not cover

  • Effectiveness verification of a single action, which needs its own success criteria, observation window and evidence, and lives in the verification record referenced from this review.
  • Root cause analysis, which belongs to the investigation of the individual event and uses a named method rather than an aggregate judgement.
  • Management review itself, which must consider audit results, objectives, resources and interested-party feedback alongside this input, not instead of them.
  • Regulatory notification duties, which run on their own statutory clocks and are unaffected by whether the corrective action later proved effective.
  • The corrective actions arising from this review, which need raising as CAPA records with owners and dates, since a systemic cause named here and left in the review is not an action.

Global

Corrective Action Effectiveness Trend requirements by country

The duty to correct is universal. The duty to check that correcting worked is explicit in the management system standards and in regulated-sector rules, and implicit almost everywhere else through the requirement to review and adapt preventive measures.

United States

OSH Act General Duty Clause; 21 CFR 117.165 for food; 21 CFR 820 for devices

No general duty to trend corrective action effectiveness, but explicit verification duties in FDA-regulated sectors.

For a regulated manufacturer, an action closed without effectiveness verification is citable on its own, and the same observation appearing across two inspections is what escalates a report to a warning letter.

United Kingdom

Management of Health and Safety at Work Regulations 1999, reg.5

Arrangements required for the effective planning, organisation, control, monitoring and review of preventive and protective measures.

Reg.5 puts the review of measures inside the legal duty, so a recurrence with a documented prior similar event is evidence the arrangements failed rather than evidence of bad luck.

European Union

Framework Directive 89/391/EEC art.6

Employers must adapt preventive measures to changing circumstances and aim to improve existing situations.

Adaptation is the operative word: an unchanged control after a repeat event is difficult to defend under most national implementations of the Directive.

Canada

Provincial OHS regulations; CSA Z1000 and CSA Z45001

Internal responsibility system with joint health and safety committee involvement in reviewing corrective action.

In most provinces the committee has a right of access to corrective action records, which turns a recurrence trend into a committee item rather than a management-only one.

Australia

Model WHS Regulations reg.38

Control measures must be reviewed and revised where they are not effective, including after an incident or when a new hazard is identified.

A repeat event is itself the statutory trigger for review, so recurrence data is the first evidence a regulator asks for after a second similar incident.

International

ISO 45001 cl.10.2; ISO 9001 cl.10.2; ISO 13485 cl.8.5.2

Effectiveness of corrective action must be reviewed and the management system changed where required.

Certification auditors sample closed actions against subsequent events and raise the nonconformity against the process, not the individual record, when recurrence appears.

How to complete it

How to complete a corrective action effectiveness trend, step by step

The form produces two percentages and a band. Whether the review means anything is decided before any of them are calculated, by four judgements the template cannot make for you.

Define what counts as a repeat, in writing, before you count

Write the test down and keep it stable across periods: same root cause code, same area, same equipment class, or same failed barrier, within a stated window such as twelve months. Then apply it by reading this period's events against the previous two, not by looking for reopened records. A repeat rate whose definition changes between quarters is a number, not a trend, and the first honest application will produce a worse figure than the last dishonest one.

Score action strength, not action presence

Action Strength Above Retraining and Cause Goes Beyond Human Error are the two fields that carry most of the review's predictive value. An action population dominated by retraining, briefings and reminders is a population that will recur, because those actions depend on the same human performance that failed. Read a sample of the actual action text rather than trusting the CAPA register's own classification, which is almost always generous.

Read extent of condition as a population question

The individual investigations each asked whether the same condition existed elsewhere, and most of them answered by not asking. Across a quarter that pattern is visible: a set of narrowly scoped actions, each correct for its own machine or shift, none of which looked sideways. Where extent of condition is consistently unconsidered, the systemic cause is the investigation procedure, and no amount of better closure discipline will fix it.

Name a systemic cause the process can act on

Main Systemic Cause is a free text field, and it is the most important thing on the form. Useful answers name a defect in the CAPA process: investigations are done by the area that had the event, effectiveness criteria are written as completion dates, or actions are closed by their owner without independent check. Answers such as poor safety culture are unactionable, and reviews producing them repeat unchanged for years.

What auditors find

Most common corrective action effectiveness trend findings

The document usually exists and is usually signed. What auditors find is that the numbers in it were produced by a method that could not have detected recurrence, and that nothing changed as a result.

FindingClauseWhat fixes it
Repeat rate calculated from reopened records, so recurrence filed under new references is invisible.ISO 45001 cl.10.2Define the repeat test on the event and root cause, and apply it across the previous two periods.
Review reports timeliness and backlog only; recurrence is not measured at all.ISO 9001 cl.10.2Make repeat rate the headline figure and demote closure statistics to context.
Effectiveness verified at the point of closure, before the condition could have recurred.ISO 13485 cl.8.5.2Set the verification date after an interval in which the event would have been expected to recur.
Action population dominated by retraining and briefings, with no higher-order controls.ISO 45001 cl.10.2Reject actions that rely on the human performance that failed unless a stronger control was assessed and refused in writing.
Extent of condition unconsidered across the whole population, so every action is local.ISO 9001 cl.10.2Require the investigation to state where else the condition could exist and what was checked.
Root causes recorded as human error or failure to follow procedure for most of the period.ISO 45001 cl.10.2Return any cause that ends at a person for a further why, and record the condition that made the error likely.
Review completed but not presented to management review, or presented without the systemic cause.ISO 45001 cl.9.3Carry the named systemic cause and the process change decision into the review agenda as a single item.
Process Change Required answered None for consecutive periods while the repeat rate is static.ISO 45001 cl.10.3Treat an unchanged repeat rate over three periods as evidence that a process change is due.
Population reviewed not defined, so the percentages cannot be reproduced or compared.ISO 45001 cl.7.5.3Record the period, the count of actions in scope and the selection rule with the record.
Learning not shared across areas; the same cause is investigated independently at three lines.ISO 45001 cl.10.3Publish the systemic cause and the action taken to every area with the same equipment or task.

Case in point

Case in point: the site with a four per cent repeat rate and the same accident three times

A packaging site ran a mature corrective action process. Ninety-six per cent of actions closed on time, average days to close had fallen from thirty-one to nineteen over two years, and the backlog was shrinking. The quarterly effectiveness trend recorded a repeat rate of four per cent, and Process Effective was answered Yes for six consecutive quarters. The compliance lead calculated the repeat rate the way the previous lead had: by counting corrective actions that had been reopened.

In the same two years there had been three separate near misses involving a pedestrian and a reversing counterbalance truck at the same dock. Each arrived as a new event with a new reference. Each investigation concluded that the driver had not sounded the horn and the pedestrian had entered the marked area, and each action was a retraining session plus a reminder at shift briefing. No action was ever reopened, so the repeat rate never noticed. The fourth event was a broken foot, and the HSE inspector who attended asked for every prior event at that dock within twenty-four months.

The failure was in the definition, not the discipline. Recurrence had been defined as an administrative state of a record rather than a property of the workplace, which made it impossible to detect. When the site recalculated on root cause and location, the repeat rate for the previous four quarters came out at twenty-two per cent, and the systemic cause was obvious: investigations were performed by the area supervisor who had to keep the dock running, and every action they could implement alone was a briefing.

The template

The template, field by field

The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.

48fields
6 sections
Reference
CMP-053
Archetype
Review
Record ID
CAE-2026-000
Scoring
Repeat rate
Direction
Low is good
Singleton
Yes
Basis
ISO 45001 cl.10.2
Links
Links CAPA, Findings, Effectiveness
Tags
Improvement, CAPA
Sections
6
Fields
48
Follow up fields
3
Repeating sections
0
Links out
3
Field typesOwn ID, generated on saveCase thread and parentPick list from a registryLinked to another templateFollow up, dashed outlineScored

Header

10 fields
Text

Review ID*

Generated on save

Auto sequence. Format CAE-2026-000.

The record's own ID. Other templates point at this value.

Single Choice

Status*

Scored

Drives who this goes to next.

  • Planned2 pts
  • In progress2 pts
  • Complete3 pts
  • Deferred0 pts
  • Open0 pts
  • Closed3 pts
  • Overdue0 pts
Date & Time

Date and Time*

Users

Completed By*

Pick List

Site*

From FDN-001 Site NameFilter: Status is Active
Text

Site ID*

Linked

Format SITE-000.

Links to FDN-001 Site ID

Text

Period Reviewed*

Users

Reviewed By*

Numeric Answer

CAPAs In Scope*

Scored
Info

A High Repeat Rate Means The Process Makes Paperwork

The single best measure of whether corrective action works is how often the same thing happens again. Everything else is activity.

Volume and timeliness

6 fields
Single Choice

CAPAs Raised*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

CAPAs Closed On Time*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Overdue CAPAs*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Average Days To Close*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

CAPAs Extended More Than Once*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Backlog Growing Or Shrinking*

GrowingStableShrinking

Quality

6 fields
Single Choice

Root Cause Recorded For Each*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Cause Goes Beyond Human Error*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Action Strength Above Retraining*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Preventive Action Considered*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Extent Of Condition Considered*

Scored
  • Yes2 pts
  • No0 pts
  • Not applicableexcluded from denominator
Single Choice

Effectiveness Verified*

Scored
  • Yes3 pts
  • Scheduled1 pt
  • No0 pts

Outcome

6 fields
Single Choice

Repeat Events Occurred*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Repeat Findings At Audit*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Same Root Cause Recurring*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Same Area Recurring*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Verification Found Actions Ineffective*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Learning Shared Across Areas*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts

Related records

1 field
Text

Effectiveness Verification ID

OptionalLinked

A sample verification reviewed in this trend.

Links to FDN-016 Verification ID

Outcome

19 fields
Numeric Answer

Repeat Rate Percent*

Scored
Numeric Answer

Weak Actions Percent*

Scored
Single Choice

Process Effective*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Text

Main Systemic Cause

Optional
Single Choice

Process Change Required*

Scored
  • None3 pts
  • Minor1 pt
  • Major0 pts
Single Choice

Feeds Management Review*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Numeric Answer

Items Assessed*

Excludes anything marked N/A.

Numeric Answer

Items Failed*

Numeric Answer

Score Percent*

Scored

Calculated on submission. High is good. N/A items leave the denominator.

Single Choice

Result Band*

Scored
  • Pass3 pts
  • Caution1 pt
  • Fail0 pts
Numeric Answer

Completeness Percent*

How much of the template was actually answered. A high score on a half completed form is not a high score.

Single Choice

Action Required*

Scored

Raise the action record, then enter its reference here.

  • No2 pts
  • Yes0 pts
Single Choice

Priority

OptionalScoredShows if Action Required equals Yes
  • High0 pts
  • Medium1 pt
  • Low3 pts
Text

CAPA ID

OptionalLinkedShows if Action Required equals Yes

Format CAPA-2026-00000.

Links to FDN-014 CAPA ID

Users

Action Owner

OptionalShows if Action Required equals Yes
Users

Compliance Lead*

Signature

Signature*

Users

Site Manager*

Signature

Second Signature*

CMP-053 · record IDs look like CAE-2026-000 · Links CAPA, Findings, Effectiveness

Open in Knowella

Run it with agents

From a document you fill in to a programme that runs itself

The review itself is an afternoon's work. What fails around it is the data: the events that were never coded to a cause, the actions whose text nobody read, and the systemic cause that was named last quarter and acted on by nobody.

KnowComply

Holds the corrective action population by period and site, matches this period's events against earlier ones on cause and area, and produces the repeat rate the review is meant to report.

Ella
Ella

Reads the action text rather than its classification, flags the population as weak where actions rely on retraining and briefing, and tracks whether last period's systemic cause produced anything.

KnowSafe

Supplies the incident and near-miss records with their causes and locations, which is the only source from which recurrence can honestly be computed.

KnowQuality

Supplies the nonconformity and audit finding side of the same population, so a repeat finding at audit is counted against the same process as a repeat event on the floor.

This template lives in KnowComply — audit and governance. Audit programmes, legal register, management review, risk and certification.

Meet KnowComply→

Glossary

Corrective Action Effectiveness Trend definitions and key terms

Corrective action
Action to eliminate the cause of a detected nonconformity or incident so that it does not recur, as distinct from the correction that deals with the event itself.
Preventive action
Action taken against a potential nonconformity that has not yet occurred, typically arising from a condition found somewhere else.
Repeat rate
The proportion of events in a period that match an earlier event on root cause, area or failed barrier within a stated window. The measure this review exists to produce.
Extent of condition
The check on whether the same condition exists beyond the place it was found, which turns a local repair into a corrective action.
Effectiveness verification
Confirmation after an interval that the condition the action targeted has stopped occurring, judged against criteria set when the action was raised.
Weak action
An action that depends on the same human performance that failed, typically retraining, a briefing, a reminder or a revised procedure with no change to the conditions.
Systemic cause
A defect in the management process itself rather than in the event under investigation, such as investigations being carried out by the area that had the event.
Escape point
The point in the process where the problem should have been detected and was not, which usually needs a separate action from the cause itself.

FAQ

Frequently asked questions about corrective action effectiveness trend

Is closure rate a measure of effectiveness?+

No. It is a measure of administration. A site can close every action on time, verify every one, and keep having the same events, because closure records that somebody did something and effectiveness records that the something worked. Closure rate is worth reporting as context, because a large overdue backlog does predict poor effectiveness, but it is not the answer to the question this review asks.

How long after closure should effectiveness be judged?+

Long enough for the condition to have recurred if the action failed. For a daily task that means weeks; for a quarterly maintenance activity it means at least two cycles; for a seasonal process it means the next season. Verification signed on the day of closure proves only that the action was implemented, which is a different question and one the closure already answered.

What repeat rate is acceptable?+

The direction matters more than the level, because the level depends entirely on your definition of a repeat. A site moving from twenty-two per cent to fourteen over three quarters with a stable definition is improving. A site reporting three per cent every quarter is almost certainly measuring reopened records. Set your own baseline in the first honest period and judge against it.

Should this review cover safety, quality and environmental actions together?+

Together, if the CAPA process is shared, because the systemic causes are shared too. Investigations performed by the area that had the event, effectiveness criteria written as dates, and actions closed by their own owner are process defects that produce recurrence in all three domains. Split the reporting by domain if the audiences differ, but analyse the population as one.

Who decides whether the process is effective overall?+

The reviewer proposes and management review decides, which is why Feeds Management Review is on the form. The judgement is not arithmetic: a low repeat rate with a high weak-action percentage is a process about to deteriorate, and a rising repeat rate immediately after the definition was tightened is a process getting healthier. Both need arguing rather than scoring.

How many records of this review should we hold?+

One per period per site. The review names the period it covers and the population of actions in scope, so it is inherently a repeating record rather than a register maintained in place, and comparability between periods is the whole point. Keep the definition of a repeat stable across them, and record any change to it on the face of the record that first uses the new rule.

Keep going

Related templates and programmes

Siddarth Singh

Written and reviewed by

Siddarth Singh

Founder & Chief Executive Officer, Knowella

Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.

  • Certified Safety Professional (CSP), Board of Certified Safety Professionals
  • MBA, University of Chicago Booth School of Business
  • MS and BS, The Ohio State University, Industrial and Systems Engineering
  • Six Sigma Black Belt
Verify with BCSP →

Sources and last review. Reviewed 16 August 2026 against:

  • ISO 45001:2018 clauses 10.2, 10.3, 9.1.1 and 9.3
  • ISO 9001:2015 clauses 10.2 and 9.1.3
  • ISO 13485:2016 clause 8.5.2, corrective action
  • 21 CFR 117.165, verification of implementation and effectiveness (FDA preventive controls for human food)
  • Management of Health and Safety at Work Regulations 1999, regulation 5 (GB)
  • Model WHS Regulations regulation 38, review of control measures (Australia)
  • BRCGS Food Safety Issue 9 clause 3.7, corrective and preventive action

This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.