i Care TracerPreparing for an accreditation survey in ninety days
Ninety days is enough for a facility with an existing foundation that needs its gaps closed. What follows is an execution plan week by week: who does what, what each week must hand over, and how priorities are reordered when time runs short.
Before you start: three decisions in one sitting
The preparation programmes that stall are the ones that start working before three decisions are made. Get leadership in a room for an hour and leave with these written down.
Who leads?
One named person, not a committee. Committees review; individuals lead. And they need at least partial release from their normal duties — a leader who leads in the gaps between other work leads on paper only.
What is in scope?
Which departments and services fall inside the survey. Name them. An unwritten scope expands quietly, and in week ten you discover a unit nobody assessed.
What does "ready" mean?
Define it numerically before you begin: no open essential safety item · every policy inside its review cycle · a practice record for every critical policy. Without a definition you will not know when to stop, and you will not know you are behind.
Weeks 1–2 · The self-assessment, done honestly
A self-assessment is not an exercise in filling a form. It is the single exercise that determines what you do for the remaining twelve weeks, and all of its value is in its honesty.
One mistake ruins it: letting each department assess itself. A department knows its weak points and does not enjoy writing them down, and the result is an all-green assessment that gives you nothing to work on.
- Have the questions asked by someone from outside the unit. A ward nurse asking in clinics, a pharmacist asking in the emergency department. The outsider asks why; the insider already knows and does not ask.
- Ask for the record, not the policy. "Show me the last five times you did this" reveals many times what "do you have a policy?" reveals.
- Write each gap in a closable form. "Documentation is weak" is not a gap. "The blood bank fridge monitoring log is missing four days in July" is.
- Fix nothing during these two weeks. Fixing while assessing stops the assessing. Record it and move on.
Weeks 3–4 · Ordering the gaps — the decision that decides the plan
The assessment will produce a longer list than you expect. Ordering it is not administrative housekeeping; it is the decision that determines whether you arrive. Order on two axes only: safety impact and effort to close.
| Category | Safety impact · effort | When it closes |
|---|---|---|
| Critical | High · any effort | Immediately, before anything else. These do not enter the ordering at all. |
| Quick wins | Medium · low | Weeks 5–8 · they close by the dozen and carry the team's morale |
| Projects | High · high | Start week 5, run as a project with a plan — not as a line on a list |
| Deferred | Low · high | Recorded in a post-survey plan — and never deleted |
Weeks 5–8 · The document layer — the easiest and the most dangerous
This is the easiest phase, because it is entirely in your hands and requires nobody to change their behaviour. It is the most dangerous phase for the same reason: it feels like rapid progress while nothing in the field has changed.
Get it done, but watch the clock. A facility that spends six weeks polishing documents and leaves two for records will be surprised at the survey.
- Every policy outside its review cycle: reviewed, approved and reissued with a new version — not merely redated.
- Every policy named in the assessment that does not exist: written, or the reference to it removed. A cross-reference to a non-existent document is a finding in its own right.
- Document alignment: a policy saying one thing while its procedure says another reads as internal contradiction.
- A distribution list: who must have read each policy, and how that is evidenced.
Weeks 9–10 · The record layer — what makes a record acceptable
The record is what proves the policy is practised. Not everything called a record is accepted. An acceptable record has four properties:
- Continuous: no unexplained gaps. A log that stops for two weeks raises a worse question than no log at all.
- Attributable: who recorded, and when. A signature or an account — not anonymous handwriting.
- Consistent across units: complete in one and patchy in another means there is no system, only conscientious individuals.
- Retrievable: you can reach the last ten entries in a minute. A correct record that cannot be produced during the survey is, in effect, absent.
Weeks 11–12 · The competence layer
The difference between a training file and a competency file is the difference between attended and able. The survey asks about the second.
Do not attempt to assess everyone on everything. Identify the high-risk roles and the critical tasks within them, and assess those. One documented competency assessment of a nurse on a critical task weighs more than twenty attendance certificates.
- Choose a method that fits the task: direct observation, return demonstration or simulation — not a written test for a manual skill.
- The assessor must be qualified to assess, and nobody assesses themselves.
- Every assessment not passed needs a plan and a dated reassessment. A failed assessment with no plan is worse than no assessment.
Week 13 · The mock trace — the most valuable week in the plan
This week exposes in hours what three months of file review does not: the gap between what is written and what is practised.
- Pick three traces: an inpatient, a high-alert medication, and a new employee. Follow each from entry point to end.
- Do not tell the units when. An announced trace measures one day's readiness.
- Ask the staff member who is actually there, not the unit head. The unit head knows the policy; the question is whether the person performing it does.
- Log every question not answered clearly — and do not fix it on the spot. Finish the trace, then collect the results.
- Close what surfaced within the same week. What is not closed that week will not be closed before the survey.
What each phase must hand over
| Period | Deliverable | Owner |
|---|---|---|
| Weeks 1–2 | A numbered gap list, each with a department and an owner | Programme lead |
| Weeks 3–4 | The list sorted into four categories, with a schedule | Programme lead + leadership |
| Weeks 5–8 | A policy library entirely inside its cycles, plus a distribution list | Quality department |
| Weeks 9–10 | A continuous practice record for every critical policy | Unit heads |
| Weeks 11–12 | Documented competence for high-risk roles | HR + unit heads |
| Week 13 | The mock-trace report, with every gap in it closed | Programme lead |
If you fall behind — and most facilities do
When time gets short, facilities start accelerating everything in parallel. That is the worst available decision. Under pressure the rule is ordering, not acceleration:
- Essential safety items first, without exception. They are not traded against time.
- Then the record layer for critical policies — not for every policy.
- Then the mock trace, even if it is one day instead of a week.
- And last, polishing non-critical documents. That is what gets deferred; nothing above it does.
Frequently asked
Is ninety days really enough?
It is enough for a facility with a foundation — a policy library, incident reporting, indicators with a series of measurements — that needs gaps closed. A facility starting from nothing usually needs nine to twelve months, because outcome standards require a series of measurements that cannot be compressed.
Who should lead the programme?
One named person, mandated by leadership, with at least partial release from their normal duties. Committees review and decide, but they do not lead daily work for three months.
How many people does the self-assessment need?
Fewer than you expect. Four to six people from different units, each asking questions in a unit that is not their own, produce a more honest assessment than a large team in which every unit assesses itself.
Do we pause normal operations during preparation?
No — and the impulse itself signals the programme was built wrongly. Preparation that halts operations collapses after the survey and things revert. The three layers have to be built as the way the work is done, not as a campaign.
What if a major gap appears in the final week?
Log it in a written plan with an owner and a date, and actually start on it. A known, scheduled gap reads as a facility that monitors itself; a gap the surveyor finds before you do reads as one that does not.
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.
Ten recurring accreditation findings — and their real cause
Every recurring finding has a systemic cause, not an individual one. Ten findings by domain, each with its root cause, its fix, and how closure is proven.
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.
Start from an honest assessment
Twenty-four questions in five minutes give you your facility's readiness by domain and where the work starts. No account, no commitment.
Start the readiness check