Design Change Tracking in Construction: A UK Guide
Master the art of logging design revisions and managing variations on UK building sites to ensure your team never builds from superseded drawings again.
By James Shorter ·
Design Change Tracking in Construction: A UK Guide
Design change tracking means logging every change to the design as it is requested, checking what it does to cost, programme and quality, getting a named person to approve it, and making sure the people on site build to the new information. On a UK job that usually means one register, one version of each drawing, and a variation raised whenever the change moves scope or price. This guide shows how to set that up without adding a night of paperwork.
TL;DR
- Log every design change the day it is raised: who asked, why, what it affects, who decides.
- Price the effect on cost and programme before work starts, and get approval in writing.
- Mark old drawings as superseded the moment a revision is issued, and tell site directly.
- Treat a design change that alters scope or price as a variation, with an audit trail back to the RFI or instruction.
- Keep it all in one list per job so nobody rebuilds the story from WhatsApp messages later.
Table of Contents
- What design change tracking actually covers
- Why untracked changes cost money
- There is no single UK standard process
- The change lifecycle: proposal to site
- What to record for every change
- Who reviews and who approves
- Assessing the effect on cost, programme and quality
- How design changes, RFIs and variations fit together
- Stopping people building from old drawings
- Perspective: why the group chat is where changes go missing
- Doing this in BRCKS
- A simple routine you can start on your next job
- Common mistakes
- FAQ
- Sources
What design change tracking actually covers
A design change is any alteration to what was drawn, specified or agreed. The client moves a wall. The engineer revises a beam. The architect swaps a window. The electrician finds the consumer unit cannot go where the drawing shows it.
Tracking is the record of that change from first request to finished work. The Scottish Government’s project handbook says that recording changes to decision-making is needed for effective management and for an audit trail of accountability. That is the whole point. When someone asks in six months why the kitchen is 200mm narrower, you can answer with a date, a name and a document.
Drawings are not static either. One professional account describes design drawings as living documents that evolve through design, bidding and construction. Expect change. The job is to control it.
Why untracked changes cost money
Changes are normal. AIA best practice guidance says they are the rule on construction projects, not the exception. The problem is the untracked ones.
The usual causes are owner-driven changes, design omissions and coordination gaps on site, as the AGC project planning guide for owners sets out. The damage tends to follow a pattern. Baker Tilly’s analysis of change orders lists unauthorised work, ambiguous requests and delayed approvals as common issues that stall projects or lead to disputes.
On a residential job it looks like this:
- The client says “move the socket” on site. Nobody writes it down.
- The sparky does it. The plasterer has already boarded.
- At final account the client disputes the charge, and you have a photo with no date and a chat thread nobody can find.
None of that is a design problem. It is a record problem.
There is no single UK standard process
The Construction Innovation Hub’s 2022 report notes that there is no formally recognised or standardised change control process in the UK, with methods ranging from paper-based to fully digital. So you will not find one form that every contract demands. Your contract (JCT, NEC or a bespoke small works agreement) sets the approval route and the notice periods. Your tracking has to fit that route.
What you can standardise is your own habit. The next sections give a version that works on small and mid-sized UK jobs.
The change lifecycle: proposal to site
The Association for Project Management describes change control as the process by which requests to change the approved baseline are captured, evaluated and then approved, rejected or deferred. Its steps run: log the request in a register, review it, evaluate impact in detail, recommend a decision, update the plan if approved, then implement and monitor.
Translated to a UK site:
- Raise. Anyone can raise a change: client, designer, main contractor, trade. It goes into the register the same day, with the drawing reference.
- Review. The project manager or contract administrator checks if it is a real change or a clarification. If the drawing is unclear, that is an RFI first.
- Assess. Price it. Check programme, lead times, building regulations, safety and any knock-on to other trades.
- Decide. The person with authority under the contract approves, rejects or defers. Record who and when.
- Issue. Revise the drawing, mark the old one superseded, send the instruction.
- Implement and close. Site builds it, you photograph it, and the entry is closed against the work done.
Skip step 3 and you get arguments later. Skip step 5 and you get the wrong thing built.
What to record for every change
The Scottish Government handbook says to record the change’s origin, reason, impacts, decision authority and implementation. It also lists the supporting documents: a document control register, a change request form, a change control register, the cost plan and the programme.
For a UK residential or small commercial job, a workable entry looks like this:
| Field | What goes in it |
|---|---|
| Reference | CH-014, numbered in order |
| Date raised | The day it was first asked for |
| Raised by | Client, architect, structural engineer, trade |
| Drawing and revision | A-102 rev C, and the revision it replaces |
| Reason | Client preference, design error, site condition, regulations |
| Description | One or two plain sentences |
| Cost effect | Added, omitted or nil, with a quote attached |
| Programme effect | Days added, or none |
| Other effects | Scope, quality, safety, other trades |
| Decision | Approved, rejected or deferred, by whom, on what date |
| Instruction issued | Date and how it was sent |
| Status | Open, in progress, built, closed |
If an entry has no decision-maker and no date, it is not a tracked change. It is a rumour.
Who reviews and who approves
The handbook is clear that approval authority depends on the contract and project arrangements. Do not guess. Read the contract and write down, at the start, who can instruct a change and up to what value.
On larger jobs, RICS guidance says the quantity surveyor and project manager should assemble documentation for each change monthly, including formal instructions, the contract’s legal basis and cost breakdowns. A small builder without a QS can still copy the habit: once a month, go down the register and check every approved change has its paperwork attached.
One rule worth holding to: the client’s verbal “yes” on site is not an instruction. Confirm it in writing the same day, in the job record, before anyone picks up a tool.
Assessing the effect on cost, programme and quality
Recording a change is half of it. RICS makes the point that handling changes well is not only about recording them but about taking opportunities to improve outcomes, such as cutting cost or time. A design change is sometimes the cheaper route.
When you assess, run the same five checks every time:
- Cost: labour, materials, plant, preliminaries, and anything already ordered that is now wasted.
- Programme: lead times, which trades are held up, whether it sits on the critical path.
- Scope: does it add to or remove from what was priced?
- Quality: does it change a specification, tolerance or finish?
- Safety and compliance: building regulations, fire strategy, structural sign-off, RAMS that now need updating.
Write the answer to each, even when it is “none”. A blank cell looks like you did not check.
How design changes, RFIs and variations fit together
People mix these up, so keep them apart:
| Term | What it is | Typical trigger |
|---|---|---|
| RFI | A question about unclear or conflicting information | Drawing and spec disagree |
| Instruction | A direction to do something, often from the designer or contract administrator | Answer to an RFI, or a design decision |
| Design change | A revision to the drawn or specified design | Client, designer or site condition |
| Variation | A contractual change to scope, price or time | Any instruction that alters what was priced |
According to RICS guidance, under UK contracts design changes are often managed as variations, and they are frequently initiated or recorded through RFIs, site instructions and formal change processes that link the technical change to entitlement for cost or time. In plain terms: the RFI explains why, the instruction says what, the variation settles the money. Keep all three linked in one entry. Some US-sourced material calls variations change orders, and you will see both terms in UK paperwork. We use variation first.
Our own guides cover the money side in more detail: the variation order template and the project manager’s guide to change orders.
Stopping people building from old drawings
This is where design change tracking earns its keep. RICS says approved changes must be communicated formally through updated drawings, specifications and site instructions, and that a change process should include registering changes, distributing and filing documents and making sure affected drawings are updated. Old versions should be explicitly marked superseded when a revision is issued.
On site, that translates to four habits:
- One home for drawings. Not the van, not three email chains, not a camera roll.
- Revision letter on every sheet, and the register shows which is current.
- Direct notice. When a revision is issued, tell the trades it affects, by name, the same day.
- Remove the old one. Pull printed copies from the site office and the van.
We go deeper in our guides to drawing version control for UK builders and document control in construction.
Perspective: why the group chat is where changes go missing
We built BRCKS because most design changes on small and mid-sized UK jobs are agreed in a message, a phone call or a conversation in the driveway. That is not carelessness. It is how site works. The change is real, but the record sits in a WhatsApp group of 40 people and 600 photos.
Our view is that the tracking has to start where the conversation starts. If you ask a site team to stop chatting and fill in a form at night, the form loses. So in BRCKS the update stays a chat message, and one tap turns it into a variation, an RFI, a snag or a checklist item, filed against the right job. Subcontractors and clients can keep using WhatsApp for free and install nothing, and the update still lands in the same record.
The tool matters less than the discipline: log it the day it is asked, price it before the work starts, confirm it in writing, and kill the old drawing. Do those four things in a notebook and you are ahead of most jobs. We just make it faster.
— James
Doing this in BRCKS
BRCKS is a chat app for site teams that keeps one list per job. A message about a changed detail becomes a logged variation or RFI with one tap, drawings sit as versioned project files, and variations and RFIs carry an audit trail so you can show who asked, who approved and when.
The core site team uses the iPhone and Android app, the office uses BRCKS Web, and subcontractors and clients join free through WhatsApp. Teams is £40 per seat per month billed annually (£50 billed monthly), Solo is £20 per month, and there is a 14-day free trial. See the pricing page for the current plans, or look at construction software for builders.
If you want to see a change run from site message to approved variation, you can book a BRCKS demo.
A simple routine you can start on your next job
You do not need software to begin. You need a routine.
- Day one: set up the register. Number the changes. Write down who can instruct and approve, and up to what value.
- Daily: anything said on site that alters the design goes in the register before you leave.
- Before work starts: cost and programme effect written down, decision recorded.
- On approval: revised drawing issued, old one marked superseded, affected trades told by name.
- Weekly: review open changes at the site meeting. Chase anything undecided for more than a few days.
- Monthly: check each approved change has its instruction, cost breakdown and sign-off attached, as RICS recommends on larger jobs.
- Handover: the closed register becomes part of the project record. Our guide to decision tracking on UK residential projects covers how to keep the client’s choices in the same trail.
For wider habits around who does what and when, see our notes on project coordination best practice.
Common mistakes
- Treating small changes as too small to log. The socket moves are the ones that end up in a final account dispute.
- Logging the change but not the effect. An entry with no cost or programme line is half a record.
- Approving after the work. Retrospective approval is a negotiation, not a control.
- Issuing the revision but not telling anyone. A new PDF in a folder is not communication.
- Keeping separate lists. One for RFIs, one for variations, one for snags. Link them or merge them.
FAQ
What is the difference between a design change and a variation?
A design change is a revision to the drawn or specified design. A variation is the contractual consequence when that change alters scope, price or time. One design change can lead to a variation, or to nothing if it has no effect on what was priced.
Do I need software to track design changes?
No. A numbered register and strict drawing control will do on a small job. Software helps when several people raise changes from site, because it files each message to the right job and keeps the audit trail without separate write-up.
Who should approve a design change?
The person with authority under your contract, which is often the client or their contract administrator for anything affecting scope or price. The Scottish Government handbook states that approval authority depends on the contract and project arrangements, so check yours and record the limits at the start.
How do I stop subcontractors using superseded drawings?
Keep one current set in one place, mark the old revision as superseded when the new one is issued, and tell the affected trades directly. Pull old printed copies from site.
Sources
- Chapter 16: Change Control in Construction Projects, Scottish Government
- Technical Insights: Change Control, Construction Innovation Hub
- Design Changes and Record Drawings, ASCE Library
- Managing Uncertainty and Expectations in Building Design, AGC
- Manage construction change orders to reduce risks, Baker Tilly
- AIA Best Practices: a no-drama approach to changes
- Change control and management, RICS
- What is change control?, Association for Project Management
Recommended
- Drawing Version Control for UK Builders | Golden Thread
- Construction Variation Log Template for UK Builders
- Construction Task Tracking: A UK Project Manager’s Guide
How BRCKS Can Help
Managing design changes effectively is essential for maintaining project margins and ensuring compliance across the UK construction landscape. BRCKS simplifies this process by providing a centralised platform where every revision is logged, communicated, and tracked in real time. By digitising your change management workflow, you can reduce administrative friction and ensure your site teams are always working from the latest information. We invite you to discover how BRCKS can bring greater clarity and control to your next project. Learn more at BRCKS and explore our full feature set.