Skip to content

Should variations be raised from site or from the office?

Both, at different moments: the site spots the change and flags it the day it happens, and the office confirms it in the contract's form and prices it, and the handover between them is where change gets lost.

Updated: 22 August 2026

The answer

The question is really about a handover, and change gets lost exactly where the handover is missing. The site is where a variation is first visible: the extra dig, the revised detail, the instruction given on the scaffold, the condition nobody expected once the wall came down. If the people on site are not trained and expected to flag those the day they happen, the change is invisible until it is too late to prove. So the site owns spotting and flagging, promptly, in whatever quick form suits, a photo, a note, a message to the office, the moment something departs from the drawings or the priced scope. The office owns what happens next: confirming the instruction in the form the contract requires, entering it on the register, pricing it against the contract's rules, and carrying it into the application. Neither half works alone. A site that flags change with no office discipline behind it generates notes that never become confirmed, registered, priced variations. An office that runs an immaculate process but hears about change late is administering a version of the job weeks behind reality. The fix is a simple, known route from site to office: everyone knows what a change looks like and who to tell, and a standing office routine turns each flag into a confirmed, registered, priced line. Get that handover right and change is captured while it is cheap; leave it to chance and it surfaces, expensively, at the final account.

Example

Take a small main contractor whose site teams are excellent at the work and silent about change: extras get done to keep the employer happy, and the office only learns of them when someone mentions it in passing, often weeks later. Predictably, the final accounts are a running battle, because half the change was never confirmed, priced or claimed at the time. The remedy is a route, not a new system. The site teams are told exactly what counts as change and given one way to flag it, a short standard message to the commercial inbox the day it happens, with a photo. The office commits to turning every flag around inside the week: a confirmation in the contract's form, a register entry, a price against the contract rates, a line in the next application. Within two jobs the change is captured as it arises, the site teams stop carrying the risk of remembering, and the final accounts shrink to a check of an account both sides watched being built.