Avoid Disputes: Drawing Version Control for UK Builders (Golden Thread)

Discover how to implement a robust drawing version control system to comply with golden thread guidance and prevent costly site errors and disputes.

By James Shorter ·

Avoid Disputes: Drawing Version Control for UK Builders (Golden Thread)

Hands comparing construction drawing revisions

Drawing version control is a controlled register plus versioned storage and approvals, linked to every site diary, photo, RFI and variation. The single action to take right now: check your drawing register against the drawing currently in use on site, and confirm the latest revision is the one linked to the project record. Government guidance on the golden thread treats this as a baseline requirement, not a nice-to-have, and tools such as BRCKS exist to hold that record for you.

TL;DR:

  • Maintaining a separate, clearly labelled register with current and superseded drawings is essential to prevent outdated revisions from remaining in use on site.
  • Every drawing revision must be accompanied by detailed metadata linking it to site records, RFIs, or variations, ensuring accountability and easy reference.
  • A responsible individual, called the distribution owner, should oversee the drawing register, issue authorised revisions, and ensure superseded drawings are removed promptly from site.
  • Using software that automatically stores all revisions, records approvals, and links drawings to site documentation minimises disputes and speeds up audit retrieval.
  • Physical site controls, like removing superseded drawings from boards immediately and briefing trades on changes, are crucial to match digital processes and comply with government guidance.
BRCKS
brcks.io
Keep Every Drawing Revision Traceable
BRCKS keeps versioned project files, RFIs, variations and site records together, giving UK building teams a searchable project history.
See BRCKS in action

Table of Contents

Step by step: receive, register, review, approve, issue, supersede

Every drawing revision should move through the same states, in the same order, every time. Skip a step and you lose the audit trail that proves what was on site and when.

  1. Receive: log the date, the originator and the revision ID against the drawing register.
  2. Check: compare the incoming revision against the register and the project’s EIR or PEP requirements.
  3. Review: mark the drawing as “in review” until someone with authority has checked it.
  4. Approve: record who approved it, when, and why, not just that it happened.
  5. Issue: send the authorised copy to named recipients, not a general folder.
  6. Supersede: mark the old revision as superseded the moment the new one is issued.

This sequence mirrors the process set out in contractor quality control guidance, which requires checks at each stage before a drawing reaches site. The explicit states matter because a drawing that’s merely “on the server” tells you nothing about whether it’s been checked or approved. At design review stages, Imperial College’s process requires uploading end-of-stage information to a common data environment and formally approving anything that doesn’t meet requirements before it’s used.

Once a revision is issued, two things happen straight away: superseded copies come off site, physically and digitally, and the gangs affected get briefed before work continues.

Pro Tip: Name one person as the distribution owner for every project. If nobody owns issuing and removal, superseded drawings quietly stay in use.

Linking a revision to diaries, RFIs, photos and variations

A version number on its own proves nothing. What proves compliance is the link between that revision and the site record created while it was current.

Capture these fields every time a drawing is used or referenced:

  • Drawing reference and revision ID.
  • Issuance date and the name of the approver.
  • A brief summary of what changed from the previous version.

In practice this means a site diary entry carries the revision ID alongside its dated photo, an RFI references the exact revision it queries along with its approval status, and any resulting variation is logged against that same revision. Done properly, this answers two questions that come up in every dispute: which revision applied on a given date, and what approvals or briefings exist to prove the team knew about it.

UK government guidance states that a project record-keeping system should include version control so users can see changes, alongside preserved current and superseded records and a full audit trail. That’s the standard your site paperwork is being measured against, whether or not the project is formally in scope.

The common failure is storing PDFs with no metadata, or naming files so loosely that “latest” is a guess rather than a fact.

On-site controls: registers, labelling and briefings

Digital discipline only works if the physical site matches it. A single register, split into current and superseded, is the anchor for both.

  • Keep one drawing register with clearly separated “current” and “superseded” sections, digital and hard copy.
  • Prefix superseded files (SS-) and move them out of the active folder immediately, never just rename them in place.
  • Run a sign-out and sign-in process for hard copies, with a named owner responsible for updating what’s displayed on site.
  • Brief affected trades before work resumes, covering safety, programme and cost implications of the change, not just the drawing itself.

