-
ENTERPRISE INTELLIGENCE
OPERATIONAL ORCHESTRATION
RESILIENT INFRASTRUCTURE
TALENT & CAPACITY
-
Technologies
90% of large infrastructure projects go over budget. The average overrun is 28%. The leading cause isn't materials or labor — it's coordination failures that begin the moment ICT is deferred to construction documents. This guide, written from an RCDD perspective, shows architect firms exactly where those failures originate and how to stop them at the design stage.
of Enterprise ICT Execution
Design Through Closeout
Professionals Hold This Credential
BICSI Compliant
of large infrastructure projects go over budget — average overrun of 28% (Flyvbjerg Research)
in annual U.S. construction costs directly attributed to coordination failures and rework
of ICT-related change orders: information not shown on architect CDs at time of bid
Electrical, MEP, Fire Alarm, AV, Security & Access — all have ICT coordination touchpoints that create conflicts when no RCDD is involved
When telecommunications infrastructure first appears at the CD phase, architectural layouts are frozen, MEP routing is locked, and structural drawings are complete. There is no room to integrate ICT cleanly. Every conflict becomes a change order. Every change order becomes a schedule risk.
Telecommunications rooms designed without rack clearance, PDU space, cooling capacity, and cable management room cannot serve their function at occupancy — let alone at the 10-year mark. Retrofitting is expensive. Relocating is worse. And both are avoidable.
Conduit and cable tray designed at full fill ratios on day one has no room to absorb moves, adds, and changes. Within 18 months of occupancy, most buildings exceed their original device count. Pathways that cannot expand drive renovation costs on projects that should have been closed.
Modern enterprise environments require AP densities 3–5x what was standard a decade ago. Wi-Fi 6E and 5G coexistence requirements affect ceiling coordination, structural attachment, and power allocation in ways legacy specifications never anticipated.
Without a qualified ICT designer, every trade interprets scope differently. The result is inconsistent labeling, inadequate documentation, field deviations from design intent, and post-occupancy corrections that arrive as client complaints.
Why the information gap between design intent and what appears on CDs at bid is the single most expensive and preventable problem in ICT infrastructure.
A full coordination map: Electrical (Division 26), Security & Access (Division 28), AV Integration, Fire Alarm/Life Safety, and MEP — with the specific touchpoints that generate conflicts when RCDD oversight is absent.
Design Consultation (SD through DD), Specification & Documentation (DD through CDs), and Field Execution & Closeout (CA through Occupancy) — with specific deliverables at each stage.
From telecom room sizing for 10-year growth to pathway reserve capacity to RCDD assignment thresholds — the decisions that cost nothing to make correctly at SD and a great deal to fix in the field.
What the RCDD designation requires, what fewer than 1 in 20 ICT professionals hold it, and why it is the single most effective investment on any project over 5,000 SF.
ICT is no longer limited to data and voice. It now connects life safety systems, access control, wireless coverage, building security, AV integration, and operational technology. Every one of those systems has a physical layer dependency and every one of those dependencies is shaped by decisions made during schematic design.
When those decisions are left to late-stage coordination or delegated to the lowest bid, they don't disappear. They reappear as RFIs, change orders, post-occupancy failures, and client callbacks that outlast the project itself.
The standard has shifted. The expectation has not.
the specific design-stage decisions that generate ICT change orders and how to prevent them before CDs are issued
so your team knows exactly where ICT intersects with Electrical, MEP, AV, Fire Alarm, and Security before conflicts appear in the field
the credential explained plainly, the threshold for when it applies, and what it delivers at each project phase
what complete ICT closeout documentation looks like and why it protects design intent long after occupancy
“Every change order we have ever seen tied to ICT infrastructure had the same root cause: the right questions were not asked at the right stage of design. An RCDD in the room during schematic design costs a fraction of what it costs to fix the problem in the field.”
-Zachary Walton, RCDD | ICT Infrastructure Engineering Manager, V-Soft Consulting