When we introduced Asset Intelligence in June’s issue, we set out why the built environment needs a coherent discipline for managing information across the life of a building. This time we explore where that discipline starts: on site, during design and construction, in the hands of the people who create the information every building depends on
Asset Intelligence is the discipline that ensures the people responsible for buildings can find, trust and act on the information they need to keep them safe, compliant and performing. For project delivery teams, that means what you create now becomes the information an operator relies on for the next 50 years.
Handover is not the finish line
Every capital project ends the same way. Drawings, models, manuals, certificates and asset registers are assembled, checked against the contract and handed over to the client. For the delivery team, that moment marks completion. For the building, it marks the start of decades of use.
This is one of the industry’s most persistent information risks, and the one delivery teams are closest to. Information produced during design and construction is structured for project delivery, for approvals, for sign off, for closing the final account. It is rarely structured for the operational decisions a building’s owners and operators will need to make for the rest of its working life.
Even well executed handovers, on projects that meet every contractual requirement, routinely produce information that operations teams cannot navigate and have little reason to open.
This is the performance gap. It is the gap between what an organisation holds about a building and what it can act on with confidence.
Every building sits in one of four information conditions. Information structured during construction but lost or degraded at handover. Information that fragments through years of uncoordinated change. Information that was never created in structured form at all. Information that exists but is buried in the volume.
The first and the third of these sit squarely in the construction phase, and they are the ones delivery teams are best placed to prevent.
Why good intentions are not enough
None of this happens because delivery teams do not care about the buildings they hand over. It happens because of how the industry is structured. Constructors are contracted, measured and paid to complete a project, not to guarantee data quality for an operator they may never work with again.
Information requirements are often set late or set by people with limited visibility of how the building will actually be run. Clear information requirements exist precisely to close this gap, translating what an organisation needs into terms that can be specified, contracted and measured. Where they are treated as a compliance exercise rather than an operational brief, they rarely deliver what an operations team can use.
The same applies to how information is produced through the supply chain. Managing subcontractor deliverables against work packages, tracking submissions, reviewing quality and closing out compliance obligations is demanding work, and it usually happens under pressure in the closing weeks of a programme.
Asset Intelligence treats this production process as work that deserves its own rigour, distinct from the project programme it runs alongside, because the quality of what gets created here determines whether a building performs as designed or spends its first years being rediscovered by the people trying to run it.
A different way to think about handover
Asset Intelligence reframes handover from an endpoint into a starting point. Information produced during delivery becomes the baseline against which every future change to the building is recorded and managed.
That requires thinking about the building’s future operational use from the outset of a project, not retrofitting it once the model is complete. It also requires validating what has been produced against defined requirements, with a level of confidence that a compliance sign off alone does not provide.
None of this demands perfection on day one. Asset Intelligence works on the principle of progressive confidence. Delivery teams do not need to solve every information challenge on every project. They need to be clear about what matters most for how the building will be operated. Get that right and build from there.
Why it matters to project delivery now
The regulatory pressure on this is only increasing. The Building Safety Act’s Golden Thread requirements expect accurate, accessible and current information to be maintained throughout a building’s life, with personal accountability for failure. Net zero commitments depend on reliable baseline data that has to come from somewhere. Investors and boards are asking harder questions about the buildings in their portfolios, and the answers depend on the same information delivery teams create.
Getting this right does not add new work to a project. It changes how existing work is done, so the effort already going into requirements, capture and handover produces something an operator can actually use. That is the value construction teams are in the best position to deliver, and it is why Asset Intelligence starts where the building itself starts: on site.
*Please note, this is a commercial profile.
The post Asset Intelligence: The discipline that starts on site and outlasts the project appeared first on Planning, Building & Construction Today.
