CONSTRUCTION · SYSTEM
IN SHORT
Applications built on the contract calendar from job data you already hold, invoices chased automatically with escalation, and retention tracked so releases are claimed rather than forgotten.
Why applications go in late
The information needed exists — day sheets, measures, variations, materials — but assembling it competes with everything else in a commercial team's week. Miss the date and payment slips a full cycle.
How the workflow runs
Each contract carries its application dates. Ahead of each one the system assembles the draft from the job record, flags gaps in supporting evidence, and hands the commercial lead a package to review. After issue, the chasing ladder runs: polite reminder, firm reminder, escalation to the named contact, then internal escalation.
Retention
Retention amounts and release dates are tracked per contract, with reminders raised before each release becomes claimable — including the defects-period release most businesses lose track of.
What you get
- Application drafted ahead of every contract date
- Evidence gaps flagged before submission, not after rejection
- Escalating chase ladder with human escalation points
- Retention register with release-date reminders
Questions we get asked
- Will it send emails to clients without us seeing them?
- Only where you choose. The default is that the first reminder is automatic and anything firmer requires a person to approve. You set the line.
- Does it work with Xero or Sage?
- Yes, both integrate. Invoice status and payment data come from the accounting system so the chase stops the moment money lands.
Keep reading
- AI for constructionThe full industry hub
- Case studyHow a Scottish groundworks and civils contractor cut enquiry response times and got applications in on schedule.
- Construction automation in EdinburghLocal coverage and context
- Construction automation in GlasgowLocal coverage and context
- ROI calculatorModel savings and payback
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.
