There is a specific type of conversation that most Irish FM contractors know well. A client calls — or worse, emails — to say that a fault logged three days ago has not been attended to, that the SLA for that category of work was 24 hours, and that this is the second time this month. The contractor does not know this because their SLA tracking is done in a spreadsheet that nobody checks between Monday morning and Friday afternoon.
The reactive FM problem is well-documented. Most FM businesses spend the majority of their time responding to faults rather than preventing them. But the SLA management problem is distinct from the reactive maintenance problem — and it is often more damaging commercially, because it shows up in client reporting, contract reviews, and ultimately in whether a contract is renewed.
How most Irish FM contractors track SLAs today
The standard approach is a combination of a job management system — or spreadsheet — and email. A fault is logged, a job is created, and a target completion date is set. In theory, someone checks the open jobs against their target dates. In practice, this check happens when someone remembers to do it, or when a client complains.
The fundamental problem with this approach is that it is retrospective. The breach has already happened before the check reveals it. By the time the client is informed — if they are informed proactively at all — the SLA has been missed and the relationship has taken a hit.
Monthly SLA reports are often compiled manually from job management data, which introduces a second problem: accuracy. If the job management data is not complete — if some jobs were handled verbally or outside the system — the report does not reflect reality. A client who receives a 94% SLA compliance figure and knows from their own experience that it was closer to 80% has a problem with the contractor that goes beyond any individual missed response time.
The business cost of late breach detection
The cost of a single missed SLA is usually small — a phone call, an apology, perhaps a credit. The cost of a pattern of missed SLAs, identified late and reported inaccurately, is much larger.
Client relationship damage. FM contracts are typically long-term. The trust that underlies them is built over years. A pattern of late breach detection — discovered by the client rather than communicated proactively by the contractor — erodes that trust in a way that is difficult to recover. Clients who do not trust their FM contractor’s reporting begin to manage the relationship defensively, which means more oversight, more governance requirements, and eventually a competitive tender.
Contract risk. Most FM contracts include SLA penalty provisions. Missed SLAs above a threshold trigger penalty credits, and repeated failures can trigger break clauses. A contractor who does not know their real SLA performance until after the client has reported it is flying blind on their contract exposure.
Revenue loss. Beyond penalty credits, there is a less obvious revenue impact: underbilling. When jobs are not properly closed in the system, the time and materials associated with them cannot be invoiced. In a reactive FM business where job volume is high, the cumulative unbilled time from jobs that fell through the cracks can be significant.
What real-time SLA tracking looks like in a connected FM system
In a properly configured FM operational system, SLA tracking is not a reporting function — it is a real-time monitoring function. Every job has an SLA category, and every SLA category has a response time and a completion time. The system tracks elapsed time from job creation and raises an alert before the SLA is breached — not after.
The alert goes to the relevant engineer, their supervisor, and — if the SLA is missed despite the alert — to the contract manager. The escalation path is configured once per client contract and applies automatically to every job under that contract. There is no reliance on someone remembering to check.
At month end, the SLA compliance report is generated directly from job data. It reflects actual response and completion times, not estimated ones. If the compliance figure is 91%, it is 91% because that is what the data shows — not because that is what someone calculated in a spreadsheet.
PPM scheduling as SLA prevention
The best SLA management is the prevention of the reactive fault that triggers the SLA clock in the first place. Planned preventive maintenance — correctly scheduled and executed — reduces the volume of reactive faults and therefore the number of SLA events that need to be managed.
In a connected FM system, PPM schedules are generated from asset records and service intervals. When a planned maintenance task falls due, it is automatically raised as a work order, assigned to the appropriate engineer, and tracked to completion. The completion data feeds back into the asset record, updating the next scheduled service date. Compliance certificates — gas, electrical, legionella — are attached to the relevant assets and flagged when they approach expiry.
The combination of automated SLA monitoring on reactive work and systematic PPM scheduling on planned work is what separates FM operators who grow their contracts from those who spend their time defending them.
If your current SLA reporting relies on spreadsheets and manual checks, the risk of discovering a breach from a client call rather than your own system is significant. FacilityManagementOS is built around this problem — to see how it works in practice, book a discovery call.