EVIDENCE
Every output has a source. Every change has a trail. Every approval has a timestamp. If a client disputes a variation, the evidence is already there.
THE THREE GUARANTEES
A scope item links to the drawing region (and revision) that produced it. A variation links to the client note (with timestamp) that triggered it. A buying suggestion links to the supplier invoice (with date and reference) that informed the price.
Scope item 018 · rear steel bearing pad
Drawing S-104 · Rev C · viewport 2Open questions surface inline. Confidence indicators surface inline. Assumptions surface inline. No buried "trust us." Your estimator (or QS, or site manager) sees what's confident, what isn't, and approves accordingly.
Confirm whether steel is included in Rev C structural note.
Edits, approvals, rejections, reruns, and version diffs are timestamped, attributed, and traceable. If a client disputes a variation in month nine, the decision log shows what changed, when, who signed off, and what evidence supported it.
THE DISPUTE
"We priced it off Rev B. Rev C had different foundations. We didn't catch it. Cost about £14k."
Most disputes start in WhatsApp threads and finish with one side feeling cheated. The pattern is always the same: a decision happened that nobody recorded; a change happened that nobody flagged; a revision happened that nobody reviewed.
The evidence layer doesn't prevent disputes. It changes the conversation. When the client says "that wasn't in the quote," you can show them the drawing, the revision, the voice note, the moment your team approved it, and the moment they approved it. Not as a "gotcha" — as a way of getting back to working together.
This is the audit trail you'd want even if no AI was involved.
HONEST POSITIONING
We don't claim 100% accuracy. Every output has a confidence indicator.
We don't claim to replace estimators, QSs, or site managers. They approve before anything ships.
We don't claim to be the final record. Your contract, your sign-offs, your professional indemnity — those remain yours. BuildGuider is the evidence that supports them.
DEFENSIBILITY
We can't make that claim in the abstract — every dispute is different and a court or adjudicator decides what's admissible. What we can say: the evidence layer captures what every contractual record should — timestamps, attributions, source references, and approvals. We've designed it to be the audit trail you'd want even if no AI was involved.
In the UK, on secured infrastructure. We can share architecture details on request during pilot conversations.
Yes. All your project data — drawings, voice notes, invoices, scopes, variations, decision logs — is exportable. We don't hold your records hostage.
Project-level access controls. Your team sees your projects. Your clients (via the homeowner layer) see only what you choose to share with them.
Every output is reviewed by a human before it ships to a quote, a programme, a purchase, or a contract. The mechanism is review-first. If a wrong output makes it through, that's on us to improve — and on the audit trail to show what happened.
START SMALL
Send us a real drawing pack from a real project. We'll show you what BuildGuider reads, what it flags, and what it produces — before any commercial conversation. Thirty minutes.
Start the pilot →