Keep the golden thread on a higher-risk building

Set the information requirements out as a matrix: what has to be delivered, by whom, at what point and to what standard, with the quality gates each set has to pass. Everything downstream is then measured against this rather than against habit.

Why: The golden thread fails at the beginning far more often than at the end. Nobody hands over a building with no information; they hand over a great deal of information nobody asked for, in a form nobody can search, which under a regime that expects the accountable person to answer a question quickly is the same as having none.

Run the information through the common data environment states, from work in progress to shared, published and archived, with a suitability code on every container saying what it may be used for. Moving a container between states is a gate somebody passes, not a drag between folders.

Why: The difference between a drawing you may build from and a drawing somebody is still working on is the single most expensive distinction on a construction project, and a folder name cannot carry it. A suitability code travels with the container, so whoever opens it six months later knows what it was fit for without ringing the person who made it.

Hold the drawings, specifications, calculations, product data and certificates as one register with versions, so the current revision is obvious and the superseded one is still there. Tag and file them the way the requirements matrix asked for, not the way each discipline would prefer.

Why: The regime expects information to be current and findable, and those two fail together: a register where the latest revision is ambiguous is a register where somebody eventually builds from the wrong sheet. Keeping superseded versions rather than overwriting them also answers the question that comes up in every investigation, which is what was known at the time.

Run the review cycle with the approving authority: record the submission with the document version pinned to it, log each remark, respond to it and close out the decision. When the live document moves on, a remark raised against the submitted version is flagged as stale rather than silently remapped onto the new one.

Why: A remark answered against a drawing that has changed since submission is an answer to a question nobody asked. Pinning the version makes the exchange reconstructable, which is the whole ask of a gateway: show what you submitted, what you were told about it, and what you did in response.

Bind the information into the handover package: the as-built set, the operation and maintenance information, the test and commissioning certificates, the fire and structural information, and the manifest that says what is in there. Issue it to whoever becomes accountable for the building in occupation.

Why: The golden thread does not stop at practical completion, it changes hands. A package that arrives as a folder tree with no manifest becomes an archive nobody opens within a month, and the next person who needs to know how the building was actually built starts again from whatever drawings are still on site.