LANDSCAPING · SYSTEM

AI round and crew scheduling for grounds maintenance

IN SHORT

The round rebuilds itself when weather or sickness hits: a suggested re-sequence, one approval, and every affected customer told before they notice.

The weekly rebuild

Grounds maintenance schedules are fragile. A wet Tuesday moves six visits, which moves the rest of the week, which nobody tells the customers about. The office then spends Friday fielding calls.

How the workflow runs

The system holds each contract's visit frequency and window. It watches weather and crew availability, proposes a re-sequenced week optimised for travel and contract compliance, and — once approved — messages affected customers with the new date.

Contract compliance

Where a contract specifies cuts per season or a maximum interval, the schedule is checked against that obligation and shortfalls are flagged early enough to fix.

What you get

  • Weather-aware re-sequencing with one-click approval
  • Automatic customer notification of moved visits
  • Travel-optimised day lists per crew
  • Contract-obligation tracking across the season

Questions we get asked

Do crews need a new app?
No. Day lists can go out by message or into the job system you already use.
Who decides the final schedule?
Your scheduler. The system proposes; a person approves before any customer hears about a change.

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.