Harper James is a UK full-service commercial law firm advising businesses on the laws of England and Wales. In technology contracts, service levels define the operational standard a supplier must meet and the consequences of failing to meet it.
A service-level schedule normally sets measurable commitments, such as system availability, response times, resolution times, support hours, incident escalation and maintenance procedures. Each metric needs a clear method of measurement. For example, “99.9% availability” should state the measurement period, the systems included, the calculation method and whether planned maintenance, force majeure events or customer-caused outages are excluded. Terms such as “business day”, “critical incident” and “resolution” also require precise definitions.
The contract should explain what happens when a service level is missed.
Common remedies include service credits, corrective action plans, fee
reductions, repeated-failure reviews and termination rights. A service
credit is usually calculated by reference to the affected service or the
relevant billing period. The parties should state whether service
credits are the customer’s exclusive remedy for that failure, whether
they are subject to a cap, and how the customer claims them. Separate
liability provisions should address losses that fall outside the
service-level regime, including confidentiality, data protection and
intellectual property breaches.
Before signing, the customer should compare the service levels with its operational needs and identify the services that are genuinely business-critical. The parties should allocate responsibility for monitoring, record keeping and reporting, and establish a process for disputing measurements. The schedule should also cover planned changes, subcontractors, security incidents and service continuity. During the contract term, performance reports should be reviewed against the agreed metrics, with escalation routes used before recurring failures become a termination dispute.