PROPERTY & FM · SYSTEM
IN SHORT
Every statutory and planned obligation held against the asset with its due date, chased ahead of expiry, evidenced with the certificate read and checked — and a portfolio view of what is compliant, due and overdue today.
The problem
Compliance across a portfolio is a large number of small, identical, date-driven tasks. It is almost always tracked in a spreadsheet maintained by one competent person, and it works right up until that person is on holiday, or the portfolio grows, or a certificate comes back incomplete and nobody notices because the row got ticked.
How it works
Every obligation is held against the asset and the building with its frequency and due date: gas safety, electrical installation condition, fire risk assessment and remedials, lift inspection, water hygiene, asbestos re-inspection, emergency lighting, PPM schedules. Contractors are instructed and chased ahead of the date. Returned certificates are read, checked for the fields that matter — date, engineer, registration number, outcome, remedial actions — and either accepted or flagged. Remedial actions found inside a certificate are raised as jobs in their own right, which is where most portfolios quietly leak.
Where the money is
Mostly risk, and the hours are real too. The specific value is being able to show a client, an insurer or an inspector not just the certificate but the process behind it — what was due, when it was chased, what came back, what was raised as a result — for any date in the period.
What stays with your people
Every judgement about competence, adequacy and risk. The system does not decide whether a fire risk assessment is acceptable or whether a remedial is urgent. It makes sure 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
- Contractors instructed and chased ahead of expiry
- Certificates read and checked for the fields that matter
- Remedial actions inside certificates raised as jobs automatically
- Portfolio view of compliant, due and overdue, refreshed live
Questions we get asked
- Can it read scanned and photographed certificates?
- Yes, with a confidence check. Anything unclear is flagged to a person rather than recorded as compliant — a false positive here is far more expensive than a few minutes of review.
- Does it sign anything off?
- No. It tracks, chases, reads and evidences. Acceptance stays with the person who carries the duty, and the audit trail records who accepted what and when.
- Will it work across a mixed portfolio?
- That is the normal case. Obligations are configured per asset type and per building, so residential blocks, commercial units and managed sites can each carry different schedules under one 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.
