From Handover to Operations: Making Day One Work

The industry pays twice for the same data

Every asset in a building was specified, procured, installed and commissioned. Somebody wrote down what it was, where it went, what its warranty said and how often it needs servicing. That information existed, in full, on the day the building was handed over.

And then, very often, it did not arrive — or it arrived as four hundred PDFs in a folder structure nobody can navigate, which is the same thing wearing a suit. So the operator sends people out with a torch and a clipboard to find out what is in the plant rooms.

NIST priced the annual cost of poor construction-to-operations data handover, and the share of it borne by owners simply re-verifying information they had already paid to create. That figure is set out with its source on our asset-management module page. It is not the cost of missing data. It is the cost of an industry paying a second time to learn what data it already commissioned.

One caveat, said plainly: the study is from 2002. It remains the standard citation, which is itself part of the story.

Handover is the golden moment, and it comes once

Equipment lists, warranties, preventive-maintenance schedules, O&M manuals — captured at commissioning, when the people who installed the plant are still standing next to it.

COBie is the standard format for delivering that data from construction into operations. The format is not the point. The point is that the data is captured while the knowledge still exists in the building, rather than reconstructed later by people who were not there.

And it has to be specified as a deliverable, in the contract, with acceptance criteria. Otherwise it will be produced in the last week of the job, by whoever is left, and it will look exactly like what it is.

The quiet loss is warranty. An asset that never made it onto the register carries a warranty nobody claims — and it expires without anyone knowing it existed. Nothing announces it. That is precisely what makes it expensive.

As-builts are a rolling product, not a closeout scramble

The standard failure is a red pen and a memory. As-builts marked up months after the work was concealed, by somebody who was not there, producing a document that shows where the services were supposed to go.

The cost of that lands on the operator, years later, drilling into a wall to find a pipe nobody recorded. And it is unrecoverable, because the only way to verify an as-built after the fact is to open something up.

Update them as the work is concealed, alongside the pre-cover photographs of the same work. Those two records are the same record viewed twice, and a project that captures one and not the other has done half a job at full cost.

The register either starts true, or it starts wrong

An asset register rots by default. That is not a failure of diligence; it is the natural state of a document everybody depends on and nobody owns. And the rot begins at handover.

A register built from a proper structured handover starts complete. A register rebuilt by hand from whatever the operations team could find starts incomplete on the day it is created — and it never catches up, because nobody funds a survey of a building that is already open.

From there the consequences are financial rather than administrative. Insurance values are overstated. Property tax is paid on equipment scrapped three renovations ago. Preventive maintenance fires against assets that do not exist, so a technician is sent to find a pump that was removed — while a real asset, on no register anywhere, goes unmaintained.

Get the hierarchy right, because accounting depends on it

Property, system, asset, component. And the componentisation is not a preference — IAS 16 requires significant components to be depreciated separately.

A register that lumps everything together as "M&E plant" makes a component replacement impossible to derecognise. So the old compressor stays on the books while the new one is added, and the same value is counted twice, permanently.

Componentise deep enough that significant-value components can be separately depreciated and removed when replaced. And no deeper than you can actually maintain, because a register nobody can keep current will lie to you — and it will do so with great precision.

• FF&E — depreciable, typically reserve-funded, replaced on a cycle. On the register.
• Building systems — plant and infrastructure, the longest lives, managed by criticality. On the register, componentised.
• OS&E — linen, glassware, crockery. Expensed, par-tracked, and NOT register items. Putting ten thousand glasses on the fixed-asset register does not make it thorough; it makes it unusable.

Criticality is what turns a list into a strategy

Rank every asset by safety, guest impact and revenue impact against its likelihood of failure. That ranking then sets preventive-maintenance frequency, spares holding and response priority.

Without it, maintenance spend gets spread evenly across everything — which sounds fair and is simply peanut-butter. The critical chiller and the corridor extract fan receive the same attention, and only one of them needs it.

This is also the input that decides the maintenance strategy per asset: reactive, calendar-based, meter-based or condition-based. None of the four is wrong. Running all your assets on one of them is.

Day one, and the certificate chain nobody watches

A building with zero snags and no occupancy permission cannot be handed over. The completion-certificate chain — final authority inspections, conformity certification, occupancy permission — runs at the end, in series, with external bodies who did not agree to your handover date.

Everybody watches the snag list, because it is visible and has a burn-down chart. The certificate chain usually sits with one person in a spreadsheet, and it determines the date just as absolutely.

Work backwards from the handover date and find out when the first inspection actually has to be booked. The answer is almost always earlier than anybody assumed.

And the records have to outlive the project team

The project disbands. The shared drive gets archived. IT eventually reclaims the storage. All of this is reasonable, and all of it is planned around the project’s life.

But the claim is not on the project’s timeline. In the UAE, decennial liability for structural defects runs for ten years from completion and cannot be excluded by contract. The photographs, the as-builts and the test records either still exist at that point, or they do not.

That gets decided exactly once — deliberately, by somebody thinking about a dispute that has not happened — or it gets decided by a storage clear-down nobody was consulted about, in a year nobody remembers.