OmniClass for STACK

Access licensed OmniClass data through The Construction Standard platform, or request API access to prepare mapped references and supported imports for STACK.

Quick answer

Use The Construction Standard to access licensed OmniClass table-specific classification numbers and titles, then map the references into the STACK workflow your team already uses. Start with platform lookup for individual references, or contact us about API and data access for a larger import or a custom software workflow.

Where OmniClass fits

OmniClass organizes construction information across multiple tables. Start by deciding what you are classifying, such as an element, product, or space, and choose the relevant table. Keep the table identity with the code; an OmniClass product entry is not interchangeable with a specification-section number or an elemental cost grouping.

The standard you choose should follow the information requirement. Using STACK does not, by itself, mean your project needs every CSI classification system. Confirm the classification, edition, and destination field before preparing the data.

Working with STACK

Coordinate takeoff and estimate information with the classifications required by your project. STACK offers estimating and data connections, but this does not establish native support for every CSI taxonomy in every account.

A vendor-supported ERP connection is separate from TCS data access. Preserve your existing cost codes when adding another classification dimension.

Access the data through the platform or an API

The Construction Standard provides licensed access to CSI Dynamic Standards through its web platform. Search for a number or title, review the classification in context, and use the applicable edition when preparing your project references.

For larger workflows, API-style and data access can be made available to companies on request under the applicable plan and terms. Tell us which standard, edition, dataset, and destination you need so the access method and scope can be confirmed. This may support an administrator preparing an import file or a developer building a repeatable data-transfer process.

Platform lookup, bulk data delivery, and API access serve different workflows. Confirm the format and scope for the access route you choose before designing an importer. Your team configures the mapping and transfer into STACK; these pages describe data use rather than a prebuilt TCS connector or automatic synchronization service.

Prepare the data for STACK

Use platform lookup to prepare references or request licensed API access for a custom mapping process. Confirm which estimate fields, import templates, or connected systems can carry the values in your STACK configuration before attempting a bulk load.

A practical preparation sequence is:

  1. Choose the destination. Identify the record type, parameter, reference table, or import template that will hold the classification. Where the software already contains classification data, compare it first instead of creating a second competing list.
  2. Map the fields. Include OmniClass table, classification number, title, edition, and the local object identifier. Preserve code punctuation and leading zeros. Keep the authoritative classification value separate from local record IDs, display labels, and accounting keys.
  3. Prepare the hierarchy. Where the destination supports parents and children, load or identify parent records before linking descendants. Where it only accepts flat references, retain the hierarchy in the source mapping rather than inventing unsupported nesting.
  4. Load a small sample. Use the destination's documented import process, supported API, or configured entry fields. Check required fields, duplicate handling, code lengths, and whether the operation creates records or updates existing ones.
  5. Review the result. Compare the imported numbers and titles with the licensed source and inspect their links to project records. Keep the field mapping and edition with the import so a later update can be reviewed and repeated.

Keep classifications aligned with your project

A code import does not automatically update when a new standards edition is published. Assign an owner for reviewing changes and decide when an existing project should retain its agreed edition. Replacing local identifiers without reviewing their relationships can disrupt estimates, model references, or asset records.

When information moves between specifications, estimates, models, and operations, document how the classifications relate. A work result can contribute to several building systems, and a building system can involve several specification sections. Treat these relationships as mappings to review, rather than assuming that all three standards use the same codes or a one-to-one conversion.

Start with the workflow you already use

Explore OmniClass in the platform for individual references. For a planned import or recurring data feed, review OmniClass API and data access and access options. Share the target software, required fields, and expected update process so the data-access route can be matched to the work.

Sources for this workflow

  • [CSI: OmniClass](https://www.csiresources.org/standards/OmniClass/standards-OmniClass-about)
  • [The Construction Standard: API and data access](https://theconstructionstandard.com/CSI-standards-api)
  • [STACK: documented integrations](https://www.stackct.com/integrations/)

Vendor documentation describes the referenced product or version. Confirm the available fields and transfer tools in your own deployment before preparing a full import.

Access Current CSI Standards

CSI Dynamic Standards provides authorized access to MasterFormat, UniFormat, and OmniClass through a connected, edition-aware platform. Create an account to view access options, or review pricing for organization-wide standards use.

Sources and review scope

Reviewed against CSI standards information, TCS data-access guidance, and the cited vendor documentation where available. Product and version requirements must be confirmed for the destination workflow. Content review date: November 3, 2026.

COMMON QUESTIONS
Access licensed OmniClass references in The Construction Standard platform, then map them to the appropriate fields in your STACK workflow. Use platform lookup to prepare references or request licensed API access for a custom mapping process. Confirm which estimate fields, import templates, or connected systems can carry the values in your STACK configuration before attempting a bulk load.
API-style and data access can be made available to companies on request under the applicable plan and terms. Contact The Construction Standard with the OmniClass dataset, edition, and STACK destination you need. Confirm the delivery format and scope, then use your team's configured import or API process to transfer the data.
OmniClass organizes construction information across multiple tables. Start by deciding what you are classifying, such as an element, product, or space, and choose the relevant table. Keep the table identity with the code; an OmniClass product entry is not interchangeable with a specification-section number or an elemental cost grouping. A vendor-supported ERP connection is separate from TCS data access. Preserve your existing cost codes when adding another classification dimension. Confirm the target fields and supported transfer method with your software administrator.
Updates in STACK follow the transfer process your team configures. Platform lookup and API access provide source data; a prebuilt TCS connector or automatic synchronization is not included by this guidance. Track the standard and edition with each load and review changes before updating existing project records.
CSI Dynamic Standards℠

Access MasterFormat®, UniFormat®,
and OmniClass®

Learn more