Northline Service Desk (fictional) reports resolution times to its depots every week. The support lead, Morgan Reed, asks you to explain why HELP-12 shows as breached when the customer held things up.
The data: the Resolution time SLA as it stands, and the HELP requests with their status history. HELP-12 sat in Waiting for customer from Thursday 14:00 to Monday 9:30.
Done looks like: a corrected SLA that pauses on customer waits and counts working hours only, HELP-12 resolved on Tuesday at 13:00 inside its goal, and an explanation backed by the clock.
Northline's support lead is unhappy. HELP-12, a cracked handheld screen, shows as breached on the resolution report, yet the customer took four days to send the device back. The lead wants to know whether the desk failed or the clock is wrong, and wants the request closed in time if it can still be.
The current SLA, Resolution time, counts every hour of every day and never pauses. Investigate before you change anything: find the open service requests, then fix the definition one condition at a time and read HELP-12's clock after each change. Each step keeps your earlier fixes.
The case ends with the explanation you give the lead. It has to rest on the clock, the calendar and the request history, not on how the report looks.
Diagnose a clock condition by condition, then explain it from the history.