# Corrective action plan template > A corrective action plan (CAPA) template that tracks each action from decision to proof. It records the problem and cause, the action strength, an owner, a due date, evidence of completion and a later effectiveness check. The rule it enforces: an action is done when someone has verified the problem stopped, not when the task is checked off. Source: https://incidentkit.ai/templates/corrective-action-plan ยท Updated Oct 5, 2026 ## When to use it - An investigation or root cause analysis has named causes and you need a plan with owners and dates. - An audit finding, survey deficiency or inspection citation needs an internal action plan behind the formal reply. - A recordable injury or a high-potential near miss calls for a documented fix and follow-up. - A QAPI performance improvement project needs its actions tracked until the measure moves. - An insurer, accreditor or governing body asks to see that corrective actions were done and worked. ## The template ### 1. Plan header - Plan ID - Source: Incident investigation / Root cause analysis / Near-miss trend / Survey or inspection finding / Audit finding / Complaint or grievance / QAPI data review / Other - Related incident, finding or analysis reference - Date opened - Facility or department - Plan owner (one name and role) - Executive sponsor (The leader who can remove barriers and approve resources.) ### 2. Problem and cause - Problem statement (What went wrong, where and how often. No names.) - Root cause or causes this plan addresses (Copy the causal statements from your analysis. If the cause is unknown, the first action is to find it.) - Risk if nothing changes - Priority: Low / Medium / High / Critical: act now - Containment: what was done right away (Interim steps that protect people today, like removing equipment. Containment is not the fix.) ### 3. Action (copy this section for each action) - Action (Start with a verb: 'Install motion-sensor night lights in every resident bathroom', not 'Improve lighting'.) - Action type: Corrective: fixes this event / Preventive: stops the same cause elsewhere / Containment: interim measure / Both corrective and preventive - Action strength (Pair a weaker action with a stronger one. Training alone rarely holds.): Stronger: design change, forcing function, simplify or standardize / Intermediate: checklist, redundancy, software or staffing change / Weaker: training, policy or reminder - Owner (one name and role) (One accountable person, not a team. Work can be handed off, accountability cannot.) - Start date - Due date (Set a real date, sooner for higher risk. If it slips, record the new date and why.) - Resources or approval needed - Status: Not started / In progress / Complete: awaiting verification / Verified effective / Overdue / Cancelled: reason recorded ### 4. Evidence of completion - What proves the action was done? (Name the evidence before you start: a closed work order, a photo, a signed training roster with test results, a policy with its version, a settings screenshot.) - Evidence location (file, link or binder) - Date completed - Verified by (Someone other than the owner should confirm the evidence.) - Date verified ### 5. Effectiveness check - What measure shows the problem is gone? (Pick a measure tied to the cause: audit pass rate, repeat events, observed compliance.) - Target and how long it must hold (For example: no repeat events and every audit passing for three months.) - Baseline before the action (number and period) - Effectiveness check date (Set it when you plan, not when the action closes. Allow enough time for several cycles.) - Result at the check (number and period) - Outcome: Effective: problem resolved and sustained / Partly effective: adjust the action / Not effective: reopen the analysis - Next monitoring date, if sustained ### 6. Review and escalation - Reviewed by the QAPI or safety committee - Committee review date - Barriers or delays - Escalated to (leader) and reason - Lessons shared with other units or sites ### 7. Closure - Every action is verified - The effectiveness check passed - Closure summary - Plan owner - Quality, risk or EHS leader - Closure date ## How to fill it out well 1. Start from causes, not symptoms. Each action should trace back to a root cause in your analysis. 2. Write each action as a specific change with a verb. If someone could do it and no one would notice, it is too vague. 3. Rank each action's strength. Aim for at least one stronger or intermediate action per cause, and use weaker actions to support them. 4. Give each action one owner, a due date and the evidence that will prove it. Decide all three when you plan. 5. Have someone other than the owner verify completion against the evidence, and attach it. 6. Set the effectiveness measure and check date before work starts. Close the plan only when the check passes. 7. Review open and overdue actions at every QAPI or safety committee meeting. Copy the Action section for each added action. ## Tips - Three strong actions beat ten vague ones. Fewer, specific actions get finished and checked. - Do not extend due dates silently. A slipped date is a leadership decision, and the reason belongs in the record. - Keep containment apart from the fix. Containment protects people this week. The fix changes the system. - Ask the people who do the work if the action will hold at 3 a.m. on a short-staffed night. - AHRQ PSNet lists measuring results among the keys to effective root cause analysis. The effectiveness check is that step. A survey reply is separate: see [what to put in a plan of correction](https://incidentkit.ai/blog/what-to-put-in-a-plan-of-correction). ## Frequently asked questions ### What is a corrective action plan? A written list of the specific changes that will fix a problem and keep it from coming back. Each action has an owner, due date, proof it was done and a check that it worked. Often called CAPA, for [corrective and preventive action](https://incidentkit.ai/glossary/corrective-and-preventive-action). ### What is the difference between corrective and preventive action? Corrective action fixes the cause of a problem that already happened. Preventive action stops the same cause from causing a problem elsewhere, like another unit, shift or site. A good plan does both. ### What is an effectiveness check? A planned, later look at data to confirm the problem stopped. Nursing home QAPI requires measuring success after acting and tracking results so gains last (42 CFR 483.75(d)(1)). ASC rules require making sure improvements last (42 CFR 416.43(c)(2)). See [effectiveness review](https://incidentkit.ai/glossary/effectiveness-review). ### How strong should corrective actions be? IHI recommends at least one stronger or intermediate action for each cause. Stronger actions change the design or process. Training and policy changes are often needed but rarely last alone. Leaders should approve, and one person should own and measure each by a set date. ### Who should own a corrective action? One named person, not a team. The owner is accountable for finishing it and for status reports, and can hand off the work. IHI says to assign one person, who may be outside the analysis team, and a completion date. Someone else should verify it. ## Sources - [IHI Patient Safety Essentials Toolkit: Action Hierarchy (part of RCA2), as hosted by the Minnesota Department of Health](https://www.health.mn.gov/facilities/patientsafety/adverseevents/toolkit/docs/safetytoolkit_actionhierarchy.pdf) - [eCFR: 42 CFR 483.75, Quality assurance and performance improvement (nursing homes)](https://www.ecfr.gov/current/title-42/section-483.75) - [eCFR: 42 CFR 416.43, Quality assessment and performance improvement (ASC)](https://www.ecfr.gov/current/title-42/section-416.43) - [AHRQ PSNet: Root cause analysis (primer)](https://psnet.ahrq.gov/primer/root-cause-analysis) ## Related - [Corrective Actions: How to Close Them With Proof](https://incidentkit.ai/use-cases/close-corrective-actions) - [Corrective and preventive actions (CAPA) tracking](https://incidentkit.ai/product/corrective-actions) - [Root cause analysis and CAPA: methods and strong actions](https://incidentkit.ai/guides/root-cause-analysis-and-capa-guide) - [Corrective and preventive action: definition and meaning](https://incidentkit.ai/glossary/corrective-and-preventive-action) - [Effectiveness review: definition and meaning](https://incidentkit.ai/glossary/effectiveness-review) - [Root Cause Analysis Worksheet (5 Whys Template)](https://incidentkit.ai/templates/root-cause-analysis-worksheet)