Maintenance Operations research
What a work order first-response time can and cannot prove
A research brief on work order first-response times, separating an acknowledgement from a repair and a fast reply from a resolved problem.
| 3 sources sources
Table of contents
A resident reports a leaking tap at 8 a.m. and receives an automated reply at 8:01. The first-response report shows a one-minute response and a satisfied service level. The tap is still leaking a week later.
A first-response time is a useful operational measure and a poor proof of service. This brief examines what it can show, what it hides, and how to report it.
Defining the response
A response can be an automated acknowledgement, a human reply, or a scheduled visit. Each is a different event, and the report should say which one it measures.
Write the definition down. A report that counts the automatic reply as a response will look excellent and tell the resident nothing.
What the measure can show
The measure can show whether tickets are acknowledged and how quickly a human picks them up. It can show the queues where the first contact is slow.
It can support a staffing decision when paired with the repair time. A fast acknowledgement with a slow repair is a different problem from a slow acknowledgement.
What the measure cannot show
The measure cannot show whether the issue was fixed. A response is the start of the process, not the end.
It cannot show whether the resident understood the reply. A generic message can be fast and useless.
It also cannot show the quality of the repair. That needs the close-out note and, in some cases, a follow-up with the resident.
Methodology and limits
This brief reviews public guidance on internal control, housing standards, and small-business operations, and maps it to a private work order record. The sources support documentation and review discipline; they do not set a target response time.
We tested the proposed fields against four common cases: an automated acknowledgement, a human reply with a question, a scheduled visit, and a ticket with no response. The fields kept those cases distinguishable.
Separate the stages
Record acknowledgement, human response, scheduled visit, and completion as separate stages. Each has a different owner and a different failure mode.
A report that collapses the stages produces a number that no one can act on. The stage is the finding.
Report the tail
Report the median and the slowest tickets. A cluster of late responses in one building or one trade is a specific problem.
List the oldest open tickets with the stage they are waiting on. A ticket that has been acknowledged but not scheduled is a different issue from one that has never been read.
A worked example
A property reports a one-hour median first response. The completion data shows that 30 percent of tickets take more than two weeks to close.
The fast response is real, and the service is slow. The review focuses on scheduling and parts rather than on the acknowledgement step.
Repair close-out
The close-out note is the evidence that the repair happened. Record the work done, the parts used, and the resident confirmation.
A ticket closed without a note is an open question. The audit should flag the closures without evidence.
Resident follow-up
For the oldest tickets, a short follow-up call can reveal whether the issue is resolved. Record the call and the response.
A resident who says the problem persists is giving the team a second chance to fix it before it escalates.
Reporting
Report the counts by stage, the oldest open tickets, and the completion rate. A one-page summary is enough for the weekly review.
Keep the definitions stable. A changing report cannot be compared.
Reporting cadence
Review the stages weekly and the pattern monthly. The weekly pass catches the stalled tickets; the monthly pass looks at the trades and buildings.
Keep the definitions stable. A changing measure cannot show whether the process improved.
Limits and appropriate use
This brief is a method note, not an empirical study. It does not establish a response standard. Results depend on the accuracy of the ticket data.
Small portfolios should read the counts and the oldest tickets directly rather than rely on an average.
Conclusion
A first-response time shows acknowledgement. Used with scheduling and completion data, it shows where the maintenance process stalls. Used alone, it rewards a fast reply and can hide a queue that never finishes.