Designs evolve after award — items added, specs modified, methods changed. Every adjustment has a cost that needs capturing, justifying, and submitting. We prepare variations the way they get approved.
Project designs evolve — your cost estimates should too. When a project is awarded, you expect to work with a fixed scope and budget. In reality, designers often continue refining the job after the contract is signed. New items get added. Existing ones get removed. Specifications get modified. Methods change. Every one of these adjustments has a cost — and every one needs to be properly captured, justified, and submitted. We prepare variations the way they need to be prepared to get approved — with the same first-principles estimating method we apply to original tenders. Whether the change sits in water, sewer, pump station, or stormwater scope, we price it line by line. For common questions about how we work, see our FAQs.
Almost any change to the original tendered scope can become a variation. We price the full range of design and scope changes across water, sewer, stormwater, pump station, and broader civil work:
Whether the variation adds cost or removes it, the same standard of documentation applies. Credit adjustments need the same defensible breakdown as additions.
Variations are rarely abstract. They’re specific changes to specific items in specific drawings. Here are some real examples drawn from years of pricing infrastructure work:
These aren’t just technical adjustments. They’re changes that affect your bottom line. Pricing them properly — and submitting them in a form that gets approved — is what separates a recovered cost from an absorbed one.
Material substitution, method change, scope addition, latent conditions — send the change documents through. We’ll prepare the priced submission ready for approval.
Design modifications lead to cost changes, but clients won’t approve claims without proper justification. The same change submitted two different ways can get two different outcomes — approved without dispute in one case, rejected or stuck in negotiation in the other.
Variations get rejected, delayed, or disputed for three main reasons:
Failing to track and submit variations properly means absorbing costs that should have been recovered. On a typical multi-month project, unrecovered variations can erode the margin entirely — one more reason why specialist estimating costs less than building this capability in-house. Getting variations right isn’t optional — it’s where the difference between a profitable job and a break-even one often lives.
A well-prepared variation answers every reasonable question the approver might have before they ask it. Done properly, it gets approved on first review. Done poorly, it bounces between parties for weeks.
Our variation submissions include:
The goal is always the same: a submission that gives the approver everything they need to say yes, with no missing information that triggers a request for clarification.
Depending on the contract structure, a variation may need approval from one or more parties:
We tailor the submission to the audience. A variation going to a head contractor needs different framing than one going directly to a client engineering manager — though the underlying cost breakdown is the same. We prepare submissions that match how the approver actually reviews them.
Material substitution, method change, scope addition, or latent conditions — send the change documents through. We acknowledge within two hours during AEST business and prepare the priced submission ready for approval.