CONSTRUCTION · SYSTEM
IN SHORT
Paperwork is late because it is captured twice: once on site in a phone, once in the office in a spreadsheet. Capture it once, read it automatically, file it against the job and cost code, and chase what is missing before the valuation, not after.
What actually goes wrong
Site teams do record things — in WhatsApp groups, camera rolls, paper day sheets and text messages to the contracts manager. The failure is the second step. Someone in the office has to find it all, work out which job it belongs to, retype it and file it. That job is nobody's favourite, so it happens on Friday, or the week of the valuation, or never.
What it costs
Unrecorded hours, plant left on hire, delivery notes that cannot be matched to invoices, and — the expensive one — work you did that you cannot evidence when the QS queries it. Contractors routinely write off day works they genuinely carried out because the paperwork does not exist in a form anyone will accept.
How the fix works
Site staff keep using their phone. Photos, notes, delivery notes and signed sheets go to one place, and the system reads them: what job, what date, what cost code, what quantity, whose signature. Extractions it is unsure about are flagged for a human rather than guessed. Anything expected but missing — a day sheet for a shift that was booked, a signed ticket for a delivery — is chased automatically.
What stays with your people
Approval of anything that hits a valuation or a subcontractor payment. Safety documentation is filed and tracked, never judged: the system tells you a RAMS is missing or expiring, it does not decide whether one is adequate.
What you get
- One capture point for photos, notes, tickets and sheets
- Automatic reading of job, date, cost code and quantities
- Uncertain extractions escalated to a person, not guessed
- Missing paperwork chased before the valuation, not after
- A complete, searchable job file when a claim or query lands
Questions we get asked
- Do site teams need to learn new software?
- Deliberately as little as possible. Most builds keep the existing habit — a phone camera and a group — and do the work behind it. Adoption dies when you ask a site team to fill in forms.
- Can it read handwritten day sheets?
- Usually yes, with a confidence check. Anything the model is unsure of goes to a person to confirm rather than being written into the job record.
- Where does the data end up?
- In your systems — the job record, the accounting package, the document store you already use — inside your own tenancy with an audit trail of every extraction.
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.
