Keep control of variations before they become a cost surprise

On a small housing development, changes rarely arrive in one tidy place. A revised drawing comes by email. A subcontractor sends a price. A site conversation reveals extra work. Someone updates the budget, but the supporting approval stays in an inbox.

A useful AI workflow brings those pieces into one change register and highlights what needs a decision. The aim is simple: know what has changed, what it could cost, who has approved it and what still needs checking.

Start with one register

You do not need a new project management system to begin. An existing spreadsheet can work, provided everyone uses the same reference for each change and can find its supporting documents.

Give each proposed change a unique number and record:

• The plot, trade, location and reason for the change.
• The original requirement and the proposed replacement or addition.
• Links to the drawing revision, instruction, quotation and relevant correspondence.
• The original allowance, quoted adjustment and latest reviewed forecast.
• The cost status, instruction status and payment status as separate fields.
• The person responsible, next action, decision deadline and possible programme effect.

Keep a record of revisions. A newer quotation should supersede the earlier version visibly, rather than quietly overwrite the evidence.

What AI can do

Feed the workflow a controlled folder or export containing agreed project correspondence, quotations, drawing registers and the current change register. It can identify possible changes, extract key details and suggest a new entry or an update to an existing one.

For example, it could connect a supplier's revised window quotation with an architect's email about a larger opening, then flag that the structural implications and installation date remain unconfirmed. Each extracted item should link to its source and show where information is missing.

The output should be a draft register update and a short decision list, not an automatic instruction to proceed. A project manager, quantity surveyor or other agreed commercial reviewer checks the scope, numbers and status before accepting the update.

Change procedures depend on the arrangements for the project. The RICS guidance on change control and management is a useful reference for setting up the process. Your register should support the applicable procedure, not replace it.

An illustrative example: a revised kitchen package

Imagine a development budget already includes an £8,000 kitchen package for one plot. A revised specification produces a replacement quotation of £9,600, on the same tax and scope basis.

The potential increase is £1,600. It is not another £9,600 on top of the existing £8,000. The draft entry should show the original allowance, replacement total and difference, with the calculation visible.

Before accepting that figure, check whether delivery, fitting, appliance changes and any omitted items are treated consistently. If the supplier sends a later quotation of £9,900, retain the old quotation as superseded and update the potential increase to £1,900. Do not add both quotations to the forecast.

If the revised kitchen has not been authorised, it belongs in the potential-change total. It should not appear as an approved commitment simply because someone requested a price.

Keep the statuses meaningful

A single label such as “approved” is often too vague. A design choice may be agreed while its price is still being negotiated. Work may be instructed before its final valuation is settled. An approved amount may still be unpaid.

Separate those questions so the weekly summary can distinguish:

• Potential changes awaiting a decision or a usable quotation.
• Instructed changes whose commercial value still needs agreement.
• Agreed changes included in the latest cost forecast.
• Invoices received, checked and paid against those changes.

Keep uncertain amounts visible and explain whether the forecast includes them. Never silently treat “not yet priced” as zero. The RICS guidance on valuing change explains that definitions and valuation provisions vary between contract forms, including JCT, NEC and FIDIC. AI should flag questions for the appropriate reviewer, not decide contractual entitlement.

Build a short weekly review

Ask for one page showing new changes, overdue decisions, missing quotations, possible duplicate entries and the movement in forecast cost since the previous review. Reconcile it with the budget and invoice records, checking that changes have not been counted in more than one place.

For a straightforward register using agreed exports and templates, an initial setup might take five to ten working days. That is an indicative Next Step Ventures estimate, dependent on document quality, access and review availability; integrations and complex project structures take longer.

A sensible first step is to test the workflow on one live project and a small set of known changes. Check whether it finds the right evidence and produces a decision list the team can actually use.