MasterFormat Division 27 – Communications in the Programming & Planning Phase

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

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

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

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

Division 27 Sections Referenced in Programming & Planning

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

• 27 05 00 – Common Work Results for Communications
• 27 10 00 – Structured Cabling
• 27 20 00 – Data Communications
• 27 30 00 – Voice Communications
• 27 40 00 – Audio-Video Communications

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

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

• First-pass specification TOC

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

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

These issues are compounded when Division 27 sections must coordinate with other divisions. This division includes structured cabling, data communications, voice communications, audio-video communications, distributed communication and monitoring, and electronic safety and security. The more trades and disciplines that touch Division 27 scope during programming & planning, the higher the cost of classification errors.

Cross-Standard Connections for Division 27 in Programming & Planning

UniFormat: Division 27 maps to UniFormat D50 (Electrical) subsection—the communications infrastructure that supports building operations and occupant connectivity.

OmniClass: OmniClass Table 23 (Products) classifies cabling, networking, and AV equipment; Table 12 (Spaces) connects systems to the spaces they serve.

During the programming & planning phase, these cross-references ensure that Division 27 specifications align with element-level classifications and lifecycle tags. Teams who rely on low-voltage engineers designing communications systems and it infrastructure planners to maintain these connections manually risk inconsistencies that surface as coordination issues downstream.

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

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