Throughout my career as a low-voltage / ICT technology consultant, I’ve seen projects soar—and others stumble. Surprisingly, the common pitfalls aren’t always about tight budgets, compressed schedules, or even impossible site conditions. More often, the trouble lies in how technology design is (or isn’t) integrated into the project from the start. For architects, interior designers, and project managers, avoiding these mistakes can save months of rework, thousands in change orders, and countless coordination headaches.

Mistake 1: Engaging a Technology Consultant Too Late

This is the most common—and costly—oversight. Architects often assemble their team of civil, structural, MEP, lighting, and landscape consultants right away, but leave technology design off the roster. By the time a low-voltage consultant is engaged—often late in design development—it’s too late to properly integrate telecom rooms, pathways, or infrastructure. The result? Delayed construction packages, incomplete cost estimates, and a flood of late-stage design bulletins.

Takeaway for architects: Bring your technology consultant to the table during proposal and concept design. Early input reduces downstream surprises.

Mistake 2: Skipping Key IT Collaboration Sessions

Hiring a technology consultant early is only half the battle. Too often, technology is deprioritized in design meetings in favor of permitting, budgets, or regulatory approvals. Meanwhile, valuable conversations between the Owner’s IT team, AV team, and the low-voltage consultant never happen—or happen too late. Even if the Owner has design standards, every project has unique site conditions and user needs that require discussion.

Takeaway for architects: Prioritize early workshops with the Owner’s IT and AV stakeholders. These sessions clarify goals, surface challenges, and help produce accurate cost and schedule forecasts.

Mistake 3: Missed FF&E Coordination

Furniture planning directly drives technology infrastructure. Last-minute changes—like swapping lounge seating for dense workstations—can drastically impact electrical loads, poke-thru locations, or telecom pathways. If these updates don’t reach the low-voltage consultant, expect costly field fixes: new core drills, upsized electrical panels, or added network switches.

Takeaway for architects: Finalize furniture layouts early and communicate changes across all disciplines, not just the architect and Owner.

Mistake 4: Unclear Procurement Responsibilities

On many projects, no one can clearly answer: Who is buying what technology —and when? Below is an example of what we see reflected in project documents:

• General Contractor (GC): Typically handles infrastructure (think conduits, IT structured cabling, power).
• Owner’s IT team: Purchases active IT network equipment (switches, access points).
• Owner’s FF&E budget: Often covers AV systems (displays, cameras, speakers, microphones).

While this is common, it’s not the rule for every project. Each project has it’s own procurement profile which dictates budgets, timelines, and scope delineation. Without clarity, items may get double-counted—or worse, omitted entirely.

Takeaway for architects: Document who owns each system early. Aligning budgets and bid packages prevents finger-pointing and keeps construction documents focused.

Mistake 5: Treating the “AV/IT Consultant” as a Catch All

Hiring a technology ICT consultant does not automatically include AV or security design. Just like MEP—where “M” doesn’t mean you automatically get “E” and “P” without scope specificity— ICT technology has distinct specialties that usually fall under one of three main disciplines:

• Telecom Structured Cabling Systems – Includes passive copper and fiber cabling, patch panels, racks, cable management, and pathways.
• Audiovisual Systems – Includes displays, microphones, speakers, cameras, AV control systems, and room scheduling panels. Many devices touch the IT network that the Owner will eventually stand up.
• Electronic Security Systems – Systems that manage facility security, including access control, video surveillance (CCTV), intrusion detection, and alarm monitoring. Typically include door controllers, cameras, servers/recorders, and credential management.

Architects should read the RFP’s carefully for signs that all three disciplines are required as part of the subconsultant team requirements. Each has its own standards, best practices, and coordination needs. A telecom consultant may design the data outlet for a display—but not specify the display itself, its control method, or power/cooling requirements. Many firms can do all 3, but that doesn’t mean they’ve always priced it into their proposal especially during competitive situations.

Takeaway for architects: Confirm exactly which systems your ICT technology consultant is responsible for during the RFP stage—and where additional expertise may be needed.

Final Thoughts

These five mistakes show up on nearly every project in some capacity – but they aren’t the only ones I see. The consequences are predictable: design delays, last-minute scrambles, and unplanned costs. For architects and design professionals, integrating low-voltage design early and intentionally isn’t just about avoiding headaches—it’s about protecting your project’s schedule, budget, and long-term performance.

About the Author

Ernie Beck, CTS-D, WELL AP is a seasoned design professional and Technology Department Leader at Engenium Group, specializing in Building Technology solutions, including Audiovisual, IT, Security, and Smart Building Technologies. With over 15 years of experience in systems integration and design consulting, he leads a team of experts to deliver high-quality, future-ready technology solutions. Since 2021, he has also served as a lecturer at the Harvard Graduate School of Design, focusing on advanced technologies and high-performance buildings.