gribitYour logbook →
← All guides

Safety Document Version Control: A Practical Guide

Published · gribit

Safety document revisions beside a control sheet

Safety document version control means that everyone in your business works from the one current, approved version of each document, and that you can show what changed, when and who approved it. For a small business, that comes down to five habits: one live copy, a consistent file name, a version number, a short change history and a review date. None of it needs expensive software.

This guide shows how to set those habits up, what to name your files, how long to keep old versions, and how to keep the checks you carry out (fire alarm tests, first-aid kit inspections) as tidy as the policies behind them.

Gribit
gribit.co.uk
Keep Safety Checks Easier to Manage
Gribit helps you record recurring safety checks, manage follow-ups and store certificates and documents in one digital logbook.
Explore the digital logbook

TL;DR

  • Keep one live version of each safety document in an active folder and move superseded versions to an archive, never deleting them.
  • Name files the same way every time: document type, subject, location if relevant, version number and review date.
  • Record every change in a short history table: new version number, what changed, who changed it and when.
  • Give each document a review date and a named owner, so documents do not expire quietly.
  • Keep records of checks separate from policies: a policy is versioned, a check is logged each time it happens.

Table of Contents

What safety document version control actually means

Version control is the management of multiple revisions of a document. In practice it uses a document control sheet and a version number built into the file name, which helps preserve a document’s authenticity, tell it apart from later copies and give you an audit trail of how it developed. That is how NHS Fife’s version control and naming guidance describes it.

The same guidance explains why this matters most for electronic files: they can easily be changed by several people, and the changes may not be obvious. A fire evacuation procedure edited by a manager on Monday and by a deputy on Thursday can leave two “final” files and no record of which one staff were told about.

For a pub, shop, salon, office or village hall, the risks are practical:

  • A new starter is trained from an out-of-date fire procedure.
  • A risk assessment is updated but the printed copy on the office wall is not.
  • An inspector, insurer or licensing officer asks for the current document and you find three candidates.
  • Nobody can say who approved the last change.

Keep it proportionate

The Health and Safety Executive is clear that paperwork is a means, not the goal. Its guidance Managing for health and safety (HSG65) says health and safety documentation should be functional and concise, with the emphasis on effectiveness rather than the volume of paperwork. It also says employers with five or more people must record the significant findings of risk assessments in writing.

So version control is not about building a bureaucracy. It is about making sure the few documents you do have are the right ones, and that people can find them. The same principle applies to any policy that needs to stay current, such as a remote work security policy that has to follow changes in how your team works.

Which documents need version control

Start with documents that tell people what to do or record a decision about risk:

  • Health and safety policy
  • Risk assessments, including fire risk assessments
  • Emergency and evacuation procedures
  • Safe working procedures and method statements
  • Training matrices and induction material
  • Checklists and forms that you reuse

That last group is easy to overlook. A reusable checklist, for example a facilities team’s office furniture installation checklist, gets copied, adapted and re-saved many times. If the template is not versioned, old copies keep circulating long after the template has improved.

Completed records, such as a signed weekly fire alarm test, are different. You do not revise them; you add a new one each time. We come back to that distinction below.

Weekly fire alarm test logbook beside control panel

A simple five-step system

The Institute of Fire Safety Managers’ Formal Document Policy and the university and NHS guidance in the sections below all point to the same core routine. Here it is, scaled for a small site.

  1. Create a single home. Choose one folder structure, shared drive or system where current safety documents live. The Royal Yachting Association’s guidance on safety management system documentation advises collating documents in one place and making sure staff and volunteers know where to find them.
  2. Name an approver. Decide who signs off each document. Use a role, such as “Premises Manager”, rather than only a personal name, so the responsibility survives when someone leaves.
  3. Number and date every document. Put the version number and date in the file name and in the document itself, ideally in the footer.
  4. Record each change. Add a line to the document’s history table every time it is revised.
  5. Archive, don’t delete. When a new version is approved, move the old one to an archive folder and make sure only the live version remains where staff look.

The IFSM policy states that the version number and date should be updated in the footer and in the formal document library, and that the previous version should not be deleted but saved in an online archive folder. That is a good model for a small business, too.

Naming conventions that people will actually follow

A useful file name tells you what a document is before you open it. A sensible pattern includes the document type, the subject, the site or department if you have more than one, the version number and the review date. The exact order matters far less than using it every time.

NHS Fife’s guidance recommends keeping naming rules for documents and folders as simple and clear as possible, and preferring a broader approach that users can understand and remember over a more detailed and sophisticated one. If your rules need a manual, staff will stop following them.

