The basics

Written directives vs proofs of compliance

The difference between a written directive and a proof of compliance, why accreditation needs both, and how to tell which one each standard is asking for.

On this page

If you are new to accreditation, two terms will come up in almost every conversation: the written directive and the proof of compliance. They sound like jargon, but the idea behind them is simple, and once it clicks, standards become much easier to read.

A written directive says what your agency will do. A proof of compliance shows that it did it.

Most of accreditation is putting those two things side by side for every requirement in your manual. This guide explains each one, why you nearly always need both, and how to read a standard to see what it is asking for.

What a written directive is

A written directive is any written instruction your agency issues that staff are expected to follow. Depending on your agency, that might be a general order, a policy, a procedure, a rule, a standard operating procedure or a formal memo. Your manual may define the term more precisely, so check its glossary.

A good written directive for accreditation purposes has a few things in common:

  • It is official. It has been approved by whoever has the authority to approve it, and it says so.
  • It is current. It is the version in force today, not a draft and not last year’s version.
  • It is specific. It says who does what, and when. “Supervisors will review reports” is weaker than “The on-duty supervisor reviews each report within one shift.”
  • It is known. The people it applies to have received it and can find it. Many agencies record that each person has read it.

A written directive is your agency’s rule. It’s the answer to an assessor’s first question: do you have a rule that meets this requirement?

What a proof of compliance is

A proof of compliance is the record that shows the rule is actually followed. It’s the completed form, the signed review, the training roster, the inspection log, the photo, the yearly report.

Proofs answer the assessor’s second question: do you actually do what your rule says?

Our guide on what makes a strong proof of compliance goes into detail. The short version: a proof shows the practice rather than the policy, covers the period your program asks for, and covers every part of the requirement.

Why you nearly always need both

A directive without proof is a paper policy. It tells an assessor what should happen but not whether it does. Plenty of agencies have well-written policies that nobody follows, and accreditation exists partly to tell the difference.

Proof without a directive is a practice without a rule. You may well be doing the right thing, but if it isn’t written down, it depends on the people doing it. When they leave, the practice can leave with them.

Put together, the two show an assessor that your agency has decided how something should be done and then does it that way. That combination is what accreditation is checking.

How to read a standard for what it wants

Not every standard asks for the same thing. Some only need a directive. Some need a directive and proof. A few are mostly about proof, such as a yearly report or review that has to exist.

Read the wording closely. A standard that talks about the agency having a written policy or procedure is asking for a directive. A standard that talks about something being done, conducted, reviewed or reported is usually asking for proof that it happened. Many standards ask for both in the same breath.

Your manual and your accrediting body are the authority here. Many manuals include commentary or guidance that explains what evidence is expected. When it’s genuinely unclear, ask. A short question to your accrediting body or assessor early on is much better than a finding later.

Match the directive to every subpoint

Standards are often broken into subpoints, labeled a, b, c and so on. A standard is only met when every subpoint is met.

This is where many files fall short. A use of force policy might cover reporting in detail and say nothing about supervisory review. If the standard has a subpoint for each, the policy meets one and leaves a gap in the other, even though it’s “the use of force policy.”

For each subpoint, find the sentence in your directive that meets it. If you can’t point to a sentence, you have a gap. Fill it by updating the directive in your agency’s own words, in a way that reflects what you actually do. Copying the standard’s wording into a policy without changing practice doesn’t solve anything.

A worked example

Here is a made-up standard, not taken from any real manual, to show how the pieces fit:

Sample standard: The agency has a written directive requiring (a) a written report for every vehicle pursuit, (b) supervisory review of each report, and (c) a yearly review of all pursuit reports.

Subpoint The directive shows Proof shows
a. Written report for every pursuit Section 4.1: “The officer completes a pursuit report before the end of shift.” Completed pursuit reports from across the period
b. Supervisory review Section 4.3: “The shift supervisor reviews and signs each report.” The same reports, showing the supervisor’s signature and date
c. Yearly review Section 4.6: “Each January the Operations Commander reviews all pursuit reports from the prior year.” The signed yearly review memo for each year in the period

Every subpoint has a line in the directive and a record that shows it happened. That’s what a complete file looks like.

When a directive changes

Policies change, and accreditation files have to keep up. When you revise a directive:

  • Keep the old version. Proofs created under the old policy were measured against it, and an assessor may need to see both.
  • Note the date the new version took effect, so it’s clear which proofs fall under which version.
  • Make sure the people it applies to have received and acknowledged the new version.
  • Check which standards the policy supports and update those files, so the highlighted lines still match.

How Badge 6 handles the two

Badge 6 keeps directives and proofs separate on purpose, because they do different jobs.

Each standard has a Written Directives tab and a Proof of Compliance tab. Add Written Directive attaches a published policy from your Document Library. Add Proof attaches a record from your Proof Library. In both, you highlight the lines that matter, by hand or with AI, and tag each highlight to the subpoints it covers, so you can see at a glance where a subpoint has a directive but no proof, or the other way round.

When you upload a new policy, Quick Check lists the standards it touches, so you know which files to update. Policy versions are kept, and your Policy Admin can require officers to acknowledge a new version, which records the acknowledgment for you.

The vocabulary is the easy part. The real work is making sure every requirement has a rule and every rule has a record. Get that habit right and the rest of accreditation follows.

This Is Accreditation: Simplified. This Is Badge 6.

Want to see how this works in Badge 6?

A 30-minute walkthrough with someone who has done accreditation. Bring a policy and your standards, and we’ll show you what Badge 6 finds.