It’s 6am on a Monday, your phone’s going, and it’s the night security guard telling you that half the third floor is at 28 degrees and the other half hasn’t had heating come on at all. You’re not even dressed yet and you’re already firefighting. By the time you get to site, there are two tenant complaints logged, your ops manager wants an update for the client meeting at 9, and you know — you just know — that the weekend callout engineer bodged something on the AHU that’s now causing a knock-on fault across the whole floor. This wasn’t supposed to be your morning. But it is, because it always is.
This is the reality for the majority of FM teams in the UK. The facilities management industry is worth an estimated £52.5 billion, and yet research consistently shows that most of it operates in reactive mode. A recent IWFM survey found that 73% of FM teams are forced into reactive problem-solving at least once a week, with 43% of those teams subsequently missing SLA targets as a direct result. That’s not an efficiency problem — that’s a structural one. And for buildings with BMS systems that should be preventing exactly these kinds of failures, it raises a serious question: why are we still firefighting?
Reactive maintenance is exactly what it sounds like — something breaks, and you fix it. The boiler trips, you call someone out. An actuator seizes on an FCU, a tenant complains about the cold, and a callout gets raised. There’s no prediction, no prevention, no forward planning. It’s entirely event-driven, and the event is almost always a failure.
Planned maintenance — sometimes called planned preventative maintenance or PPM — is the opposite approach. You schedule regular inspections, checks, and servicing based on manufacturer recommendations, industry standards, and the operational profile of the building. For a BMS, that means quarterly controller health checks, sensor calibration verification, alarm configuration reviews, trend log analysis, actuator stroke testing, and time schedule audits. The goal is to catch problems while they’re still small, long before they become tenant complaints or emergency callouts.
The distinction matters because the BMS is the single system that ties everything else together. If the boiler plant, the AHUs, the FCUs, the lighting, and the metering are all connected through a building management system, then the health of that BMS directly determines how well everything else runs. A poorly maintained BMS doesn’t just fail on its own — it drags everything connected to it down with it.
The financial argument for planned maintenance over reactive maintenance is not subtle. Emergency callout rates in the UK building services sector typically run between £85 and £150 per hour, with minimum charges of two to four hours and out-of-hours premiums of 1.5x to 2x the standard rate. Parts sourced reactively — when a controller has failed and the building is down — carry premiums of 20–40% over the same components purchased as planned spares, simply because of the urgency and the lack of competitive quoting.
But the callout cost is only the visible portion. The real damage from reactive maintenance is in the downtime, the energy waste, and the contract risk. A building running with a failed BMS controller on one floor might have FCUs stuck in full heating mode for days before anyone notices, burning through energy and making the space uninhabitable. Research shows that 60–67% of FM clients have raised formal complaints or threatened contract non-renewal over recurring reactive failures. When your client is questioning whether to renew, the cost of a few planned visits looks trivial by comparison.
Budget pressure makes this worse, not better. Industry data shows that 75% of FM teams identify budget constraints as their single biggest challenge, with 40% reporting actual budget decreases year on year. The natural response to budget pressure is to cut planned maintenance and deal with things as they break — but that’s precisely the cycle that drives costs up. Every pound saved on a skipped quarterly visit gets spent three times over on the emergency callout it eventually causes.
If planned maintenance is so clearly better, why do so many teams stay stuck in reactive mode? The answer isn’t laziness or ignorance — it’s a combination of structural problems that compound on each other.
Staff shortages are the most immediate barrier. The IWFM research found that 68% of FM organisations are unable to recruit and retain the staff they need. When you’re running a building with half the engineering team you need, there simply isn’t the capacity to deliver a proactive maintenance programme. Every hour that could be spent on planned inspections gets consumed by the latest emergency, and the backlog of preventative work grows until it becomes meaningless.
Legacy BMS systems make this harder still. A building running a 15-year-old Trend 963 supervisor with IQ3 controllers that haven’t been firmware-updated in a decade is not set up for proactive maintenance. The trend logging might not be configured. The alarms might never have been properly set up — or they were set up once, nobody maintained them, and now they either fire constantly on nuisance trips or don’t fire at all when something genuinely fails. Without trending data and properly configured alarms, the BMS is effectively blind, and so is the FM team.
Then there’s the compliance gap. Research indicates that 44% of FM teams admit that half or more of their compliance tasks go untracked. Maintenance schedules exist on paper but aren’t followed in practice. PPM tasks get deferred, then deferred again, then quietly dropped. The building’s planned maintenance regime exists as a spreadsheet that nobody updates, a CAFM system that nobody trusts, or a filing cabinet that nobody opens. And when 76% of teams blame siloed systems and poor real-time visibility for their inability to work proactively, you can see how the whole thing falls apart.
Poor contractor communication sits at the centre of all of this. When the FM team, the BMS maintenance provider, the mechanical contractor, and the electrical contractor are all working from different information, with different priorities, and no shared visibility of what’s happening in the building, compliance failures are inevitable. The BMS provider might flag a sensor drift during a quarterly visit, note it in their report, and assume the FM team will action it. The FM team might never read the report, or read it and assume the BMS provider will fix it on their next visit. Six months later, the sensor has drifted so far that the AHU is overcooling the entire floor and nobody knows why.
The UK has clear, well-established standards for BMS planned maintenance, and they’re far more specific than most FM teams realise.
SFG20, the standard maintenance specification for building engineering services, provides detailed task-level maintenance schedules for BMS and controls equipment. SFG20 specifies distinct inspection frequencies for different classes of BMS component — outstation controllers require semi-annual functional testing including I/O verification and communication checks, while field devices such as temperature sensors and valve actuators require annual calibration verification and stroke testing. SFG20 also mandates that BMS software backups are taken and verified at defined intervals, and that alarm parameters are reviewed against the current building operational profile at least annually. These aren’t suggestions — they’re the benchmark that any competent maintenance contract should be built against.
CIBSE Guide M: Maintenance Engineering and Management takes a broader view, setting out the management framework for building services maintenance as a whole. Guide M specifies that maintenance planning for BMS systems should include a defined criticality assessment of all controlled plant, with maintenance intervals set proportionate to the consequence of failure. For BMS-controlled HVAC systems, Guide M recommends that planned maintenance intervals should not exceed six months for critical systems (primary heating and cooling plant controls) and twelve months for non-critical systems (individual zone controllers and standalone sensors). The guide also requires that maintenance records are kept in sufficient detail to support trend analysis of component failure rates — something that almost no FM team actually does in practice.
CIBSE Guide H: Building Control Systems adds the technical layer. Guide H states that a properly specified BMS should include defined maintenance and support arrangements as part of the overall system design, and that the criticality classification of controlled plant should directly inform the response and restoration requirements in any maintenance agreement. In practical terms, that means the chiller plant controller and the meeting room FCU controller should not be on the same maintenance schedule or the same SLA tier — and any planned maintenance programme that treats them identically hasn’t been properly designed.
We saw the cost of reactive maintenance first-hand on the Pinsent Masons project in the City of London — a 16-floor commercial office building where the FCU infrastructure had been left to degrade over years of minimal planned maintenance.
When we were brought in, the building had dozens of FCU controllers that were failing intermittently, creating comfort complaints across multiple floors. The previous approach had been entirely reactive: wait for a tenant to complain, send an engineer, replace the failed unit, move on to the next complaint. The result was a constant cycle of callouts, patchy repairs, and an FM team that was permanently firefighting.
Our approach was fundamentally different. Rather than continuing to react to individual failures, we designed and delivered a proactive FCU replacement programme across all 16 floors. We surveyed every FCU controller, identified the units that were showing early signs of failure through trend analysis and diagnostic testing, and planned a structured replacement programme using Trend controllers. Because the building was fully occupied, all work had to be carried out during weekend-only access windows — which meant the planning, logistics, and sequencing had to be right first time.
The result was a building that went from weekly reactive callouts to a stable, properly maintained control infrastructure with full trending, alarming, and remote visibility. The FM team got their time back, the tenants stopped complaining, and the building’s SLA performance went from consistently missed to consistently met. That’s what the shift from reactive to planned actually looks like in a real building — not in a whitepaper, but across 16 floors of occupied office space with real tenants and real commercial pressure.
A properly structured BMS planned maintenance programme has four key elements working together: scheduled inspections, configured alarming, active trend analysis, and regular review meetings.
Scheduled inspections should follow SFG20 task specifications as a minimum, covering controller diagnostics, sensor calibration, actuator testing, network health checks, alarm configuration reviews, and software backup verification. These should be carried out at defined intervals — typically quarterly for critical plant controls and bi-annually for standard zone controllers — with written reports that actually say something useful rather than just confirming attendance.
Alarm configuration is where most buildings fall down. A BMS with no alarms configured is a monitoring system that doesn’t monitor anything. A BMS with alarms configured but never reviewed is worse — it generates noise that trains everyone to ignore it, so when a genuine critical alarm fires, nobody responds. Good alarm management means a tiered alarm structure with critical, high, medium, and low priorities, defined response procedures for each tier, and a regular review cycle to remove nuisance alarms and add new ones as the building’s operational profile changes.
Trend logging is the foundation of proactive maintenance. If you’re not logging supply and return temperatures, valve positions, fan speeds, and room conditions over time, you have no way of spotting the gradual drift that precedes most BMS-related failures. A sensor that’s reading 2 degrees high today will be reading 5 degrees high in six months, and by then it’s causing comfort complaints and energy waste. Trend analysis catches that drift early — but only if someone is actually looking at the data.
Quarterly review meetings between the FM team and the BMS maintenance provider close the loop. These should cover PPM completion rates, outstanding actions from previous visits, alarm performance (false alarm rate, missed alarms, response times), trend analysis findings, upcoming plant changes that affect the BMS, and forward planning for the next quarter. Without these reviews, the maintenance programme becomes a set of isolated visits with no continuity between them.
If you recognise more than two of the following, your building is operating in reactive mode and the BMS planned maintenance programme either doesn’t exist or isn’t working:
Any one of these on its own is a problem. Three or more together, and you’re not maintaining a building — you’re managing a crisis on repeat.
The shift from reactive to planned BMS maintenance isn’t a luxury — it’s a commercial necessity. The numbers are clear: reactive maintenance costs more, takes longer, damages SLA performance, burns out staff, and puts contracts at risk. Planned maintenance catches problems early, reduces callouts, improves energy performance, and gives FM teams the visibility they need to manage buildings properly rather than lurching from one emergency to the next.
The buildings that get this right aren’t doing anything revolutionary. They’re running structured PPM programmes aligned with SFG20 task specifications, configured BMS alarming that actually tells someone when something needs attention, trend analysis that spots problems before they become failures, and regular review meetings that keep the FM team and the maintenance provider aligned.
If your building is stuck in reactive mode and you want to understand what a properly structured BMS planned maintenance programme looks like for your site, get in touch with us. We work with FM teams across London and the South East to design and deliver maintenance strategies that actually work — not just on paper, but in real buildings with real tenants and real pressure to perform. You can also read our guide to BMS maintenance contracts for more on what to look for in a maintenance agreement, or our overview of preventive maintenance strategies for BMS for the broader approach.
Our team of building automation specialists is ready to help you optimise your building's performance and efficiency.
Get in Touch
