AI Is Only as Reliable as the Standards Behind It

MasterFormat^®, UniFormat^®, and OmniClass^® have served the industry as a shared language for decades. But construction itself never stops moving. New systems, materials, and delivery methods show up every year.

Updates that once arrived every five years or more now come several times a year. MasterFormat 2026 alone added more than 2100 new listings, and UniFormat is expanding beyond buildings into transportation and utility infrastructure for the first time.

The pace is good for the industry, but a PDF edition saved years ago, or a crosswalk built by hand, falls behind with every release. When nobody keeps those connections current, the gaps show up later as rework and manual cleanup.

Most companies close that gap by hand, and that work rarely has a clear owner. As the industry evolves, new standard editions must be created to account for new verticals, and reliable crosswalks become a foundation for apples-to-apples comparisons across specifications, BIM, bidding, procurement, contracting, and maintenance.

Now, we’re seeing more and more companies hitting a breaking point where that manual approach is no longer sustainable.

Where the Risk Starts

Most organizations rely on all three standards, each for a different part of the work. Procurement optimizes for MasterFormat because it’s enforceable in a contract. Precon and cost teams rely on UniFormat because that’s how a building is naturally estimated, system by system, before trades are assigned. Facilities need OmniClass, because they track objects and assets rather than line items.

Each choice is the right one for the department making it. The problem is that no one connects them. Reconciling the standards becomes manual, constant, and harder to sustain. When it isn’t handled at the enterprise level, the owner pays for it.

These costs already show up as:

Padded contingency budgets to cover doubt
Excess RFIs and change orders
Hours spent manually re-keying handover data into CMMS
Staff time spent maintaining spreadsheet crosswalks
BIM models that have to be reclassified by hand before facilities can use them

Take contingency as one example. In The Owner’s Premium, CSI’s Keith Robinson writes that the owner reps he talks to now budget closer to 20% contingency, up from about 3% for most of his career. On a $100 million project, that’s the difference between setting aside $3 million and setting aside $20 million.

Manual spreadsheets with gaps between UniFormat exterior walls, MasterFormat work results, and OmniClass building assets: spaces, products, and properties

The rest tends to surface at the worst possible time, usually in a dispute or a stalled handover. Fixing it typically only happens if the owner asks for it, as it’s rare that any single department downstream has the incentive to build that connection on its own.

The Cost of Reconciling by Hand

We’ve heard from several companies that they’ve built their own crosswalks between the standards, mapping cost codes to contract classifications and facilities records, one line at a time. Reconciling these systems requires significant time and dedicated staff, with no incentive for any one department to take it on alone.

Some of these same teams are now feeding that homegrown mapping into AI tools to tag cost data and specifications faster. That’s the moment a small, years-old inconsistency in a spreadsheet becomes something a model repeats confidently, at scale, across every project, without anyone realizing it’s wrong. An AI system is only as reliable as the data it’s grounded on, and for most owners today, that data is whatever a team built for itself years ago and never had reason to revisit.

None of that prior work needs to be undone. Think about it like building codes: a code edition gets adopted, and that’s what a project is designed and inspected against, sometimes for years as different jurisdictions adopt a new edition on their own schedule. In the meantime, code officials keep publishing interpretations, clarifications, and corrections, without changing the code itself. CDS treats MasterFormat, UniFormat, and OmniClass the same way.

The historicals stay exactly as they are, while CDS delivers ongoing corrections and connections to maintain the data set and enrich it over time.

A Foundation That Outlasts Every Project

Architects, specifiers, estimators, owners, contractors, and facilities managers often already rely on the same classifications throughout company processes. When a dispute lands on someone's desk, counsel ends up working from them too. Keeping them current and connected costs far less than rebuilding them when a problem hits or a team turns over.