Prefer to listen?
This article is also available as a podcast episode
Few terms in the BIM world generate as much confusion — and as much box-ticking — as COBie. It appears in information requirements, gets demanded on projects that have no use for it, and is delivered as a giant spreadsheet nobody ever opens. Yet the idea behind COBie is genuinely useful. The problem is that it is often required without anyone asking the only question that matters: what is it for, and do we actually need it?
What COBie actually is
COBie — the Construction Operations Building information exchange — is a structured way of capturing and handing over the information a client needs to operate and maintain a building. Rather than the geometry of a BIM model, COBie is concerned with the data about the assets: the equipment, spaces, systems, and components, along with their attributes — who made them, when they were installed, what maintenance they need. It is usually delivered in a defined spreadsheet format, and it is designed to be populated gradually through design and construction rather than assembled at the end. In essence, COBie is a disciplined answer to a real question: how do we hand over asset information in a consistent, usable, digital form?
Where COBie fits in the BIM picture
COBie is one way of structuring the information exchanges that ISO 19650 talks about, and it should flow from what the client actually asked for. If your Employer’s Information Requirements and BIM Execution Plan are clear about the asset information you need and why, COBie becomes a sensible delivery mechanism. If they are not, COBie becomes exactly the kind of expensive box-ticking that gives BIM a bad name — data produced to satisfy a requirement nobody understood.
Do you actually need it?
This is the question too rarely asked. COBie earns its keep when the answers point toward a genuine operational need:
- Will you actually use the asset data? If you operate a computer-aided facilities management or maintenance system that can consume COBie, it is valuable. If the spreadsheet will sit unopened, it is not.
- Is it a client or funder requirement? On many public and larger projects it is mandated — in which case the question is not whether but how to deliver it well.
- Do you have a way to check and use it? COBie data you cannot validate or apply is a cost without a benefit.
For many SME projects the honest answer is that a well-structured set of asset and O&M information matters far more than the specific COBie format. The principle — capture good asset data progressively and hand it over in a usable form — is almost always right. The particular deliverable should follow genuine need, not habit.
The bottom line
COBie is a good answer to a real problem — handing over structured, usable asset information — but only when that problem exists on your project. Decide what asset information you genuinely need and how you will use it, then let that drive whether COBie is the right vehicle. Require it thoughtlessly and you pay for data nobody uses; require it deliberately and it becomes a genuinely valuable handover.
Unsure whether your project actually needs COBie — or how to deliver it well? JC Virtual PMs helps SME clients set information requirements that deliver value, not box-ticking. Get in touch to get it right.


Leave a Reply