Six weeks before CO, the GC is running a punch list. The access control integrator shows up — not for the pre-construction meeting, for the first time — and starts asking questions nobody budgeted answers for.
Where’s the equipment room? What size conduit did you pull to the exterior entries? Is there a dedicated circuit for the access control panels?
The answers are: we didn’t know you needed that, it’s not in the drawings, and the walls are closed.
That meeting happens on more projects than anyone in the industry likes to admit. It isn’t the integrator’s fault, and it usually isn’t the GC’s either. It’s the predictable result of treating low-voltage technology as something that gets sorted out during construction — a procurement item rather than a design discipline.
Low-voltage technology is designed in pre-construction or it’s retrofitted at change-order rates. There is no third option.
What an ICT designer actually does
An ICT designer produces construction documents for a building’s low-voltage technology systems. The scope covers:
- Access control — readers, controllers, locking hardware, software platform
- Video surveillance — cameras, recording infrastructure, VMS, analytics
- Structured cabling — data, voice, cable pathways, telecom rooms
- Distributed antenna systems — cellular signal amplification, public safety radio
- Audio-visual systems — common area AV, conference rooms, amenity displays
- Network infrastructure — switches, wireless access points, rack and stack
The output is a specification and a set of drawings, in the same format as the architect’s and the structural engineer’s. It goes out to bid. Multiple integrators price against it. The ICT designer then reviews the installation for compliance with what was specified.
That last step matters more than it sounds. A specification with nobody checking it is a suggestion. Construction administration is where the drawings get compared against what actually got installed — where you find out that the conduit run took a different path, that the panel landed in a room without adequate cooling, or that a substituted device doesn’t support the credential type the rest of the system was built around. Those are cheap findings during construction and expensive ones after turnover.
An ICT designer produces construction documents for every technology system in the building. The integrator installs against those documents. They are not the same job.
That last distinction is the one that gets collapsed most often, and collapsing it is where the trouble starts.
The sequencing argument — why timing is the whole game
Technology infrastructure is embedded in the building structure. Conduit, cable pathways, sleeve penetrations, equipment rooms, dedicated circuits — all of it is installed during construction, before walls close. Once framing and finishes go in, the infrastructure is fixed.
The window closes in sequence, and faster than most people expect:
- Schematic design — the technology program is established: equipment room locations, riser pathways, major infrastructure decisions. This is where ICT input most directly affects the architectural and structural drawings.
- Design development — system architecture is defined, conduit routing designed, coordination drawings produced for the GC, electrical, and IT scopes.
- Construction documents — the specification is completed and the bid package issued. Integrators price against a defined scope.
- Rough-in — conduit pulled, sleeves installed, backboards mounted. This is the last window for hardwired technology infrastructure.
- Framing and close-in — walls close. The infrastructure that exists is the infrastructure the building has.
- Substantial completion — systems installed, commissioned, tested. Construction administration review catches deviations from the specification.
Each of those phases costs a different amount to change your mind in. That’s the entire argument.
Technology decisions made during schematic design cost design fees. Technology decisions made during construction cost change orders. Technology decisions made after occupancy cost change orders plus construction disruption plus resident impact.
What it costs when technology arrives late
These are the four patterns that show up most often. The ranges are what remediation typically runs, depending on when the gap is discovered.
The equipment room that isn’t big enough. The architect designed a 6x8 telecom room. The ICT scope requires 10x12. Discovered at schematic design, a wall moves — minor disruption. Discovered at rough-in, it’s demolition and reframing: $8,000–$15,000 plus schedule impact. Discovered at commissioning, the equipment simply doesn’t fit, and you’re issuing a change order at the worst possible moment in the job.
The conduit that wasn’t pulled to the exterior entries. Hardwired exterior access control requires 1-inch conduit from the IDF to each door. In base scope before rough-in, that’s roughly $4,200 across six doors. After rough-in but before walls close, premium labor puts it at $7,500–$9,000. After walls close, it’s $2,500–$4,000 per door — $15,000–$24,000 total — plus the conversation about whether you now compromise on wireless locks instead.
The Wi-Fi access points nobody coordinated. The IT contractor designed wireless coverage for units and common areas. The access control scope specifies online Wi-Fi locks for corridors. Nobody put those two facts in the same room. At commissioning, seventeen corridor doors have intermittent connectivity. Resolution: seven additional access points, ceiling patching, network reconfiguration — $12,000–$18,000 plus three weeks of commissioning delay.
The fire alarm interface that was never designed. Mag-locks on stairwell re-entry doors require a fail-safe release interface with the fire alarm system. The fire alarm contractor wasn’t told there would be mag-locks. AHJ inspection reveals the interface isn’t installed. Resolution: $4,500–$7,000, plus a CO delay measured in weeks.
These are not unusual scenarios. They are the predictable results of a technology scope that arrived after the coordination window closed. Every one of them was preventable at design development for a fraction of the remediation cost.
The coordination nobody else owns
An integrator coordinates their own scope. That’s the job, and a good one does it well. But technology systems depend on decisions made across every other discipline in the building, and those cross-discipline decisions have to belong to someone.
- With the architect — door hardware schedules, frame prep, equipment room locations and sizing, wall-blocking requirements
- With the structural engineer — riser sleeve locations through slabs, equipment room floor loading, blocking for heavy wall-mounted equipment
- With the electrical engineer — dedicated circuit requirements, panel capacity, grounding, lighting in telecom rooms
- With the mechanical engineer — cooling loads for telecom rooms, equipment clearances
- With the IT and network engineer — Wi-Fi AP locations coordinated against access control coverage, VLAN configuration, switch capacity
- With the fire alarm designer — mag-lock release interfaces, door holder coordination, fire-rated penetration requirements
- With the GC — sequencing of rough-in, coordination across the low-voltage and electrical scopes, pull box locations
Look at that list and notice how many of those conversations have to happen before anything is installed — and how few of them are in any single trade’s scope.
The integrator installs what they bid. The ICT designer coordinates everything the integrator’s installation depends on — across every discipline in the building — before any of it is built.
How the design fee pays for itself
There’s a procurement argument here that’s separate from the coordination one, and it’s often the one that closes the conversation.
Without an independent specification, the integrator defines the scope. That scope then goes to exactly one integrator — the one who wrote it. There’s no competitive bid, because there’s no document that competing integrators can price against with any confidence the scopes are equivalent.
This is worth sitting with, because owners often believe they are getting competitive pricing. Three integrators submit three proposals, the numbers differ, and the lowest one looks like a win. But if each integrator wrote their own scope, those three numbers describe three different buildings. One included the access points the wireless locks depend on and two didn’t. One priced CO-phase training as a line item and the others left it out. Comparing them is not a bid comparison — it’s a guess dressed up as one.
With an ICT specification, three to five integrators bid the same document, and the owner sees market rate for a defined scope. The comparison becomes apples to apples, and a low number becomes meaningful information rather than a warning sign.
The math on a $1.2M low-voltage scope:
- Competitive bidding typically produces 8–15% lower installed cost than a sole-source integrator relationship
- At 8%, that’s $96,000. At 15%, $180,000.
- An ICT design fee runs 1.5–2.5% of the low-voltage scope: $18,000–$30,000
On a $1.2M low-voltage scope, competitive bidding from a proper specification recovers the design fee before a single panel is mounted. Everything else the ICT designer prevents is free.
Five questions that tell you where you stand
If you want to know whether the technology scope on your project is being managed proactively or reactively, these five questions will tell you quickly.
- “Is there an ICT specification in the construction documents?” If no, the scope is being left to the integrator to define.
- “Who coordinated the technology infrastructure requirements with the architect and MEP engineers?” If the answer is “the integrator will handle that during construction,” the coordination hasn’t happened.
- “What size are the telecom rooms, and who determined that size?” If the architect’s standard room was used without a technology-specific load calculation, the rooms may be undersized.
- “Is there a conduit plan for hardwired exterior access control, and is it in the GC’s scope?” If the access control contractor will “figure that out during installation,” the conduit isn’t in anyone’s scope.
- “What’s the Wi-Fi coverage plan for corridor and amenity doors with wireless locks, and how was it coordinated with the access control scope?” If those two scopes haven’t been explicitly coordinated, connectivity gaps will surface at commissioning.
When to engage
- Ideal — schematic design. Maximum leverage, minimum cost. Equipment rooms can still be sized correctly rather than negotiated for, and riser pathways can be placed where the systems want them instead of where there happens to be room left over.
- Workable — design development. Building configuration is largely set, but construction documents aren’t complete. Most infrastructure decisions are still open, and coordination drawings can still reach the other disciplines in time to matter.
- Late but recoverable — early construction documents, before the GC prices. The architecture is fixed, but a proper specification can still be written, which means competitive bidding is still on the table and the procurement savings are still available.
- Damage control — after construction starts. Works within what already exists. The goal shifts from optimizing the design to catching the gaps before they become change orders, and that’s still worth doing.
Every one of these is a legitimate place to start. They just have different ceilings on what can still be fixed — and the ceiling drops with every phase that closes.
The best time to engage an ICT designer was during schematic design. The second best time is today.
The short version
Low-voltage technology is not a late-stage coordination item. It’s a design discipline — one that requires professional expertise, construction document output, cross-discipline coordination, and a specification that holds the integrator accountable to something written down before the work started.
The building either gets that in pre-construction, or it pays for the absence of it later.
If you’re working through pre-construction scope now and want a second set of eyes on it, start a conversation. If you’re new here, the Brooks Journal explains what we publish and why.