LOGISTICS · SYSTEM

AI backload matching to cut empty running

IN SHORT

Empty legs identified from the live plan and matched against regular traffic and available loads, so the planner sees a viable shortlist and a rate instead of a list of phone calls.

The problem

Everyone knows empty running costs money and nobody has an hour to fix it in the middle of a shift. Marginal backloads get skipped because the search is more expensive than the load.

How it works

The system reads the live plan for return legs, then searches your own repeating customer traffic first — the loads you already have relationships for — before connected external sources. Every candidate is filtered by vehicle suitability, remaining drivers' hours, timing and geography, then ranked with an indicative rate for the planner to accept or ignore.

Where the money is

Empty miles are close to pure cost. A few percentage points off the empty-running figure across a fleet moves the annual margin more than most cost programmes, and it is measurable from week one.

What you get

  • Return legs detected automatically from the live plan
  • Your own regular customers searched before external boards
  • Drivers' hours and vehicle type treated as hard constraints
  • Ranked shortlist with an indicative rate, not a raw feed
  • Weekly empty-mile reporting to prove the improvement

Questions we get asked

Do we have to subscribe to load boards?
No. Most of the early gain comes from mining your own repeating traffic. Boards can be connected later where the API and your subscription allow.
Can the planner overrule it?
Always, and they will. It is a shortlist, not an instruction.
How is the rate suggested?
From your own historic rates on similar lanes, plus any agreed customer schedule. It is a starting point for the planner, never a committed price.

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.