Compliance Evidence Records: What to Keep and How

Published 26 October 2026 · gribit

Fire safety records gathered for inspection

Compliance evidence records are the dated, traceable documents that prove your safety checks happened and that faults were dealt with. For a UK small business that means check logs, test results, certificates, training records and the follow-up to anything that failed. If an inspector, insurer or new manager asks “how do you know?”, these records are your answer.

This guide explains what counts as evidence, what each entry should contain, how long particular records must be held, and how to keep it all findable without a stack of folders.

Gribit

Keep safety evidence in one place

Gribit helps you record recurring safety checks, track follow-ups and store certificates and documents in a digital logbook.

Visit Gribit

TL;DR

Evidence is more than a certificate: it is the check, the date, the person, the result and what was done about any fault.
Fire and rescue services expect records of alarm tests, escape-route checks, equipment maintenance, training, drills and remedial action.
Electronic records are acceptable for work equipment inspections, if they are secure and can be produced to an enforcing authority on request.
Retention periods differ by check: Legionella monitoring records, for example, must be kept for at least 5 years, goods-vehicle records for at least 15 months.
A digital logbook with reminders, follow-up tracking and stored certificates keeps all of this in one place, at £49 per site per year with Gribit.

What counts as compliance evidence

The phrase comes from regulated industries, where it usually means documentation such as policies, procedures, audit logs and training records that show an organisation is meeting legal, regulatory or internal standards. For a shop, pub, salon, office or village hall, the idea is the same but the paperwork is more practical.

Think of evidence in three layers:

The check itself. A weekly fire alarm test, a first-aid kit inspection, an emergency light test, a visual check of a ladder.
The supporting documents. Certificates from engineers, risk assessments, servicing reports, training certificates.
The follow-up. What was found, who was told, what was fixed and when.

Most businesses are reasonable at the second layer, because certificates arrive as PDFs or paper. The first and third layers are where gaps appear: a test that was done but never written down is, to an inspector, a test that cannot be shown.

Examples of compliance documentation

Common examples include business licences, permits, training logs, signed policy acknowledgements and safety inspection certificates. In a UK small-business setting, that translates to:

Fire risk assessment and its review dates
Fire alarm test log and emergency lighting test log
Fire extinguisher service records
First-aid kit check records and first-aider training certificates
Electrical and gas safety certificates
Legionella risk assessment and temperature or flushing records, where relevant
Equipment inspection reports, tags or labels
Accident book entries and incident follow-up
Staff training and fire drill records

What fire and rescue services expect you to record

Fire safety is where the expectations are clearest. County Durham and Darlington Fire and Rescue Service recommends keeping records of:

significant findings and actions from the fire risk assessment
checks and tests of escape routes and fire systems
false alarms
emergency lighting and firefighting equipment maintenance
training and evacuation drills
alterations, repairs and audits
incidents with accident potential, and the remedial action afterwards

It also says competence details may be recorded, and it treats the quality of your records as an indicator of the quality of your wider safety management. In other words, tidy records suggest a tidy operation, and the reverse is also true.

When a fire safety officer visits, Bedfordshire Fire and Rescue Service notes that they may ask to see the fire risk assessment, maintenance logs for firefighting equipment, staff training records and test records for systems such as alarms and emergency lighting. Have those four things retrievable in minutes, not hours.

Records are one half of fire planning; what people actually do in an emergency is the other. A posted fire action sheet and map puts the instructions where people will see them, while your logbook proves the equipment behind those instructions was checked.

What each entry should say

A line reading “alarm tested, OK” is weak evidence. Avon Fire and Rescue Service’s fire log book guidance shows what a stronger entry looks like. It asks businesses to record:

whether the test was visual or full
whether it was done by staff or by a recognised engineer
any faults found
the remedial action
the date the fault was reported
all action taken and the date it was completed

It also makes the point that records may be electronic or paper, and that complete logs help show due diligence under the Fire Safety Order 2005 and let you follow reported faults through to completed corrective action.

You can turn that into a standard entry for almost any routine check:

Field	Example
What was checked	Fire alarm, call point 4 (rear corridor)
Date and time	Recorded automatically or by the person checking
Who did it	Named person, and whether staff or contractor
Type of check	Visual or full test
Result	Pass, fail or needs attention
Fault and action	What was wrong, who was told, what was done
Date closed	When the fix was confirmed
Attachments	Engineer’s report, photo, certificate

The last two rows are the ones most paper logbooks miss. A fault that is logged but never closed is worse than no entry, because it shows you knew.

How long to keep records

There is no single UK retention period for safety records. It depends on the check and the rule behind it. These are the ones the official sources state clearly:

Record	Minimum retention	Source
Work equipment inspection results	Until the next inspection	HSE and PUWER 1998
Legionella control records	While current, plus at least 2 years	HSE
Legionella monitoring inspection records	At least 5 years	HSE
Goods-vehicle inspection and maintenance records	At least 15 months	GOV.UK
Certain construction inspection reports	On site until work ends, then 3 months at an office	HSE CIS47

Two other rules affect what you write down in the first place. Employers with five or more employees must record their risk assessment findings, and businesses with more than 10 employees must keep an accident book under social security law, as the same HSE guide explains.

For landlords and managers of premises with gas appliances, the Gas Safety (Installation and Use) Regulations 1994 require records stating inspection dates, defects identified and remedial action, and those records must be made available to an affected tenant on request and reasonable notice.

Not everything needs a formal record. The HSE says that for low-risk work equipment a quick visual check before use is often enough, so the aim is not to log every glance at a stepladder. Decide which checks your risk assessment says matter, and record those properly.

