# How to close corrective actions with proof

> A corrective action is closed only when the change is in place and a dated check shows it worked. Give each action one owner, a due date, a success measure and a check date. Prefer design changes to retraining.

Source: https://incidentkit.ai/use-cases/close-corrective-actions · Updated Oct 5, 2026

For: Quality or EHS manager who owns the corrective-action log

## When is a corrective action closed?

It is closed when the change is in place and a dated check shows it worked. Done is not closed. CMS's nursing home rule wants improvements measured and sustained (42 CFR 483.75(d)(1)).

The ASC (surgery center) rule agrees: improvements must be sustained (42 CFR 416.43(c)(2)) and evaluated for effectiveness (416.43(e)(2)).

Use four statuses: open, done (evidence attached), verified (a second person checked) and closed. A failed check reopens the action.

## The parts of a good corrective action

Every action needs eight parts. Miss one and it stays open or closes with no proof.

| Part | What good looks like | Weak version |
| --- | --- | --- |
| Link to cause | Names the factor it answers | Fix the problem |
| Action | One concrete change | Be more careful |
| Strength | Design change, not a reminder | Retrain staff |
| Owner | One named role | Nursing |
| Due date | A calendar date | ASAP |
| Evidence | Photo, work order, procedure | Done |
| Success measure | A count or visible result | Improved |
| Check date | A review at 30, 60 or 90 days | None |

### What counts as evidence

| Type of action | Evidence that counts | Not enough |
| --- | --- | --- |
| Equipment or layout change | Work order, dated photo, test record | A verbal yes |
| Procedure change | Signed procedure and a use audit | An email announcing it |
| Training | Competency check and observed-practice audit | A sign-in sheet alone |
| Monitoring plan | Each check recorded on its date | A plan with blanks |

## Choose stronger actions

RCA2, the patient safety guide from the National Patient Safety Foundation (now part of IHI), ranks actions by strength. Forcing functions and standard equipment are strong; education is weak. Industry uses the NIOSH hierarchy of controls.

| Strength | Healthcare | Industrial |
| --- | --- | --- |
| Stronger | A scan that blocks a wrong-drug pick | Eliminate the hazard; add a guard or interlock |
| Middle | Fewer steps that rely on memory | Procedures, rotation, access limits |
| Weaker | Education, new policies, reminders | Protective equipment, which needs steady use |

Pair a weaker action with a stronger one, or use it when it is all you control.

## Two worked examples

One action from each setting, as logged.

|  | Healthcare | Industrial |
| --- | --- | --- |
| Event | Wrong-strength vial caught at a scan | Machine guard left off after cleaning |
| Contributing factor | Two strengths shelved together | No guard check before restart |
| Action | Store them apart, labelled differently | Fit an interlock that stops the machine |
| Owner and due date | Pharmacy lead, within 14 days | Maintenance manager, within 30 days |
| Evidence | Photo of the new shelving | Work order and test record |
| Success measure | No mixed strengths in monthly audits | Zero bypass events on the line |
| Check | Shelf audit at 30 and 90 days, by a second pharmacist | Interlock test and event review at 60 days, by EHS |

These are illustrations, not data from any facility. A second person runs each check. A few strong actions beat a long list of weak ones.

## A close-out routine

Five weekly steps keep actions honest.

1. **Assign at sign-off** Create each action at sign-off: owner, due date, success measure, check date.
2. **Review overdue items weekly** Take ten minutes on late items. Escalate to the owner's manager after 7 days overdue, to the QAPI or safety committee after 30.
3. **Attach evidence at completion** The owner uploads proof: a photo, work order or revised procedure.
4. **Run the check on the date** A second person compares the measure to the baseline, such as falls before and after.
5. **Close or reopen** If the measure moved, close it. If not, reopen with a stronger action and a new date.

## Mistakes to avoid

These habits flatter the log.

- Closing at completion. An email does not show the problem stopped.
- Retraining as the only action. It is the weakest.
- Shared ownership. Pick one owner; list helpers separately.
- Moving due dates without a note. Keep the original date and reason.
- Owners verifying their own fix. Use a second person.
- Monitoring that fades. CMS's F867 example: monthly checks for three months, no evidence for month two.
- Vague actions. If you cannot say what would show failure, rewrite it.

## How IncidentKit changes the job

[Corrective actions](https://incidentkit.ai/product/corrective-actions) carry an owner, due date, evidence and effectiveness check. Nothing closes until a person verifies it. Each links to its [investigation](https://incidentkit.ai/product/investigations).

The [audit trail](https://incidentkit.ai/product/audit-trail) records every change, date moves included. [Analytics](https://incidentkit.ai/product/analytics) show whether the cluster shrank.

## Before and after

- **Before:** Actions say "educate staff" and close when the email goes out.
  **After:** One owner, one due date, one success measure.
- **Before:** Several people own an action, so no one does.
  **After:** Nothing closes until evidence is attached and a person verifies.
- **Before:** Due dates slip while the log stays green.
  **After:** Date changes stay in the audit trail.
- **Before:** No one can show a surveyor, insurer or board that a fix worked.
  **After:** Effectiveness checks are set up front.

## Frequently asked questions

### What is the difference between a correction, a corrective action and a preventive action?

A correction fixes the problem in front of you. A corrective action removes the cause. A preventive action acts on a risk before an event. Programs often track all three as CAPA.

### How long should an effectiveness check wait?

Long enough for the event to recur if the fix failed: 30 days for frequent events, a proxy such as audit results for rare ones. Set the date when you create the action.

### Who should verify that an action worked?

Someone other than the owner, such as a quality lead or a supervisor from another area, who checks evidence.

### What should happen when an action is overdue?

Escalate by a set rule, such as to the owner's manager after 7 days and the QAPI committee after 30. Record the new date and reason, and keep the original.

## Sources

- [CMS: State Operations Manual Appendix PP, F867 (42 CFR 483.75(c)-(e), (g))](https://www.cms.gov/medicare/provider-enrollment-and-certification/guidanceforlawsandregulations/downloads/appendix-pp-state-operations-manual.pdf)
- [eCFR: 42 CFR 416.43, ASC QAPI](https://www.ecfr.gov/current/title-42/section-416.43)
- [AHRQ PSNet: RCA2 and the evolution of root cause analysis](https://psnet.ahrq.gov/perspective/conversation-jessica-behrhorst-about-evolution-root-cause-analysis)
- [IHI: RCA2, Improving Root Cause Analyses and Actions to Prevent Harm](https://www.ihi.org/library/tools/rca2-improving-root-cause-analyses-and-actions-prevent-harm)
- [CDC NIOSH: Hierarchy of controls](https://www.cdc.gov/niosh/hierarchy-of-controls/about/index.html)

## Related

- [Corrective and preventive actions (CAPA) tracking](https://incidentkit.ai/product/corrective-actions)
- [Corrective Action Plan Template (CAPA, Printable)](https://incidentkit.ai/templates/corrective-action-plan)
- [Effectiveness review: definition and meaning](https://incidentkit.ai/glossary/effectiveness-review)
- [Corrective and preventive action: definition and meaning](https://incidentkit.ai/glossary/corrective-and-preventive-action)
- [Root cause analysis and CAPA: methods and strong actions](https://incidentkit.ai/guides/root-cause-analysis-and-capa-guide)
- [Hierarchy of controls: definition and meaning](https://incidentkit.ai/glossary/hierarchy-of-controls)