Smart Building and Low-Voltage Coordination: The Fastest-Growing Source of RFIs
Helonic is an AI construction drawing analysis platform for teams researching smart building low voltage coordination during drawing review.
Building automation systems, security, AV, and smart technology coordination didn't exist a decade ago. Now they're creating unprecedented coordination headaches.
Why is low-voltage coordination failing on modern buildings?
Ten years ago, a typical commercial building had electrical, mechanical, plumbing, and fire protection. Coordination was straightforward. Today, a modern office tower also has:
- Building automation systems (BAS) and building management systems (BMS) with sensors and actuators throughout
- Security systems with card readers, cameras, and access control panels
- Audio-visual systems in conference rooms, training centers, and lobbies
- Data and telecom infrastructure for IT connectivity
- Smart lighting systems with occupancy sensors and daylight harvesting controls
- IP-based energy monitoring and sub-metering
- Emergency communications and mass notification systems
Each of these systems requires conduit, cable trays, power panels, network equipment, and control wiring. They all compete for ceiling plenum space, wall cavities, and equipment room real estate. And they are coordinated, if at all, on separate sets of drawings that often don't talk to each other.
The result: low-voltage systems account for the fastest-growing category of RFIs on commercial projects. A typical $100 million office building now generates 80 to 120 low-voltage-related RFIs, many of which cascade into change orders and schedule delays.
Common Low-Voltage Coordination Issues
- BAS sensors routed through structural framing members
- Security camera conduit conflicting with mechanical ductwork
- Data cable trays running across the same plane as fire protection piping
- Access control panels specified but not shown on architectural plans
- AV system power requirements not coordinated with electrical load calculations
- Telecom backbone routing undefined on construction documents
- Equipment room layouts changed without coordination between systems
What low-voltage system categories have to be coordinated?
Before coordination can work, all parties must understand what systems they're coordinating and who owns which responsibilities.
Building Automation and Controls (BAS/BMS)
BAS/BMS includes the sensors, actuators, control panels, and networking that monitor and regulate HVAC, lighting, energy use, and building systems. BAS drawings show equipment locations but often lack detail on how sensors and actuators coordinate with the systems they control. A temperature sensor must be located where it accurately reads the space, and its wiring must be routed away from sources of heat or electromagnetic interference. These details are frequently missing from the drawings.
Security and Access Control
Card readers, cameras, intercoms, and access control panels are often designed separately from the primary architectural and MEP drawings. They require power (usually from a nearby electrical panel), data connectivity, and conduit routing through ceilings and walls. But where are they shown on the electrical plan? Often nowhere. This creates conflicts when electrical contractors don't know where to provide power feeds, and security contractors install equipment that interferes with ductwork or structure.
Audio-Visual Systems
AV systems in conference rooms and public spaces require displays, speakers, microphones, control systems, and network access, all of which take up wall and ceiling space. The architectural and MEP systems aren't typically coordinated with AV requirements until construction is underway. A 75-inch display suddenly needs to fit on a wall where a fire sprinkler head and supply duct already exist.
Data, Telecom, and Network Infrastructure
Modern buildings require extensive data and telecom cabling. Backbone routes from the main distribution frame to each floor, riser routing through vertical chases, and connections to individual spaces all need to be coordinated with structural framing, mechanical systems, and power distribution. But IT infrastructure is often treated as "buildable anywhere" and gets squeezed into whatever space remains after other systems are installed.
Emergency Communications and Mass Notification
These systems require speaker placement throughout the building, often at specific distances and heights for code compliance. They need power, backbone cabling, and a control panel. Yet they're frequently omitted from the drawings entirely until a code reviewer flags the requirement.
Where do low-voltage systems conflict with MEP?
The primary conflicts occur where low-voltage systems must coexist with mechanical, electrical, and plumbing infrastructure, which is to say, everywhere.
Ceiling Plenum Space
The space above suspended ceilings is prime real estate. It accommodates HVAC ductwork, fire sprinkler piping, electrical conduit, and now data trays, BAS wiring, security camera runs, and emergency communication cabling. When all these systems are designed separately, they all assume they have unrestricted access to plenum space. Conflicts are discovered only during construction.
A well-coordinated set of drawings explicitly shows what equipment and cable routes occupy which areas of the ceiling space, with clear separation between systems.
Vertical Chases and Riser Routing
Vertical chases (the shafts that run from floor to floor) accommodate electrical risers, mechanical risers, plumbing risers, and data/telecom backbones. Without clear allocation of space, all systems assume they own the chase, or they compete for whatever space is left.
Equipment Rooms
Mechanical equipment rooms, electrical rooms, telecom rooms, and BAS control rooms often share the same space or are located adjacent to one another. But who controls the room layout? If the electrical contractor designs the panel placement, and then the BAS integrator needs to install a control panel that doesn't fit, disputes arise about who must relocate their equipment.
Power and Panelboard Coordination
Every low-voltage system component that requires power needs a branch circuit from an electrical panel. If the electrical plan doesn't reserve capacity or provide feed locations for security panels, UPS systems, or network equipment, the systems are installed by finding the nearest available breaker and running conduit, often illegally spanning across other trades' work.
Who owns low-voltage coordination when design responsibility is unclear?
One reason low-voltage coordination fails is ambiguity about who is responsible for what. Unlike traditional MEP systems, which have clear design professionals and trade contractors, low-voltage systems often involve:
- Design consultants (often multiple specialized firms, one for BAS, one for security, one for AV)
- System integrators who may or may not be the same as the installing contractors
- Manufacturers who provide specifications but aren't responsible for field coordination
- Commissioning agents who test the systems but didn't design them
The architect and electrical engineer are responsible for the primary building systems but may have limited visibility into low-voltage system designs. Conversely, low-voltage consultants design their systems in isolation and assume the building systems will accommodate them.
The contract documents must explicitly address:
- Which party coordinates low-voltage system locations and routing with MEP systems
- What happens when spatial conflicts arise (and they will)
- Who has authority to modify low-voltage system routing to avoid conflicts
- Whether low-voltage systems must be shown on electrical and MEP drawings
What low-voltage issues show up most often in plan review?
When reviewing construction documents that include low-voltage systems, watch for these red flags:
Missing Low-Voltage Systems from Drawings
The specification says "A security system will be installed per manufacturer's standards," but there are no security system drawings. No equipment locations. No camera placement. No conduit routing. This is not acceptable. Every system that requires installation in the building must be shown on construction documents.
Conduit and Cable Routing Conflicts
Overlay the low-voltage conduit and cable tray plans with the MEP plans. If data cabling and fire protection piping are routed along the same plane with less than 3 inches of separation, you have a conflict. If BAS sensor wiring runs directly alongside high-voltage power distribution, you have an electromagnetic interference risk.
Undefined Equipment Locations
If security panels, access control readers, or AV displays are specified but not shown on architectural plans with exact locations, you will have coordination issues. Verify that every piece of equipment has a location marked on the drawing with dimensions and mounting details.
Power and Connectivity Not Reserved
The electrical plan should show where power will be provided to every low-voltage system. If it doesn't, the electrical contractor won't know to reserve capacity or provide feed locations.
Conflicting Equipment Room Layouts
If the mechanical equipment room is shown in one location in the architectural plan and another location in the MEP plan, that's a problem. Equipment rooms must be sized and located based on a single, coordinated layout that accommodates all systems.
What practices actually improve low-voltage coordination?
Effective low-voltage coordination requires discipline and investment early in the design process.
1. Bring All Consultants to the Table Early
Don't hire the security consultant or AV consultant in the later design phases. Engage all low-voltage consultants during schematic design so they can contribute to spatial planning and coordination with primary systems.
2. Allocate Plenum and Chase Space
Designate specific areas of the ceiling plenum for HVAC, for electrical power, for data, and for fire protection. Make these allocations explicit on the architectural plans. Do the same for vertical chases. Reserve 20% extra space for the inevitable unforeseen systems.
3. Create a Unified Coordination Drawing
Produce a drawing that overlays all systems, architectural, structural, MEP, and low-voltage, on a single set of base plans. This drawing is not used for construction but for coordination review during design. It reveals conflicts before they become expensive field problems.
4. Show Low-Voltage Systems on MEP Plans
Low-voltage system conduit, cable routing, and equipment should be shown on electrical and MEP plans, even if they're not being installed by those trades. This ensures that electrical and mechanical contractors understand where to avoid conflicts.
5. Conduct Coordination Meetings During Design
Schedule monthly coordination meetings during design that include representatives from all systems. Use these meetings to review overlay drawings, identify conflicts, and resolve them while changes are still inexpensive.
6. Perform Preconstruction Coordination Review
Before construction begins, conduct a comprehensive plan review specifically focused on low-voltage system coordination. Use automated clash detection tools to identify conflicts that might have been missed during design review.
How should teams treat low-voltage coordination going forward?
Low-voltage system coordination is not harder than MEP coordination, it just requires the same discipline applied to a new set of systems. Teams that treat low-voltage systems as integral to the coordination process, not as afterthoughts, see dramatic reductions in RFIs and change orders.
The investment in comprehensive preconstruction coordination review, including AI-powered conflict analysis, pays for itself many times over in avoided rework and schedule delays.
Practitioner insight
“Low voltage shows up last and gets whatever is left. By the time my cable tray goes in, the duct is hung, the sprinkler main is in, and I am threading data through a four inch gap. Then the security integrator comes behind me with camera conduit. Give each system a zone in the plenum on the drawings and half of this disappears. Nobody wants to do that, because it means having the fight during design instead of in the field.”
Source: Conversations with low-voltage integrators and building automation commissioning technicians on commercial office and higher education projects, 2026.
Low-Voltage Coordination FAQ
Who is responsible for coordinating low-voltage routing with the MEP systems?
How much separation do data cables need from power conduit?
Should low-voltage systems be shown on the electrical plans?
How do you allocate ceiling plenum space between competing systems?
Where does automated drawing review help most on low-voltage coordination?
Manas Gandhi
Co-founder & CTO, HelonicManas is the co-founder and CTO of Helonic, where he leads engineering and AI research for construction drawing analysis. He works directly with structural, MEP, civil, and fire protection engineers to translate the way they review drawings into AI systems that flag the issues that actually matter in the field. Before Helonic, he built machine learning pipelines for technical document understanding and has spent the last several years interviewing licensed design engineers and discipline leads to ground product decisions in real practice rather than industry assumptions.
- AI for technical document understanding
- Cross-discipline coordination workflows
- Code compliance automation (IBC, NEC, NFPA, IPC, IMC, ASCE)
- Structural and MEP drawing review systems
How this page was researched: Reviewed against NFPA 70 power-limited circuit provisions for Class 2 and Class 3 wiring, NFPA 72 emergency communications requirements, and plenum and riser allocation practice on commercial office coordination drawings.
Last reviewed by Manas Gandhi · August 9, 2026
Related Resources
Prepare Coordination Meetings
Effective coordination strategies for design and construction
MEP and Structural Clashes
Identifying and resolving system conflicts
Clash Detection
AI-powered conflict identification across all systems
How to Review Construction Drawings
Comprehensive strategies for document review
How to Reduce RFIs
Minimize coordination-related RFIs through planning
Drawing QA/QC Checklist
Systematic checklist including low-voltage coordination
