The golden thread: Can your records explain what changed and why?

A digital record becomes useful when it connects a building decision to its evidence, authorisation and physical outcome. For higher-risk buildings in England, that connection needs to survive changes of product, contractor and owner

A contractor proposes an alternative product because the specified item is unavailable. The design team exchanges emails, a revised drawing appears in the common data environment, and the replacement reaches site. Months later, someone asks which assessment supported the substitution, whether installation followed its conditions and who authorised the change. Finding the drawing answers only part of the question. The important record is the connection between the original requirement, the proposed alteration and the evidence supporting the completed work.

This is a useful way to examine the golden thread. A project may hold thousands of documents while leaving important decisions difficult to reconstruct. Equally, an orderly record can contain unresolved technical questions. Digital construction teams therefore need to assess both information management and the underlying evidence. Searchable files, signatures and dashboards help people find and track work; they do not determine whether the design or installation is adequate. That distinction matters whenever a software workflow is described as a complete compliance solution.

Establish the building and the legal phase

The statutory regime discussed here applies in England. The government’s guidance on higher-risk building criteria distinguishes design and construction, work to existing buildings and occupation. Broadly, the height or storey threshold is at least 18 metres or at least seven storeys, combined with relevant use criteria. Design and construction scope includes buildings with at least two residential units, hospitals and care homes, subject to exclusions. The occupation criteria require at least two residential units and exclude buildings used entirely as hospitals or care homes, among other exclusions. Mixed uses, connected structures and prescribed measurement rules require particular attention.

A project team should record how it established the building’s scope and which phase its decisions concern. Treating every tall building identically, or applying England’s arrangements across the UK, can produce the wrong responsibilities and information requests. For an unusual structure, the scope assessment needs competent input rather than a software tick box. The register of applicable duties should also remain separate from broader organisational ambitions: a client can seek good records across its whole estate without claiming that every property is subject to the same statutory golden thread requirements.

Define an evidence chain people can follow

The Building Safety Regulator’s golden thread guidance requires relevant information to be kept digitally, secured, available and usable. It allocates responsibilities to clients, principal designers, principal contractors and, during occupation, accountable persons. The practical question for an information manager is how a later user will follow the evidence without relying on someone who remembers the project. A document’s location alone is a weak answer if its status, relevance and relationship to the installed work remain unclear.

For a significant design decision, a useful record links the requirement to the affected location, the evidence considered, the decision-maker and the resulting instruction. It should distinguish an assumption awaiting verification from a conclusion supported by testing or inspection. Record the limits of an assessment as carefully as the result. If evidence applies only to a particular assembly, substrate or installation method, removing that context can make a technically accurate document misleading when reused elsewhere. Consistent identifiers help preserve these relationships as drawings and products change.

Make change control visible before installation

Under BSR’s guidance on changes to a higher-risk building project, controlled changes must be assessed through the required process. Major changes require BSR approval before the related work proceeds; notifiable changes must be submitted before the relevant work starts. Uploading a revision or receiving an automated acknowledgement is not the same as gaining approval. Classification depends on what changes and their regulatory implications, so project teams need technical judgement and a clear route for escalating uncertainty.

The common data environment should reflect those distinctions. A substitution under review should not look identical to an instruction released for construction. Procurement, design and site teams need access to an intelligible status and the conditions attached to it. Otherwise, an order placed to protect the programme can become an unintended assumption that the proposal has been accepted. An effective change record also points to every affected drawing, calculation, specification and installation instruction, preventing one updated document from coexisting with several apparently current contradictions.

Connect the decision to what was built

Consider a hypothetical alteration to a service penetration through a fire-resisting element. The digital record might contain an accepted detail, a product reference and a photograph. Each has a different evidential purpose. The detail explains the intended arrangement; the product information describes relevant performance and conditions; the site evidence records what could actually be observed. None should silently substitute for the others. A photograph taken after concealment may identify a location while showing little about the installation feature that needed verification.

Inspection planning should therefore identify what must be captured, at which stage and by whom. Location references need enough precision to distinguish adjacent or repeated installations. Where an inspection finds a defect, the original observation should remain connected to the correction and subsequent check. Deleting the failed record produces a cleaner dashboard but removes useful history. Where evidence cannot establish the condition, the record should show that limitation and the action required. Uncertainty should be managed explicitly, rather than hidden behind a completed form.

Preserve responsibility when organisations change

Responsibility can become blurred when an information manager administers a system used by multiple duty holders. Giving that person responsibility for naming conventions or access does not automatically give them authority to accept technical work. The project needs to identify who prepares information, who checks its content, who can authorise its use and who resolves disputed conclusions. Those roles may change between design, construction and occupation. A handover of permissions is insufficient if the new organisation does not understand the outstanding decisions it inherits.

The building control approval guidance makes clear that a client can nominate someone to manage an application while retaining legal responsibility. The same distinction is instructive when procuring information services. Contracts should describe the service and evidence expected without implying that appointing a platform provider removes statutory duties. When a designer, contractor or managing agent changes, review unresolved issues, access rights, export arrangements and the names attached to future actions before the departing team becomes unavailable.

Test whether the next user can act

A useful review exercise begins with a realistic question: identify the current arrangement in a selected location, explain a change and retrieve the evidence that supports it. Ask someone outside the originating team to complete the exercise using their ordinary permissions. This tests understandable organisation as well as technical access. If they need an administrator to translate every file name, the information is not yet ready for routine use. Repeat the exercise for an unresolved issue, because outstanding work often disappears from view when files are packaged for handover.

For occupation, the building record needs a funded owner and a route for subsequent amendments. A maintenance intervention can alter the evidence on which a safety decision rests. The person receiving a contractor’s completion report should know whether it triggers an update to an asset record, drawing, risk assessment or other controlled information. Archive arrangements also need testing: a retained document is of limited use if its software licence expires, links break, or access belongs to a former supplier’s account.

Measure the gaps that matter

Counting uploaded files rewards volume. More useful management information distinguishes missing evidence, rejected evidence, unresolved technical questions and changes awaiting the required action. The age and consequence of each gap matter more than an overall percentage complete. A small number of unresolved safety-critical items can deserve more attention than hundreds of routine naming errors. Reports should let senior decision-makers see which activities depend on those gaps being closed and who has the authority and resources to resolve them.

PBC Today’s earlier coverage of connected golden thread data examined how common platforms support collaboration. The next operational test is more demanding: can the organisation explain a particular decision and demonstrate its result? That requires usable evidence, clear responsibility and continuing scrutiny as the building changes. A record that answers those questions gives designers, contractors and building managers something they can work with when the people who first assembled it have moved on.

The post The golden thread: Can your records explain what changed and why? appeared first on Planning, Building & Construction Today.

Leave a Reply

Your email address will not be published. Required fields are marked *

The golden thread: Can your records explain what changed and why?
Close Search Window
↑