Document version control: 8 ways to automate

What document version control covers

Document version control is how a business makes sure everyone works from the current version of a procedure, checklist, risk assessment or policy, and that old versions are taken out of use. Each issued version gets a number and a date. Each change is written down with the reason for it. Someone checks it and someone approves it. Then every old copy, on the wall, in a folder or on a shared drive, is replaced. Many businesses write this up as a document control procedure.

Writing the new version is the easy part. Getting it to every place it is used is harder. A new cleaning schedule goes on the shared drive, but the laminated copy in the kitchen is from last year. A new risk assessment is approved, but the site team still has the old one in the van. Version control is the record that the change reached the places where people use the document.

The UK rules on keeping documents current

The law does not usually say "use version numbers", but it often says documents must be kept up to date. The Management of Health and Safety at Work Regulations 1999 say a risk assessment must be reviewed if there is reason to think it is no longer valid or there has been a significant change, and changed if the review shows it needs to be. Employers with five or more employees must record the significant findings. If the old one is still in the site folder, the change has not reached the people doing the work.

Food businesses have a similar duty. Article 5 of Regulation 852/2004, as it applies in the UK, requires food safety procedures based on HACCP principles and documents and records to show they work. It also says that when the product, process or any step changes, the business must review the procedure and make the changes needed. Version control is how you show that review happened and the new procedure is the one in use.

What makes version control work

A number on the page only helps if everyone can see which number is current. The versions below start with a simple change record and add review, approval, photos of the new copy in place, and follow-up on old copies one at a time.

#1 - The change record

Who it's for: One person who owns a few procedures or checklists.

What it is: A change record is one change to one document, on a phone. It asks which document and the new version number and date, and what changed and why. Eight checks come before it goes live: version and date on every page, the change log, review by someone else, approval, the old version withdrawn and kept, old copies replaced, users told, and a next review date. Then the next review date and anything not done. Every change is recorded with its reason.

In practice: A café owner updates her allergen procedure after a new supplier changes a recipe. She opens the change record, writes version 4 and the reason, and ticks the checks. She writes that the copy in the staff room is replaced but the one in the front of house folder is not yet, because the folder is at the other site.

Why it works: The eight checks follow the change from the screen to the place people use it. Most version problems are not about the content. They are about an old copy left somewhere.

The common failure is stopping when the document is saved. The new file exists, so the job feels done, but the people who use it still have the old one. The checks about replacing copies and telling people make you finish that part. The reason line matters too. Six months later, nobody remembers why the procedure changed, and the reason is what stops someone changing it back.

Steps included:

• 1 text input (which document and version)
• 1 text input (what changed and why)
• 1 checklist (8 checks before it goes live)
• 1 text input (next review date)
• 1 text input (anything not done)

When to upgrade:

1. Several people change documents
2. You need to show the new version is in place
3. Changes need a named approver
4. The same documents change again and again

#2 - With guidance above the checks

Who it's for: Teams where several people write or update documents.

What it is: The same change record, with two guidance panels above it. The first says how to number a version: a number and date on every page, drafts not numbered as issued, and one line in the change log for each change. The second says how to replace old copies: find every place it is used, replace each one, mark the old file withdrawn rather than deleting it, and tell people what changed. Everyone numbers and replaces documents the same way.

In practice: A cleaning company has four supervisors who each update site checklists. One had been naming files "final", "final 2" and "final new". He reads the first panel and starts using version numbers and dates. The second panel reminds him that the client's copy in their reception folder needs replacing too.

What it adds to the previous template:

1. How to number a version, the same way every time
2. How to find and replace every old copy
3. Why to keep old versions, not delete them

Why it works: Without a rule, every person invents their own numbering, and nobody can tell which file is current. The first panel gives one rule, so a version number means the same thing whoever wrote it.

Keeping the old version matters as much as replacing it. If something goes wrong, you may need to show which procedure was in use on a given date. A deleted file cannot show that. Marking it withdrawn, and keeping it, gives you the history. The second panel also asks people to say what changed, not just that it did. "New version attached" gets ignored. "We now probe chicken at the thickest part" gets read.

Steps included:

• 1 guidance panel (how to number a version)
• 1 guidance panel (how to replace old copies)
• The five steps from #1

