The as-built golden thread: closing the gap between designed and built

What does "as-built" actually demand?

Gateway 3's core evidential demand is simple to state: the application must include as-built plans and documents reflecting what was actually built, and the golden thread handed to the accountable person must describe the building that exists, not the one that was approved. Between those two sentences sits most of the pain in the completion process, because on a real project the built thing always differs from the approved thing in a hundred small ways, and the regime's entire question is whether you controlled, recorded and can prove those differences.

The change control regime handles the differences as they happen; the as-built golden thread is where they all land. Approved drawing, plus logged changes, plus installation records, should reconcile to the as-built drawing exactly. When they do, the final inspection confirms what the documents already told the assessor. When they do not, you have manufactured the BSR's third named stall reason: discrepancies between the as-built records and the systems and materials actually installed.

How do discrepancies actually happen?

Rarely through negligence; usually through drift. A substituted product that genuinely was equivalent, agreed on a call, installed, and never walked back into the drawing set. A services route moved on site around a clash, recorded in the subcontractor's markups but not the federated model. Commissioning settings that differ from the design assumptions because the building, as balanced, needed them to. Each is defensible; undocumented, each is a discrepancy, and the assessor who finds one undocumented difference has every reason to wonder what else diverged.

The pattern to notice: every discrepancy is a record that existed somewhere, in someone's markups, messages or memory, and failed to reach the golden thread. Which is why the fix is not heroic documentation at the end but contemporaneous site records flowing into the thread continuously.

What does progressive as-builting look like?

Element by element, closed as built. When a floor's fire compartmentation completes, its as-built drawings are updated, its installation and inspection records filed, its photographs of concealed work attached, and that element is closed while the evidence is fresh and the installer is still on site to answer questions. The golden thread grows a verified layer at a time, and by the time notifiable work completes, the as-built record already exists because it was never allowed to lag more than one element behind the building.

Contrast the alternative, still common: a document push at practical completion, reconstructing a year of changes from subcontractor files and surveys, against the 8-week determination clock with the occupation gap burning money. The projects clearing Gateway 3 fastest, the pattern our tracker exists to document, made as-builting a weekly habit, not a completion event.

Who owns the as-built thread, and what should they do this week?

During construction the principal contractor controls most of what needs capturing, with the principal designer owning the design-side updates, but ownership only works when it is explicit: a named person, a defined structure, a weekly reconciliation of drawings against change log against installation records. If that discipline does not exist on your project yet, start it with the current work front rather than resolving to back-fill history: close out the elements completing this month properly, and schedule the archaeology for what is already covered up as a defined, priced exercise instead of a completion-week surprise. The thread you hand the accountable person at handover is the one the building lives with; build it like it matters, because from 1 October 2026 the levy check and the evidence check arrive together.