It's 9 AM on a Tuesday. Your Statement of Deficiencies arrived. Your administrator is staring at you. The surveyor noted four deficiencies. You have 10 calendar days to submit your Plan of Correction.
This is not a drill. You don't have time to figure out CMS requirements from scratch. This guide gives you everything you need: the legal framework, a free template you can actually use today, and the specific language patterns that get PoCs accepted on first review โ plus the mistakes that send them back.
If you want to skip the theory and get pre-formatted, department-specific PoC templates for the most common F-tags, those are in the Plan of Correction Templates pack ($69). This article gives you the framework. The templates give you the words.
You Got Your SOD. Now What?
First: breathe. A Statement of Deficiencies is not a death sentence. It's a document that tells you specifically what CMS believes you did wrong and gives you the chance to respond in writing. That response โ your Plan of Correction โ is your opportunity to demonstrate that you understand the problem and have fixed it.
Second: note your deadlines. The federal requirement is 10 calendar days from receipt of the SOD to submit your PoC (42 CFR ยง488.402(f)). Some states have tighter windows. Check your state's specific requirements, because a late PoC is worse than an imperfect one.
Third: assign ownership. One person writes the PoC for each citation. Multi-tag citations are where facilities get in trouble by distributing the writing across departments without a coordinator. Someone needs to hold the whole document together โ usually the DON, administrator, or compliance officer.
The most common first-draft PoC mistake is written under stress, at speed, and submitted before anyone re-reads it against the actual CMS regulatory requirement being cited. Take two hours to actually read the F-tag language in your SOD. Not the description โ the regulation itself. That tells you exactly what "fixed" looks like in CMS's mind.
Fourth: read all of the SOD carefully before writing any of the PoC. Citations frequently reference each other. A staffing issue (F725) is often linked to a care quality issue (F684). Writing them in isolation produces plans that look disconnected and unconvincing.
The 5 Required CMS Elements โ What Every PoC Must Contain
CMS requires every Plan of Correction to address five specific elements for each cited deficiency. These aren't suggestions โ they're the checklist a state surveyor uses to determine whether to accept or reject your plan. Missing or vaguely addressing any of them means rejection and a correction cycle that costs you days.
Address the specific residents identified in the SOD. What happened to them? What will you do โ or what have you already done โ to address their individual situation?
"Resident [X] will be assessed by the attending physician within 48 hours and a care plan update will be completed by [DATE]."
CMS wants to know you're thinking beyond the cited residents. How do you find everyone at risk from the same systemic failure?
"A full-house audit of all residents with [condition] will be completed by the DON by [DATE] to identify any additional residents affected."
This is the most important element โ and the one most facilities get wrong. System changes, policy revisions, process updates. Not "staff will be reminded."
"Policy #IC-04 will be revised to require documented hand hygiene observations every shift, effective [DATE]. All nursing staff will complete competency sign-off by [DATE]."
Who is watching? How often? What are they looking at? CMS wants a monitoring mechanism, not just a promise.
"The Infection Control Nurse will conduct weekly audits of 10 randomly selected hand hygiene observations for 90 days, with results reported to the QAPI committee monthly."
A specific, realistic date. Not "ongoing." Not "as soon as possible." A calendar date. CMS uses this date to schedule re-surveys.
"All corrective actions will be completed by [DATE]."
CMS reviewers read hundreds of PoCs. They can spot when a facility copy-pasted the five elements structure without actually addressing the specific citation. Make sure each element directly ties back to the specific deficient practice described in the SOD โ not a generic description of what the element should say.
Free Plan of Correction Template Framework
Here is a usable template structure. This is a starting point โ the specific language must be tailored to your citation. Copy this format for each deficiency cited in your SOD.
Facility Name: ___________________________
Citation (F-Tag #): ______________ Severity: ______________ Scope: ______________
Element 1 โ Corrective Action for Affected Residents:
The following resident(s) cited in this deficiency: [List resident identifiers or initials]. For each affected resident, the following actions have been/will be completed:
โข [Action 1 + responsible person + completion date]
โข [Action 2 + responsible person + completion date]
All affected residents will be re-assessed by [TITLE] by [DATE].
Element 2 โ Identification of Other At-Risk Residents:
To identify residents who may be affected by the same deficient practice, the following audit/review will be completed:
โข [Audit description] conducted by [TITLE] by [DATE]
โข Criteria used to identify at-risk residents: [List criteria]
โข Results will be reviewed by [TITLE] and corrective action taken for any additional residents identified.
Element 3 โ Systemic Changes to Prevent Recurrence:
The following system-level changes will be implemented to prevent recurrence:
โข [Policy/procedure change + effective date]
โข [Staff education/competency + completion date]
โข [Process change + implementation date]
These changes address the root cause of the deficiency, which was identified as: [Root cause statement].
Element 4 โ Monitoring Plan:
Ongoing monitoring to ensure sustained compliance will include:
โข [Audit type] conducted by [TITLE] [frequency] for [duration]
โข Results reported to [COMMITTEE/SUPERVISOR] [frequency]
โข Threshold for escalation: [Define what triggers a higher level of response]
โข Monitoring will be incorporated into the facility's QAPI program beginning [DATE].
Element 5 โ Completion Date:
All corrective actions will be completed by: [DATE]
A few notes on using this template:
- Dates must be real. If you write a completion date that has already passed by the time CMS reviews your PoC, you have a problem. Use dates you can actually meet.
- The root cause statement in Element 3 matters. It demonstrates that you understand why the deficiency happened โ not just that it happened. Generic root causes ("staff was not following policy") are red flags.
- Element 4 monitoring must be specific. "Ongoing monitoring" is not a monitoring plan. Name the audit tool, the frequency, the person responsible, and where results go.
Common Mistakes That Get PoCs Rejected
We analyzed what 80% of the PoCs we reviewed had in common: the same avoidable patterns appear over and over. Here's what gets plans sent back.
Mistake 1: Vague Corrective Actions
What it looks like: "Staff will be re-educated on the policy. Going forward, we will ensure compliance."
Why CMS rejects it: "Re-education" is not a corrective action โ it's a placeholder. CMS wants to know what specifically will change, who will change it, and when. "Staff will be re-educated" without naming the training content, the trainer, the date, and how competency will be verified is meaningless.
Fix it: "All nursing staff on the unit will complete a competency skills check on [specific procedure] conducted by the DON, to be completed by [DATE]. Competency records will be maintained in personnel files. New staff will complete the same competency during orientation beginning [DATE]."
Mistake 2: No Root Cause Analysis
What it looks like: The PoC describes what happened and what will be done but never explains why it happened.
Why CMS rejects it: Without a root cause, your systemic changes look reactive and disconnected. If you don't know why the failure occurred, CMS has no reason to believe your fix will hold.
Fix it: Before writing Element 3, do an actual root cause analysis. Was it a knowledge gap? A process gap? A supervision gap? A staffing issue? The answer shapes everything that follows. A PoC for a fall that identifies "the call light was out of resident reach" as the root cause will look completely different from one that identifies "call light checks were not part of the rounding protocol."
Mistake 3: Copy-Paste Boilerplate
What it looks like: The same paragraph appears across multiple citations with only the F-tag number changed. Generic language like "the facility will implement a comprehensive monitoring program" that could apply to any deficiency.
Why CMS rejects it: It signals that the facility is not taking the specific deficiency seriously. Surveyors recognize boilerplate. It also frequently fails to address the specific facts of the citation.
Fix it: Each citation gets a tailored response. Reference the specific residents cited, the specific unit or department, the specific date range of the deficiency, and the specific policy being revised. Make it clear you read the SOD.
Mistake 4: Unrealistic Completion Dates
What it looks like: Completion dates of "immediately" for complex systemic changes, or dates that are already past by the time CMS reviews the PoC.
Why it's a problem: "Immediately" cannot be verified. Past dates mean you're claiming the fix is done before CMS can confirm it. If a re-survey finds the same deficiency after you claimed immediate correction, you're in a much worse position.
Fix it: Use specific calendar dates, 2โ6 weeks out for most corrective actions. For monitoring plans, set a 90-day endpoint with interim checkpoints. Don't promise things you can't prove.
Mistake 5: Fixing the Person, Not the System
What it looks like: "The staff member responsible has been counseled / retrained / terminated." The entire corrective action focuses on a single employee.
Why CMS rejects it: CMS's model of deficiency correction is systems-based, not person-based. If the only fix is removing or disciplining one individual, the deficiency is likely to recur when that person is replaced. CMS wants to see structural changes that prevent the next person from making the same mistake.
Fix it: Address the individual situation briefly in Element 1, then pivot to the systemic fix in Element 3. Policy change, supervision structure change, monitoring mechanism change. Personnel actions can be mentioned but must not be the primary corrective action.
Skip the Blank Page. Get Department-Specific PoC Templates.
The framework in this article is solid โ but writing a PoC from scratch under a 10-day deadline is brutal. The Plan of Correction Templates pack includes pre-formatted templates for the most common F-tags, organized by department: nursing, dietary, activities, social services, and more. Fill in the specifics. Submit with confidence.
Real Examples: Good vs. Bad Corrective Actions
The fastest way to understand what CMS wants is to see the difference between language that gets accepted and language that gets rejected. These examples are drawn from patterns in public CMS survey records (anonymized and generalized).
Example 1: F689 โ Fall with Injury (Resident Harm)
| โ Rejected Language | โ Accepted Language |
|---|---|
| Staff will be reminded to follow fall prevention protocols. The resident has been moved to a safer room. We will monitor going forward. | Resident A's care plan was updated on [DATE] to include bed alarm, hourly rounding, and floor mat placement. A full-house fall risk audit was completed by the DON on [DATE] โ 12 residents were identified as high-risk and their care plans were reviewed and updated by [DATE]. Policy F689-01 was revised to require 2-hour rounding documentation for all residents rated high-risk on the Morse Fall Scale. The charge nurse will audit 5 randomly selected high-risk rooms per shift for 90 days, with results reported to the QAPI committee monthly. All corrective actions completed by [DATE]. |
Example 2: F880 โ Infection Control (Hand Hygiene)
| โ Rejected Language | โ Accepted Language |
|---|---|
| Staff have been educated on proper hand hygiene. In-service training was provided. Staff have signed acknowledgment forms. We will continue to monitor compliance. | The DON conducted a full-building hand hygiene competency observation for all nursing staff (RN, LPN, CNA) between [DATE] and [DATE]. 4 staff members were identified with technique deficiencies and received one-on-one remediation by the Infection Control Nurse. Policy IC-01 was updated to require documented hand hygiene observations as part of monthly supervisory rounds. The Infection Control Nurse will complete a minimum of 20 covert hand hygiene observations per week for 12 weeks, with results documented on Form IC-14 and reported to QAPI. Threshold for escalation: any department with compliance below 90% triggers an immediate department-level in-service. New hire orientation updated to include return demonstration of hand hygiene technique. All corrective actions completed by [DATE]. |
Example 3: F758 โ Psychotropic Medications Without Indication (Unnecessary Medications)
| โ Rejected Language | โ Accepted Language |
|---|---|
| The physician has been notified. Staff will ensure all medications have proper documentation. The Director of Nursing will conduct monthly medication reviews. | Resident B's attending physician was contacted on [DATE] and an emergency medication review was conducted. Psychiatric consult was obtained on [DATE]. Medication documentation was updated to reflect documented clinical indication and gradual dose reduction plan. A full-house psychotropic medication audit was conducted by the DON and Consultant Pharmacist between [DATE] and [DATE]. 6 additional residents were identified for physician review โ all reviews completed by [DATE], documentation updated accordingly. The monthly pharmacist medication regimen review process was revised to include a specific psychotropic appropriateness checklist (Form MED-07), effective [DATE]. The Medical Director will co-review all new psychotropic prescriptions prior to administration beginning [DATE]. Monthly psychotropic tracking reports will be reviewed by the QAPI committee with specific attention to GDR compliance. All corrective actions completed by [DATE]. |
Every good example does the same things: names specific people with titles, uses specific dates, references specific policies or forms, describes a measurable monitoring mechanism, and addresses system-level change beyond the immediate incident. That's the formula.
Step-by-Step: How to Write a PoC That Survives Re-Survey
Here's the process that produces PoCs with the highest acceptance rate. Don't skip the early steps โ they're where most bad PoCs go wrong before a word is written.
-
1Read the full SOD against the actual regulatory languagePull up the F-tag regulation on CMS.gov or your F-tag reference. The SOD tells you what happened. The regulation tells you what "fixed" means. You must respond to the regulatory requirement, not just the surveyor's narrative. Most facilities respond to the anecdote. CMS accepts responses to the regulation.
-
2Do a root cause analysis before writing anythingGather your charge nurses, DON, and department heads. Walk through what actually happened. Was it a knowledge gap? A supervision gap? A policy gap? An equipment issue? A communication failure? Write down your root cause statement. Every subsequent element flows from this.
-
3Identify all affected residents โ not just the cited onesUse the root cause to define your audit criteria. If the deficiency was X, who else could be affected by the same systemic failure? Conduct the audit, document the results, and address any additional residents found. This shows CMS you're thinking systemically โ which is exactly what they want to see.
-
4Draft the systemic changes with specific owners and datesFor each system change: name the policy being revised (with policy number if you have it), name the person responsible for the revision, set a completion date, describe the new process. If you're adding training, name the training content, trainer, audience, completion date, and how competency is verified. Make every action auditable.
-
5Design a monitoring plan CMS can trackYour monitoring plan must include: what is being audited, who is auditing, how often, for how long, where results are documented, and what triggers escalation. Connect it to your QAPI program. Monthly QAPI reporting is the gold standard. 90 days of heightened monitoring following a citation is the typical expected duration for non-IJ findings.
-
6Pick a completion date you can actually meetDon't pick "immediately" unless you genuinely completed all corrective actions before submitting. Pick a date 2โ4 weeks out for most actions. If you have a 90-day monitoring component, your completion date should reflect that. Make sure the date is achievable given your staffing reality.
-
7Review against the five elements before submittingPrint the five-element checklist. Read your draft. Does each element directly address the cited deficiency? Are all dates specific? Is the root cause addressed? Are names and titles included? Is monitoring quantified? One person who wasn't involved in writing it should read it for logic gaps before it goes out.
-
8Start your documentation trail immediatelyFrom the moment you submit the PoC, start building the evidence file: audit forms, sign-in sheets, policy revision dates, meeting minutes, QAPI committee notes. If CMS comes back for a re-survey, this documentation is what validates your PoC. Many facilities submit excellent plans and then fail re-survey because they can't prove they did what they said they would.
Department-Specific Templates: When the Generic Framework Isn't Enough
The framework above covers the universal structure. But the language, the specific policy references, the audit forms, and the monitoring mechanisms vary significantly by department and F-tag type. An F689 fall PoC looks nothing like an F758 psychotropic medication PoC, which looks nothing like an F880 infection control PoC.
The differences matter because CMS reviewers know their content areas. A generic fall prevention monitoring plan submitted for an F689 citation will be spotted immediately. A PoC that references specific Morse Fall Scale thresholds, rounding documentation protocols, and hourly rounding audit tools signals that the facility actually understands the regulatory requirement.
Below are the departments and F-tag categories where we see the most PoC submissions โ and where generic language fails most often:
Nursing / Clinical Quality (Most Common)
- F684 (Quality of Care) โ Requires specific care plan interventions, physician notification timelines, and outcome monitoring
- F689 (Accident/Fall Prevention) โ Requires fall risk assessment methodology, environmental audit components, and restraint alternatives documentation
- F725/F726 (Sufficient Staffing) โ Requires census-based staffing analysis, PBJ data validation, and HPPD calculation methodology (see our guide on nursing home staffing schedule templates)
- F757/F758 (Medication Management / Psychotropics) โ Requires pharmacy review protocol, prescriber consultation process, and GDR monitoring framework
- F880 (Infection Control) โ Requires ICAP-based protocol references, hand hygiene observation methodology, and exposure risk assessment
Dietary
- F804/F805 (Nutritional Adequacy / Therapeutic Diets) โ Requires dietitian review timelines, physician order cross-check process, weight monitoring protocols
- F812 (Food Safety / Sanitation) โ Requires temperature log validation, HACCP plan review, and corrective action for out-of-range findings
Activities / Psychosocial
- F679 (Activities Program) โ Requires activity assessment documentation, individual preference documentation, participation tracking methodology
Social Services
- F622/F623 (Discharge Planning) โ Requires interdisciplinary team involvement documentation, resident/family preference documentation, post-discharge follow-up protocol
The Plan of Correction Templates ($69) include department-specific, pre-formatted templates for the 20 most-cited F-tags โ organized by department. Each template includes pre-filled language for Elements 1โ5, example root cause statements, suggested audit tool references, and monitoring plan language calibrated to that specific regulatory requirement. Fill in the blanks, add your dates and names, and submit. For DONs and admins responding to a multi-tag SOD under a 10-day deadline, it's the fastest path to a clean plan.
After You Submit: The Documentation Sprint You Can't Skip
Submitting a great PoC is the easy part. The hard part is proving you actually did what you said you would when CMS comes back โ and they will come back.
Re-survey timing varies by severity. Immediate Jeopardy (IJ) and G-level and above citations typically trigger a re-survey within 15 business days. Lower-severity findings may not generate a re-survey at all, but CMS will verify at your next standard survey.
When the re-survey happens, surveyors will pull your PoC and look for evidence of everything in it. This is where facilities that submitted good PoCs still fail: the plan looked great on paper, but the documentation trail is thin.
What to Document Starting Day One
- Audit logs โ every audit form referenced in your monitoring plan, date-stamped, with signatures
- Policy revision history โ the revised policy, the approval date, the distribution list, staff acknowledgment signatures
- Training records โ sign-in sheets, competency verification forms, attestations
- QAPI meeting minutes โ showing that the monitoring data was actually presented and reviewed
- Care plan updates โ for all residents identified in Elements 1 and 2, updated with specific interventions
- Physician communications โ for citations involving medical care, document the notification date, the response, and the outcome
Create a binder or digital folder specifically for this citation. Label it by F-tag number. Keep it organized. When the surveyor asks to see your evidence of correction โ and they will โ you want to hand them a complete packet, not scramble for sign-in sheets.
The question CMS is really asking at re-survey isn't "did you write a good plan?" It's "did you actually change anything?" The documentation sprint is how you prove the answer is yes. A facility that submitted a mediocre PoC but has a thick evidence file often does better at re-survey than one that submitted a perfect plan and then treated it as a filing exercise.
Finally: learn from the process. 80% of plans of correction we've reviewed had the same avoidable mistakes. Most of them were facilities that had been through the process before. Running a mock survey before your next standard survey โ using what you learned from this citation โ is the single highest-leverage thing you can do to avoid finding yourself here again.
When you're ready to write your next PoC, our Plan of Correction templates bundle includes CMS-formatted PoC forms, root cause analysis worksheets, and corrective action tracking tools โ so your team spends time on strategy, not formatting.
Already have your deficiency? Take the Survey Readiness Quiz to see your full compliance picture →