Here is an example pattern and some file names built from it:

Part Example Why it helps
Document type RA (risk assessment) Sorts similar files together
Subject Kitchen Says what it covers
Site or area HighStreet Separates multi-site documents
Version v2.1 Shows which revision it is
Review date Review-2027-03 Shows when it falls due

Put together: RA_Kitchen_HighStreet_v2.1_Review-2027-03. A fire procedure might read Procedure_FireEvacuation_VillageHall_v1.0_Review-2027-06.

Some practical tips:

  • Avoid words such as “final”, “final2” or “latest”. They stop being true the moment someone edits the file.
  • Use the year first in dates (2027-03) so files sort in order.
  • Avoid spaces and special characters if you share files between systems.
  • Write the convention on one page and keep it with the documents.

The IFSM policy goes a step further and gives every formal document a unique identification code relating to the subject area and the type of document. If you have more than a dozen documents, a short code like RA-004 is worth adding.

Version numbers: a scheme you can explain in a minute

A widely used approach, set out in NHS Shetland’s good practice guidance, works well for small organisations:

  • The first draft is 0.1, then 0.2, 0.3 and so on while it is being written and reviewed.
  • When it is complete and approved, it becomes version 1.0.
  • Minor revisions after that are 1.1, 1.2 and so on, until a major rewrite takes it to 2.0.

This tells anyone at a glance whether a document is a draft (below 1.0) or approved, and how far it has moved on. A simple rule of thumb: change the number after the point for wording, contact details or minor corrections; change the number before the point when the arrangements themselves change, such as a new evacuation route.

The same guidance suggests protecting approved versions with a read-only setting, so that any edit prompts the user to save the file under a new title. The University of Nottingham’s version control guidance makes the same point: it is easy to update a document and forget to change the version number in the file name or the document, and saving approved versions as read-only forces a new version when someone edits.

Keep a change history in the document

File names alone cannot tell you who changed what. Nottingham’s guidance says exactly that: a naming convention will not tell you who made a change or what it was, so where that matters you should use a version control table.

The University of Edinburgh’s document version control procedure asks for a history table in the document, showing the new version number, what was changed, who made the change and when. NHS Fife’s document control sheet records the same four things. A small-business version looks like this:

Version Date Changed by What changed
0.1 2 Feb 2026 Premises Manager First draft
1.0 16 Feb 2026 Owner (approver) Approved for use
1.1 9 Jun 2026 Premises Manager Added new fire assembly point
2.0 3 Nov 2026 Owner (approver) Rewritten after kitchen extension

Put it on the first or last page. It takes a minute to update and saves hours when someone asks why the procedure changed.

A register for everything

Once you have more than a handful of documents, add a one-page register listing each document’s name, number, version number and version date, and update it whenever a document is amended. That is the approach in an Australian heritage railway guide, Element 7 on document control, which also advises recording reviews where nothing needed changing, so you can demonstrate the review took place. The rules are from Australia, but the habit translates to any small site.

Review dates: stop documents ageing quietly

A document can be perfectly filed and still be wrong. A risk assessment written two years ago may not reflect today’s equipment, tasks or staff. A review date in the file name and footer fixes that, as long as someone is responsible for acting on it.

The IFSM policy says formal documents should be reviewed at least every three years, or more often where required. For safety documents in a small business, think by risk rather than by calendar alone:

  • Review a risk assessment whenever something significant changes: new equipment, a layout change, a new activity, an incident or near miss.
  • Review policies and emergency procedures on a fixed cycle, at least as often as your own policy states.
  • Treat repeating checks as a routine, not a document: they are logged each time they happen.

Add a recurring calendar reminder for each review date, assigned to the named owner. A date written in a file name that nobody is prompted to look at is just decoration.

Getting old copies out of circulation

The most common failure in version control is not the missing document but the extra one. Staff print a procedure, pin it up, and a year later it is still there after the digital version has been replaced.

Here is what the guidance suggests:

  • Clearly mark superseded documents. Edinburgh’s procedure says superseded documents should be identified as such, removed from circulation and archived electronically, so they are not available for general use once the new version is effective.
  • Track printed copies. The Australian rail guidance advises keeping track of who holds paper copies, so they can be replaced when the document changes. In a small site, that can be as simple as a line in the register: “Printed copies: kitchen wall, staff room, reception.”
  • Delete drafts once the final version is agreed. Nottingham says that in most cases drafts can be deleted after approval, to reduce the confusion of duplicates. Keep approved earlier versions, but not every working draft.
  • Use job titles in documents. The rail guidance recommends referring to position holders by title rather than personal name, so you avoid rewriting when people leave.
  • Tell people what changed. The same guidance says managers should check that what happens in practice matches the latest written procedure and that everyone knows about changes since they last worked. A short note at the start of a shift or in the staff group chat is often enough.

