PROPERTY & FM · SYSTEM

AI contractor coordination for property and FM teams

IN SHORT

Dispatch to the right contractor, chase acknowledgement and attendance without a person doing it, and escalate before the SLA breaks — with the whole conversation recorded against the job.

The problem

Issuing the job is quick. What costs the day is everything after: did they get it, did they accept it, have they booked it with the resident, did they attend, did they complete it, where is the paperwork. Each of those is an email or a phone call, multiplied by every open job, and it is nobody's actual role — so it gets done for the loud jobs and not the quiet ones.

How it works

Jobs are issued to the contractor matched by trade, area, current load and, where you hold it, performance history. Acknowledgement is chased on a schedule you set. Attendance and completion updates are requested automatically and, where the contractor replies by email, the reply is read and the job status updated without a person transcribing it. Anything approaching its SLA without progress is escalated to the responsible manager with the history attached.

Where the money is

In the jobs that would otherwise go quiet. Every FM business has a tail of open jobs nobody is actively chasing, and that tail is where complaints, escalations and client reviews come from. Chasing costs nothing to automate and it changes the shape of your open-job report within a month.

What stays with your people

Choosing to override the contractor match, authorising spend above threshold, and every difficult conversation. The system does the repetitive chasing so your managers arrive at the difficult ones informed and on time.

What you get

  • Contractor matched by trade, area, load and performance history
  • Acknowledgement, attendance and completion chased automatically
  • Email replies read and the job status updated without retyping
  • Escalation before the SLA breaks, not after
  • Full timestamped history on every job for client reporting

Questions we get asked

Does it choose contractors without us?
It proposes the match from your own rules and history. Whether it dispatches automatically is your decision per job type — most clients start with automatic dispatch on low-value routine trades and manual approval on everything else.
Our contractors do not use a portal. Does that matter?
No. Email and, where appropriate, SMS work perfectly well as the interface. The automation is on your side of the conversation; the contractor experience does not have to change for it to work.
Can it track SLA performance by contractor?
Yes, and it is usually the first genuinely useful supply chain report a client gets — acceptance time, attendance time, completion time and reopen rate per contractor, built from real job data rather than an annual review.

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.