LOGISTICS · SYSTEM

Tacho, defect and licence admin is eating the week

IN SHORT

Compliance is not hard, it is relentless: the same checks, the same chasing, every week, with an O-licence riding on it. Track every expiry and obligation automatically, chase the gaps early, and keep an audit trail that stands up.

What actually goes wrong

Downloads are missed, defect sheets come back incomplete, licence checks slip past their date, and inspection intervals are tracked in a spreadsheet one person maintains. Nothing fails loudly until an audit or an incident makes it fail all at once.

What it costs

Beyond the admin hours: the risk. Operators know the exposure — the paperwork gap that only surfaces when a DVSA visit or an incident investigation is already under way.

How the fix works

Every recurring obligation is held with its due date: downloads, defect returns, licence checks, inspections, insurance, driver qualifications. The system chases the responsible person ahead of the date, escalates when a date passes, reads returned documents to confirm they are complete, and keeps a timestamped record of what was chased, supplied and accepted.

What stays with your people

Every compliance judgement. The transport manager decides whether a defect grounds a vehicle or a driver is fit to drive; the system makes sure they have the information in time and the evidence afterwards.

What you get

  • Every recurring obligation tracked to a date, per vehicle and driver
  • Chasing before the deadline, escalation after it
  • Returned documents read and checked for completeness
  • A timestamped audit trail of every chase and response
  • One dashboard showing what is compliant, due and overdue today

Questions we get asked

Does the AI decide whether we are compliant?
No. It tracks, chases and evidences. Compliance decisions sit with your transport manager, which is where the legal duty sits.
Can it read defect sheets and inspection reports?
Yes, including photographed paper. Anything unclear is flagged for a person rather than recorded as complete.
How does this help in an audit?
You can show not just the records but the process: what was due, when it was chased, who responded and what was accepted, for any date in the period.

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.