Evidencing compliance: what an auditor actually wants to see

A facilities team can be genuinely, diligently compliant and still struggle badly when someone asks them to prove it on short notice. Being compliant and being able to evidence compliance quickly are related skills, but they're not the same one, and the gap between them is where a lot of otherwise well-run teams get caught out.

What "evidence" actually means to an auditor

An auditor, an insurer, a client, or a landlord asking for evidence of compliance generally wants three things together: that the required inspection or test happened, when it happened, and what the outcome was — including whether any finding was followed up. A certificate on its own proves the first two. It doesn't prove the third, and the third is frequently the part that actually matters most.

Where evidence trails typically break

The inspection itself usually happens — most teams aren't skipping the statutory work entirely. What breaks down is the trail afterward: a certificate filed in an inbox rather than against the specific asset it relates to, a defect noted on the report but never turned into a tracked job, or records split across several people's personal folders with no single place that shows the whole picture. Asked for evidence with a week's notice, that's a genuinely difficult trail to reconstruct convincingly.

• –Certificates filed generically rather than linked to the specific asset or location they relate to
• –No visible link between a defect noted on a report and the job that fixed it
• –Evidence spread across email inboxes, shared drives and paper files with no single source of truth
• –No easy way to answer "show me everything overdue right now" without manually checking several separate records

Building a trail that holds up under real scrutiny

A trail that holds up links each inspection directly to the asset it covers, records the outcome (not just "passed" or "failed" but what was actually found), and shows the resulting job through to sign-off where one was needed. That's really the same discipline as what should happen when an inspection finds a defect — evidence quality is mostly downstream of whether findings get properly closed out, not a separate record-keeping exercise layered on top.

Why this matters beyond audits

A good evidence trail isn't just useful for the rare occasion someone formally audits the estate — it's the same information a facilities manager needs internally to answer "are we actually on top of this" honestly, and it's the raw material behind any estate-wide compliance reporting sent up to leadership. Teams that treat evidencing as a byproduct of doing the work properly, rather than a separate admin task bolted on afterward, tend to find audits far less stressful when they do come.

What an auditor does with a folder

An auditor given a complete compliance folder will usually pick two or three items and follow them all the way through — find the inspection, find the findings, find the jobs those findings raised, find the evidence the work was done, find the sign-off. What they are testing is not whether documents exist but whether the chain holds. One broken link tells them more about the estate than a hundred filed certificates.

It is why evidence assembled retrospectively rarely survives this. The chain either existed as the work happened or it is being reconstructed, and the second is usually visible in the dates.

Common mistakes

• –Holding certificates without the remedial jobs they generated
• –No link between a finding, the job raised and the evidence of completion
• –Sign-off recorded without saying who signed or when
• –Assembling the folder before an audit rather than maintaining it continuously
• –Evidence spread across inboxes, drives and contractor portals
• –No way to demonstrate the chain for a single asset on request