Forth SystemsForth Systems

CONSTRUCTION · SYSTEM

AI site paperwork and photo capture for construction

IN SHORT

Site teams keep sending what they already send — photos, day sheets, delivery notes over WhatsApp or email. The system reads them, works out the job and cost code, files them against the right record and chases whatever is missing at the end of each day.

What it replaces

Paperwork typed up twice: once on site, again in the office. Photos scattered across personal phones. Delivery notes that surface three weeks later when the supplier invoice is queried. Nobody wants to run another app on site, so the answer is to accept the channels the site already uses.

How the workflow runs

A shared number or address receives whatever site sends. The system reads the image or document, identifies job, date, gang and cost code from content and context, files it in your document store and posts the entry to the job record. Anything ambiguous goes to a short review queue rather than being guessed.

Why it matters commercially

Complete daily records are what win variation and delay arguments months later. Automated capture means the record exists whether or not anyone had time to build it.

What you get

  • No new app for site teams — use the channels they already use
  • Photos and documents coded to job and cost code automatically
  • Daily completeness check with chase messages for missing sheets
  • Searchable evidence trail for variations, delays and disputes

Questions we get asked

Can site teams keep using WhatsApp?
Yes. That is usually the point. We ingest from a business number or shared inbox so nothing changes for the people on site.
What if a photo has no context?
It is queued for a quick human tag rather than filed incorrectly. The system learns from repeated corrections, and the volume of the queue falls quickly.

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.