PROPERTY & FM · SYSTEM
IN SHORT
SLAs slip in the gap between a repair being reported and a job being raised, not on site. Reading and raising every report the hour it arrives, then chasing acknowledgement automatically, recovers a day and a half per job without touching your supply chain.
What actually goes wrong
The SLA clock starts when the resident reports the fault. The job is raised when someone has read the email, worked out which property and unit it belongs to, judged the urgency and typed it into the system. On a busy portfolio that gap is routinely a day, sometimes three over a weekend. By the time the contractor is instructed, a third of the window is gone — and then the contractor, quite reasonably, gets blamed for the breach.
What it costs
It costs the contract. SLA performance is the number a client sees at every review, and it is the number that decides renewals in competitive tenders. It also costs complaint handling time, because the residents who chase are the ones whose jobs went quiet early, and every chase is another message into the same overloaded inbox.
How the fix works
Every report is read on arrival, whatever the channel, and matched to the property, unit and asset. It is classified by trade and urgency, and raised as a job with the correct target date immediately. Safety-critical categories are escalated to a person by hard rule rather than by classifier confidence. Once dispatched, acknowledgement and attendance are chased automatically, and anything approaching its deadline without progress is escalated with the full history attached.
What stays with your people
The judgement calls and the difficult conversations. Whether a repair is recoverable, whether a contractor is right for a sensitive resident, whether a fault points at something structural. The automation removes the delay and the retyping, not the management.
What you get
- Every report read and raised the hour it arrives, on any channel
- Matched to property, unit and asset from your own records
- Emergencies escalated by hard rule, never by model confidence
- Acknowledgement and attendance chased without a person doing it
- Escalation before the SLA breaks, with the history attached
Questions we get asked
- Will this make our contractors faster?
- It will make them start sooner, which is usually the same thing in the client's report. It also gives you real acceptance and attendance times per contractor, so the conversations you do need to have with your supply chain are based on data rather than impression.
- How quickly can it be running?
- Triage and chasing are usually the fastest workflows to put live — four to six weeks from the start of a build, because the inputs are just email and the process already exists in people's heads.
- What about out-of-hours reports?
- They are the strongest case for it. Out of hours is exactly when a report sits unread, so hard-rule routing to your emergency path plus automatic acknowledgement to the resident changes both the response time and the complaint volume.
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.
