Building safety information: planning controlled project records
Admin · 22 October 2026
Illustrative image. Photo by Jonathan Borba on Unsplash. Unsplash License.
Building safety information is difficult to assemble reliably if the project starts thinking about it only at handover. Decisions, changes and evidence develop throughout design and construction, often across several organisations. A late request for every relevant document can produce a large collection without a clear account of what it describes. Planning the record early helps the team connect requirements, responsibilities and the evidence produced by the actual work.
The first task is to establish the obligations applicable to the building, location and project, with appropriate professional advice. Requirements are not identical across every setting. This article proposes an information-management workflow; it does not determine statutory scope, assign dutyholder roles or provide a complete compliance checklist. Those matters must be established through the project’s competent advisers and actual arrangements.
Confirm the applicable framework
The Building Safety Regulator’s golden-thread guidance covers information responsibilities for higher-risk building projects and accountable persons for high-rise residential buildings in England. It should be read in its stated context rather than presented as a universal requirement for every construction project. Ask the responsible advisers to identify the relevant obligations and explain what information and decisions the project needs to plan.
Record the advice and the resulting requirements in a controlled source. Identify who maintains that source and how changes in scope or applicable requirements will be reviewed. The project team needs a clear route for questions rather than several competing interpretations circulating in correspondence. Where a matter remains unresolved, give it an owner and a decision date.
Define the purpose of each record
Ask what a record demonstrates, who will use it and which requirement it addresses. This helps distinguish useful evidence from background material. A document can be genuine and relevant without answering the particular question being reviewed. The information schedule should connect the required output to its intended use and the people competent to assess it.
Avoid equating file volume with completeness. Several versions of a proposal do not necessarily provide the accepted design or the evidence of installed work. Identify the authoritative record and preserve appropriate links to its history. The receiving team should understand the current position without reconstructing every discussion that preceded it.
Allocate production and review
For each significant information requirement, identify the author, contributors, reviewer and acceptance route under the project’s arrangements. Distinguish administrative checks from technical assessment. A document controller can manage references and workflows without verifying every statement about a system. The relevant specialists need clear responsibility and time to review the content within their remit.
Check allocations against appointments and procurement scopes through the proper process. An information matrix should expose gaps rather than assign work informally to a party that has not agreed it. If a specialist contribution is needed, identify who will procure it and when the output is required. Leaving that decision until close-out can make the record difficult to complete.
Use stable references and locations
Agree how the information identifies systems, elements and relevant areas. The structure should allow a reviewer to connect evidence to the work it concerns. A certificate or photograph without adequate context may be difficult to interpret. Ask the responsible teams what identification is necessary and establish a consistent approach before evidence collection begins.
Keep references aligned across design, procurement and installation records where required. If a product or layout changes, update the relevant relationships through the controlled process. Retain the history without allowing an earlier option to appear current. This helps the team trace how the accepted arrangement developed and which evidence applies to it.
Plan evidence around the work
Identify when information can be produced and when it needs review. Some evidence depends on design decisions, some on supplier submissions and some on activities during installation or testing. The competent specialists should determine the actual requirements. Connect those dependencies to the programme so that the record is built progressively rather than requested after access has changed.
Consider a hypothetical package where an agreed check must occur before work becomes concealed. The record plan needs the location, responsible person, review arrangements and timing established in advance. A general request for photographs after completion cannot automatically recreate the missing evidence. Early planning gives the team an opportunity to organise the required process properly.
Control changes to the accepted basis
A revised product, design or method can affect the information needed. Identify the records and reviewers affected when a change is assessed. The project’s actual governance and contractual process determines the approval route. Information management should support that process by preserving the request, assessment, decision and consequential updates.
Confirm implementation in the record as well as in the work. If an approved change reaches the installer but not the final drawings or supporting evidence, the project can hand over an inconsistent account. Assign a person to coordinate the updates and identify how completion will be verified. The task should not depend on an assumption that every supplier will notice the change independently.
Make access and security practical
Establish the project’s arrangements for authorised access, protection and sharing of information with appropriate advice. Users need the records relevant to their responsibilities, while sensitive material requires suitable controls. A system that is inaccessible to the people who need it can undermine an otherwise careful record. Equally, convenience should not mean uncontrolled circulation of every file.
Test the arrangements with representative users. Can an authorised reviewer locate the current information and understand its status? Can the receiving organisation obtain access through the agreed process? Identify problems while the project can adjust the structure or permissions. A successful test concerns actual retrieval, not simply confirmation that an account was created.
Review gaps specifically
Maintain an information-gap record that names the missing output, owner, required date and consequence. Avoid broad statements such as safety records incomplete. Decision makers need to understand what question remains unanswered and which action could resolve it. The relevant specialist should assess the significance rather than a reporting percentage being used as a substitute.
Distinguish missing information from content awaiting review or evidence requiring further assessment. These statuses call for different actions. Keep the record current as matters are resolved and link the accepted output to the requirement. This creates a more reliable account of readiness than a folder checklist marked complete when a file has merely been uploaded.
Prepare the receiving organisation
Agree the form, structure and transfer arrangements with the people who will maintain the information. Their needs should influence the plan early. Provide suitable familiarisation and ask them to test retrieval using realistic questions. Record their feedback and resolve consequential gaps through the appropriate process.
At transfer, identify the accepted record, outstanding actions and responsibilities for later updates. Preserve the applicable evidence of receipt and acceptance under the project’s arrangements. A usable handover requires more than sending a download link; the recipient needs to understand what it has received and how it relates to the building.
Retain the learning
Review which information was difficult to obtain and why. The cause may be an unclear scope, a late decision or a weak relationship between evidence and location. Apply those findings to future appointments and programme planning. The benefit is a clearer process rather than another generic instruction to improve documentation.
Controlled project records work best when each important output has a defined purpose, a responsible producer and a route to competent review. Building that structure at inception helps preserve an understandable account of the work and gives the receiving organisation a more dependable basis for its own responsibilities.
Give consequential information gaps the same visibility as other project dependencies, with a clear action, decision owner and date connected to the work affected.