Where you are unsure of the period for a particular check, keep records at least as long as the rule above suggests and ask your insurer, your fire risk assessor or the relevant enforcing authority. Do not guess in the shorter direction.

Where to keep records so you can produce them

The HSE is clear that inspection records do not have to be on paper. A computer record is acceptable, provided it is secure and can be produced to an enforcing authority when asked. Three practical tests follow from that.

Can you find it in two minutes?

An inspector at the door will not wait while you hunt for last March’s emergency lighting certificate. Records should be organised by site, then by item or location, then by date.

Is it secure?

The HSE’s basic guidance says records that contain personal details should be stored confidentially in a secure place. A shared drawer in a back office or an unprotected spreadsheet on a shared laptop does not meet that standard.

Would it survive damage to the building?

Fire services including Bedfordshire recommend an off-site copy of important safety logbooks so evidence can be recovered after site damage. A single paper logbook hanging in the manager’s office is exactly the record that disappears in the incident you most need it for.

Do reviews leave a trace?

Reviewing your fire risk assessment is not enough; the GOV.UK 5-step checklist says to keep a record of the review and the date it was completed. The same habit applies to every recurring check: the review is part of the evidence.

What to do when a check finds a fault, or evidence is missing

If a check finds a defect, the first step is to report it. The HSE’s guidance for work equipment says faults should be reported to a supervisor, and the PUWER regulations expect deterioration to be detected and remedied in good time. A workable routine:

Record the fault the moment it is found, with date and who found it.
Tell the person responsible and note that you did.
Take the item out of use or put a temporary control in place if it affects safety.
Arrange the repair and attach the engineer’s report or invoice.
Record the completion date and who confirmed it was fixed.

If evidence is missing, for instance a test you cannot prove happened, do not backfill entries or invent dates. Record the gap honestly, carry out the check now, date it today and log it. An honest gap followed by a recorded fix reads far better than a suspiciously perfect run of ticks.

The HSE’s guide to managing for health and safety describes active monitoring, such as routine checks, and reactive monitoring, such as incident investigation, with documentation bridging the two. Your fault log is where they meet.

Compliance evidence records versus a compliance report

People often search for both. A compliance report is a summary: it collates information on efforts to meet applicable standards, and can set out the scope, findings, compliance status and timelines for improvement. Evidence records are the raw material behind it.

For a small site, a useful report is one page: what you checked this quarter, what failed, what is still open, and what is due next. If your records are structured, that page can be produced by exporting them rather than by rewriting from memory.

Our view: evidence is a habit, not a folder

We built Gribit because the same pattern kept appearing in small businesses. The checks are done, mostly. The certificates exist, somewhere. What fails is the joining up: nobody can see at a glance what is due, who did last week’s test, or whether the fault from last month was ever fixed.

Our view: evidence is a habit, not a folder — overview diagram

Paper logbooks and spreadsheets both depend on someone remembering to open them. The most valuable thing a system can do is remove that dependency. Reminders arrive on time, the check takes a minute to record, faults stay open until someone closes them, and the certificate sits next to the check it supports. When a manager leaves or a new member of staff takes over, the history stays with the site, not in someone’s head.

We also think the follow-up matters more than the tick. A logbook full of passes proves little if the one fail from March has no closing entry. Build your routine around closing things out, and the evidence largely takes care of itself.

— Jon

Setting up your own evidence system

Whether you use paper, a spreadsheet or software, the structure is the same.

Step 1: List the checks your site needs

Start from your fire risk assessment and any other risk assessments. Typical items for a pub, shop, salon, office or village hall: fire alarm test, emergency lighting, extinguishers, escape routes, first-aid kit, electrical equipment, and water systems where relevant.

Step 2: Set the frequency and the owner

For each check, name the frequency and a responsible person plus a backup. Checks without a named owner are the ones that lapse.

Step 3: Decide what “done” looks like

Use the entry fields in the table above. Agree on what counts as pass, fail and needs attention, so two different people record the same thing in the same way.

Step 4: Attach the paperwork to the check

Store certificates and reports against the item they relate to, not in a general pile. When an inspector asks about the alarm system, you want the test log and the engineer’s certificate together.

Step 5: Review monthly

A ten-minute monthly look at open faults and upcoming due dates catches most problems before they become findings.

Doing this with a digital logbook

Gribit is a digital logbook for small businesses. You schedule recurring checks such as fire alarm tests and first-aid kit inspections, record results, track follow-up actions, and store certificates and supporting documents in the same place. You can assign staff access, receive automated reminders, export records, and organise checks by site, item or location.

The annual plan is £49 per site per year, so a pub with one premises pays for one site. If you want to see whether it fits your routine, you can start with the Gribit site logbook and set up your first checks.

FAQ

What are examples of compliance documentation?

For a small UK business, typical examples are the fire risk assessment, alarm and emergency lighting test logs, extinguisher service records, first-aid kit checks, electrical and gas safety certificates, training records and accident book entries. Fire and rescue services such as County Durham and Darlington also list drills, false alarms, repairs and audits.

Do compliance records have to be on paper?

No. The HSE says inspection records can be a computer record or another format, provided they are secure and can be produced to an enforcing authority on request. Avon Fire and Rescue Service also accepts electronic or paper fire logs.

How long should I keep safety check records?

It depends on the check. Work equipment inspection results must be kept until the next inspection, Legionella monitoring records for at least 5 years, and goods-vehicle inspection records for at least 15 months. See the retention table above and confirm the rule for your own check with the relevant enforcing authority.

What should I do if a check finds a fault?

Record it straight away, report it to the responsible person, make the item safe, arrange the repair and log the completion date. Keep the engineer’s report with the entry so the whole story is in one place.