Paper Trails in the Cloud: Verifying a Connected Building’s Safety File
In newer blocks and recently retrofitted estates, building-safety information increasingly lives in software rather than a filing cabinet. Fire-door sensors report whether a door is shut; evacuation-alert systems log their own tests; maintenance platforms generate work orders and close them again. For a buyer or renter, the appeal is obvious: a single screen that appears to confirm the building is in order.
The difficulty is that a digital record is not the same as a reliable one. A green tick may show that a sensor is online, not that a door closes properly. A closed work order may show that an administrator clicked a button, not that an engineer attended. Under the Building Safety Act 2022, the ‘golden thread’ of information is meant to make safety records accurate, proportionate and readily available. Reading that record properly requires the habits of an auditor rather than the optimism of a brochure reader.
What the golden thread actually asks for
The golden thread is often described as if it were a product to be bought. In practice it is a discipline: a structured approach to creating, storing and updating information about a building’s design, construction and ongoing management. For higher-risk buildings — broadly those at least 18 metres or seven storeys tall with two or more residential units — the principal accountable person must maintain a safety case and the information that supports it.
Before exchange or before signing a tenancy, ask for the information-management strategy and the asset information plan. These documents should explain what information is held, who is responsible for it and how changes are recorded. If the answer is a login to a resident app, that is not an information-management strategy. It is a window onto whichever fields the software happens to display.
Why a green dashboard can mislead
Connected safety systems produce two very different kinds of output. The first is status data: a door is open or closed, a detector is reachable, a panel is fault-free. The second is evidence: a test certificate, a dated photograph, an engineer’s signature, a unique asset identifier matched to a physical component. A credible record contains both. A decorative one contains only the first.
Ask for the exception report rather than the compliance summary. What failed in the past twelve months? How long did each fault remain open? Which assets recur? A building with three fire doors that have been adjusted repeatedly tells you more than a dashboard showing 98 per cent compliance. Look, too, for override codes and ‘pinned open’ events: sensors can record that a door was held open, but they cannot record why, or whether anyone followed up.
The provenance test: five questions to ask
First, who is the accountable person for the building, and which organisation holds the safety data? Second, is each log generated automatically by a device, entered manually by a contractor, or both — and can the two be distinguished? Third, what audit trail exists for edits: who changed a record, when, and on what authority? Fourth, what is the retention period and in what format can the data be exported? Fifth, what happens to the record at handover, whether to a new leaseholder, a new managing agent or a purchaser of the freehold?
The fifth question is the one most often overlooked. Safety software is frequently licensed to a landlord or managing agent rather than to the building. A buyer may inherit a login that expires, or a leaseholder may find that the evidence behind a service-charge item sits in a system they cannot access. Check the lease and the transfer documents for any assignment of software licences, and ask whether a full export — not a PDF summary — will be provided.
Fire doors and evacuation systems in practice
Fire doors are a useful test case because they are both physical and sensored. A magnetic or reed-switch monitor can confirm that a door was closed at a given moment. It cannot confirm that the gap beneath the door is within tolerance, that the hinges are sound or that the intumescent strip is intact. Ask for the most recent fire risk assessment and the fire-door inspection regime, then sample five or ten asset IDs from the register and match them to doors you can see. If the register cannot be reconciled with the building, the wider record deserves scrutiny.
In blocks with evacuation-alert systems, ask for test records and for evidence that residents have been familiarised with the system. For smoke ventilation, sprinklers and alarms, request the cause-and-effect schedule and the last set of test results. These are engineering documents, not marketing assets, and their presence or absence is telling.
Maintenance trails, not maintenance theatre
Planned preventive maintenance is not the same as reactive repair, and a platform that merges the two can flatter a building’s history. Ask for twelve months of work orders with completion evidence attached: dates, engineer names, parts used, photographs where relevant. Then ask about the software itself. When does vendor support end? Is there a data-escrow arrangement? Can the managing agent extract the asset register through an API if the contract changes?
These questions matter because connected safety systems are subject to obsolescence in a way that a paper log is not. A building whose fire-door monitoring depends on a discontinued gateway is not safer for having been digitised; it is simply dependent on a supply chain that may not outlast the mortgage.
Who controls the record
Under UK GDPR, the managing agent or landlord will usually be the data controller for safety information, with the software vendor acting as processor. Residents have rights to access their own data, and the Building Safety Act gives residents in higher-risk buildings specific rights to request information. Those rights are useful, but they are not a substitute for due diligence at the point of purchase or letting.
Ask, in writing, for a data-room index and a sample export. Confirm whether the service charge includes a line for monitoring subscriptions, software licences or sensor replacement, and how those costs are expected to change. A safety system that is well maintained but funded by an unclear recurring charge is a different proposition from one that is simply well presented.
A practical request list before you commit
- The information-management strategy and asset information plan.
- An asset register with unique identifiers, matched to physical locations.
- Twelve months of exception and fault reports, including closure evidence.
- The current fire risk assessment and the fire-door inspection regime.
- Evacuation-alert test records and resident familiarisation evidence.
- A sample of maintenance work orders with completion attachments.
- Confirmation of data ownership, retention, export format and handover arrangements.
- Software support end dates and contingency arrangements.
A safety record that cannot be interrogated is decoration. The question is not whether a building has a dashboard, but whether the evidence behind it would satisfy an inspector — and whether you, as the next occupier or owner, will be able to see it.