The Remedy Clause That Changes Nothing

Every contract that includes a service level has some form of remedy attached to it. A response time that is missed, a delivery that is late, an availability threshold that is breached — each of these triggers something: a credit, a discount off the next invoice, a right to terminate if it happens often enough. The language looks rigorous and the concept sounds right, and most of these remedy clauses are then never enforced, or enforced in ways that produce a small credit rather than a change in the underlying performance. Procurement teams who negotiated the clause in good faith find, eighteen months into the contract, that the supplier is habitually missing SLAs and the remedies are being absorbed as a cost of doing business rather than addressed as a performance problem.

The failure is almost never a drafting failure. The clause is there. The issue is that the remedy, as designed, does not make poor performance more expensive for the supplier than improving performance would be. When a credit is smaller than the cost of the operational change needed to avoid it, the credit is simply a discount on a lower quality of service, and the supplier has been told, functionally, that the current performance level is acceptable at the current price.

What a remedy is actually supposed to do

A well-designed remedy clause is not primarily about compensation. It is about incentive. The compensation for late delivery, however it is calculated, rarely covers the actual cost to the business of the disruption the failure caused. Trying to make the remedy compensatory tends to produce arguments about the real cost, which are expensive and rarely conclusive.

What a remedy can do, if designed correctly, is make the gap between performing and not performing large enough that performing is the supplier's commercial preference. That means the credit has to be set at a level the supplier's account team will notice, it has to be easy to calculate and apply without requiring an argument about whether the SLA was actually missed, and it has to escalate when failures recur rather than plateau. A flat credit per missed SLA that never changes, regardless of frequency, gives the supplier a stable cost curve they can price against. An escalating structure that makes the tenth failure significantly more expensive than the first gives them a reason to fix the underlying problem rather than manage the cost.

What to negotiate before the contract is signed

The time to design the remedy properly is before signature, not after the first SLA breach. The questions worth asking during the negotiation are whether the credit level is set relative to the value of the service rather than an arbitrary flat figure, whether the supplier will be required to track and report performance proactively or whether the buyer carries all the monitoring burden, and whether the termination right that sits behind the credits is realistic or purely theoretical.

A termination right that can only be exercised after twelve consecutive months of missed SLAs, with ninety days notice, and only if the buyer has followed a formal escalation process, is not a realistic termination right. It is a drafting exercise. A supplier who has examined the clause knows it will never be used, and that knowledge changes how they respond to informal complaints about service levels.

Making the existing contract work

When the remedy clause is already in place and not working, the problem is usually a combination of the credit level being too low, the tracking being too informal, and the escalation conversation having been avoided for too long. Applying the formal remedy mechanism, even if the initial credit is small, sends a different signal than continuing to raise performance concerns verbally. It resets the contract as an instrument rather than a backdrop, and it often produces a more substantive response from the supplier than months of account-level discussion has managed.

The shift from informal complaint to formal remedy is where most performance conversations stall. The supplier challenges the measurement, questions the data, or offers reassurances that have been given before — and the buyer retreats into another round of account-level discussion rather than activating the clause. Voice2Evolve puts buyers into that specific moment, against a supplier who pushes back on the measurement, so the decision to hold the formal position is not made for the first time under live pressure.

Procurement takeaway

• Set remedy credit levels during contract negotiation at a threshold the supplier's account team will notice and escalate internally — if the credit is cheaper than fixing the problem, it functions as a discount on poor service.
• Build an escalating penalty structure into every SLA remedy clause so that repeated failures become significantly more expensive than the first, giving the supplier a financial reason to address the root cause.
• Require the supplier to track and report SLA performance proactively as a contract obligation — do not carry the monitoring burden yourself.
• Apply the formal remedy mechanism at the first documented breach rather than continuing to raise it verbally; activating the contract sends a different signal than another account review.