The Approval Trap in Building Technology

A technology project can be approved, funded, and ready for installation while the system selected is already approaching obsolescence. In this episode of Built, Wired & Secured, Alex Morgan examines how slow procurement decisions can become one of the greatest risks in a building technology program.

Michael Harrington, a commercial property manager, and James Rogers, a facilities leader, discuss what happens when access control, network infrastructure, building automation, or HVAC controls remain stuck in committee for months or years. Their central warning is simple: if the approval process takes longer than the useful life of the technology being considered, the organization may be buying yesterday’s solution at tomorrow’s price.

What Is the Approval Trap?

The approval trap occurs when the time required to approve a technology purchase exceeds the period during which that technology remains relevant. A project may begin with a sound needs assessment, appropriate vendor research, and a reasonable budget. But after repeated reviews, postponed meetings, and additional sign-offs, the selected product may be nearing end-of-life, discontinued, or already operating on outdated firmware by the time it is installed.

The guests explain that many organizations still plan around a 10-year technology life cycle. That assumption may have been reasonable in earlier decades, but the refresh cycle for access control, network equipment, and building automation is often closer to five years—and sometimes three. Procurement processes that remain anchored to a 10-year planning model can leave owners buying systems that are outdated halfway through their expected service life.

The Operational Cost of Delayed Decisions

Higher maintenance demands: Facilities teams may be forced to patch, support, and troubleshoot systems that were already behind when they were installed.
Energy inefficiency: Outdated building automation systems can require manual intervention and prevent teams from managing schedules efficiently.
Security gaps: Aging access control platforms and end-of-life firmware can limit support and increase exposure.
Emergency spending: Delayed approvals can turn planned upgrades into urgent projects involving rush fees, overtime, and premium installation costs.
Tenant dissatisfaction: Slow networks, unreliable access control, and poorly performing HVAC systems are visible to tenants and can affect satisfaction and retention.

One example involves an access control system that had reached end of life. Although the need for replacement was known and quotes had been collected, the project was repeatedly deferred. By the time approval arrived, the property was dealing with after-hours service calls and failing locks. The installation had to be completed under emergency conditions, increasing the cost of the project.

Another example involved an HVAC controls upgrade that remained in development for two years. Once the project was finally approved, the vendor had discontinued the product line that had been selected. The team had to return to the beginning of the process, while the building continued through another summer of inefficient cooling.

Strategies for Breaking the Cycle

The conversation focuses on practical ways to make procurement more responsive without removing appropriate oversight.

Map life cycles against approval timelines: If a project typically takes 18 months to approve, begin planning before the current system reaches the end of its useful life.
Create tiered decision thresholds: Routine, like-for-like replacements should not necessarily require the same review process as major transformative projects.
Build fast paths for common refreshes: Organizations can pilot streamlined approval for categories such as access control readers or network switches.
Use pre-approved technology standards: Vetted products and vendors reduce the need to start from scratch every time a replacement is needed.
Measure procurement speed: Approval time should be tracked as a key performance indicator. A two-year approval process is a process problem, not simply a technology problem.

Speed Without Recklessness

The goal is not to rush every purchase or reduce necessary financial scrutiny. The goal is to match the level of review to the risk and scope of the decision. A routine refresh with an established standard should move differently from a major transformation involving new systems, vendors, or operating models.

A pilot can help finance and ownership teams gain confidence in a faster process. By selecting a limited category of routine replacements and monitoring the results, organizations can demonstrate that streamlined approval reduces risk rather than increasing it. Fewer emergency repairs, fewer workarounds, and more predictable project timing provide measurable evidence for expanding the approach.

A Practical Challenge for Building Owners

For the next technology project, document every step between identifying the need and authorizing the purchase. Compare that approval timeline with the remaining useful life of the system being replaced and the refresh cycle of the proposed solution. If the decision process is longer than the technology can remain relevant, the approval process itself is now a capital-planning risk.

The episode’s framework is direct: map technology life cycles, create fast paths for routine work, and measure procurement speed. When decision-making keeps pace with the systems being deployed, technology can support operations instead of becoming another source of maintenance, expense, and risk.

What You Will Learn

Why traditional 10-year technology assumptions no longer fit many building systems.
How delayed approvals create maintenance, energy, security, tenant, and budget problems.
Why emergency installation costs often result from decisions deferred in committee.
How tiered thresholds and pre-approved standards can shorten routine procurement.
Why procurement speed belongs on the same performance dashboard as technology reliability.

When the Approval Process Outlives the Technology

Building technology projects are often delayed for understandable reasons. Owners want financial discipline. Finance teams want complete documentation. Committees want to compare options. Stakeholders want confidence that the selected system will serve the property for years.

Those safeguards are valuable, but they can create a problem when the approval process moves more slowly than the technology market. A project that takes 18 months to receive final approval may be approved on paper while the system at its center is already outdated, discontinued, or approaching the end of vendor support.

That is the approval trap: the point at which the process intended to protect a technology investment begins to undermine it.

The Life-Cycle Mismatch

In the latest episode of Built, Wired & Secured, Alex Morgan explores this issue with Michael Harrington, a commercial property manager, and James Rogers, a facilities leader who has inherited the operational consequences of delayed technology decisions.

