Variation Claim Builder | Real Minds AI

Where it works well

It assembles the scattered trail behind a variation that nobody has time to reconstruct.

Done by hand, reconstructing the chronology weeks later under time pressure is the job nobody wants — and the reason variations get written off or claimed thin.
Best for the contract administrator or project manager on a mid-sized builder or head contractor running several active jobs at once.
Across a portfolio of jobs the recaptured hours go back into checking the claim is contractually sound, not hunting through the inbox to build it.

On most jobs the entitlement genuinely exists — the client did ask for power to the shed, the trench was dug, the sparkie invoiced — but the proof is scattered across an email, a diary note, a phone photo, an SMS and an invoice, each in a different system and none of them in order.

Where it works badly

It builds a clean-looking claim even when the evidence underneath it is thin — and tidy layout makes a weak claim feel strong.

Weak where the dispute is contractual, not evidentiary — whether the work was genuinely outside scope, or whether a notice deadline has already passed, are judgements it does not make.
Feed it a superseded contract scope or a signed variation order it has not seen and it drafts a stale claim with full confidence.
If your jobs are small, your variations rare, or your paperwork already disciplined, the setup will not pay back.

The honest test

Would this chronology survive the other side's contract administrator reading it line by line? If the answer rests on a "yeah go ahead 👍", the tool has surfaced your real problem, not solved it.

If a variation was instructed verbally on site and nobody noted it, no tool can manufacture the instruction. Feed it a single ambiguous "yeah go ahead 👍" text and it will lay out a confident claim resting on nothing firmer than that.

What it doesn't do — and shouldn't

It surfaces and drafts. A person checks it against the contract and approves. That boundary is deliberate.

WHAT IT DOES

Orders the evidence into a dated chronology and links each entry to its source document

Drafts the claim reference, scope description and labour/materials/subcontractor/margin build-up

Rates how strong the instruction chain looks, so a thin chain prompts closer review

WHAT IT WON’T

Decide whether the work was genuinely outside the original scope

Confirm whether a notice deadline or time bar under your contract has passed

Issue the claim — nothing leaves the building on its say-so

A variation claim is a commercial and sometimes legal position taken against a client or principal. Under a Security of Payment regime — the Building and Construction Industry Security of Payment Act in NSW, equivalent SOP Acts across the eastern states, the Building and Construction Industry (Security of Payment) Act 2021 in WA, and the Construction Contracts (Security of Payments) Act in the NT — a claim has to properly identify the work and stand up to scrutiny, and getting it wrong can forfeit money or invite a dispute. The contract administrator whose name is on the claim stays on the decision.

What your data has to look like

Three things tied to one variation — the original scope, the instruction chain, and real cost figures.

Typical readiness

across orgs we see, before the first job

The original contract scope for that variation

Usual weak point

The instruction chain, tied to the variation

Needs shaping

Real cost figures, not later estimates

Usual weak point

A way to know which documents belong to which variation

Needs shaping

The margin rate your contract actually allows

Usual weak point

The real first job

Most builders have all of this somewhere, and almost none have it linked — emails in one inbox, diaries in an app, photos on a phone, invoices in the accounts package. Agreeing how a variation gets tagged at the moment it happens, so the trail assembles itself rather than being reconstructed, is usually the real first job. It is a change to how information is captured on site — bigger and more valuable than the AI layer that sits on top of it.

Right fit if…

You run several active jobs and lose real money to unclaimed or under-evidenced variations

You have the evidence — emails, diaries, photos, invoices — but not the time to assemble it

A contract administrator or PM is doing the assembly by hand, weeks after the fact

Your labour, materials and subcontractor figures are real recorded numbers

Walk away if…

Your variations rest on verbal instructions nobody wrote down

Your jobs are small, your variations rare, or your paperwork already disciplined

The dispute is contractual — scope or time bars — not a question of assembling evidence

You want a tool that decides whether a claim is contractually sound

Open questions

The worried-buyer questions, answered straight

It can draft a claim that looks tidy but isn’t owed, which is why the draft is a starting point, not a verdict. Every line is linked back to the source document it came from — the contract scope, the instruction, the invoice — so the contract administrator can see why it treated the work as a variation and check that against the actual contract clause. The confidence rating is a prompt to look harder where the instruction chain is thin, not a green light. The administrator decides whether the claim is sound before it leaves the building.

That is exactly the situation it is built for, and also where you must read carefully. It will assemble a chronology from an email, a diary note, a photo and an SMS, but a verbal instruction noted in a diary is weaker evidence than a signed variation order, and the tool can’t make it stronger. It surfaces what you have and where the gaps are; it does not invent a written instruction that was never given. If a variation rests only on a “yeah go ahead” text, that is a fact about your claim, not a flaw in the draft.

No. It does the assembly — finding the documents, putting them in order, drafting the build-up — which is the slow part. It does not decide whether the claim is contractually sound, whether a notice deadline has been missed, or how hard to push it commercially. Those judgements stay with your contract administrator or quantity surveyor, who now spends their time on the call rather than hunting through the inbox.

It only knows what it has been given for that variation, so a superseded scope or a later signed variation order it hasn’t seen will produce a stale draft. The build-up reflects the documents at the moment it runs, not the live state of the job. Before approving, the reviewer confirms they are working from the current contract scope and the latest instructions — the tool can’t tell that the file in front of it has been overtaken.

That is a scoping decision we make with you before anything is built, not an afterthought. The documents and pricing are commercially sensitive, so the data path — what is processed, where it sits, what is retained — is agreed up front and kept inside arrangements you control. We do not need your data to leave that boundary for the pattern to work, and we would rather under-collect than over-collect.

Treat it as an assistant, not a compliance check. Whether a claim is time-barred depends on your specific contract — an unamended AS 4000 generally does not bar a claim for a missed notice (it leaves the other party to claim damages instead), while many head contracts and bespoke contracts add a strict time bar, and missing the notice window can defeat an otherwise valid claim. The tool can flag dates and surface the instruction chain, but confirming the notice clause and the deadline is a judgement for your contract administrator. We can build the relevant clause rules in for your contracts, but the person still signs off.

What it takes to build

3–5 weeks · 4 phases

Reused from template~65%

Bespoke to this skin~35%

stack · Claude · document intake · timeline builder · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Losing money to variations you never claimed?

The honest place to start is a bite-sized first piece — usually fixing how a variation gets tagged the moment it happens. Tell us where it hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work