MasterFormat Division 32 – Exterior Improvements in the Programming & Planning Phase

Start with [CSI MasterFormat Division 32: Exterior Improvements](/MasterFormat-division-32-exterior-improvements) for the broad scope and coordination boundaries. This page addresses the narrower programming & planning phase intent.

Division 32 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 32 specifically, the programming & planning phase involves focused work on exterior improvements 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 32 during programming & planning include:

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

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

Division 32 Sections Referenced in Programming & Planning

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

• 32 10 00 – Bases, Ballasts, and Paving
• 32 12 00 – Flexible Paving
• 32 13 00 – Rigid Paving
• 32 14 00 – Unit Paving
• 32 30 00 – Site Improvements

These sections define the scope boundaries, product requirements, and execution standards for exterior improvements 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 32

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

• First-pass specification TOC

Every deliverable that references Division 32 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 32 During Programming & Planning

• Scope definitions in prose that can't be traced forward — When this occurs with Division 32 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 32 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 32 references during programming & planning, the result is rework, coordination failures, or documentation that contradicts the project manual.

These issues are compounded when Division 32 sections must coordinate with other divisions. This division includes flexible paving, rigid paving, curbs and gutters, unit paving, site improvements, planting, irrigation, and fences and gates. The more trades and disciplines that touch Division 32 scope during programming & planning, the higher the cost of classification errors.

Cross-Standard Connections for Division 32 in Programming & Planning

UniFormat: Division 32 maps to UniFormat G (Sitework)—the exterior improvement elements that complete the site.

OmniClass: OmniClass Table 23 (Products) classifies paving materials, plants, and irrigation equipment; Table 12 (Spaces) includes exterior spaces.

During the programming & planning phase, these cross-references ensure that Division 32 specifications align with element-level classifications and lifecycle tags. Teams who rely on landscape architects designing exterior spaces and paving and site work contractors to maintain these connections manually risk inconsistencies that surface as coordination issues downstream.

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

CSI Dynamic Standards includes Division 32 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 32 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 32 references in every deliverable stay accurate and consistent with the rest of the project manual.