Topic

Managing Project Specifications for Design-Build Projects

On a design-build project, the same team writes specifications, prices the work, and builds it—often at the same time. CSI standards provide an organizing framework for keeping project information connected from the owner’s first requirements through operations. CSI does not sell specification-writing software.

Keep the Preliminary Project Description active throughout the project

A Preliminary Project Description (PPD), organized by UniFormat, can provide a consistent structure throughout the project. In this approach, the team continues updating it as requirements develop into design decisions, specifications, and construction information.

1. Owner's Statement of Requirements (OSoR)

The owner states performance requirements for each UniFormat element (substructure, shell, interiors, services, etc.). It describes what each system has to do, not how. On a design-build project, this forms the core of the request for proposals or criteria package.

2. Proposals in the same structure

Proponents respond element by element using the same UniFormat outline. The owner can compare proposals against a common structure and identify where each response meets or departs from the Owner’s Statement of Requirements.

3. Basis of Design / preliminary documentation

The selected proposal becomes the basis for the PPD: a Basis of Design narrative, organized by UniFormat, that records what has been decided and what remains open.

4. Design development and construction documents

As the design develops, each UniFormat element is crosswalked to MasterFormat sections and written up as specifications using SectionFormat/PageFormat. Continue updating the PPD so that specified products can be traced back to the owner requirements behind them.

5. Bid packages and contract formation

Trade packages are put together from the MasterFormat sections.

6. Contract administration

The project team logs submittals, RFIs, substitutions, and changes against the same elements, keeping the reasoning behind decisions connected to the project requirements.

7. Closeout and operations

Carry the UniFormat, MasterFormat, and OmniClass classifications into the final project record to support asset tagging, operations and maintenance documentation, and downstream data requirements.

A method built on CSI standards

Using the PPD throughout the project is an expanded application of PPDFormat known as Progressive Project Documentation. It is a developing method built on CSI standards, not an official CSI standard or packaged product.

CSI products that support this

  • The standards themselves: MasterFormat, UniFormat, PPDFormat, SectionFormat/PageFormat and OmniClass. The MasterFormat 2026 Edition includes built-in cross-references between MasterFormat, UniFormat and OmniClass, which is exactly the crosswalk this approach depends on.

  • Practice guides: Project Delivery, Construction Specifications, and Construction Contract Administration.

  • Education and certification: CDT for the whole project team, CCS for spec writers, CCCA for contract administrators, and CCPR for product reps.

How CDS supports Progressive Project Documentation

CSI Dynamic Standards provides crosswalks between UniFormat and MasterFormat numbers and titles. These relationships support the development of a PPD-based document organized by UniFormat.

CDS keeps each UniFormat element linked to its MasterFormat sections and OmniClass classifications through the MasterFormat 2026 cross-references and CDS's crosswalk capability.

Discuss your project

Tell us whether you’re the owner or the design-builder, what kinds of projects you work on, and how you manage specifications today.

Contact Us