How long to keep old versions and records

There is no single UK retention period for all safety paperwork. It depends on the record, and some have their own rules. Treat these as pointers and check the rule for your own sector.

  • Moorepay’s guide to which health and safety records to keep gives five years as a good rule of thumb for most records. It says risk assessment records should be kept for as long as the activity they cover continues, and notes that civil injury claims can be made up to three years after an incident, so it is wise to keep assessments for the previous three years.
  • Records of reportable incidents under RIDDOR 2013 must be kept for at least three years, according to this RIDDOR guide. The record includes the date and method of reporting, the date, time and place of the event, personal details of those involved and a brief description.
  • The IFSM policy sets its own internal rule of at least five years for health and safety information.
  • For comparison, the UK Government’s JSP 375 retention table, written for the Ministry of Defence, lists three years for safety inspection records and for safe systems of work, six years for training records, and 40 years for records linked to hazards such as asbestos or noise. Your own obligations depend on your hazards, so use it only to see how much retention periods vary.

If you handle asbestos, noise exposure, or are in a regulated sector, ask your insurer, trade body or a qualified health and safety adviser what applies to you before you set an archive policy.

Our perspective: version the policy, log the checks

Most small businesses we speak to do not struggle with the policy document. They struggle with everything around it: the weekly fire alarm test someone forgot to write down, the first-aid kit that was checked but never restocked, the certificate that lives in a drawer nobody can find.

Version control is a good discipline for documents that describe how you work. But a lot of safety paperwork is not a document that gets revised. It is a record that gets repeated. A fire alarm test is not version 1.1 of last week’s test; it is a new entry, with a date, a result and a name against it. Treating those entries as files to name, number and archive adds work without adding safety.

That is why we built Gribit as a digital logbook. Recurring checks are scheduled, results are recorded in one place, follow-up actions are tracked until they are closed, and certificates and supporting documents sit alongside the checks they relate to. Automated reminders mean the check does not depend on someone’s memory, and centralised records make it easy to hand over to a new member of staff, because everything is where the next person expects it.

Our view is simple: keep your policies tidy with the habits in this guide, and let a logbook do the repetitive part. You spend less time managing paperwork and more time fixing what the checks turn up.

Jon

Putting it together: policies and checks

A workable split for a small site looks like this:

Type of record Examples How to control it
Controlled documents Risk assessments, fire procedures, policies Version number, history table, review date, archive of old versions
Repeating checks Fire alarm tests, emergency light checks, first-aid kit inspections Schedule, record each result, track actions to completion
Supporting evidence Servicing certificates, training certificates Store with the check or item they relate to, note expiry or renewal dates

The second and third rows are where most small sites lose track, because they involve dates, people and follow-up rather than editing a file. The RYA guidance says it should be possible to trace what happens in practice back to the documentation. A logbook entry that links a check to the procedure it follows does exactly that.

Try a digital logbook for your site

If your checks currently live in a paper book, a spreadsheet or someone’s head, Gribit gives you one place to schedule them, record results, track follow-up actions and store certificates. You can assign staff access, set automated reminders, export records and organise checks by site, item or location.

The Site Logbook annual plan costs £49 per year per site.

Gribit

See the digital logbook for business checks

FAQ

What is the simplest way to version control a safety document?

Keep one live copy in an active folder, put a version number and date in the file name and footer, and add a line to a change history table whenever it is revised. Move the previous version to an archive folder instead of deleting it. Name one person or role as the approver.

What should a safety document file name include?

Include the document type, the subject, the site or department if relevant, the version number and the review date. Apply the same pattern to every file. NHS Fife’s guidance prefers a simple scheme that people understand and remember over a detailed one they will not follow.

How long should I keep old versions of safety documents?

It depends on the record. Five years is a common rule of thumb for most health and safety records, RIDDOR incident records must be kept for at least three years, and some hazards need far longer. Check your sector’s rules with your insurer, trade body or a qualified adviser.

How do I stop staff using out-of-date printed copies?

Mark superseded documents clearly, remove them from circulation and keep a list of where printed copies are displayed, so each one can be replaced when the document changes. Tell staff what has changed when a new version comes into effect.

Sources