What we will and will not claim.
Plenty of software in this sector implies it makes you compliant. It cannot, and neither can we. What the platform does is keep the evidence of what a competent person found in a state that holds up when somebody asks — which is a smaller claim, and a true one.
Supports compliance workflows · Not legal advice · No compliance guarantee
A usable evidence trail — door by door, over time.
The term comes from the Building Safety Act 2022, where the duty to keep building information usable over time falls on higher-risk buildings. Three properties keep a record usable years later. None of them is a feature you would put on a billboard, and all three are what fails first.
-
01
One record, not five systems
Inspections, remedials, photographs and outputs stay attached to the same door or penetration record — so the story does not split across emails, spreadsheets and a shared drive, and nobody has to reconstruct it under pressure.
-
02
Traceable history
Each record shows what changed, when, and who changed it. Exports come from the same underlying data as the screen, so a PDF issued last March and the record today tell the same story.
-
03
Identity that survives time
A door keeps its ID between visits. That sounds trivial until a second contractor renumbers a block and eighteen months of history stops lining up with anything.
Where the software stops and you begin.
This is the section most vendors leave out. It is the one worth reading.
- What the platform does
- Records what a competent person found, when they found it, and what was done about it — then keeps that record together, dated, attributable and exportable.
- What it does not do
- It does not certify doors or fire stopping systems, it does not provide legal advice, and it does not guarantee that a building is compliant.
- Who decides pass or fail
- A competent person, during an inspection. The platform records the outcome of that judgement; it does not make it. The record is evidence, not a verdict.
- Who certifies the work
- You do, or your installer does. Where a job needs a certificate, that comes from whoever carried out the work and holds the competence to stand behind it. The platform deliberately does not issue one — we are not a certification body and verify nobody’s competence, so we are in no position to attest to it. What it does is hold the proof: what was done, by whom, when, photographed, alongside any certificate you upload.
- Who sets the intervals
- Your statutory duties and your own fire risk assessment. We do not publish inspection or survey frequencies of our own.
- Where responsibility sits
- With your organisation. Joined-up records strengthen an evidence trail; they do not transfer a legal duty to a software supplier.
Nothing on this page is legal advice, and nothing here changes the duties that apply to your buildings. If you need to know what those duties are, ask somebody qualified to tell you — then use this to evidence that you met them.
What you would actually hand over.
Every page below is a genuine output. Open them — no account, no card, no form.
The ones that matter legally.
Q01
Where does the legal duty actually come from?
Compliance
Q02
What does Regulation 10 require, and does this help?
Compliance
Q03
Is the platform a compliance guarantee?
Compliance
Q04
What does the golden thread mean in practice here?
Evidence
Q05
Will this satisfy our auditor?
Evidence
Q06
Do you align with a particular standard?
Standards
Q07
What happens to the evidence if we change supplier?
Handover
Judge the evidence, not the marketing.
Run a real building through the trial and look at what comes out the other end. That is the only honest way to decide whether the record would hold up for you.
No card. Cancel anytime.
Summary
Invoice