i Care TracerBuilding an approved policy library
In most facilities the problem is not that policies are missing. It is that nobody knows which version is current. This page is about building a library where current and superseded can be told apart in seconds — document lifecycle, who approves what, and how staff acknowledgement is proven.
The symptoms of an unhealthy library
Before building anything, examine what you have. An unhealthy library announces itself:
- One policy in three places in three different versions, with no way to tell which is newest.
- Files named "Medication policy — final 2", "final revised", "final last".
- A document referring to a procedure that does not exist, or to a department that was restructured.
- Nobody knows who approved this policy, or when.
- A new employee does not know where to read their unit's policies, so they ask a colleague.
Eight fields that make a document governable
Every document in the library carries these fields, without exception. Missing any one means an obvious question about the document has no answer.
| Field | Why it is necessary |
|---|---|
| Reference number | A stable identifier that does not change across versions, used in cross-references |
| Title | Describes the subject, not the department — "High-alert medication handling", not "Pharmacy policy 3" |
| Version number | Distinguishes the current version from its predecessors unambiguously |
| Approval date | When it became effective |
| Next review date | The field that stops documents dying quietly |
| Author, reviewer, approver | Three names, not one |
| Scope | Who it applies to — vagueness here means it applies to nobody |
| Linked documents | The procedures and forms that depend on it, so they are updated with it |
The document lifecycle — six stages
A library is a system, not a folder. A system means every document has a known position in a cycle, and every move between positions has a condition.
1 · Draft
Written by someone who does the work, not by someone who manages quality. A policy written by a person who has never stood in the unit describes imagined work.
2 · Review
Read by those it affects and those with the expertise. Review is not a formality — one serious comment is worth more than ten signatures.
3 · Approval
The authorised person approves. Only here does it become effective. Before this moment it is neither distributed nor referenced.
4 · Publication
Made available in the one official place and announced to the distribution list. Publication is a separate act from approval; an approved but unpublished policy does not exist in practice.
5 · Periodic review
Before the review date, not after. A review may conclude "unchanged" — a legitimate decision, recorded with its date.
6 · Archiving
A superseded document is archived, never deleted. It is marked superseded, removed from users' reach, and kept in the record, because an old incident may have to be judged against it.
Who approves what — three roles one person does not hold
Approval level follows document type rather than size: a facility-wide policy is approved by leadership, a procedure inside a unit by the unit head. Routing everything to leadership creates a queue that paralyses the library; pushing everything down to units creates contradictions between them.
| Role | Who performs it | What it guarantees |
|---|---|---|
| Author | Someone who performs the described work | That the policy describes what actually happens, not what is assumed |
| Reviewer | A specialist or an affected unit head | Technical correctness and consistency with other documents |
| Approver | The authorised person for that document type | Institutional commitment — and who answers for it |
Numbering and versioning — simple rules that prevent large messes
- The reference number is fixed for the life of the document. Only the version changes.
- Any content change raises the version and requires fresh approval. A typo does not — but changing a step in a procedure does, however small it looks.
- Every version has a one-line change record: what changed and why. That line is what makes the next review possible.
- A reference number from a withdrawn document is never reused.
- A filename is not a version-control system. Control lives in the document's metadata, not in its name.
How staff acknowledgement is proven — and it is asked about
Publishing the policy is not enough. What is required is evidence that those who must know it do, and that question arises in almost every survey.
- A distribution list per policy: who must have read it, by role rather than by name — "all ICU nurses", not a name list that goes stale.
- Dated proof of acknowledgement: a signature or an electronic record. The date matters as much as the signature.
- For critical policies acknowledgement alone is insufficient — pair it with a competency assessment. Reading the pre-surgical verification procedure is one thing; being able to perform it is another.
- A new version means acknowledgement is repeated. Proof against version two does not cover version three.
- New employees: acknowledging their unit's policies is part of onboarding, not a task left to them.
Three mistakes that build a dead library
Copying from another hospital
A borrowed policy describes work that does not happen here — with department names you do not have and roles that do not exist. A surveyor uncovers it with one question to a staff member. Borrow the structure if you like; write the content from your own reality.
A policy for everything
A library of four hundred documents is neither reviewed nor read. Write a policy when there is a recurring decision that needs standardising or a risk that needs controlling. Everything else is a work instruction, not a policy.
An annual mass review
Gathering every document for review in one month produces a formal review: dates get stamped and nothing gets read. Distribute review dates across the year, and review becomes a small weekly task rather than an annual campaign.
From nothing to a working library
Rationalisation is the psychologically hardest stage, because it means admitting half of what was built is not usable. But without it you build governance on top of chaos, and what you get is documented chaos.
| Stage | The work | Output |
|---|---|---|
| Inventory | Collect everything that exists from everywhere, deleting and judging nothing | One list of every document and where it lives |
| Rationalisation | Remove duplicates, identify the newest version per subject | One document per subject |
| Governance | Add the eight fields to every surviving document | A library that can be queried |
| Gaps | Which critical subjects have no policy? | A writing list ordered by risk |
| Operation | Distribute review dates, activate distribution lists | A library run by alerts rather than campaigns |
Frequently asked
What is the difference between a policy, a procedure and a work instruction?
A policy states what we commit to and why. A procedure states how it is carried out and by whom. A work instruction describes a single operational step in detail. Confusing them produces twenty-page policies nobody reads.
How many policies does a facility need?
There is no correct number. The working test is one document for every recurring decision that needs standardising and every risk that needs controlling. If you cannot review what you hold within its cycles, you hold more than you can carry.
Can policies be approved electronically?
Yes, provided approval is attributable to a named person with a date and time, and the record cannot be altered retroactively. An electronic signature whose author is unknown is not an approval.
What do we do with old policies when they are superseded?
Archive rather than delete: mark them superseded, remove them from users' reach, and keep them in the record. An incident from two years ago is judged against the policy effective that day, not today's.
Do we need a document management system?
Nobody requires one. The practical difference is alerting: a library of two hundred documents each with a review date needs something to warn before the date falls due. Without automatic alerts, the lapsed document is discovered at the survey rather than before it.
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.
The library is the first thing asked about
The readiness check covers document control alongside the other domains, and gives you your position in five minutes. No account.
Start the readiness check