Show Notes
The Expansion Room Test
A technology project can be funded, approved, and ready to install—and still create a problem the moment the installation team reaches the building. This episode examines a practical planning question for commercial buildings: does the building have enough expansion room for its next technology layer?
The conversation uses a security and automation expansion as an example, but the framework applies to connectivity, access control, tenant technology, monitoring systems, and other upgrades. The central point is simple: selecting equipment is only one part of the project. A building also needs usable pathways, maintainable technology rooms, dependable power and cooling, clear operating responsibilities, and documentation that remains useful long after installation day.
Why Equipment Fit Is Not Enough
A project can appear straightforward on paper until the team discovers that the only practical cable route passes through an area technicians must access every week. The technology may fit, but the building may not support it in a way that remains workable over time.
That creates a different type of project risk. Instead of a device failing to power on, the organization may face:
- A redesign after approval because an installation route cannot be serviced safely.
- Delays caused by crowded pathways or technology rooms.
- Higher operational burden during every future maintenance visit.
- Longer service interruptions when replacement equipment cannot be reached easily.
- Unexpected conflicts over shared building resources.
The episode encourages teams to stop treating an upgrade as an isolated purchase. Property, facilities, IT, security, and the project lead should have one shared conversation about where the change will live, what it needs, who it affects, and who will operate it.
Physical Capacity Means Usable Capacity
Seeing open wall space or an empty-looking area in a technology room does not automatically mean capacity is available. A room must allow technicians to install equipment, inspect it, label it, remove components, and work safely during a maintenance window.
A section of wall may look open during a walkthrough, but it is not usable capacity if reaching it requires technicians to lean over other equipment or work around blocked access. The same principle applies to pathways. A route shown on a drawing still has to be navigable around existing services, identifiable in the future, and serviceable after the project is complete.
New work that creates an untraceable tangle may add connectivity while reducing maintainability. The discussion emphasizes that reliability begins with disciplined maintenance, and disciplined maintenance depends on giving people a clear and safe way to do their work.
Shared Space Is Not Automatically Available Space
Technology rooms and pathways are often shared resources. Property may see base-building space, IT may see technology space, and security or tenant projects may depend on the same room, pathway, power source, or cooling capacity. An area that appears empty may already be needed for future maintenance, emergency access, or another planned technology phase.
The episode describes this as borrowed capacity. A project may fit today by blocking access, consuming remaining room, or leaving no practical route for future work. The consequences may not become visible until a failure occurs and a technician arrives with a replacement component but has nowhere safe to work.
That is why teams should ask not only whether a resource is physically open today, but also who depends on it, who owns it, and what future work it must still support.
Power and Cooling Must Be Evaluated Under Real Conditions
A room that feels comfortable during a walkthrough is not necessarily ready for additional equipment. A single observation does not explain how the space performs on a warm day, during a cooling interruption, while another team is performing maintenance, or after new electrical load is added.
The same applies to power. The question is not simply whether equipment can be energized. Teams need to consider whether the building can support the added demand with appropriate reliability, maintenance practices, and a recovery plan.
These conditions matter directly to occupants. Tenants may never know what happened inside a technology room, but they notice when access, comfort, availability, or response time changes. A system can operate successfully on day one while consuming the remaining cooling margin or making routine access substantially harder. It is functional, but it has made the building less resilient.
Operational Capacity Is the Capacity You Cannot See
Floor plans do not answer the operational questions that determine whether a new system remains dependable. Every added technology layer creates obligations:
- Who receives and responds to alerts?
- Who knows what normal operation looks like?
- Who performs or coordinates maintenance?
- Who approves changes?
- Who keeps records current?
- Who decides when an issue affects building operations?
If these responsibilities remain vague, the building has added capability without adding dependable control. The project may be technically complete but operationally unfinished.
The discussion also highlights the importance of documentation arriving with the work. Teams need current records showing what changed, where systems are located, what normal operation looks like, and who should be contacted when behavior changes years later. In many cases, that information matters more to long-term reliability than the original project presentation.
A Practical Review Before Installation
The expansion room test is not presented as a replacement for site-specific engineering. It is a practical review teams can use before a project becomes difficult to change.
Start by bringing the right groups together and describing the change in operational terms. What is being added? Where will it live? What does it need? What could it affect? How will it be maintained?
Then physically walk the sequence:
- Where does the material enter the building?
- Where does it travel?
- Where does it terminate?
- Can people safely reach each point?
- What happens during maintenance, not just installation?
Rank constraints by consequence. A documentation gap may be correctable before deployment. A pathway that cannot be serviced or a condition that threatens continuity should receive immediate attention.
Five Questions to Ask Before Approval
- Is there a usable pathway?
- Is there a maintainable room?
- Can power and cooling support the change under real conditions?
- Does the team have the capacity to monitor and maintain it?
- Are ownership, assumptions, and future changes documented?
One additional question ties the review together: what breaks if this goes down? Asking it early helps teams identify dependencies while the plan can still change.
The Decision: Proceed, Revise, or Pause
A useful review ends with a clear decision: proceed, revise, or pause for a deeper assessment. If the team cannot agree on who owns the space, who supports the system, or what happens during a failure, that uncertainty is a project constraint—not something to defer until installation.
The warning phrase is, “We will figure that out during installation.” When that appears, an important dependency has likely not been discussed. Technology should support operations rather than complicate them. If there is no maintenance story, planning is not finished.
Can Your Building Support Its Next Technology Layer?
Technology projects often begin with a clear goal: add security, automation, connectivity, or another capability that improves the building. The equipment is selected, the budget is approved, and the project appears ready to move forward.
Then installation begins, and the building reveals a constraint that was never fully considered. The cable route passes through a space technicians need to access regularly. The technology room has wall space but no safe working clearance. Power is available, but cooling margin is uncertain. An alarm will exist, but nobody has clearly agreed who watches it.
These are not small details. They determine whether a new technology layer becomes a dependable part of building operations or a source of recurring disruption.
A practical way to evaluate this risk is the expansion room test: before approving an installation, ask whether the building has room not only to install the technology, but also to power, cool, access, maintain, document, and operate it reliably.
Technology Must Fit the Building Around It
It is easy to focus on what the equipment can do. A new security or automation system may offer valuable capabilities, and the equipment list may be technically sound. But a building must provide more than a place to mount hardware.
It must provide a workable path from entry point to termination. It must provide a technology room where technicians can safely inspect, label, replace, and service components. It must provide environmental conditions that remain stable beyond one pleasant walkthrough. It must provide enough operational capacity for people to monitor the system, coordinate maintenance, and respond when something changes.
When those surrounding conditions are missing, a project can be functional on installation day and still weaken the building over time. That is the difference between asking, “Can we install this?” and asking, “Can we operate this reliably?”
Visible Space Is Not Always Usable Capacity
One of the most common planning errors is treating visible space as usable space. A clear section of wall may look like an obvious location for new equipment. But can a technician reach it during a maintenance window? Can a component be removed without leaning across other systems? Is there room to label work clearly and inspect it safely?
If the answer is no, that apparent capacity is not truly available.
The same applies to cable pathways. A drawing may show a route, but a route is only useful if people can install it without creating a maintenance trap. It also needs to remain identifiable when another team returns years later to troubleshoot, upgrade, or replace equipment.
Adding new connectivity through a path that becomes tangled or difficult to trace may solve a short-term installation need while creating a long-term service problem. Reliability starts with maintenance, and maintenance starts with clear access.
Shared Resources Create Hidden Dependencies
Technology rooms, pathways, power, and cooling are frequently shared resources. Property teams may view a room as base-building space. Facilities teams may operate the room. IT may depend on it for connectivity. Security systems and tenant projects may also rely on the same resources.
That means an empty-looking section of a room is not automatically unclaimed. It may be needed for future equipment, emergency access, a planned project phase, or routine maintenance.
When a project consumes shared capacity without documenting the decision, it effectively borrows from the next maintenance window or the next emergency. The impact may stay hidden until a technician arrives with replacement equipment and finds there is no safe place to work. At that point, an earlier planning shortcut can become a lengthy service interruption.
Before using shared capacity, teams should clarify who owns the space, who depends on it, what future work is expected, and what access must remain available.
Power and Cooling Require More Than a Walkthrough
A technology room can feel comfortable when a project team visits it and still be a poor candidate for additional load. A walkthrough captures one moment, not the full operating reality of the space.
Teams should look beyond present conditions. How does the room perform on a warm day? What happens during a cooling interruption? How will another maintenance activity affect the environment? Does the proposed equipment consume the remaining cooling margin? Can the electrical environment support the added demand with the expected reliability and recovery planning?
Power planning has the same distinction. It is not enough to confirm that a device can be energized. The more meaningful question is whether the building can support the equipment consistently, maintain it appropriately, and recover when conditions change.
Occupants experience the consequences even when they never see the technology room. They notice when access systems, comfort, availability, or response times are affected. A resilient building protects those outcomes by considering operating conditions before new load becomes part of daily operations.
Operational Capacity Is a Core Infrastructure Requirement
Some of the most important capacity constraints do not appear on a floor plan. A building may have physical room for new technology but lack the people, processes, and records required to manage it.
Every new system creates operating obligations. Someone needs to understand what normal looks like. Someone needs to receive relevant alerts. Someone needs to coordinate maintenance and recognize when an issue affects other building operations. Someone needs to maintain records of changes, dependencies, contacts, and current configuration.
Without that clarity, the project can be technically complete but operationally unfinished.
Shared ownership often becomes visible at the boundaries between teams. Property may own the space. Facilities may manage access and environmental support. IT may operate connectivity. Security may rely on the resulting system. A project team may finish installation and move on, leaving a gap if monitoring, maintenance, change approval, and recordkeeping were never assigned.
Those gaps erode reliability over time. A technician cannot locate a current record. An alarm reaches a team that does not monitor it. A maintenance window is scheduled without understanding another system dependency. Each issue may seem minor in isolation, but together they create avoidable operational risk.
Run the Expansion Room Test Before the Plan Is Locked
The expansion room test is a planning framework, not a replacement for site-specific engineering. It helps teams identify the questions that should be resolved while the project can still be adjusted.
Begin by gathering the people who will be responsible for the result: property, facilities, IT, security, and the project lead. Describe the planned change in operational terms rather than only in terms of equipment.
- What is being added?
- Where will it live?
- What pathway, room, power, cooling, and access requirements does it create?
- What existing systems or teams could it affect?
- Who will monitor, maintain, and document it?
- What happens if it goes down?
Then walk the actual sequence. Follow the path from where material enters the building, through the route it must travel, to the place where it terminates. Confirm that people can safely access each point. Ask what happens during maintenance, not only during installation.
This physical review exposes issues when they are still relatively easy to resolve. It can reveal a pathway that cannot be serviced, a room that cannot be worked in safely, or a shared resource that has not been assigned clearly.
Prioritize Constraints by Consequence
Not every gap carries the same risk. A documentation issue may be repairable before deployment. A pathway that cannot be accessed safely, a room with insufficient environmental support, or an unresolved condition that threatens continuity deserves immediate attention.
Writing down assumptions is equally important. If access depends on a maintenance schedule, record it. If room availability depends on another project, record it. If another technology phase is expected later, record that as well. Documentation turns informal knowledge into an operational reference that remains useful after the project team has moved on.
The review should conclude with a decision: proceed, revise, or pause for a deeper assessment. If there is no agreement about ownership, support, or failure response, that uncertainty is a real project constraint.
Build for the Maintenance Story
The phrase “we will figure that out during installation” is a warning sign. It often means a dependency has not been discussed, not that the dependency will disappear.
Strong building technology planning gives the installation a maintenance story. It establishes how the system will be accessed, serviced, monitored, supported, and documented. That is how teams protect availability, reduce emergency repairs, and make future expansion easier instead of harder.
Before approving the next technology layer, ask whether there is a usable pathway, a maintainable room, adequate power and cooling under real conditions, operational capacity to support the system, and clear documentation of ownership and future change. The answers will shape whether the technology simply works on day one or continues supporting the building for years to come.
Listen to the full Built, Wired & Secured episode for a practical discussion of how property, facilities, IT, security, and project teams can apply this review before a building upgrade is locked in.