The discussion highlights a significant change in building technology planning. Many organizations still think in terms of a 10-year life cycle. That assumption may have made sense for older generations of building systems, but access control, network equipment, and building automation now change much faster. A five-year refresh cycle is common in some categories, and certain systems may need attention after only three years.

If a property takes 18 months to approve a project, that delay consumes a substantial portion of the technology’s useful life. The organization may begin with a current solution and end with a system that is already behind the market before installation is complete.

Obsolescence Is an Operations Problem

Technology obsolescence is not limited to an IT department or a future capital-planning concern. It directly affects the people operating the property.

A building with an outdated access control platform may experience unreliable locks, limited vendor support, and firmware that is no longer current. A property with aging network equipment may struggle with performance and availability. An older building automation system may require someone to visit a mechanical room simply to adjust a schedule. These conditions consume staff time and make routine operations more difficult than they should be.

The effects are also visible to tenants. Slow networks, malfunctioning access control, and inconsistent HVAC performance can reduce satisfaction and create the impression that the property is not keeping pace with its occupants’ needs. A system that was meant to improve the tenant experience can instead become a recurring source of complaints.

There is a financial impact as well. Aging systems often require more maintenance, more energy, and more workarounds. When a planned replacement is delayed until failure becomes unavoidable, the project may shift into emergency mode. Rush fees, overtime, expedited shipping, and limited scheduling options can all increase the final cost.

What Emergency Mode Looks Like

One example discussed in the episode involves an end-of-life access control system. The property team completed a needs assessment, gathered quotes, and presented the project for approval. The request was repeatedly pushed to a future meeting while the old system continued to deteriorate.

Eventually, the locks began creating after-hours service calls. By the time approval was granted, the project could no longer be handled as a carefully scheduled upgrade. The team paid rush fees and overtime to get the installation completed. The delay did not eliminate the need for the project; it made the project more expensive and more disruptive.

A separate HVAC controls example shows another risk. A building team spent two years working toward an upgrade, only to discover after approval that the vendor had discontinued the product line selected earlier. The team had to begin again, and the property endured another summer of inefficient cooling.

In both situations, the core problem was not a lack of awareness. The teams knew what needed to be done. The problem was that the decision process could not keep pace with the condition of the systems or the technology market.

Three Ways to Escape the Approval Trap

1. Compare approval time with technology life cycles

Start by documenting how long a technology project actually takes to move from identification to authorization. Then compare that timeline with the remaining useful life of the current system and the refresh cycle of the replacement category.

If approval requires 18 months, planning cannot begin when the system is already failing. The process must start while the current platform still has enough useful life to support a deliberate transition. This approach reduces the likelihood that an organization will be forced into an emergency purchase.

2. Create different approval paths for different risks

A routine, like-for-like replacement should not necessarily receive the same level of review as a major transformation. Tiered decision thresholds can preserve scrutiny for high-impact projects while allowing predictable refreshes to move more quickly.

That does not mean removing finance or ownership from the process. It means defining in advance which projects qualify for a fast path. An organization might begin with a pilot covering routine access control reader replacements or network switch refreshes. Results from the pilot can demonstrate whether the faster path reduces risk and emergency work.

3. Establish pre-approved standards and measure speed

Pre-approved technology standards can eliminate months of repeated evaluation. When vendors and products have already been vetted against the organization’s requirements, the procurement team is choosing from an approved list instead of beginning the research process again for every replacement.

Procurement speed should also be measured. If it consistently takes two years to approve a technology project, that is a process performance issue. Tracking approval duration, deferrals, emergency costs, and project restarts gives leaders the evidence needed to improve the workflow.

Fast Does Not Mean Careless

The answer is not to rush every technology decision. A poorly chosen system can create years of operational problems, and major projects deserve careful review. The objective is to align the level of scrutiny with the size, complexity, and risk of the decision.

A well-designed process protects the organization without allowing routine work to become trapped in a full-scale committee cycle. It gives finance teams clear controls, gives facilities teams predictable timing, and gives technology leaders a way to plan around real product life cycles.

The best day in operations is the day nobody notices. Reliable systems work quietly in the background, supporting tenants and staff without creating emergencies. That outcome becomes much harder to achieve when the approval process delays action until a system is failing or the selected product is no longer available.

Make Procurement Part of the Technology Strategy

Technology planning is not complete when a refresh schedule is written. The organization must also understand how decisions move through its approval structure. A capital plan that ignores procurement speed is missing a critical part of the risk picture.

For your next building technology project, map every approval step. Record how long each step takes, identify where decisions are deferred, and compare the total duration with the life cycle of the system being purchased. If the process moves more slowly than the technology, the process—not the equipment—may be the project’s greatest risk.

The episode offers a practical starting point: map technology life cycles, create fast paths for routine refreshes, and treat procurement speed as a key performance indicator. For a deeper discussion of how these decisions affect commercial properties, listen to the full episode of Built, Wired & Secured.

The Approval Trap: When Procurement Decisions Outlive the Technology They Were Meant to Buy

Show Notes