Every Irish FM operator has a version of the same story. A reactive job comes in. It goes into someone’s email. It gets acknowledged. It gets assigned, eventually. Somewhere between acknowledgement and assignment, the SLA clock has been ticking — and nobody is watching it.
Then a client calls. The SLA has been breached. The relationship has taken a hit. The review meeting next month is going to be uncomfortable.
SLA breaches are not usually caused by poor service delivery. They are caused by poor visibility. The work gets done — but not in time, because nobody could see the timer running.
What SLA management actually requires
To manage SLAs properly, an FM operator needs four capabilities:
- Timer starting at the right moment. Not when the job is assigned, not when work starts — when the job is received. For reactive maintenance, the SLA clock starts at job creation. The system needs to know this and track it automatically.
- Escalation before breach. An alert that fires when a job reaches 80% of its SLA window. Not an alert when the SLA is breached — that is already too late. An alert while there is still time to act.
- Priority-based SLA tiers. Not all jobs have the same SLA. An emergency reactive job (P1) might have a 4-hour response SLA. A routine planned job (P3) might have 48 hours. The system needs to apply the right SLA based on job priority.
- Reporting for client review meetings. Monthly SLA performance reports, broken down by site, job type, and priority. Not assembled from email records — generated directly from the job management system.
The inbox problem
Managing reactive jobs from an inbox is the most common FM workflow in Ireland — and the most dangerous one for SLA compliance. Here is why:
An email inbox has no SLA awareness. It does not know that the job reported at 9:03am on a Monday has a 4-hour response SLA. It does not alert anyone at 11:00am when 2 hours have elapsed. It does not flag the job as breached at 1:03pm. It just sits there, between a supplier invoice and a tenant complaint, waiting to be opened.
The engineer who receives the job may be on site. Their inbox may not get checked until 2pm. By then, the SLA is gone.
Live SLA monitoring: what it looks like in practice
In a properly configured FM operations system, SLA management works differently:
When a job is created — whether by a tenant via a portal, a client email processed into the system, or a direct data entry — an SLA timer starts immediately. The system knows the job priority (P1, P2, P3) and applies the correct SLA window.
The job appears on a live dashboard with its SLA status colour-coded: green (within SLA), amber (approaching breach, typically >80% elapsed), red (breached). Any operations manager looking at the dashboard can see the SLA status of every open job at a glance.
At configurable thresholds — say, 80% of the SLA window elapsed — an automated alert fires to the assigned engineer and their line manager. The alert does not require anyone to check a report. It arrives because the system knows the timer is running.
This shifts SLA management from reactive (finding out after a breach) to proactive (preventing breaches before they happen).
Planned preventative maintenance and SLA
PPM compliance is a different kind of SLA — one defined by asset maintenance intervals rather than response times. A boiler that requires a 6-monthly service has a compliance deadline twice a year. A fire alarm test may be required quarterly. A lift inspection may be annual.
When PPM schedules are managed in spreadsheets, the pattern is consistent: visits get missed, compliance records are incomplete, and audit preparation is painful. When they are managed in a connected system, work orders are generated automatically against the schedule, engineers are assigned, and completion is recorded with documentation.
The compliance record is built as a by-product of doing the work — not assembled after the fact.
What SLA performance data reveals
Once you have SLA tracking in place, the data that accumulates is valuable beyond compliance. You can see which sites consistently generate P1 jobs. Which engineers have the best response rates. Which job types are most likely to breach. Which clients generate the most reactive work.
This intelligence changes how FM contracts are priced and staffed. It makes the case for PPM investment on specific assets. It gives you the evidence to have honest conversations with clients about their sites.
Managing SLAs is not just about avoiding contract penalties. It is about running a better FM operation — and the data is how you know you’re doing it.