PROPERTY & FM · SYSTEM
IN SHORT
The risk is not the missed renewal you can see — it is the remedial action buried inside a certificate nobody opened, on a row already ticked as compliant. Reading every returned certificate and raising its remedials as jobs closes the gap a spreadsheet cannot.
What actually goes wrong
A spreadsheet tracks whether a document arrived. It cannot tell you whether the document says what you needed it to say. A gas safety record comes back with an unsafe appliance noted, a fire risk assessment comes back with fourteen remedial actions, an EICR comes back unsatisfactory — and the row gets ticked, because the row only ever meant 'received'. Six months later an incident or an audit finds the remedials nobody raised.
What it costs
This is the one place in property management where the downside is not commercial. Beyond that, it is the single most exposed dependency in most portfolios: one competent person, one file, no process behind it. When they leave, the knowledge of what is actually due leaves too.
How the fix works
Every obligation is held against the asset and the building with its frequency and due date. Contractors are instructed and chased ahead of the date rather than after it. Returned certificates are read and checked for the fields that matter — date, engineer, registration, outcome, remedial actions — and remedials found inside a document are raised as jobs in their own right. Anything unclear is flagged to a person rather than recorded as compliant.
What stays with your people
Every judgement about competence, adequacy and risk. The system never decides whether an assessment is acceptable or a remedial is urgent. It guarantees that nothing is missed, unread, or ticked off on the strength of a document nobody opened.
What you get
- Obligations held per asset and per building with due dates
- Certificates read and checked, not just logged as received
- Remedial actions inside certificates raised as jobs automatically
- Chasing ahead of expiry, escalation after it
- An evidenced audit trail for any date in the period
Questions we get asked
- Can it read scanned and photographed certificates?
- Yes, with a confidence check. Anything unclear goes to a person rather than being recorded as compliant — a false positive here is far more expensive than a few minutes of review.
- Does it replace our compliance software?
- Not if you have some. It connects to it and adds the parts most systems leave to humans: chasing, reading what comes back, and raising the remedials found inside it.
- Will it work across residential and commercial in one portfolio?
- That is the normal case. Obligations are configured per asset type and per building, so different schedules sit under one portfolio view.
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.
