Your building knows which rooftop unit was replaced in 2019. It knows the warranty on the elevator motor expires in four months. It knows the fire suppression system on the third floor was specified by a manufacturer whose support line now rings to a disconnected number.

The problem is, no one asked. And even if they did, the answer is buried somewhere between a filing cabinet, a SharePoint site that got migrated twice, and the memory of a facilities manager who retired last spring.

The system of record that few trust

Facilities management platforms were built to fix this. CMMS tools promise a single source of truth for building operations: work orders, preventive maintenance schedules, equipment records, service history.

And to be fair, they do a reasonable job at the operational layer. Scheduling maintenance, tracking open work orders, managing vendor relationships.

But most CMMS implementations are incomplete, outdated, or both. The data inside is only as good as what someone entered on day one. And in most cases, day one looked like this: the project closed months behind schedule, a contractor handed over boxes of binders, and someone in the facilities department was told to get it into the system. Some of it got in. Most of it didn’t. Equipment schedules were partially loaded. O&M manuals were scanned as flat PDFs with no metadata. As-built drawings reflected design intent, not what was actually installed.

Every maintenance decision since then has been built on that incomplete foundation.

The half-life of building data

Building documentation decays from the moment it’s created. Equipment gets replaced without records getting updated. A renovation changes the HVAC zoning on two floors but the drawings in the CMMS still show the original layout. A manufacturer discontinues a product line and the warranty contact in the system now leads nowhere.

Facilities teams know this. They work around it constantly. They build personal knowledge in their heads. They keep paper files at their desks. They develop relationships with local vendors who remember the install because they did the work.

This institutional knowledge is extraordinarily fragile. When that facilities manager retires, or when a portfolio changes hands, or when a new director asks “what kind of chiller do we have in Building C”, the answer is often silence. The CMMS has a record. But few people trust it.

Why closeout is the root cause

The FM platform gets blamed for bad data. The actual problem happened years earlier, during construction.

Construction is the only moment in a building’s life when organized, accurate, complete information exists about every system installed. Every trade knows exactly what they put in. Every material has documentation. Every piece of equipment has specs, warranties, and installation records.

The moment construction ends, that information begins to scatter. Subcontractors move to the next job. Project managers archive their files. The general contractor closes out the project and moves on.

By the time the binders reach the facilities team, they’re already incomplete. And no party had a financial incentive to make them otherwise, the contractor’s incentive ended at substantial completion, and the facilities team had no leverage to require better.

What better looks like

The buildings that get managed well operationally share one characteristic: someone decided, before construction started, what information had to be captured and in what form.

Not a closeout checklist. A data standard. Specifying that equipment records include manufacturer, model number, serial number, warranty terms, maintenance intervals, and contact information for the manufacturer’s support line, and that these records be delivered in a format the facilities management system can actually ingest, not as a scanned PDF.

That specification, written into the construction contract before a single drawing is issued, changes the economics of information capture. The contractor who knows they won’t receive final payment until the data standard is met has a different relationship to closeout documentation than the contractor who knows a box of binders will satisfy the requirement.

The asset your building represents

You’ve spent tens of millions of dollars constructing an asset that will serve your organization for decades. The information that tells you how to maintain, operate, and eventually renovate that asset has a value proportional to the building itself.

Treat it that way. Require complete, queryable, portable data as a contract deliverable. Get your facilities team involved during design to specify what they’ll actually need. Build the data standard before you build the building.

Your building already knows things. The question is whether you’ll be able to ask it.