Plan of Correction: How to Respond to Survey Deficiencies (With Examples)
A plan of correction home health agencies submit after a survey is often rushed out in the final hours before the deadline, written to sound good rather than to hold up. We have sat on both sides of that document — writing them as operators, and adjudicating them as surveyors and hearing officers. We can tell within the first paragraph whether a PoC was built to satisfy a reviewer or just to make the problem go away on paper.
A weak PoC doesn't just risk rejection. It invites a revisit, a directed plan of correction, or — in condition-level situations — a real conversation about certification. Here is what we look for, from the reviewer's chair, and how to build a PoC that clears the first time.
What are the 5 required elements of a plan of correction?
Every acceptable PoC, regardless of tag or discipline, answers five questions in writing:
- What specific corrective action will be taken for the affected patient(s)/situation? Not a philosophy — an action, with a name and a date.
- How will the agency identify other patients who could be affected by the same deficient practice? This is the step agencies skip most often, and it's the first thing reviewers check.
- What systemic changes (policy, process, training) will prevent recurrence? Not "re-education" alone — what actually changed in the workflow.
- Who is responsible, and what is the completion date? A named title (not "staff"), a real date.
- How will the agency monitor effectiveness going forward, and for how long? This is the element that gets PoCs rejected more than any other.
Key takeaway: a PoC that skips the "how will you know it worked" element will almost always bounce back for revision, costing you a cycle you don't have time for.
Monitoring language surveyors actually look for
Vague monitoring commitments are the single most common reason we send a PoC back when reviewing on behalf of a state agency. "Supervisor will monitor compliance" tells a reviewer nothing. What we want to see:
- Sample size — "10% of active charts monthly" or "100% of charts for 30 days, then 20% for 90 days."
- Tool — a named audit tool, not a vague reference ("Medication Reconciliation Audit Tool, attached").
- Threshold — what compliance percentage triggers escalation (commonly 90–100% depending on the tag).
- Reporting loop — who reviews results, how often, and where it's documented (QAPI minutes, governing body report).
- Duration — a defined monitoring period with a stated end point or transition to routine QAPI tracking.
If your PoC monitoring section reads like a single sentence, it is not ready to submit.
PoC example snippets for common tags
These are illustrative patterns, not templates to copy verbatim — tailor every PoC to your actual chart review and your actual staff.
Missed visit / scheduling deficiency:
"Effective [date], the Clinical Manager will review the visit schedule for all active patients within 48 hours of the missed visit to identify any patient whose plan of care visit frequency was not met. Scheduling coordinators will complete a revised scheduling workflow training by [date]. The Clinical Manager will audit 100% of scheduled visits against completed visits weekly for 60 days, then monthly for 90 days, reporting results to the monthly QAPI committee."
Plan of care not updated to reflect patient status change:
"The QA Nurse will review the clinical record of the identified patient and update the plan of care within 5 business days. All active charts will be reviewed within 30 days to identify any plan of care requiring update based on recent status change documentation. Clinical staff will complete training on physician notification and plan of care revision timelines by [date]. Ongoing audits of 20% of active charts will occur monthly for 6 months."
Infection control / hand hygiene observation finding:
"Competency re-validation for all field staff will be completed by [date] using [named skills checklist]. Unannounced direct observation audits of infection control practice will be conducted on no less than 2 staff per discipline monthly for 90 days by the Clinical Supervisor, with results reported to QAPI."
Notice the pattern: specific role, specific number, specific timeframe, specific reporting destination.
When does a condition-level deficiency threaten certification?
A condition-level finding (as opposed to a standard-level tag) means the surveyor determined the agency's overall capacity to meet a CoP under 42 CFR Part 484 is in question — not just one instance of non-compliance. This is a different conversation.
Condition-level findings can trigger:
- A shortened PoC timeline (often as little as 10 days rather than the usual timeframe).
- A directed plan of correction, where the state or CMS, not the agency, dictates specific corrective steps — a signal that your own PoC-writing credibility has already taken a hit.
- Follow-up or revisit survey before acceptance.
- In Immediate Jeopardy (IJ) situations, a required IJ removal plan submitted on an accelerated timeline, often with evidence of implementation before the surveyor even leaves, followed by an unannounced revisit to validate.
Key takeaway: at the condition level, "we fixed it" is not enough — you must prove, with documentation in hand before the revisit, that the fix is already operating.
IJ removal plans get special scrutiny because they have to demonstrate the jeopardy is abated now, not pending future action. We have seen agencies lose certification not because the clinical problem was unfixable, but because the removal plan read like a standard PoC instead of an urgent, evidence-backed abatement document.
How do consultants pressure-test a plan of correction before submission?
Before a PoC goes out the door, our team runs it through the same lens a reviewer will:
- Read every corrective action and ask, "would this survive a revisit tomorrow?"
- Confirm the "identification of other affected patients" step is not missing or soft.
- Check that every date is achievable given current staffing — reviewers notice optimistic timelines that agencies can't actually hit.
- Verify audit tools referenced in the PoC actually exist and are attached or available.
- Cross-check the PoC against the Statement of Deficiencies line by line, tag by tag — partial responses are a common rejection trigger.
This is the same discipline our founder outlines in Survivor! Ten Practical Steps to Survey Survival — the PoC is step nine, and it only works if steps one through eight (documentation readiness, mock surveys, staff competency) were already in place before the surveyor arrived.
What should your agency do this week?
- Pull your last two accepted PoCs and check them against the five-element framework above — most agencies find at least one gap.
- Confirm your QAPI committee has a standing process to receive and act on PoC monitoring data, not just file it.
- If you're carrying a condition-level tag history, get a second set of eyes on your systemic correction language before your next survey, not after.
A PoC is a legal and clinical document, not a formality — and reviewers read it that way. If your team wants a second set of eyes on a live plan of correction, a mock survey, or ongoing QAPI support, talk to the Solutions for Care team.




