MasterFormat Division 34 – Transportation in the Programming & Planning Phase

Start with [CSI MasterFormat Division 34: Transportation](/MasterFormat-division-34-transportation) for the broad scope and coordination boundaries. This page addresses the narrower programming & planning phase intent.

Division 34 Activities During Programming & Planning

The programming and planning phase sets the foundation for every subsequent project decision. Capturing Owner Project Requirements (OPR), Basis of Design, and early scope definitions in UniFormat elements ensures design intent is structured data that estimators, specifiers, and builders can use—not just prose that requires interpretation. For Division 34 specifically, the programming & planning phase involves focused work on transportation scope, products, and execution requirements. Use relationships between UniFormat and MasterFormat to surface likely specification sections as systems firm up. Generate first-pass Tables of Contents and assign section owners early.

Key activities for Division 34 during programming & planning include:

• Surface likely MasterFormat sections as building systems are defined — as it relates to transportation sections and the products, methods, and quality standards they define
• Generate first-pass TOC and assign specification section owners — as it relates to transportation sections and the products, methods, and quality standards they define

Each of these activities requires current, accurate Division 34 section numbers. When teams reference outdated or incorrect section numbers during programming & planning, the errors propagate into every subsequent phase.

Division 34 Sections Referenced in Programming & Planning

The following Division 34 sections are commonly referenced during programming & planning work:

• 34 10 00 – Guideways/Railways
• 34 20 00 – Traction Power
• 34 40 00 – Transportation Signaling and Control Equipment
• 34 70 00 – Transportation Construction and Equipment
• 34 80 00 – Bridges

These sections define the scope boundaries, product requirements, and execution standards for transportation work. During programming & planning, these section references appear in first-pass specification toc and must be consistent with the project manual.

Programming & Planning Deliverables That Reference Division 34

Project teams produce or consume these deliverables during the programming & planning phase, many of which directly reference Division 34 sections:

• First-pass specification TOC

Every deliverable that references Division 34 must use current section numbers and titles. A single incorrect section reference in a programming & planning deliverable can trigger RFIs, scope disputes, or change orders during construction.

Common Issues with Division 34 During Programming & Planning

• Scope definitions in prose that can't be traced forward — When this occurs with Division 34 references during programming & planning, the result is rework, coordination failures, or documentation that contradicts the project manual.
• No elemental structure for early cost modeling — When this occurs with Division 34 references during programming & planning, the result is rework, coordination failures, or documentation that contradicts the project manual.
• Design intent lost between programming and schematic design — When this occurs with Division 34 references during programming & planning, the result is rework, coordination failures, or documentation that contradicts the project manual.

These issues are compounded when Division 34 sections must coordinate with other divisions. This division includes roadways, railways, bridges, and aviation systems. The more trades and disciplines that touch Division 34 scope during programming & planning, the higher the cost of classification errors.

Cross-Standard Connections for Division 34 in Programming & Planning

UniFormat: Division 34 extends beyond building-focused UniFormat into infrastructure-scale transportation elements.

OmniClass: OmniClass Table 11 (Construction Entities) classifies transportation infrastructure as built environment entities.

During the programming & planning phase, these cross-references ensure that Division 34 specifications align with element-level classifications and lifecycle tags. Teams who rely on transportation engineers and designers and bridge engineers specifying structural systems to maintain these connections manually risk inconsistencies that surface as coordination issues downstream.

How CSI Dynamic Standards Helps with Division 34 in Programming & Planning

CSI Dynamic Standards includes Division 34 as part of a connected, edition-aware classification system—licensed through The Construction Standard. Built for real project work from concept to closeout and beyond, it provides always-current Division 34 section numbers and titles, governed cross-references to UniFormat and OmniClass, and edition tracking that prevents programming & planning deliverables from referencing obsolete classification data. For teams working through the programming & planning phase, this means Division 34 references in every deliverable stay accurate and consistent with the rest of the project manual.