Gateway 3 Handover: The As-Built Record That Survives

The building is finished. The scaffold is down, the client is asking about keys, and an email lands from the main contractor asking for your handover file by the end of the month, because until the completion application goes in, nobody moves in. The schedule attached is longer than the one you answered at Gateway 2, and this time it has to describe what was actually built.

What's Actually Being Asked

The Building Safety Act put a hard stop at the end of a higher-risk building's construction, the last of its three gateways. For buildings in scope (broadly, at least 18 metres or seven storeys with two or more residential units, with care homes and hospitals at that height also in scope during design and construction), the client applies to the Building Safety Regulator for a completion certificate once the work is finished. Occupation waits on that decision, whether for the whole building or, where a staged route was agreed, for the part being handed over: the regulator has to be satisfied the work complies with the applicable building regulations requirements, and the building has to be registered, before people move in. The procedural detail sits in the higher-risk building procedural regulations made under the Act.

Two things separate Gateway 3 from the submission you helped assemble at Gateway 2. The first is tense. Gateway 2 asked how the building was going to comply; Gateway 3 asks whether the building in front of the regulator does comply, which means the record has to describe the building as built, including the changes made along the way, recorded to the level the change-control regime asks for.

The second is that the golden thread does not stop when the work does. It changes hands. The information kept during design and construction has to be passed to the principal accountable person (or accountable person) who will hold the building in occupation, in a form they can keep, use, update and hand on again. Your package is one strand of that record, and it has to arrive in a state a stranger can use, because the person receiving it was not in your design meetings and the person reading it in fifteen years will not have met anyone who was.

The Evidence That Answers It

What a specialist contractor is asked to contribute at handover is narrower than it looks. It comes down to six families of record, all of which describe the same thing from different angles: what is on the building, and why it is defensible.

• As-built design information. The drawings, details and specifications that describe what is installed, not what was tendered. Where the two differ, the record has to show the difference and the approval behind it.
• Change records. Every deviation from the approved design: what it was, how it was classified for change-control purposes, who decided, when, and what was notified. Change control during construction is easy to treat as paperwork, and the completion certificate application asks for records of the changes made during construction directly.
• Product and system evidence. The products actually fitted, with the test evidence, declarations of performance and third-party certification that support them. Where a substitution was made on site, the evidence trail has to follow the substitute, not the original.
• Installation and inspection evidence. Inspection and test plans, hold-point sign-offs, dated photographs, test results, and closed-out defects, each tied to a location in the building rather than a week in a programme.
• Competence evidence. Who did the work, what qualified them, and, critically, what qualified them on the date they did it. A certificate that expired three months into a two-year installation does not evidence the second half of it.
• Operation and maintenance information. How the installed system behaves, what its performance depends on, and what has to be inspected, maintained or replaced to keep it performing. This is the part the accountable person actually uses.

Why the Spreadsheet Version Fails

Very little of this is genuinely missing. The information usually exists. It just does not exist in one place. The as-built markups are on a drawing in a site office. The change approvals are in an email thread nobody can find the end of. The installation photographs are on three phones, two of which have left the company. The competence records are a training matrix that was accurate the day it was exported. Assembling a handover file from that landscape is archaeology, and it fails twice over: it is slow, arriving weeks after the date the programme assumed, and it is weak, because a document compiled at the end can assert what happened but cannot demonstrate when the evidence was captured or that it matches the building. Handover is not the end of that record's life. It is the beginning of its longest phase, under limitation periods the Building Safety Act extended well beyond the old six years.

Keeping It Provable

The alternative is not a better filing effort at the end. It is to stop treating handover as a document to assemble and start treating the project as a record you keep. If as-built information, change decisions, product evidence, inspection records and competence are captured as the work happens, each anchored to the part of the building it describes, then your contribution to the completion application becomes an export rather than an excavation. The test is simple: if the job stopped today, could you hand over a record of what has been built so far, without asking anyone to remember anything? A record that passes that test on a Tuesday in the middle of the job is a record that passes it at handover.

The Monday Checklist

1. Identify which of your live packages sit on higher-risk buildings, and when each one is due to reach completion. That date is what your record has to be ready for.
2. Ask now, through the principal contractor and up to the client, what format the completion information has to arrive in and who will be receiving it.
3. Take one package and list every change made since the approved design. If that list takes more than an hour to build, your change record is not a record.
4. Check that the product evidence you hold matches what was installed, including every substitution, and not just what was specified.
5. Sample five installation photographs at random and see whether each one tells you the date, the location and who took it. If it does not, it is a picture, not evidence.
6. Check competence records against the dates on the job, not against today, and note the gaps while there is still time to close them.
7. Decide who owns the handover record inside your business and give them the job before the final month, not during it.

Where BrieXO Fits

BrieXO's FIELD bundle keeps site records, inspection and photo evidence, competence records and recorded decisions in one living record, anchored to the building, so the site-side strands of that record (what was done, where, by whom, and what was decided) accumulate while the work happens instead of being reconstructed in the final month. Design and commercial modules are on the roadmap. It supports your dutyholder duties; it doesn't discharge them. See how the record is built and handed on in our golden thread software overview.

Related reading:the evidence Gateway 2 asks subcontractors for, the specialist contractor's guide to the golden thread, and the full gateway process.

George Sfica is a senior design manager at a specialist façade contractor, with 23 years in manufacturing and construction, eleven of them in façades and external envelopes, spanning fabrication, installation and design management, an MSc in Façade Engineering and an IFE Level 2 Certificate in Passive Fire Protection. He is the founder of BrieXO.