The approval of a policy can feel like the end of a difficult piece of work. In reality, it is the point at which the harder work becomes visible.
In human services, policy commitments concern important parts of a person’s life: safety, privacy, consent, dignity, culture, complaints, medication, records and the right to be heard. Approval establishes the rule. It does not establish the practice.
An organization may have a sound policy and inconsistent practice. Staff may know that a rule exists but interpret it differently. A supervisor may create a practical workaround that never reaches the written procedure. Training may occur without any check that participants understood it. Years later, the policy remains in the manual while the real system lives in custom, memory and hurried decisions.
The distance between those two things is the evidence gap: what an organization says it does compared with what it can show happens in practice.
I encountered this repeatedly while leading policy implementation and accreditation work. Drafting could resolve an ambiguity on paper, but it did not tell us whether the new expectation had reached supervision, training, forms or daily decisions. The most useful question was often very ordinary: what would I expect to see next week if this policy were truly in effect?
The gap matters for legal reasons. It also matters because people rely on these systems. A privacy policy offers little protection if staff are unclear about when information can be shared. A complaints policy offers little accountability if nobody explains it in an accessible way. A consent policy may look complete while the actual conversation is rushed, undocumented or treated as a signature exercise.
Canadian law does not generally demand perfection from every organization. It does, however, expect reasonable systems, lawful decisions and credible records. The precise duty depends on the setting, legislation, contract and professional responsibilities involved. Across those differences, one principle is remarkably consistent: an organization should be able to explain what it required, what it did and how it responded when something went wrong.
The Canadian Accreditation Council’s standards illustrate the connection. Its accreditation framework examines governance, practice and outcomes. The point is not simply whether policies exist, but whether an organization has effective systems and can demonstrate practice. Accreditation is voluntary in many settings, but the underlying lesson applies widely.
Closing the evidence gap begins with clarity, but clarity alone is not enough.
Every important policy should identify who does what. Phrases such as “the organization will ensure” sound authoritative but can conceal uncertainty. Which role receives the concern? Who decides? Who documents? Who reviews? Who follows up? A person should be able to read the policy and find the path from principle to action.
The next step is translation. Staff need more than the policy text. They need examples that resemble their work. What does confidentiality require when a worried family member calls? What should happen when a young person disagrees with a plan? When does an incident require immediate escalation? Scenarios expose ambiguity before a real event does.
Training should then produce useful evidence. Attendance records are helpful, but they answer only one question: who was present? Depending on the risk, an organization may also need knowledge checks, observed practice, supervision notes, file reviews or follow-up discussions. The objective is not to collect paper for its own sake. It is to know whether the practice was understood and used.
Supervision is where many policies become real. A good supervisor connects written requirements to current decisions, reviews records, corrects misunderstandings and notices patterns. If the same exception appears repeatedly, the problem may not be individual performance. The policy may be unclear, the process may be unrealistic or staff may lack a resource the organization assumed was available.
Organizations also need a way to learn from departures. When practice does not meet policy, the response should be proportionate and fair. Sometimes a person made a poor decision. Sometimes the system made the preferred decision unusually difficult. Corrective action should address both possibilities. Updating a document without changing the conditions that produced the problem is unlikely to prevent its return.
Documentation deserves special care. There is a temptation to answer every risk with another form. That can create an appearance of control while taking time away from the relationship at the centre of the service. Good records are purposeful. They show key decisions, consent, actions, review and follow-up. They are written so that another responsible person can understand what occurred. They do not require staff to record the same fact in four places.
For boards and senior leaders, the evidence gap is a governance issue. They should not receive only assurances that policies are current. They need meaningful information about how high-risk policies are implemented, what reviews have found, whether complaints and incidents reveal patterns and whether corrective actions have held over time.
The same applies to funders and regulators. Reporting requirements should test the outcomes and safeguards that matter. A large volume of data can coexist with poor visibility. More numbers do not automatically produce more accountability.
Actions need a reliable record. That record protects the people receiving service, supports fair review, helps staff learn and allows leaders to govern honestly.
Policy implementation is complete enough to trust only when the organization can trace the commitment into ordinary work: who was equipped, what changed, what evidence was reviewed and what happened when practice fell short. The purpose of that trace is not to produce a perfect file. It is to make the organization’s promises dependable.

