Change arrives from everywhere
The architect issues an instruction to change the cladding fixings. The client's project manager emails asking for an extra door. The M&E consultant revises a drawing and the contractor says it adds cost. At the site meeting, three items are discussed that might be variations, and the minutes record them in a sentence each.
Somebody is meant to add all of this to the variations spreadsheet. Some of it gets there. Some sits in an email nobody filed. Months later, the contractor submits a list of changes as part of the final account, and half the items are a surprise.
Why the variations log falls behind
The log itself is usually fine. The trouble is that it depends on someone remembering to update it from several sources, each in a different format.
- Instructions come as PDFs, emails and marked-up drawings, with no single reference system.
- Site meeting minutes mention possible changes but nobody turns them into log entries.
- The contractor's notifications and your records use different numbering, so matching them is manual.
- Status changes, such as a quotation received or a value agreed, are updated in batches rather than as they happen.
- Supporting evidence lives in inboxes, not with the entry it supports.
The damage from an incomplete register
The client gets a cost report that looks healthier than the job really is, then a shock at the end. Final accounts take longer because each disputed item needs its history reconstructed from old emails. And your surveyors spend their time searching rather than valuing.
| Stage | What goes wrong today | What the register does |
|---|---|---|
| Change raised | Mentioned in an email or meeting only | Captured as a potential variation for review |
| Instruction issued | PDF filed somewhere | Linked to the entry with its date |
| Contractor quotation | Arrives by email, not logged | Attached and status updated |
| Valuation | Spreadsheet cell, no working | Value and basis recorded |
| Agreement | Confirmed verbally or in a thread | Recorded with who agreed and when |
The register we build
- We connect to the project mailbox or your Microsoft 365 folders and watch for instructions, change requests and contractor notifications.
- A language model reads each message and attachment and proposes a register entry: description, source, date and likely reference. A surveyor accepts, merges or rejects it.
- Meeting minutes are scanned the same way, so a change discussed on site becomes an item to review rather than a sentence in a PDF.
- Each entry links to its instruction, drawings, quotation and correspondence, stored in one place.
- Contractor references are mapped to yours, so both sides can be read against each other.
- Status moves through the stages your practice uses, with dates, and items stuck at one stage are listed for follow-up.
- The register feeds the cost report and the valuation, so the same figures appear everywhere.
Whether an item is a variation at all, and what it is worth, is a commercial and contractual decision for your surveyor. The register captures and organises. It never decides entitlement.
A register people trust
Surveyors review a short list of proposed entries each morning instead of combing inboxes at month end. The cost report reflects every known change, including the unpriced ones. When the final account comes round, each item already carries its history.
The client's project manager can be given a read-only view of the register, filtered to what they need to see, which cuts down the 'where are we on changes' emails. Early warning of cost movement becomes a routine line in the monthly report rather than a conversation nobody wants to start.
Is your variations log behind?
- The contractor's list of variations contains items you had not logged.
- Site meeting minutes mention changes that never reach the register.
- Finding the instruction for a variation means searching email.
- The cost report and the variations log disagree.
- Only one person really knows the state of variations on a job.