Published on :
June 19, 2026
by
Anisha Bhattacharjee
One of the healthcare facilities we work with had been operating under our approach to proactive asset governance for several months when an Air Handling Unit on site began showing something worth paying attention to.
No alarm had triggered. No ticket had been raised. To anyone looking at the system, it was working fine.
And yet a decision was made to intervene, to dispatch, inspect, and act. In a budget review, that's exactly the kind of spend that gets questioned. Why was this necessary? What was actually wrong? If nothing had failed, what were we paying for?
The answers exist. Speed oscillation swinging between 0 and 100%, airflow and pressure signals behaving inconsistently with what that asset should have been showing under those conditions, the diagnostic picture was there at the moment the decision was made, and it stayed there. The inspection confirmed an emerging mechanical issue. In a continuously occupied facility, an unplanned failure carries a different cost entirely, contractor rates, downtime, operational disruption, and none of that happened.
That's the case FM teams rarely get to make in a budget room. Not because the reasoning wasn't sound, but because the reasoning was never captured.
That's what a decision layer changes. But to understand why it matters, it helps to look at what most FM teams are working with today.
CMMS and BMS do exactly what they were designed to do. CMMS records activity, work orders raised, engineers dispatched, tickets closed. BMS monitors building conditions, temperature, humidity, equipment status, and triggers alerts when thresholds are breached. Both layers are necessary and they work.
But they record responses, not reasoning. In a reactive FM environment, the sequence is: something deteriorates past a threshold, a response is triggered, the work gets done, the ticket gets closed. What led to that point, the asset condition before failure, the decisions that were considered and deferred, the moments where earlier intervention was possible, none of that is captured.
So what the current system produces, over time, is a detailed record of what happened. And almost no record of why.
According to the SFG20 State of Facilities Management Report 2025, 75% of FM professionals cite budget constraints as their primary pressure, with 40% reporting an actual decrease in budget over the past year. Finance teams are no longer reviewing maintenance spend at a high level. They're going line by line, and they're asking for justification.
FM teams are walking into those conversations with records that show what was done. Not why it needed to be done.
When that gap can't be bridged, the pattern is predictable. Budget gets cut because the evidence isn't there to defend it. Interventions get deferred. Assets deteriorate further. Reactive spend climbs, and that climbing reactive spend becomes the argument against FM in the next budget cycle. The decisions that produced this outcome were never recorded, so the cause is invisible and the cost looks like mismanagement.
The questions finance asks are reasonable: why was this decision taken when nothing had visibly failed? If you hadn't intervened, what would it have cost? Are decisions actually getting better over time? Each one points to the same absence.
The reasoning behind the decision was never captured. Memory is not evidence. And it doesn't survive a budget review.
Take the AHU case. The unit showed no alarm, no failed ticket, nothing that would have triggered a response in a conventional system. What existed was a diagnostic picture, speed oscillation, airflow inconsistency, pressure behaviour that didn't match what that asset should have been showing. A recommendation was made with the reasoning attached. The decision to act was taken, documented, and the outcome recorded.
That's not how most FM decisions work today. Most are made under pressure, in the moment, by people who know their assets well, but without a system designed to capture what was seen, what was weighed, and what was decided. The reasoning lives in someone's head. The work order records the action. And when finance asks why, there's nothing to show them.
A System of Decisions changes that by sitting above CMMS and BMS and capturing what those systems were never built to hold. Every recommendation comes with diagnostic context, what the asset was showing, what the risk trajectory looked like, and what the cost of waiting looked like if that decision had been deferred. Every deferral keeps the asset under active observation rather than dropping it until the next scheduled check. The decision trail is continuous, not reconstructed after the fact.
Because every decision is recorded alongside its expected outcome, it becomes possible to track whether the work being done is actually producing results. That's what the Assurance Score measures, not how much maintenance was completed, but whether decisions are translating into better asset condition over time.
The results are visible in the organisations that have introduced this layer.
One FM service provider working with Xempla across Health and Care PFIs in the UK saw reactive callouts drop by 30 to 40%, without replacing or changing their existing tools.
For one of India's fastest-growing PE-backed FM players, also working with Xempla, the Assurance Score moved from 30% to 85%, without adding central headcount, and that improving trajectory became the evidence base for every budget conversation that followed.
Without a decision record, FM teams walk into budget reviews with activity logs and no narrative. Spend gets questioned, context can't be provided, budget gets cut, and the cycle starts again.
With one, every decision is documented at the moment it was made. When finance asks why money was spent, whether on an asset that appeared fine, an intervention that looks premature, or a deferral that later escalated, the answer is already there. The diagnostic signals, the risk of waiting, the cost that was avoided. Not a summary prepared for the meeting. A record that existed before the question was ever asked.
That's what decision governance makes possible. And that's what FM teams have not had until now.
Good decisions have always been made. The problem was never the intent, it was that nothing was built to prove it.
That's changing. And the teams that move first won't just defend their budgets better. They'll be the ones finance starts to trust.
Most FM systems record the work that was completed, but not the reasoning behind why it was necessary. When finance reviews a budget line, they often see a work order or contractor invoice but not the asset signals, risk indicators, or avoided costs that led to the decision. Without that context, even the right intervention can appear unnecessary.
A work order records what action was taken, such as an inspection, repair, or replacement. A decision record captures why that action was taken, including asset condition, diagnostic signals, risk assessment, alternative options considered, and the expected outcome. One records activity; the other records reasoning.
Proactive maintenance becomes easier to defend when every intervention is linked to evidence. By capturing asset behaviour, risk trends, expected consequences of delay, and actual outcomes, FM teams can demonstrate not only what they spent, but what costs, failures, and disruptions they avoided.
A System of Decisions is a layer that sits above existing tools such as CMMS and BMS. It captures the diagnostic context, recommendations, decisions, deferrals, and outcomes associated with asset management. This creates a continuous record of why decisions were made and whether they delivered the expected results.
Decision governance provides evidence before questions are asked. Instead of relying on memory or retrospective explanations, FM teams can show the signals that triggered a recommendation, the risks of delaying action, and the outcomes achieved. This allows budget discussions to focus on value delivered rather than simply costs incurred.
Paragraph
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript
© Xempla. All rights reserved.
Terms & Conditions