FM service level agreements: response and resolution times
A facilities management service level agreement (SLA) sets out what a provider will do, by when and how the FM will check it. A response target measures how quickly the agreed first action happens. A resolution target measures how quickly the agreed outcome is reached. One fault can meet the first target and miss the second.
Which clock stops when?
A meeting-room display fails on Friday afternoon. Choose a point in this fictional job and change the hours the agreement covers.
- Response time
- 15 min
- Target 30 min
- Stopped · target met
- Resolution time
- 40 min
- Target 2 h
- Stopped · target met
The team confirms the display works. Resolution took 20 covered minutes on Friday and 20 on Monday. The weekend still mattered to anyone who needed the room.
What counts as a response or a resolution?
Start with the verbs in your service specification. If it says a technician must attend, ask for the time they reached the fault ready to work. If it promises a human acknowledgement, a helpdesk reply can satisfy that commitment. An automatic ticket number tells you when the system received the report.
A temporary replacement can restore a service while the original equipment still needs repair. Check whether your agreement accepts that workaround as a resolution, gives it a separate target, or requires a permanent fix. Keep the time the service became usable and the time someone closed the job as distinct entries.
How can a Friday fault take 40 minutes or 64 hours and 40 minutes?
In this fictional office, a meeting-room display fails on Friday. Both clocks start when the fault is reported at 16:40. A person must acknowledge the fault within 30 minutes. The display must be confirmed working within two hours. For this agreement, that confirmation is the resolution.
With weekday cover from 09:00 to 17:00, the resolution clock counts 20 minutes on Friday and 20 on Monday. The two-hour deadline is Monday at 10:40. With continuous cover, the deadline was Friday at 18:40, and 64 hours and 40 minutes had passed by the time the display worked. The people using the room experienced the same outage under either calculation.
| Event | What the record establishes |
|---|---|
| Friday 16:40 · Fault reported | The helpdesk logs the failed display. Both clocks start. |
| Friday 16:55 · Human response | The helpdesk takes ownership and tells the organiser what happens next. Response took 15 minutes under either calendar. |
| Friday 17:00 · Engineer attends | The engineer reaches the room. The display is still unavailable. |
| Monday 09:20 · Service restored | The organiser can present on the display again. The agreed resolution clock stops. |
| Monday 10:00 · Ticket closed | The helpdesk finishes the record. The organiser had use of the display 40 minutes earlier. |
How do real facilities teams define the clocks?
The University of Edinburgh’s Maintenance Service Guide gives urgent jobs two targets on page 11. The team aims to respond within one working day and complete the work within ten working days. An FM reviewing an urgent repair needs two times to judge that promise. A prompt first response alone tells them little about when the room will be usable.
The University of Lincoln’s estates service level agreement spells out what happens on site. For a Priority 2 urgent job, it calls for attendance within four hours during contract working hours, 08:30 to 17:00. It also calls for service to be restored or alternative facilities provided within 72 hours. If a team offers another room, record when that room was ready and when the original one was repaired. Each timestamp answers a different question.
What should an FM check before accepting the monthly figures?
Pick one job the report marks on time. Rebuild its timeline with the provider and ask which event a person using the building would recognise as the return of service.
- Priority and coverage. Read the priority definition and service calendar that applied when the fault was reported. A meeting room booked on Saturday can expose a gap in weekday cover even when both targets were met.
- Pauses and extensions. If the clock stopped while a part or access was unavailable, find the clause allowing it, the approval where required, and the pause and restart times. Retain the total elapsed time so the service review can still see the disruption.
- Repeat faults. If the display fails again during the next presentation, link the two reports. Check the agreement’s reopening rule and keep the original timestamps so the team can see what happened on each occasion.
- Open work. Read the response and resolution figures separately and ask which jobs were eligible for each calculation. Look at faults already past their due time that remain open at month end. A report based only on closed jobs can leave those out.