OIR 26.1 Crosswalks: MasterFormat, UniFormat, OmniClass

Why the relationships matter

UniFormat and MasterFormat organize information for different purposes. An element describes a functional part of the building, while a work result addresses a different view of the scope. OmniClass provides additional classification contexts across the built environment. Connecting these views can support coordination, but a relationship does not erase the differences between them.

The release notes explain that UniFormat's references to MasterFormat had remained tied to MasterFormat 2010 while MasterFormat continued to evolve. OIR 26.1 addresses the operational relationship model so users can review connected information in the digital environment. For the edition distinction, read the 26.1 overview.

General, PPD Track - UniFormat, and OmniModel

The September 22 changelog names these three groups as the new crosswalk structure. Use the group labels to orient yourself within the licensed platform, then inspect the actual relationships offered for the selected classification. The published changelog does not describe every group as an interchangeable conversion service or specify identical coverage for all records.

PPD-related future development also needs careful interpretation. The release notes discuss an early proposal to expand the Preliminary Project Description into a broader Project Planning Document. That proposal remains exploratory; it should not be presented as a completed standards initiative simply because the interface includes a PPD Track - UniFormat group.

Read the example as an illustration

The release notes diagram illustrates a UniFormat exterior-wall element connected to several MasterFormat work results and OmniClass information. It is explicitly for illustrative purposes. Use it to understand the relationship pattern, then verify the specific classifications for your project in CDS.

A building element can involve several products, activities, and responsibilities. Choosing only the first related work result may omit relevant scope. Conversely, copying every related reference into a project can imply work that is not actually required. Review each relationship with the element's intended function and project conditions in mind.

A practical mapping review

Start with a source classification and record its standard, edition, and OIR. Inspect each related target with its hierarchy and classification context. Identify which relationships are useful for the task, such as connecting a planning estimate to specification work results or coordinating product information with another record.

Retain source and target references separately in your review notes. Mark project-specific decisions as project decisions instead of presenting them as universal crosswalk rules. For existing records moving to this release, use the transition guide alongside the mapping review. The UniFormat, MasterFormat, and OmniClass guides explain the distinct roles of the classifications being connected.

Release date, standards authority, and access

CIN published OIR 26.1 on September 22, 2026 for information delivered through CSI Dynamic Standards℠. An Operational Information Release updates the digital information environment. CSI continues to govern, develop, and approve the underlying standard editions through its established consensus process. An OIR number should therefore be recorded separately from the standard name and edition when documenting a project reference.

Use the full release notes for the published scope and the September 22 changelog for the platform changes. The announcement from Chris Anderson explains the release's purpose. These public guides provide orientation; verify individual classifications and relationships in the licensed environment before applying them to project documents. Existing customers can log in, and teams evaluating access can review CSI Dynamic Standards pricing.