CONSTRUCTION · SYSTEM
IN SHORT
Cash is late because the paperwork is late. Assemble each application on schedule from the job record, chase invoices on a fixed ladder, and track every retention release to a date — none of which requires a person to remember anything.
What actually goes wrong
Applications depend on site records that are not ready, so they slip past the assessment date and lose a whole month. Invoices sit unpaid because chasing is somebody's fourth priority. Retention is released on dates nobody has diarised, so it is claimed late or forgotten entirely.
What it costs
A missed application date on a monthly cycle is thirty days of working capital on that contract. Retention is worse: it is pure margin, already earned, sitting in someone else's account. Most contractors we audit are carrying at least one release they had not diarised.
How the fix works
The system knows each contract's assessment dates and works backwards: what site records are needed, what is missing, who has to supply it, chased in advance. On the date, it assembles the application from the job record with the supporting evidence attached, for your QS to review and send. Unpaid invoices follow a chase ladder — polite, firmer, escalated — and every retention release is tracked to a diarised date with the claim drafted ahead of time.
What stays with your people
Every application and every escalation to a client is reviewed by a person before it goes. Cash chasing is a relationship, and the system is built to protect that, not automate over it.
What you get
- Assessment dates tracked per contract with missing records chased early
- Applications assembled on schedule with evidence attached
- A consistent invoice chase ladder that never gets forgotten
- Retention releases diarised and claimed on the date
- One live view of what is applied for, certified, paid and outstanding
Questions we get asked
- Does it integrate with our accounting system?
- In most cases yes — Xero, Sage, QuickBooks and the common construction packages. We confirm at audit stage and tell you honestly if a legacy system makes it uneconomic.
- Will clients receive automated chasing emails?
- Only within the rules you set, and anything beyond a first polite reminder is reviewed by a person. You choose which clients are handled softly.
- What is the fastest thing to fix here?
- Usually retention tracking. It is small to build, and the first release it recovers often pays for the workflow outright.
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.
