The Technology You Don't Own Yet Is Already Making Demands on Your Building

Buildings outlast the equipment inside them by decades. The technology in your facility will cycle through multiple generations during the life of your building — imaging systems, operatory equipment, surgical suites, data infrastructure, security systems, mechanical controls. Each of those cycles creates an opportunity to add capability and a risk that the building won't accommodate it cleanly. The decisions made during design and construction determine which of those two outcomes you get.

This isn't speculative. It plays out in every practice and facility that ages long enough, and the pattern is consistent: what costs almost nothing to address during construction costs significant time and money to fix after the fact.

A dental practice built without conduit rough-ins for intraoral scanning wands now runs cable across countertops and along baseboards. The technology arrived two years after opening, when the walls were finished, the casework was installed, and cutting into either was expensive enough that the owner accepted the workaround instead. The wands work. The installation looks like exactly what it is: an afterthought grafted onto a building that wasn't designed for it.

A medical clinic placed a CBCT imaging unit in a room that shared a wall with a patient consultation area. When the unit was purchased, no one ran lead shielding calculations on that wall during design because the unit wasn't in the original scope. Retrofitting radiation shielding into a finished wall is a significant construction project — open the wall, install lead sheet, close it back up, repaint, reinstall any affected casework. The cost ran five figures. The consultation room was unusable during construction. If the room had been designed with appropriate shielding from the start, the incremental cost would have been a fraction of the remediation.

A veterinary clinic declined to include a generator rough-in and transfer switch during construction. The reasoning was reasonable in isolation: no generator was in the budget, they didn't have a clear need for one yet, they could add it later. Two years after opening, a power outage interrupted a surgery. The practice added "standby power" to the priority list. Adding a generator connection to a finished building means cutting into exterior walls to run conduit, potentially upgrading the panel, and coordinating a transfer switch installation that requires an electrical shutdown. The incremental cost compared to installing the rough-in during construction was substantial. The rough-in would have cost almost nothing when the walls were open.

A light industrial building was designed and built without conduit runs to the production floor. The assumption was that the tenant's operations would be served by overhead drops and that future data infrastructure could be addressed with surface-mounted raceways. Within 18 months, the tenant's production equipment required hardwired data connections at specific floor locations. The surface raceway solution was functional but required ongoing maintenance and created trip hazard issues in a production environment. Underground conduit installed during slab construction would have eliminated the problem permanently for a fraction of the retrofit cost.

The principle underneath all of these examples is the same: conduit is cheap, blocking is cheap, stub-outs are cheap, panel capacity is cheap. None of these rough-ins require you to commit to specific equipment. They require only that you acknowledge the possibility that something will go in that space or require that capability in the future. The question to ask during design — specifically during design, when changes cost nothing but a conversation — is what you might need in five years that isn't in this design.

Power for a milling unit. Blocking in the wall for future wall-mounted displays. Conduit from the electrical room to locations where a camera system might go. A panel with unused breaker capacity rather than a panel sized exactly to current load. A roof penetration sleeved for future mechanical rather than a solid roof that requires a core drill and waterproofing retrofit later. A chase in the wall for a potential future intraoral sensor cable management system. A data conduit from the server room to every operatory, even the ones where it seems redundant today.

These decisions add almost nothing to construction cost when addressed in design. The conduit costs a few hundred dollars per run. The blocking costs nothing if the framing crew is already in the wall. The extra breaker slots in the panel are a marginal upcharge. The rough-in for a generator transfer switch is a few hours of an electrician's time and some conduit.

The retrofit versions of these decisions are categorically different in cost. Opening finished walls requires demolition, patching, painting, and often casework reinstallation. Drilling through concrete slabs requires specialized equipment and creates ongoing penetration points that need to be sealed. Cutting through a finished roof requires waterproofing work that carries its own risk profile. The labor and materials involved in any of these retrofits cost multiples of what the original rough-in would have.

The design team's job is to ask these questions systematically and document the decisions. Not every rough-in makes sense for every project. But the decision to omit should be made deliberately, with an understanding of what it would cost to add the capability later — not by default because no one asked the question.

Buildings are long-term assets. The technology you install in them is not. Designing for adaptability costs almost nothing and pays for itself the first time an equipment cycle doesn't require a construction project to accommodate. Primus handles design and construction as a single integrated process, which means the conversations about future technology happen with the team who will actually build the rough-ins. Learn more at primus-companies.com.