CDBB’s guidance on ISO 19650 workflows describes explicit states such as review, reject, amend and accept, precisely so that a revision’s history and the reasoning behind it survive rather than getting overwritten. That’s the same logic behind keeping superseded drawings visible in an archive rather than deleting them.

Pro Tip: A superseded drawing pinned to the site board is worse than no drawing at all. Remove it the moment the new one is issued, don’t wait for the next walk-round.

Worker removing superseded site drawing

What your software must actually do

Most disputes come down to one question: could you prove which revision was current on a given date, and who signed it off? The right tool answers that in seconds, not by digging through e-mail chains.

Look for these features as a minimum:

  • Versioned file storage that keeps every prior revision, not just the latest.
  • Approval metadata recording who approved a revision, and when.
  • Distribution lists and role-based notifications so the right people are told automatically.
  • Searchable revision history that returns results in plain language, not a folder tree.
  • An audit trail linking each revision to the diary entries, RFIs and variations that reference it.

A tool worth using should also capture photos, diary entries and WhatsApp threads directly into the project record, connecting to other common data environments rather than sitting apart from them. Test it with one query: “which revision was current on this date, and what work references it.” If the answer takes more than a minute, the system isn’t doing its job.

Where sites actually go wrong

Where sites actually go wrong — overview diagram

The hard part isn’t issuing a new revision. It’s proving the old one was pulled from use, and that everyone working that day knew about the change.

Most failures I’ve seen on site are procedural, not technical: a register exists but nobody owns it, or a drawing gets replaced without anyone briefing the trades already on the job. The fixes are simple and cheap. Appoint a distribution owner, enforce register discipline without exception, and attach a revision ID to every diary entry, photo and RFI as a matter of routine. Where a design change affects procurement or cost, escalate it and record the decision in the project execution plan rather than leaving it in a WhatsApp thread.

— James

How BRCKS puts this into practice

BRCKS builds the controls above into the way you already work, rather than asking you to run a separate system alongside site life. Versioned project files keep every drawing, RAMS document and quote on record, with automatic diaries, RFIs and photo filing landed against the right project without extra typing.

BRCKS

  • Versioned drawings, RAMS and quotes stored against the project, with the current and superseded copies both retained.
  • Automatic site diaries, RFI tracking and photo filing, so revision links aren’t a separate admin task.
  • Role-based notifications and a branded client portal, so approvals and updates reach the right person without chasing.

The result is an audit trail you can produce in seconds when a variation is queried, and admin time back in the working day, teams report saving 30+ minutes a day on this alone. Subcontractors and clients join free. Check BRCKS pricing, from £40 per seat per month billed annually, or see how it fits your trade on the builders overview page.

Sources

FAQ

What is drawing version control in construction?

It’s a controlled register and versioned storage system that tracks every drawing revision, its approval status and its links to site diaries, RFIs and variations. Government golden thread guidance treats this level of record-keeping as a baseline expectation for project information.

How is an audit trail different from a version history?

A version history simply lists the revisions that have existed for a drawing. An audit trail goes further, recording who approved each revision, when, and what site records, such as diaries or variations, reference it, which is what the golden thread guidance requires.

Who should be responsible for the drawing register?

One named person, often called the distribution owner, should manage the register, issue authorised copies and confirm superseded drawings are removed from site. Without that named responsibility, older drawings often stay in circulation by accident.

How do I stop superseded drawings being used on site?

Prefix superseded files clearly, move them out of the active folder immediately, and remove any hard copies from site boards the moment a new revision is issued. Briefing the affected trades before work resumes closes the gap that causes most errors.

Can project management software handle version control automatically?

Yes, provided it stores every prior revision with approval metadata and links drawings to diaries, RFIs and variations automatically. BRCKS does this by filing versioned drawings, RAMS and quotes against the right project alongside automatic diaries and RFI tracking, cutting the admin needed to keep a compliant record.

Recommended


How BRCKS Can Help

Maintaining a robust Golden Thread through precise drawing version control is no longer just best practice; it is a regulatory necessity for modern UK builders. BRCKS simplifies this complex requirement by providing a centralised platform where the latest revisions are always accessible, ensuring your site teams never work from outdated plans. By integrating these automated workflows into your daily operations, you can mitigate the risk of costly disputes and focus on delivering quality projects. We invite you to discover how BRCKS can strengthen your compliance and streamline your project management today. Learn more at BRCKS and explore our full feature set.


Sources