What a facilities compliance platform should include out of the box
It's worth being clear-eyed about what a facilities compliance platform is actually for before comparing feature lists: it exists to make sure required work happens on schedule and can be evidenced afterward. Judged against that, a surprising amount of what gets positioned as a premium add-on in this market is, functionally, something a facilities team with any statutory obligations at all genuinely needs from day one.
Asset and criticality tracking, not just a task list
A platform needs a proper asset register at its core — location, criticality, service history — not a generic task list that happens to reference equipment by name. Without that foundation, everything built on top of it (scheduling, reporting, statutory tracking) is working from an incomplete picture.
Statutory inspection routines, distinct from general PPM
Statutory inspection categories — water hygiene, electrical testing, lifting equipment, pressure systems — have different evidence and interval requirements to general planned maintenance, and a platform should support that distinction natively rather than forcing every category into the same generic recurring-task structure. A tool that treats a LOLER examination the same way it treats a lightbulb check is missing something structural, not just a nice-to-have feature.
- An asset register with location, criticality and full service history, not a bare equipment list
- Native support for statutory inspection categories with their own intervals and evidence requirements
- Reactive work orders tracked from report through to a genuinely verified sign-off
- A contractor register that surfaces expiring insurance and accreditation, not just stores certificates
- Estate-wide reporting that works across multiple buildings without manual combination of separate records
Evidence, built into the workflow rather than bolted on
The clearest sign of a platform designed with compliance genuinely in mind is whether evidence is a natural byproduct of using it day to day, rather than a separate reporting module someone has to remember to run. Good evidence practice links inspections to assets and findings to closed jobs automatically — if a platform can't do that without significant manual linking, it's providing storage, not genuine compliance support.
Where it's fair for a platform to draw the line
It's reasonable for a facilities platform to not cover everything adjacent to the job — finance and purchase order processing, building management system integration and live plant telemetry, or space planning and CAD are genuinely different problems, usually served better by dedicated tools built specifically for them. A platform trying to be all of those things at once often ends up doing the core facilities job less well than one that stays focused on it.
Where it is fair to expect a platform to stop
No platform makes an estate compliant, and any that implies otherwise is worth treating warily. What software can reasonably do is hold the asset and criticality picture, generate and track statutory routines distinctly from general maintenance, keep the evidence chain intact from finding to sign-off, and make an overdue item visible to a named person. What it cannot do is determine what your obligations are, decide who is competent, or make a judgement call about a finding.
That boundary matters when evaluating, because the useful question is not whether a platform claims compliance but whether it supports the specific obligations this estate actually carries — which requires knowing what those are first.
Common mistakes
- Expecting the platform to determine which obligations apply to the estate
- Treating statutory routines as ordinary tasks in the same schedule
- No link from an inspection finding through to the remedial job and its evidence
- Evidence that cannot be produced for a single asset on request
- Buying on a compliance claim without mapping it to your actual obligations
- Assuming a certificate store is the same as compliance management
- A compliance platform needs a proper asset register with criticality and service history at its core, not a generic task list.
- Statutory inspection categories need native support with their own intervals and evidence standards, not a one-size-fits-all task type.
- Evidence should be a natural byproduct of daily use, not a separate report someone has to remember to generate.
- A contractor register should actively surface expiring insurance and accreditation, not just store certificates.
- It's reasonable for a facilities platform to leave finance, BMS integration and space planning to dedicated tools.
About this article
The FacilityOptix team
Written by people who work daily with facilities teams on planned maintenance, statutory inspection and the records that hold up under an inspection.
- Published
- 15 June 2026
- Last revised
- 27 September 2026
How this is researched, dated and corrected is set out in our editorial standards. If something here is wrong or out of date, email hello@facilityoptix.co.uk — corrections to a regulated detail are made as soon as we can confirm them, and the revision date above moves when they are.