Evidence

What makes a strong proof of compliance

What assessors look for in a proof of compliance: the right record and date range, every subpoint covered, details redacted and a clear link to the policy.

On this page

A written directive says what your agency will do. A proof of compliance shows that it did it. When I look back at the findings I’ve seen agencies receive, very few were about a missing policy. Most were about proof: it was missing, it was from the wrong period, or it didn’t show what the standard asked for.

The good news is that strong proofs follow a pattern. Once you know what an assessor is looking for, you can build files that answer the question before it’s asked.

As always, your program’s manual has the final word on what proof it expects and for how long. Treat this as general practice and check the details against your own standards.

Start from the standard, not the filing cabinet

The most common mistake is to start with the records you happen to have and work backward to the standard. It feels efficient, but it leads to files full of documents that are related to the topic without proving the requirement.

Start the other way round. Read each subpoint and ask one question: if this really happens in our agency, what record would exist because of it?

If the subpoint says supervisors review a certain kind of report, the proof is a report with the supervisor’s review on it. If it says something happens every year, the proof is the record from each year. If it says staff receive training, the proof is a roster, lesson plan or certificate that shows who was trained, on what and when.

Once you know what record should exist, go and find it. If it doesn’t exist, you’ve found a gap in practice, not just in paperwork, and that is worth knowing early.

The qualities of a strong proof

It shows the practice, not the policy

A copy of your policy is not proof that the policy is followed. Neither is a memo reminding people to follow it. Proof is the record the practice leaves behind: a completed form, a signed review, an inspection log, a dated photo, a report.

It covers the right period

Most programs expect proof over a period of time, not a single example. Check how your manual describes it. Then pull proofs that are spread across that period, not five records from the week before the assessment. An assessor who sees every proof dated in the same month will reasonably wonder what happened the rest of the time.

It covers every subpoint

A standard with four subpoints needs evidence for all four where proof is expected. One document can cover more than one subpoint, which is fine, but make sure none is left out. A simple way to check: list the subpoints and write next to each one which document proves it and where in the document to look.

It is easy to read

Point the assessor to the part that matters. Highlight the line, the signature or the date. If a record is long, a short note saying what it shows and where saves everyone time. A proof the assessor can’t make sense of quickly is almost as weak as no proof.

It is genuine and final

Use the real record, signed and dated as it was at the time. Drafts, unsigned copies and documents recreated after the fact don’t prove much, and backdating anything is a line you never cross. If a record is incomplete, say so in a note and show what you’ve done about it.

It protects people

Proofs are usually real records, so they contain real people: officers, victims, witnesses, members of the public. Redact names, addresses, case numbers and other personal details that aren’t needed to show compliance. Keep what proves the point, such as the date, the type of record and the fact that a supervisor reviewed it. A proof redacted so heavily that nothing is left to see can’t do its job either.

Weak proofs, and what to use instead

A weak proof A stronger one
The policy itself A completed record that the policy requires
A training sign-in sheet with no topic or date A roster with the date, topic, instructor and attendees, plus the lesson plan
An email saying “done” The document that was done, such as the signed report or the inspection log
One example from last week Several examples spread across the period your program asks for
A screenshot with no context The screenshot plus a note on what it shows, where it came from and when
A summary someone wrote for the file The underlying records the summary is based on, with the summary as a guide
A record that covers two of three subpoints That record plus a second document for the missing subpoint

Collect proofs as they happen

The best proof files are built a little at a time. The worst are built in a panic.

Set up a rhythm that fits your agency. Some accreditation managers ask supervisors to send copies of certain records every month. Others keep a calendar of which records are due when and pull them on a schedule. Either way, file each proof as soon as it arrives, against the standard it supports, with the relevant part marked. A proof filed the day it’s created takes a minute. The same proof found eighteen months later can take an afternoon.

Keep a short list of the records you depend on other people for, and who to ask. When people change roles, that list is what keeps the flow of proof going.

Check your proofs the way an assessor would

Before you call a standard finished, read it cold. Open the standard, read each subpoint, and look only at what’s in the file. Could someone who has never been to your agency see that the requirement is met? If you find yourself thinking “they’ll know what I mean,” add a note or a better document.

A second reader helps. Someone who didn’t build the file will spot gaps you’ve stopped seeing.

Where Badge 6 fits

Badge 6 was designed around proofs that hold up:

  • Add Proof attaches a document from your Proof Library to a standard. The library takes PDF, Word, text, images, video and audio, sorted into categories.
  • You highlight the part of the proof that matters, by hand or with Use AI to Highlight, and tag each highlight to the subpoints it covers. The Covers panel shows any subpoint still without evidence.
  • The AI Compliance Check rates each requirement Met, Partly Met, Not Shown or Missing, which is a quick way to find weak proofs before an assessor does. It is advice, not a compliance decision.
  • The Standards Progress Report flags standards with a Weak Proof or Missing Directive, so you can see where to spend your time.
  • Redaction runs automatically on upload, across documents, images, audio and video, and a review page lists everything it found. Your agency’s own details are never redacted.

The judgment about what proves compliance stays with you, your Review Manager and your assessor. Badge 6 makes it faster to find, mark and check the evidence that supports that judgment.

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.