How accurate is the detection?

It over-flags deliberately at first. The cost of a false positive is a dismissed notification; the cost of a miss is unbilled work. The rules tighten as your team dismisses items with reasons.

Does it integrate with our commercial system?

Where your job or commercial system has an API, approved variations post straight into it. Where it does not, the QS gets a ready-to-paste draft and the record stays in the job file.

CONSTRUCTION · SYSTEM

AI variation and day-works capture for contractors

IN SHORT

The system watches the channels where extra work actually gets agreed — site messages, emails, day sheets — flags anything that reads like a variation, drafts a formal instruction from your template and sends it to the QS for approval.

The leak

Extra work is agreed verbally on site, done that week and never recorded. By the time the commercial team hears about it the client's memory of the conversation differs. For a mid-sized contractor this is routinely the single biggest recoverable margin line.

How the workflow runs

Language patterns typical of instruction — 'while you're there', 'client asked us to', 'extra load of', 'can you also' — trigger a flag with the source message attached. A draft variation is prepared with date, site, gang, likely cost code and estimated value; the QS edits and issues.

Controls

Nothing is issued to a client automatically. The workflow ends in a human approval step, and every flagged item that is dismissed is logged with a reason so the detection rules improve.

What you get

Detection across site messages, email and day sheets
Draft instruction produced from your own template
QS approval required before anything leaves the business
Weekly report of flagged, issued and dismissed variations

Questions we get asked

How accurate is the detection?: It over-flags deliberately at first. The cost of a false positive is a dismissed notification; the cost of a miss is unbilled work. The rules tighten as your team dismisses items with reasons.
Does it integrate with our commercial system?: Where your job or commercial system has an API, approved variations post straight into it. Where it does not, the QS gets a ready-to-paste draft and the record stays in the job file.

Keep reading

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
Our Kerbco permit chain 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
We run streetworks and plant operations ourselves. Every platform started as a system we needed in our own business.

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