A Building Becomes an Asset the Day Its Data Is Complete

The handover meeting I remember best had everything a handover is supposed to have. The keys sat in a small box on the table. The contractor’s team had printed the drawings and stacked them in tubes against the wall. There were signatures, congratulations, photographs. Then the facilities manager, a quiet man who had said almost nothing for two hours, asked a single question. Which of the four chillers on the roof is still under warranty, and until when? The room went silent. Somebody suggested the information was in one of the tubes. Somebody else thought the supplier could be called. Nobody knew. The building was complete. The asset was not.

That distinction is the entire subject of this piece, and it is a distinction most of the profession still refuses to make. We speak of a project as finished when construction ends, when the ribbon is cut, when the certificate is issued. In asset management the arithmetic runs the other way. The project begins at handover, because everything that determines the economic life of the building starts on that day. Maintenance starts. Warranties start. Accounting depreciation starts. Facility management, energy management, replacement planning, remaining life assessment, and capital planning all start. What the owner receives at handover is not the end of a process. It is the operating system of the next forty years. And if that operating system arrives incomplete, the building will spend decades paying for a few careless weeks.

There is a name for the confusion. Project handover and asset handover are not the same event, though they usually happen in the same meeting. Project handover transfers a physical object and its legal closeout. Asset handover transfers the knowledge required to run that object, to maintain it, to account for it, and to plan its replacement. It is entirely possible, and in practice depressingly common, to receive a complete building that cannot be operated, because the data that makes operation possible was never assembled. The international literature on facility management identifies this gap as one of the most persistent causes of operational failure worldwide, and anyone who has inherited a building without its records already knows why.

What Exactly Is Being Handed Over

Before going further, the word asset needs its proper definition, because the profession tends to use it loosely. Under ISO 55000, an asset is anything that has value to an organization and is managed to deliver that value across its life cycle. That definition is deliberately wide. An asset can be the whole building, a single room, an air handling unit, a pump, an elevator, a door, an electrical panel, a valve, a generator, a piece of furniture, or an entire system made of all of the above. The standard, first published in 2014 and revised in 2024, is built on one idea from beginning to end, that an asset is managed across its full life and not merely during its construction. The implication for architecture is immediate. The drawings describe an object. Asset management describes a lifetime.

So what does a genuine asset handover contain? Most people answer with one word, drawings, and the answer reveals how the industry still thinks. The central document is in fact the asset register, a structured record that captures, for every asset in the building, its number, its name and type, its exact location by building, floor, and room, its manufacturer, model, and serial number, its installation and commissioning dates, its warranty terms, its expected useful life, its value, and the party responsible for it. Attached to that register, each physical asset carries a tag, a number, a barcode, a QR code, sometimes an RFID chip, so that the object on the roof and the row in the database remain permanently connected. Around this core gather the operation and maintenance manuals, which describe how each system is run, cleaned, serviced, and repaired, which spare parts it consumes, which faults it tends to produce, and on what schedule it must be inspected. Then come the as built drawings, which record what was actually constructed rather than what was designed, a difference that anyone who has opened a ceiling void understands. Then the warranties with their start and end dates, the spare parts themselves, the commissioning reports, the test certificates, the training records that prove the operating team was actually taught to run what it received, and finally the digital model, whether BIM, COBie, IFC, or another structured format that a facility management system can read. That is the handover. The keys are the least valuable item on the table.

The Standard Most Architects Have Never Opened

Many architects know BIM. Far fewer know COBie, and the gap between those two facts explains a great deal about how buildings lose their memory. COBie, Construction Operations Building Information Exchange, is not a three dimensional model. It is a standardized database for transferring asset data from the project team to the operations team. It gathers the spaces, the equipment, the systems, the warranties, the maintenance requirements, the operating instructions, the suppliers, and the spare parts into a structured digital format that can be imported directly into facility management software. It first appeared in 2007 with the backing of American government institutions, and its stated purpose was precisely the silence in that handover meeting, the gap between the end of construction and the start of operation.

The detail that matters most, and the one that most of the profession has never internalized, is that COBie does not begin at handover. It begins at design. Each stage of the project adds its layer of data. Design contributes the spaces and their names. Procurement contributes the products and their suppliers. Construction contributes the serial numbers and installation records. Commissioning contributes the test results and the operating parameters. By the time handover arrives, the dataset should already exist, accumulated rather than assembled. This is why the common practice of collecting information at the end of a project is structurally doomed. Data that was never captured in month six cannot be reconstructed in month thirty. The subcontractor has left. The supplier has changed hands. The label on the pump has faded. What looks like a documentation task at closeout is in reality an archaeology project, and archaeology always recovers less than what was buried.

What is the difference between BIM and COBie?

Seen this way, the life of building information forms a single continuous chain. Design flows into procurement, procurement into construction, construction into commissioning, commissioning into handover, handover into facility management, facility management into maintenance, maintenance into replacement, and replacement, eventually, into disposal. ISO 55000 rests entirely on this chain. Break it anywhere and every link downstream weakens. The design decisions taken in the first months quietly define what can be managed in the final decades.

Where the Architect’s Work Actually Ends

