i Care TracerTen recurring accreditation findings — and their real cause
A finding that recurs at every survey is not one person's error; it is a symptom of a system. What follows is ten findings organised by domain, each with its systemic root cause, its fix, and how closure is proven — the step that usually gets forgotten.
Why the same finding returns at the next survey
When the same finding comes back three years later, the reason is almost always that the previous fix addressed the instance and not the system: the missing document was corrected, and nothing was created to stop it going missing again.
Which is why the right question in front of any finding is not how do we fix this, but what allowed it to happen, and what will prevent its return without depending on somebody paying attention?
Every item below is written on that basis: the finding, its systemic cause, a fix that works without attention, and the evidence of closure.
One · Documents
1 — A document current in form and lapsed in fact
Systemic cause: the review date is a field in the document that nobody reads. Fix: an alert with adequate lead time going to the document's owner rather than a general list, and review dates distributed across the year. Evidence of closure: a list of every document and its review date, with none of them in the past.
2 — Two policies on one subject saying different things
Systemic cause: more than one place where documents are stored, so one copy is updated and the other survives. Fix: one official source; everything else removed or marked "uncontrolled copy". Evidence of closure: a search by subject name returns exactly one effective document.
Two · Workforce
3 — A professional licence or qualification expiring during the survey
Systemic cause: expiry dates are reviewed annually or at renewal, and expiry falls between the two reviews. Fix: staged alerts — ninety, sixty and thirty days — to the employee and their manager together. Evidence of closure: a report of every licence and its date, with none expired and none expiring within thirty days without a logged action.
4 — Training evidenced by attendance rather than competence
Systemic cause: the system records attendance because it is easier to measure, while competence needs an assessor and an appointment. Fix: identify the critical tasks within high-risk roles and bind each to an appropriate method — observation or return demonstration, not a written test for a manual skill. Evidence of closure: every high-risk role has a current competency assessment by a qualified assessor.
5 — Clinical privileges that are generic or out of date
Systemic cause: privileges are granted at appointment and renewed as a formality, unconnected to performance evidence. Fix: a defined privilege list per specialty, and periodic renewal grounded in actual data rather than in elapsed time. Evidence of closure: a randomly chosen physician file with specific, dated, approved privileges — and the source of the data the renewal rested on.
Three · Medication
6 — High-alert medications handled like any other
Systemic cause: the list exists in a policy and leaves no trace in the workflow itself. Fix: make the distinction visible where people work — separate storage, visual differentiation, and a double check built into the step rather than mentioned in a document. Evidence of closure: field observation in two different units showing the same behaviour.
7 — An administration record continuous in one unit and patchy in another
Systemic cause: the system rests on individual conscientiousness rather than on a process. A unit with a disciplined person looks excellent; a unit that loses that person stops recording. Fix: assign responsibility by role rather than by name, and a short weekly review that surfaces a break within days. Evidence of closure: the same record in three different units for one period, with no unexplained gaps.
Four · Infection prevention
8 — Hand hygiene measured only before the survey
Systemic cause: measurement is a campaign rather than a process, so the number rises seasonally and then disappears. The surveyor reads the discontinuity, not the number. Fix: small continuous periodic measurement by a trained observer beats large intermittent measurement. Evidence of closure: a continuous series across at least four periods, with documented feedback to units after each round.
Five · Facility and medical equipment
9 — Equipment in use with no calibration or maintenance record
Systemic cause: there is no single asset register; equipment arrives through different routes — purchase, donation, loan — and not all of it enters the register. Fix: one entry point for every device whatever its source, and preventive maintenance driven by the register rather than by memory. Evidence of closure: pick three devices at random from the field — not from the register — and find each in the register with current maintenance.
Six · Governance
10 — Committees that meet and do not decide
Systemic cause: minutes document the discussion rather than the decision, so there is nothing to follow up. Fix: a fixed section in the minutes template — decision, owner, date — and the first item of the next meeting is follow-up on the last one's decisions. Evidence of closure: three consecutive sets of minutes showing a decision from the first followed up in the second and closed in the third.
The finding that does not appear on the list — and is the most serious
There is a situation rarely written up as a finding, yet it changes how a surveyor reads everything else they saw: a facility whose indicators are all green, that has reported no incident and received no complaint.
Because that does not happen. Facilities that report a great deal are the ones that are working; a zero means reporting has stopped, not that error has. An experienced surveyor starts examining everything else with a harder eye from that point.
The fix here is cultural rather than procedural, and it is the slowest on the list: staff must see that reporting is not punished, and see something result from their reports. The only convincing evidence of closure is a rising near-miss reporting rate while serious incidents stay low — which is the shape of a healthy system.
One rule that closes half of these findings
Look at the ten together and you will find that seven share the same systemic cause: **nothing warns before it is too late**. A review date passes, a licence expires, maintenance is missed, a record breaks — all of them knowable in advance, and nobody is warned.
A facility that depends on one person's attention works well for as long as that person is present and has the time. That is not a durable condition.
So any fix that does not end in an automatic alert or a short scheduled periodic review is not a fix. It is the same finding, postponed to the next survey.
Frequently asked
What is the difference between fixing a finding and closing it?
Fixing addresses the instance the surveyor saw. Closing addresses the cause that allowed it and proves with evidence that the new state holds. A finding fixed but not closed returns at the next survey.
When do we need root cause analysis instead of a direct corrective action?
When the event is serious, or when the same finding recurs despite a previous fix. Recurrence after a fix is evidence that the fix addressed a symptom — which is precisely the case for root cause analysis.
How long before we verify that closure held?
The interval is set at closure, not afterwards, and is chosen from the cadence of the work itself: a daily process is verified after a month, a monthly one after at least three. The rule is that enough cycles must pass for the measurement to mean anything.
Do we show a surveyor a gap we know about and have not closed?
Yes, if it is logged in a plan with an owner, a date and work actually under way. A known, scheduled gap reads as a facility that monitors itself. Concealing it turns — if it surfaces — into a credibility problem larger than the gap itself.
Which of these findings closes fastest?
Lapsed documents and lapsed licences, because fixing them is purely administrative and requires nobody to change their behaviour. The slowest are reporting culture and competency assessment, because both need time and behaviour change — which is why the slow ones are started early rather than late.
Related guides
What does CBAHI require from hospitals?
What actually has to be in place before an accreditation survey — and the six mistakes that most often cost facilities points, written from the field rather than from the manual.
Preparing for an accreditation survey in ninety days
A week-by-week plan: who does what, what each week must produce, and how to reorder priorities when time runs short.
Building an approved policy library
The problem is rarely missing policies; it is that nobody knows which version is current. Document lifecycle, who approves what, and how staff acknowledgement is proven.
Which of these ten do you have right now?
The readiness check passes through all of these domains and gives you your position in each. Five minutes, no account.
Start the readiness check