When to upgrade: When you need to show the new version is in place (#3).

#3 - With a photo of the new version

Who it's for: Businesses with posted procedures, signs or folders on site.

What it is: The guided change record, with a photo step straight after the checks. The person takes a photo of the new version in place, on the wall or in the folder, with the version number in the shot. The photo sits on the same record as the change. You can see the new version is up without going to look.

In practice: A pub group changes its cellar cleaning procedure. Each site manager photographs the new sheet on the cellar wall with version 2 showing. Head office can see eleven sites have it up and one photo still shows version 1.

What it adds to the previous template:

1. A photo of the new version in place
2. The version number in the shot
3. Proof the posted copy changed

Why it works: A tick says the old copy was replaced. A photo shows which version is on the wall. It is the quickest way to check a change reached every site.

Get the version number and date readable in the shot, and enough of the wall or folder to show where it is. If the document is in more than one place, take a photo of each one. A photo of a laminated sheet behind a newer one is worth taking too, because a second copy left in place is how the old version comes back. When an inspector or auditor asks which procedure is in use, the dated photo answers it. A month later, the same photo shows whether someone has put the old sheet back up.

Steps included:

• The guided change record from #2
• 1 photo (the new version in place)

When to upgrade: When changes need a named approver (#4).

#4 - With signatures from both sides

Who it's for: Businesses where documents need a named approver.

What it is: The photo change record, with two signatures at the end. The person who made the change signs that the record is accurate. The person responsible for the document signs that the change is approved. Every version has an author and an approver.

In practice: A care home's deputy manager updates the medication procedure after a pharmacy change. She signs the change record. The registered manager reads the change, asks one question, and signs as approver. When the inspector asks who approved the current version, both names and the date are on the record.

What it adds to the previous template:

1. A signature from the person who made the change
2. A signature from the person who approved it
3. A clear point where the new version was approved

Why it works: A change made and approved by the same person is easy to get wrong without anyone noticing. A second name means someone responsible has read it before it reaches the people who use it.

Keep the author and the approver different people where you can. The approver should be whoever is responsible for that area, such as the head chef for a kitchen procedure or the site manager for a risk assessment. They should sign against the change itself, not just the fact that a new version exists. If the approver is away, name a deputy rather than letting the author approve their own work, even for a small change. The signed record then shows who agreed to what, and when, for every version the document has had.

Steps included:

• The photo change record from #3
• 1 signature (updated by)
• 1 signature (approved by)

When to upgrade: When the same documents change again and again (#5).

#5 - With the last change on screen

Who it's for: Teams whose procedures and checklists change often.

What it is: The signed change record, with a Pilla briefing on the "which document and version" step. Pilla looks up the last change record for the same document. It says the last version number and date, what changed, who approved it, and anything that was left not done. Each change starts from the last one.

In practice: A food factory's technical manager updates the metal detector check. Pilla tells her the last version was 6, approved in June, and that the night shift folder was never updated. She checks the night folder first, finds version 5, and replaces it before issuing version 7.

What it adds to the previous template:

1. The last change to this document, before you start
2. The last version number, so the new one follows on
3. Anything left not done last time

Why it works: It is easy to number a new version wrongly, or change a document without knowing why it was last changed. The briefing puts the last version and its reason on screen.

It also catches gaps that never closed. If the last change left an old copy in a folder, the briefing shows it before the next change makes the gap worse. Over time, the briefing builds a short history for each document. That history is what the food hygiene rules and the risk assessment rules both point at: a record that the procedure was reviewed when things changed, and that the review led to a new version people actually use.

Steps included:

• The signed change record from #4
• 1 Pilla briefing of the last change, on the "which document and version" step

When to upgrade: When old copies left in use need a proper account (#6).

#6 - With more detail when old copies remain

Who it's for: Teams that need old copies found and replaced.

What it is: The same change record, with a Pilla rule on the "anything not done" step. If the note says any old copy is still in use, anyone has not been told, or it has not been reviewed or approved, the next step opens. It asks where old copies or gaps remain, who will fix each one, and by when. If everything is done, the step stays out of the way. An old copy left in use leaves with a name and a date.

In practice: A hotel group updates its fire procedure. The change record at one hotel says the copy behind each bedroom door is the old one. The follow-up opens. The manager writes that housekeeping will replace all 84 by Friday, and that the night porter has been shown the new version tonight.

What it adds to the previous template:

1. A follow-up that opens only when something is not done
2. Where old copies or gaps remain
3. Who fixes each one, and by when

Why it works: "Old copies still up" is a note. "Housekeeping to replace 84 by Friday" is a plan. The follow-up asks for it while the person knows exactly where the old copies are.

The gap between approval and replacement is when the wrong procedure gets followed. Writing down who fixes each gap, and when, shortens that gap and makes it visible. If a gap can't be fixed quickly, the follow-up is also where you note what was done in the meantime, such as telling the people affected in person. That matters most for safety documents, where the old version may now be wrong.

Steps included:

• The change record with the last change on screen, from #5
• 1 Pilla rule on the "anything not done" step
• 1 follow-up step in the chain (where old copies remain)

When to upgrade: When the person who owns the documents should hear about gaps straight away (#7).

#7 - With a direct message about the gaps

Who it's for: The person who set the change record up.

What it is: When the follow-up step is filled in, Pilla sends a direct message to the person who set the automation up. It says the document, the new version, what changed, and what is still to do and who is doing it. A change with nothing left to do sends nothing. You hear about old copies still in use the day the change goes out.

In practice: A quality manager owns 40 procedures across three sites. She gets a direct message that the new allergen matrix is up at two sites, but the third still has last month's version on the pass, with the head chef replacing it before service. She rings to check it is done by lunch.

What it adds to the previous template:

1. A direct message after the follow-up step
2. The document, the version and what is still to do
3. Nothing sent when everything is done

Why it works: The person who makes a change at one site is often not the person responsible for the document across all of them. The message joins the two up, and only when there is something to act on.

It matters most for documents where the old version is now unsafe, such as an allergen matrix after a recipe change or a fire procedure after a building change. The message carries what is still to do and who is on it, so the person reading it can decide whether to wait or step in. Set the record up as whoever owns the documents, because the message goes to the person who set it up.

Steps included:

• The follow-up change record from #6
• 1 direct message, sent when the follow-up is completed

When to upgrade: When the bigger risk is a change that never gets finished (#8).

#8 - With a chase if it is late

Who it's for: Teams with a date by which a change must be in place.

What it is: The same change record, plus a chase if it is not finished by the deadline. Pilla messages you, the person who set it up, to get it done. A change finished on time does not trigger one. A half finished change is chased, not forgotten.

In practice: A retailer issues a new cash handling procedure to every store by the end of the month. At the deadline, five stores have not finished the change record. You get a message for each. Two had the email but never printed the new sheet for the back office.

What it adds to the previous template:

1. A deadline on the change
2. A chase when the deadline passes and it is unfinished
3. No message when it was done on time

Why it works: The rest of the record only helps if it is finished. A change that is approved but never rolled out is worse than no change, because the records say one thing and the site does another.

Set the deadline by the risk. A safety or allergen change may need to be in place by the next shift. A routine wording change can wait a couple of weeks. Use the same chase for review dates, so documents do not drift past their next review without anyone noticing. Records finished on time send nothing, so the chases you get are a list of the changes still to finish.

Steps included:

• The change record from #7, including the direct message about gaps
• 1 chase if the change is not finished by the deadline

When to upgrade: This is the full route. Use an earlier version if you do not want the message or the chase.

How to pick the right version

You don't need to know the product to choose. You need to know who changes documents, where the copies live, and who approves a change.

Is it just you, or do several people change documents?

If you own a few documents yourself, #1 is enough. Once supervisors or managers update them, put the numbering and replacement rules above the checks: #2.

Are there copies on walls or in folders?

If everything is on one shared drive, ticks are enough. If copies are posted on site, add the photo: #3.

Does someone have to approve a change?

If a named person must sign off each version, add the signatures: #4.

After that, the choice is about repeat changes and gaps. If the same documents change often, use #5. If old copies left in use need a name and a date, use #6. If you want a direct message about it, use #7. If the real risk is a change that never gets finished, use #8.

Related workflows

• Staff use SOPs - getting staff to follow standard procedures
• Training signoff - recording that someone has been trained
• Safer food better business - the FSA food safety management pack
• HACCP meaning - what HACCP is and how it works
• Quality - how to automate quality management

Conclusion

Document version control makes sure everyone uses the current version of a procedure, checklist or risk assessment, and that old copies are taken out of use. Start with the eight checks, add photos and signatures when copies are posted on site or need approval, and add Pilla when the same documents change often. Open any version in the playground and use it for the next change you make.