# A fix is done when the evidence says so.

> IncidentKit tracks corrective and preventive actions (CAPA) from investigation to verification. Each action has an owner, due date, required evidence and an effectiveness check. Reminders escalate when actions slip. An incident cannot close until its actions are verified.

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

**Corrective actions (CAPA)** (correct): Every fix has an owner, a date and proof. Unverified fixes keep it open.

## What it does

- **Owner, due date, evidence** All three are required before an action can be marked complete.
- **Reminders and escalation** Overdue actions remind the owner, then escalate to the next person.
- **Effectiveness check** A scheduled follow-up asks: did the problem come back in the window you set?
- **Closure gate** The incident closes only when its actions are verified. “I think we did that” stops being an answer.
- **Suggested actions are labeled** Lauren's suggestions are marked as suggestions until a person adopts them.
- **Reporting across incidents** See open, overdue and verified actions by owner, site and type for your committee.

## How it works

1. **Create actions from findings** Each root cause gets an action.
2. **Assign owner and date** Say what evidence is required.
3. **Complete with evidence** Upload the proof.
4. **Verify effectiveness** Check at the interval you set, then close.

## Frequently asked questions

### What is the difference between corrective and preventive action?

A corrective action fixes a problem that has happened. A preventive action removes a risk before it causes an incident. IncidentKit tracks both the same way. See [CAPA in the glossary](https://incidentkit.ai/glossary/corrective-and-preventive-action).

### How do surveyors and auditors use CAPA records?

They check three things: did you find a cause, act on it, and verify the fix worked. An owner, evidence and an effectiveness review answer all three. See the [CAPA guide](https://incidentkit.ai/guides/root-cause-analysis-and-capa-guide).

### Can actions span more than one incident?

Related incidents can share a pattern. Analytics shows repeats by location, shift, equipment and cause. You can see when an action did not hold.

## Related

- [Incident investigations and root cause analysis](https://incidentkit.ai/product/investigations)
- [QAPI, survey and OSHA compliance packets](https://incidentkit.ai/product/compliance-packets)
- [Corrective Actions: How to Close Them With Proof](https://incidentkit.ai/use-cases/close-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)
- [ASC QAPI requirements: 42 CFR 416.43 explained](https://incidentkit.ai/compliance/cms-qapi/ambulatory-surgery-centers)
- [Nursing home QAPI requirements: 42 CFR 483.75 explained](https://incidentkit.ai/compliance/cms-qapi/skilled-nursing-facilities)