Here is the part of the argument that concerns this platform’s readers most directly. The architect usually believes the work ends at the IFC set. In data terms, the architect is the first asset manager on the project, whether or not the title is ever used. It is the architect who names the spaces, numbers the rooms, classifies the elements, specifies the products, assigns the codes, and produces the door schedules, the window schedules, and the finish schedules. Every one of those decisions becomes a field in the asset register years later. A room numbering system invented casually in schematic design will be typed into work orders for half a century. A vague product specification becomes an unidentifiable object that no maintenance system can track. The projects that operate smoothly in year fifteen are usually the ones whose information discipline began before the foundations did.

The contractor’s contribution follows the same logic at a different stage. Serial numbers, supplier data, warranty documents, catalogues, operation and maintenance manuals, test results, commissioning records, installation data. None of this is glamorous, and all of it is the raw material of the building’s future. And above both parties stands the owner, whose real responsibility begins earlier than either. The owner’s task is to define, before design starts, exactly what information the project must deliver at the end. The industry calls this the Asset Information Requirements, the AIR, and its logic is simple. A project team cannot produce data nobody asked for. When the requirements are written into the brief and the contract, the register accumulates naturally. When they are not, the handover becomes a negotiation over documents that were never created. Research from the American National Academies on why asset information handover fails found the same causes repeating across the industry. Absent standards and procedures. Weak contract clauses. Project teams never obligated to deliver the required data. Insufficient funding and resources. Poor stakeholder involvement. Bad document management. Not one of those causes is technical. Every one of them is a decision someone declined to make early.

One Pump, Two Lives

There is a further layer, and it is the one that connects this subject to money rather than machinery. Consider a single pump in the basement. The maintenance engineer sees running hours, service history, warranty status, and physical condition. The accountant, looking at the same object, sees none of that. The accountant sees an original cost, a useful life, a residual value, a depreciation schedule, and a book value. The same asset lives two parallel lives, one engineering and one financial, and the only bridge between them is the asset data. When the register is sound, the finance department knows what it owns, where it is, how old it is, and when it will need capital for replacement. When the register is missing, depreciation becomes guesswork, capital planning becomes improvisation, and the balance sheet describes a building that exists only on paper. The studies of building life cycle economics make the stakes explicit. Operation and maintenance costs constitute the dominant share of a building’s total life cycle cost, far exceeding the cost of design itself, which is precisely why the accurate handover of asset data has become central to controlling cost over the long term. The cheapest document in the project is the one that governs the most expensive phase of it.

This also reframes a small object that most people walk past without seeing. The barcode on the pump, the QR sticker on the door frame, is not a label. It is the identity of the asset. Without it, the object cannot be connected to its maintenance history, its warranty, its spare parts, its depreciation line, or its replacement plan, and an asset that cannot be connected to its own records has lost a large share of its operational value while remaining physically intact. In that one small sticker, architecture, engineering, accounting, and facility management meet in a single coherent idea. Value is not the object. Value is the object plus its information.

What should a project handover include?

For cities accumulating enormous building stock, this is not an administrative nicety. A municipality that owns thousands of undocumented assets is committed to reactive maintenance, emergency replacement, and premature demolition, which makes rigorous handover a sustainability instrument before it is a managerial one, since the longest lived building is the one whose condition is actually known. The news covers buildings on two days only, the day they open and the day they fail, and everything this article describes happens in the silence between those two days. Meanwhile design competitions continue to judge images of buildings at age zero, and almost never ask how the winning entry intends to be operated, while a growing body of architectural research on digital twins, COBie adoption, and life cycle information keeps demonstrating what practice keeps ignoring, that the information model of a building is becoming as consequential as its physical one.

What becomes evident, reading the standards and the failure studies together, is that the profession is being pushed toward a redefinition of the word complete. Complete no longer means built. Complete means built, documented, tagged, tested, taught, and transferable. The building that arrives without its data has not been handed over at all. It has merely changed addresses, carrying its ignorance with it into the owner’s books.

So the claim this evidence supports is sharper than a plea for better paperwork. A building becomes an asset not when its structure is finished but when its information is, because value that cannot be operated, maintained, insured, depreciated, or planned is not value yet, only cost with good lighting. Every project delivers two buildings, one made of concrete and one made of data, and the second decides how long the first gets to matter.

Ibrahim Fawakherji — ArchUp

✦ ArchUp Editorial Insight

The silence in that handover meeting — the question about the chiller warranty that nobody could answer — is not a documentation failure; it is the precise moment at which the structural incentive misalignment of the construction industry becomes spatially visible. The project team was never financially motivated to produce the asset register because their contract measured completion in certificates and keys, not in operational continuity, and the owner who failed to write information requirements into the brief before design began had already, in that omission, committed the building to decades of reactive maintenance, emergency replacement, and premature demolition — a cost that will appear in no developer’s pro forma and in no architect’s fee negotiation, but will be absorbed entirely by the facilities manager, the maintenance budget, and ultimately the occupant, in the form of failed systems, extended downtime, and the slow erosion of the building’s operational value. The article’s most structurally significant argument is its temporal inversion: COBie does not begin at handover, it begins at design, which means that every casual room-numbering decision made in schematic phase, every vague product specification written to accelerate approval, is already an asset management decision with a forty-year liability attached to it — a condition that connects directly to what Who Deteriorates First identified at the residential scale: in both cases, the decisions that determine whether a building can be operated, maintained, and inhabited with dignity are made at the earliest phases of the project by parties who will exit long before the consequences of those decisions fully materialize, and the data gap they leave behind is not an accident but the logical outcome of a procurement model that has never been asked to price the cost of institutional forgetting.