CONSTRUCTION · SYSTEM

Variations you did but never got paid for

IN SHORT

Variations are lost in the gap between the conversation on site and the formal instruction. Flag anything that looks like extra work the moment it is mentioned, draft the instruction, and put it in front of the QS while the evidence is still fresh.

What actually goes wrong

A client asks for something on site. The site manager agrees because refusing is not realistic. It is discussed, done, and mentioned in passing on a call. Nobody raises a formal instruction that week, and by the time the valuation is prepared it is one line of disputed recollection against a main contractor with better records.

What it costs

This is the loss operators most often under-estimate. A handful of unrecorded variations a month on a mid-size contract is a five-figure annual write-off, and it comes straight off margin — the cost was already incurred.

How the fix works

The system watches the channels where extra work is actually discussed — email, site notes, day sheets, captured messages — for the language of a variation: additional, extra, change, client asked, whilst we were there. Anything that matches is flagged with the source message, a draft instruction, an estimated value from your rates and the supporting photos, then sent to the QS for approval within the day.

What stays with your people

Everything contractual. No instruction is ever issued, no value ever agreed, and no client ever contacted without a person approving it. The system's job is to make sure the QS sees it in time.

What you get

  • Automatic detection of variation language across site channels
  • Draft instruction assembled with source evidence attached
  • Indicative value priced from your own rate library
  • QS approval required before anything leaves the business
  • A running register of variations raised, approved and paid

Questions we get asked

Will it flag things that are not variations?
Early on, yes — and that is the right way round. A false flag costs the QS ten seconds; a missed variation costs the job. Precision improves quickly as it learns from your approvals.
Does this need our team to change how they communicate?
No. It reads the channels they already use. Asking site staff to log variations in a portal is exactly the approach that has already failed in most businesses.
How is this evidenced if a claim goes to dispute?
Every flag keeps the original message, timestamp, author and any attached photos, with an immutable audit trail — which is usually stronger evidence than what exists today.

TRUST & CREDENTIALS

How we work, and what stands behind it

This page is maintained by Forth Systems. Everything listed below describes our own team, hosting choices and the technologies we build on — it is a statement of practice, not an independent certification or an endorsement by the vendors named.

UK team & data residency

Who builds it, and where your data sits while they do.

  • UK-based engineers

    Edinburgh-headquartered. Every system is designed, built and supported by our own UK-based engineering team — no offshore delivery pool.

  • UK / EU hosting by default

    Applications and databases are provisioned in UK or EU regions unless you require otherwise, with encryption in transit and at rest.

  • Human-in-the-loop by design

    Every AI system we ship keeps a manual override. Nothing irreversible happens without an operator able to review, edit or stop it.

  • Audit trails as standard

    Automated actions are written as first-class records — who or what did it, when, against which input — so operations stay evidence-ready.

Systems we build on

The platforms our systems run on. These are the technologies we deploy and support — not sponsorships or reseller badges.

  • OpenAI, Anthropic & Google models

    Model-agnostic delivery. We route each workload to the model that fits it on cost, latency and accuracy, and can switch without a rebuild.

  • Supabase & Postgres

    Row-level-security Postgres as the operational spine under every platform we run.

  • Stripe payments

    Payment capture, checkout and reconciliation wired directly into job and permit workflows.

  • Xero, Sage & HubSpot integrations

    Production integrations into the finance and CRM systems UK operators already run, so automation lands where the business keeps its records.

Streetworks & industry credentials

Operational domains we build in daily, with the sector systems we integrate against.

  • DfT Street Manager integration

    The permit chain we built for Kerbco creates and tracks streetworks permit applications against DfT Street Manager and local highway authority processes.

  • NRSWA-aligned workflows

    Permit, reinstatement and traffic-management workflows built to the New Roads and Street Works Act process contractors are inspected against.

  • Traffic management planning

    Roadplan produces signing and guarding layouts for council submission and for the crew installing them on site.

  • Operator-built, not consultancy-built

    Our platforms are built around real operating workflows — including the permit chain we built for our client Kerbco, a Scottish drop kerb contractor.

Insurance certificates, registration numbers and security documentation are available on request — ask the team.