Note · 3 September 2025
Reading a week of missed SLA from the work-order log
Green dashboards and red customer calls can live in the same week. The work-order log usually explains both, if you read statuses in order.
SLA screens are designed to be glanced at. A work-order log is designed to be read. When a service manager in the Klang Valley tells us the dashboard is green and the account manager says the customer is furious, we print a week of closed jobs and read them in the order they happened.
Patterns appear quickly. A pause code used as a filing cabinet. A cloned job that resets the clock. A “complete” status that still needs a follow-up visit, opened as a new ticket with a fresh entitlement. After-hours calendars that still think the company closes at five, while the contract sold 24-hour cover for a hospital chiller.
None of this is visible as a single KPI. It is visible as a sequence. That is why a configuration review spends time in the log rather than in the executive summary the vendor shipped with the licence.
The output is unglamorous: a list of work-order types to retire, pause codes to lock, and clocks that should start from site arrival rather than from ticket open. Those changes alter the colour of the dashboard. More importantly, they alter whether the dashboard is describing the same week the customer lived.