Most mock surveys fail in a specific and predictable way: the organization knows the mock survey is coming, spends two weeks tidying charts, performs well, and learns almost nothing. The exercise measured how the agency behaves when it is being watched, which is not the thing a real survey will measure. A mock survey is only useful if it tests the system as it actually runs. That requires a different design, and a tolerance for finding things.
Start with the current standard
Before anyone opens a chart, confirm which Conditions of Participation, CMS guidance, accreditor requirements and internal policies actually apply right now. Requirements change, and survey readiness work built on last year checklist produces confident, well-documented false assurance. This step also surfaces a common gap: internal policy that has drifted from the current standard. If the policy itself is out of date, chart review against that policy will confirm compliance with the wrong thing.
Sample the way a surveyor might
Use a mix of patient types, disciplines, locations and stages of care. Include admissions, recertifications, discharges, transfers and the complex cases that do not fit the usual pattern. The purpose is to test the normal process, not to review the cleanest records available. If the sample is selected by the same people who would be accountable for the findings, the sample will be unconsciously generous. Have someone else pull it, or pull it at random. Include at least a few records from periods when the organization was under pressure: a staffing gap, a census spike, a holiday week. Systems fail at their margins, and surveyors tend to find the margins.
Trace findings back to the system
When a chart has a problem, the useful question is not who made the error. It is how the error was possible. Was ownership of that step unclear? Did the EMR workflow allow the record to advance without the required element? Was training incomplete, or complete but a year ago? Did a policy conflict with another policy? A finding is worth far more when it reveals the system behind the error, because that is the version you can actually fix. Correcting twelve individual charts leaves the thirteenth to happen next month.
Turn findings into QAPI and re-test
Every finding should produce a corrective action with a named owner, a due date and a defined method of proving the fix worked. Without the last element, the loop stays open. A mock survey that ends with a PDF and no re-audit is half finished. The re-audit is where you learn whether the change survived contact with a normal week.
- Confirm the current standard before reviewing anything
- Have someone independent pull the sample
- Include complex cases and high-pressure periods
- For each finding, identify the system failure, not just the chart
- Assign owner, due date and proof of completion
- Schedule the re-audit at the same time you assign the fix
Make it survivable for the staff
One practical caution: a mock survey that feels punitive will quietly teach the organization to hide problems, which is the opposite of what you need. The teams closest to the work usually know where the weaknesses are, and they will tell you if telling you is safe. Frame the exercise as testing the system rather than the people, and be visible about acting on what is found. An organization where raising a problem reliably produces a fix will surface issues months before a surveyor would. Pfundamental Consulting supports hospice mock surveys, chart review, QAPI and operational process review, with an emphasis on findings that change how the work runs rather than reports that describe it. Compliance note: Survey requirements and interpretive guidance change. Confirm current CMS and accreditor standards before designing a readiness review.