LOGISTICS · SYSTEM

Your planners spend the day on the phone, not planning

IN SHORT

Most calls into a transport office are the same four questions: can you take this, where is it, when will it land, what did it cost. Answer those automatically from the live job record and give the planner back the hours that planning actually needs.

What actually goes wrong

Every booking, amendment and 'where's my load' arrives by phone or email into the same small team who are also solving today's breakdowns. Planning becomes reactive, the good bookings are taken on gut feel, and the office never gets ahead of the day.

What it costs

Two things: planner burnout, and margin. A plan built between interruptions is a worse plan — more empty legs, more overtime, more subcontracted loads that should have been run in-house.

How the fix works

Inbound bookings by email are read, checked against capacity and priced from your rate structure, then presented to the planner as a decision rather than a data-entry task. Status and ETA questions are answered automatically from live job and tracking data. Amendments are logged against the job with the customer's own wording kept as evidence.

What stays with your people

Accepting work, committing vehicles, and any conversation with a customer that carries a commercial consequence. Rates outside the agreed structure always route to a person.

What you get

  • Email bookings read, checked against capacity and priced automatically
  • ETA and status questions answered from live data, not by a planner
  • Amendments logged against the job with the original wording kept
  • Exceptions and non-standard rates escalated to a human
  • A measurable drop in inbound calls the office has to handle

Questions we get asked

Will customers know they are dealing with a system?
You choose the tone and the disclosure. Most operators keep it plainly branded as an automated update, with a person always one reply away.
What if a booking is unusual?
It routes straight to a planner with everything already extracted. The system is deliberately conservative about what it handles alone.
Do we need a TMS for this?
No, though it is easier with one. Where there is no TMS we work from the job records and spreadsheets that exist and connect what we can.

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.