A 4-hour SLA commits an engineer to be on site within four hours of a fault being logged, usually around the clock. Next-business-day cover commits one to arrive the following working day. Both are response commitments, not repair commitments — and that distinction is where most contract disappointment comes from.
This article sets out what each tier includes, how the clock is measured, what sits behind the promise operationally, and how to match a tier to a site without over-buying across an estate.
Need engineers on site in the UK, Europe or further afield?
Throne Solutions provides on-site IT field engineers across 60+ countries. Tell us your sites and the kind of cover you need, and we will come back with options and a quote.
What a 4-hour SLA actually commits to
A 4-hour service level means an engineer is on site within four hours of the case being logged and accepted. The usual shorthand is 24x7x4: cover 24 hours a day, 7 days a week, with a four-hour response. As Park Place Technologies puts it, “the ‘x4’ alludes to a 4-hour response, meaning we have 4 hours to acknowledge that a ticket has been opened” (Park Place Technologies).
Read that carefully. The four hours buys attendance, not a working machine. Manufacturer datasheets are explicit about the difference: HPE’s Foundation Care documentation separates on-site response from a call-to-repair commitment, and notes that “the hardware repair time may vary for specific products” and that work “may be temporarily suspended if parts or additional resources are required” (HPE Foundation Care service datasheet).
If you need a committed fix time rather than a committed arrival time, that is a different product — a call-to-repair or time-to-restore commitment — and it is priced and engineered differently. Ask for it by name.
The variants of 4-hour cover
- 24x7x4 — four-hour response, any hour, any day, holidays included.
- Business-hours 4-hour — the same four-hour window, but only inside the
working day. A Friday evening failure is a Monday morning response. - 4-hour call-to-repair — a commitment to restore, not merely to attend. Far
more demanding to deliver, and not available everywhere.
What next-business-day cover actually commits to
Next business day, almost always written NBD, commits an engineer to the site on the next working day after the case is logged. The HPE datasheet describes the equivalent window as “9 hours per day between 8:00 a.m. and 5:00 p.m. local time, Monday through Friday”, excluding the vendor’s holidays, and notes that cases “received outside the coverage window will be acknowledged the next coverage day”.
Two consequences follow, and both catch buyers out.
First, the cut-off matters more than the tier. A fault logged at 16:55 and a fault logged at 17:05 can be a full working day apart. Second, weekends and public holidays are not business days. NBD cover on a Friday afternoon is, in practice, Monday — and over a bank holiday weekend, Tuesday. If that is unacceptable for a given site, NBD is the wrong tier for that site.
How the clock is measured — and when it stops
Response clocks start when the case is logged and accepted, not when the device failed and not when your own team noticed. Three details decide whether a contract behaves the way you expected.
- Remote diagnosis can replace the visit. The HPE documentation states that
“an on-site response time will not apply if the service can be delivered using remote diagnosis,
remote support”. That is usually a good outcome — a fix in twenty minutes beats an engineer in
four hours — but it means an on-site clock is not always the clock that governs. - The clock can pause. Waiting on site access, on a customer decision, or on
a part shipped from elsewhere typically suspends the commitment rather than breaching it. How
pause is defined is one of the most consequential clauses in the contract. - Travel distance is written into the tier. HPE lists next-day response as
“next coverage day” for sites within 160 km (100 miles) of a support hub, with extended times
beyond that. Every field services provider has the same geography problem, whether or not the
contract spells it out.
That last point is the one worth pressing a prospective partner on, because it is the one that determines whether a tier is real at your address.
What sits behind a response commitment
A four-hour tier is a logistics commitment dressed as a support commitment. Delivering it at a given site requires an engineer inside the travel radius, rostered for the coverage window, with the right parts reachable in under four hours — which usually means stock held locally rather than shipped. This is why the same tier costs differently at different addresses, and why an honest provider will quote some postcodes and not others.
Next-business-day cover relaxes all three constraints. The engineer can travel further, the roster is simpler, and parts can move overnight rather than sitting in a forward location. That is the whole of the cost difference, and it is why NBD is the sensible default for most of an estate.
If you are evaluating a provider, ask where parts for your platforms are physically held, how engineers are scheduled against the coverage window, and which of your sites they will commit a four-hour tier to in writing. Vague answers to those three questions are the signal, not the price.
Matching the tier to the site, not to the estate
The common and expensive mistake is buying one tier for everything. Response time should follow business impact, which varies enormously across an estate.
- Four-hour, around the clock: production infrastructure, revenue-carrying
systems, trading or transaction platforms, core network, equipment in a
data centre where downtime cascades. - Four-hour, business hours: systems that matter during the working day and
nobody touches overnight — office infrastructure, branch servers, clinical or retail systems with
defined opening hours. - Next business day: the bulk of most estates. End-user devices, printers,
non-critical servers, anything with a spare or a workaround. - No on-site cover: genuinely disposable kit with stock on the shelf. A
decision, not a default.
Two further levers are often cheaper than upgrading a tier. Holding a spare on site turns a four-hour problem into a ten-minute swap, which can be the better buy for a single critical device. And good remote IT support
resolves a large share of faults before anyone needs to travel, which is why the strongest field contracts pair the two rather than treating on-site attendance as the first move.
How this gets priced
Response-time cover is priced per device or per site, against the response tier, the coverage window and the site’s location. A four-hour, around-the-clock tier at a remote address is the expensive end; next-business-day cover at a well-served address is the cheap end. Throne Solutions publishes no rate card, because a rate card for this would be fiction — the answer depends on your asset list and your addresses. Send both and you get a quote against the actual estate.
Planning cover for a new contract or region?
Send us the countries, sites and service level you need. It takes two minutes, and there is no obligation.
Frequently asked questions
What does a 4-hour SLA mean?
It means an engineer will be on site within four hours of the case being logged and accepted. Usually written 24x7x4, it covers any hour of any day. It is a commitment to attend, not a commitment to have the fault fixed within four hours.
What does next business day support mean?
An engineer attends on the next working day after the case is logged, within a defined working window — typically around 08:00 to 17:00 local time, Monday to Friday, excluding public holidays. A case logged after the daily cut-off, or on a Friday, moves to the following working day.
Is a 4-hour SLA a response time or a fix time?
A response time. A committed fix time is a separate product, usually called call-to-repair or time-to-restore, and it is contracted and priced differently. If the business needs a restoration commitment, ask for that specifically rather than assuming four-hour response delivers it.
Is 4-hour cover worth the extra cost?
For equipment whose failure stops revenue or operations, usually yes. For most of an estate, no. The sensible approach is to tier by business impact rather than buying one level across everything, and to consider an on-site spare for isolated critical devices instead of an estate-wide upgrade.
Does the SLA clock run overnight and at weekends?
Only on a 24×7 tier. On a business-hours tier the clock runs inside the coverage window and pauses outside it, so a Friday evening fault is answered on Monday. This is the single most common source of surprise when a contract is tested for the first time.
Can the same SLA be delivered at every site?
Not automatically. Four-hour cover depends on an engineer and the right parts being inside the travel radius, so availability is site-by-site. Manufacturer contracts state this openly through distance bands, and any field services provider faces the same constraint. Always confirm the tier per address, not per contract.
SLA-based cover from Throne Solutions
Throne Solutions provides SLA-baseret IT-support for multi-site estates, delivered through
global field services across the UK, Europe, the Nordics and the Gulf, with
hardware maintenance and
third-party maintenance behind it. Coverage by territory is set out on
Vores tilstedeværelse.
Send your asset list, your site addresses and the response tiers you need, and you will get a quote against the real estate — tiered site by site rather than priced as one block.
E-mail: info@thronesolutions.com
Request a quote ·
IT consulting and field engineering ·
Site surveys and installations
