How to close corrective actions with proof
Short answer
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.
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.
| Item | 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.
- Assign at sign-offCreate each action at sign-off: owner, due date, success measure, check date.
- Review overdue items weeklyTake ten minutes on late items. Escalate to the owner's manager after 7 days overdue, to the QAPI or safety committee after 30.
- Attach evidence at completionThe owner uploads proof: a photo, work order or revised procedure.
- Run the check on the dateA second person compares the measure to the baseline, such as falls before and after.
- Close or reopenIf 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 carry an owner, due date, evidence and effectiveness check. Nothing closes until a person verifies it. Each links to its investigation.
The audit trail records every change, date moves included. Analytics show whether the cluster shrank.
The parts of IncidentKit behind this
- Corrective actions (CAPA): Every fix has an owner, a date and proof. Unverified fixes keep it open.
- Investigations and RCA: A guided investigation: find causes, pick a disposition, and a person signs.
- Audit trail: Every edit is logged, so you can show who changed what, and when.
- Analytics: See which rooms, shifts and equipment keep showing up in your incidents.
- Routing and escalation: Severity decides who gets paged, and it escalates if nobody acts.
- Compliance packets: Records laid out the way surveyors and inspectors want them.
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))
- eCFR: 42 CFR 416.43, ASC QAPI
- AHRQ PSNet: RCA2 and the evolution of root cause analysis
- IHI: RCA2, Improving Root Cause Analyses and Actions to Prevent Harm
- CDC NIOSH: Hierarchy of controls
Reviewed against the sources above on Oct 5, 2026. Rules change: confirm current requirements with the issuing body or your counsel before relying on any summary.
Start with one incident.
Create your kit in about ten minutes and report the first incident the same day. Free to start, no card.