LOGISTICS · SYSTEM

Too much empty running and too few backloads

IN SHORT

Empty running persists because finding a backload takes phone calls nobody has time for. Match your live plan against available loads and regular customer patterns automatically, and put the viable options in front of the planner before the vehicle rolls.

What actually goes wrong

The planner knows a truck is coming back empty, but filling it means ringing round, checking boards and negotiating — while also handling today's problems. Marginal backloads get skipped because the search costs more than the load is worth.

What it costs

Fuel, driver hours and vehicle wear on miles that earn nothing. Even a modest reduction in empty running moves the margin on a fleet more than most cost-cutting exercises anyone runs.

How the fix works

The system watches the plan for return legs, then searches your own regular customer patterns, standing traffic and connected load sources for anything that fits the vehicle, the timing, the driver's remaining hours and the geography. It presents the planner with a ranked shortlist and an indicative rate, ready to accept or ignore.

What stays with your people

Accepting the load, agreeing the rate and committing the vehicle. Planners overrule the shortlist constantly and should — the system is there to remove the searching, not the deciding.

What you get

  • Return legs identified automatically from the live plan
  • Matching against your own customers before external boards
  • Driver hours and vehicle suitability checked before anything is offered
  • A ranked shortlist with indicative rates, not a raw feed
  • Empty-mile reporting so the improvement is measurable

Questions we get asked

Does this connect to load boards?
Where a board offers an API and your subscription allows it, yes. The bigger early win is usually matching against your own repeating customer traffic, which nobody has time to mine.
Will it break compliance on drivers' hours?
Remaining hours are a hard constraint on every match. Anything that would not be legal or realistic is never shown to the planner.
How do we prove it worked?
Empty miles as a percentage of total miles, before and after, reported weekly. It is one of the cleanest metrics in the business.

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.