Facility Management and Service Planning · Lesson 2

Defining and Measuring Service Levels

4 min read

Lesson objectives

  • Calculate contact time within service hours and review denominator exceptions.
Reading tools

A service level is not merely a number printed on a supplier contract. It is a shared definition of the user outcome, the point at which the clock starts, and the evidence that the service has recovered. 'Respond within one hour' may mean answering a call, arriving on site, or starting a remote diagnosis. If the parties mean different events, a report can look successful while users are still waiting. Begin by naming the service: in this lesson, climate-control reports from occupied work rooms. Define service hours, report categories, the measured clock, the source of timestamps and who can approve an exception. Define response as a documented technician contact confirming location and a first action; define restoration as an acceptable condition after testing. Those are distinct results.

Severity depends on observed facts rather than the caller's volume or the supplier's convenience. In a training scheme, a critical report interrupts an essential service or raises a potential hazard requiring the competent response path; a high report disrupts an occupied area without a suitable alternative; a routine report has limited impact and a usable alternative. These are illustrative categories, not a universal legal classification. The facility's agreement and safety procedures govern their real use. Labelling everything critical makes the promise impossible to manage and hides urgent cases. Downgrading a report after its target has been missed is equally misleading. Preserve the facts known when the original category was assigned, along with the reason and authorization for any later change.

Build a clock table: report opening, triage, owner acceptance, first response, arrival, service restoration and user verification. Suppose high-priority response is due within 30 service minutes between 08:00 and 18:00. A report opens at 16:50 and a technician calls at 17:25. The measured 35 minutes exceed the target by five. If another opens at 17:50 and receives a call at 08:10 next morning, do not count all 14 hours and 20 calendar minutes as service time. Count ten minutes to 18:00 and ten minutes after 08:00, giving 20 service minutes, provided this category is not promised out-of-hours coverage. Show which clock was used whenever reporting a result; otherwise an exclusion can become a way of concealing delay.

Calculate compliance over eligible reports rather than all messages. If there are 12 eligible high-priority reports and nine receive a timely response, compliance is 9÷12=75%. Adding three routine reports to the denominator would change the question and could improve the headline artificially. Do not remove a late report unless the agreement permits a documented reason, such as an authorized pause requested by the demand organization after a suitable alternative is provided. Even then, report exclusions separately. Distinguish average response time from the proportion meeting the target: a good average can hide two extremely late cases. A small table showing category, clock, target and substantiated exception is more useful than an unexplained overall percentage.

Lesson summary

Distinguish contact from recovery and calculate compliance using eligible reports and documented clock exceptions.