Most field service contracts lead with a response time. The figure only means something once you know which event it measures, which hours it counts and which calls it excludes. Two providers can quote the same window and commit to different outcomes.
Response, fix and resolution are separate promises
A response commitment usually means someone acknowledged the call: a ticket reference, a call from a service desk or remote diagnosis. It does not always mean an engineer on site.
An onsite commitment means a person arrives. A fix commitment means the fault is corrected, often by a part swap. Resolution is broader: the service is restored and you confirm it. A contract can quote the first while the sales conversation implies the last. Check which word sits next to the time, and read the definitions rather than the summary table.
Business hours versus 24/7
A window measured in business hours only runs during the provider’s working day. A fault logged late on a Friday against a next business day response may not see an engineer until Monday or Tuesday. Business hours also need defining: whose time zone and which public holidays apply. For an estate spread across countries, those answers change from site to site.
A 24/7 commitment removes the calendar problem. It still depends on an engineer being available near the site and on out-of-hours site access.
When the clock starts and when it pauses
The clock may start when you raise the call, when the provider accepts it, or when the call has been triaged and categorised. Each option can add delay before the commitment begins. Pause conditions matter too: waiting for site access, for a customer contact to confirm details, or for parts. A clock that stops while a part is in transit turns a fix commitment into an attendance commitment. This matters most for multi-vendor break-fix contracts, where parts for older or out-of-warranty HPE, Cisco or Dell equipment may come through a different supply chain from the engineer.
Exclusions that sit outside the headline
Exclusions are where a strong-looking window loses its value. Typical ones cover remote locations, sites needing security clearance or escorts, equipment missing from the asset register, and faults caused by third parties. Priority definitions matter as well. If only a total outage counts as top priority, a server running on one power supply after the other has failed may be logged at a lower tier with a longer window.
Questions that expose a weak commitment
- Is the stated time for response, onsite attendance, fix or resolution?
- Which event starts the clock, and who records it?
- Which conditions pause the clock, and how are pauses reported?
- Whose business hours and public holidays apply at each site?
- Are parts held near the site, or does the window assume they arrive with the engineer?
- Which locations or asset types fall outside the standard window?
- How is performance reported, and against which definition?
Ask for a worked example against a real site: a named location, a specific device and a fault raised at an awkward hour. A provider that can walk through that call, including where the clock stops, is describing a commitment it has tested. One that repeats the headline time is describing the summary table.
