NHD Partners All articles
Corporate Governance

Paying for Failure Is Not Assurance: How UK Boards Should Test Service Remedies

NHD Partners
Paying for Failure Is Not Assurance: How UK Boards Should Test Service Remedies

Service level agreements are often presented to UK boards as a neat equation: define the standard, measure the shortfall, apply the credit. The logic is attractive because it appears to convert operational risk into a financial adjustment. Yet a credit is not the same as a cure. It may compensate the buyer for a missed target while leaving the underlying cause untouched, and it can create a false sense of assurance if the remedy regime is never tested beyond its arithmetic.

For organisations that depend on third-party services, the more important question is not whether the contract can impose a credit. It is whether the remedy actually changes provider behaviour, restores service and reduces the likelihood of recurrence. That is a governance question as much as a commercial one, and it deserves board-level attention before a credit table is treated as proof of resilience.

The comfort of a credit table

A credit regime is easy to describe in a board pack. It has thresholds, percentages and a maximum liability. It looks precise. But precision is not the same as effectiveness. A credit may be too small to influence a provider’s priorities, too slow to activate, or too narrowly drawn to capture the service failure that matters most to the customer.

There is also a behavioural risk. If the credit becomes the accepted response to failure, the buyer and provider can settle into a routine of payment and apology rather than correction. The service continues to underperform, the buyer receives a modest adjustment, and the root cause remains in place. Over time, the credit regime becomes a comfort blanket rather than a control.

UK boards should therefore read the remedy schedule as a design document. It should show how the parties intend to detect failure, assign responsibility, trigger action and learn from events. A table of financial deductions is only one part of that design, and often not the most important part.

Four tests for a working remedy

First, the trigger must be clear. A remedy should attach to a defined service outcome, not simply to an activity or an input. If the contract measures the number of calls answered but not whether the customer’s issue was resolved, the credit may reward the wrong behaviour. Boards should ask whether the remedy is connected to the service promise that matters to the organisation, its customers or its regulators.

Second, the measurement must be trustworthy. UK buyers should establish who produces the performance data, how it is validated and what happens when the parties disagree. A remedy regime that depends on provider-reported data, with no independent check, is weaker than it appears. The audit committee does not need to inspect every dashboard, but it should know that the evidence behind a credit is robust.

Third, the remedy must require causation and correction. A credit should not be the end of the process. It should trigger a root cause analysis, a remediation plan with named owners and dates, and a review of whether the same failure could occur elsewhere. If the contract does not require the provider to explain why performance failed, the buyer is paying for a symptom rather than treating the cause.

Fourth, the remedy must have escalation and learning built in. A single missed target may be handled operationally. A pattern of misses should reach the governance forum, and repeated failures should prompt a formal service improvement programme. The board should be able to see whether credits are being earned repeatedly for the same issue. If they are, the remedy is not working as a control; it is working as a price list.

Reading the remedy as a governance instrument

Remedies should be aligned with the organisation’s risk appetite. A credit that is trivial relative to the value of the contract will not concentrate attention. A credit that is so severe that the provider disputes every event may create a different problem, consuming management time in argument rather than improvement. The design needs proportionality, but proportionality should be judged against the consequence of failure, not merely against the fee.

There is also a question of visibility. Board members should receive a remedy dashboard that shows not only how much has been credited, but why. Which services are failing? Is the same cause recurring? Are remediation plans closing on time? Are credits being offset against future work in a way that obscures the true cost of poor service? These are governance indicators, not just contract metrics.

Procurement teams should test the remedy regime before signature by walking through a realistic failure scenario. If a critical service fell short for a week, what would happen? Who would notice? What would the provider be required to do? What would the buyer be able to evidence? How quickly would the board hear about it? A remedy that cannot survive that conversation is unlikely to survive contact with an actual incident.

Questions for the board and procurement team

A focused set of questions can expose whether a credit regime is substantive or cosmetic. Does the remedy attach to outcomes or activity? Is the performance data independent enough to be trusted? Does a credit trigger a mandatory root cause analysis and remediation plan? Are repeat credits reported to the board as a governance concern? Is there a route to escalate persistent underperformance beyond the credit mechanism? And does the contract allow the buyer to exit or renegotiate if remediation repeatedly fails?

The answers should be documented, not assumed. A reliable service relationship depends on clear obligations, honest measurement and a shared commitment to correction. The remedy regime is one of the places where that commitment is either designed in or designed out.

From compensation to correction

Service credits have their place. They can recognise the cost of disruption and create a financial consequence for failure. But they should not be mistaken for assurance. Assurance comes from knowing that the provider can detect failure, explain it, fix it and prevent it from recurring. UK boards should audit the remedy regime with that standard in mind.

The test is not whether the contract can pay out. It is whether the relationship can correct itself. For organisations seeking a dependable service partner, that distinction matters far more than the size of the credit table.

All Articles

Related Articles

Cover You Can Audit: The Boardroom Case for Festive Staffing Evidence

Cover You Can Audit: The Boardroom Case for Festive Staffing Evidence

The Contract Date You Never Diarised: Governing Automatic Rollover Before It Governs You

The Contract Date You Never Diarised: Governing Automatic Rollover Before It Governs You

The Corridor View: Turning a Service Site Visit into Board-Level Assurance