Underpinning Contract
Definition
Underpinning Contract
An underpinning contract is an agreement between a service provider and a third-party supplier whose work is needed to meet a client commitment. The client is not a party to it — which is exactly why its terms have to mirror the client contract.
Almost no provider delivers alone — connectivity, software licences, hardware maintenance, translation, background screening and specialist capacity are routinely bought in and then resold inside a managed service.
When those inputs fail, the client’s service level fails. The provider remains fully liable to its client, and its only protection is whether the underpinning contract passes equivalent obligations down the chain.
Back-to-back drafting is the technique. Service levels, security requirements, audit rights and liability terms are written to be at least as demanding downstream as they are upstream — anything weaker is a gap the provider funds itself.
Key takeaways
- An underpinning contract sits between the provider and its own third-party supplier.
- The client has no direct rights under it and remains reliant on the provider.
- Back-to-back terms should be equal to or stricter than the client-facing obligations.
- Subcontracting never transfers the provider’s accountability to the client.
How it works
The provider maps every client obligation that depends on a third party, then negotiates supplier terms that meet or exceed it. Where a gap remains, the provider either prices the residual risk or carries it silently.
Federal subcontracting rules state the accountability principle without ambiguity. Consent to a subcontract “shall…relieve the Contractor of any responsibility for performing this contract” in no way, as the clause makes explicit.
Notification is treated as a separate duty. The contractor must “notify the Contracting Officer reasonably in advance of placing any subcontract or modification thereof for which consent is required”, which is the analogue of a client’s approval right.
| Client obligation | Underpinning requirement | Gap if weaker |
|---|---|---|
| Four-hour incident response | Supplier response inside two hours | Provider absorbs the shortfall |
| Annual security audit right | Audit right flowed down to supplier | Provider cannot evidence compliance |
| Liability cap at contract value | Supplier cap at least proportionate | Uninsured exposure sits with the provider |
| Data location restricted | Same restriction on the supplier | Client contract breached by the chain |
| Twelve-month exit notice | Matching or shorter supplier notice | Provider pays for capacity it cannot use |
The exit-notice row is the one providers discover late. A three-year supplier commitment underneath a one-year client contract is a stranded cost waiting for a non-renewal.
Examples
Underpinning contracts matter most where a critical input is bought in rather than built internally. The four cases below show the chain working as intended and failing badly.
A contact centre provider buys carrier telephony on terms that match its own client availability commitment. When an outage occurs, the carrier’s remedies fund the client’s credits.
An IT provider promises a client four-hour hardware replacement and buys next-business-day maintenance. The gap is invisible until the first failure lands on a Friday.
A payroll provider flows its client’s audit rights through to its software vendor. The client’s auditors get access, and the provider is not caught between two contracts.
A translation provider signs a two-year freelance capacity commitment under a one-year client contract. The client does not renew, and the commitment runs on regardless.
Related terms
Agreements supporting a client service differ by who the parties are and whether money is attached. The entries below separate the internal, external and third-party layers.
- Service level agreement (SLA): the client-facing commitment an underpinning contract exists to support.
- Multi vendor outsourcing: arrangements where several chains run in parallel.
- Multi sourcing model: a structure where the client contracts suppliers directly instead.
- Vendor management outsourcing: the discipline that maps and monitors the chain.
- Service desk outsourcing: delivery that typically depends on several underpinning suppliers.
- Co-sourcing: shared delivery between client and provider, not a supplier chain.
- Telecom outsourcing: the classic bought-in input behind contact centre commitments.
FAQ
How does this differ from an operational level agreement?
An operational level agreement is internal to one organisation and carries no money. An underpinning contract is with an external third party and is fully binding, with its own remedies.
Does the client have any rights under it?
Normally none, because it is not a party. Clients secure protection indirectly, through flow-down obligations and approval rights in their own contract.
Can a provider subcontract without telling the client?
Only where the contract permits it. Most client agreements require notification or consent for material subcontracting, and many restrict it outright.
What is back-to-back drafting?
Writing supplier terms to be at least as demanding as the client-facing ones. Any softer term leaves the provider funding the difference.
Who is liable when a supplier fails?
The provider, to its client, without exception. Recovery from the supplier is a separate matter and often recovers far less than was paid out.
Which terms are most often missed?
Audit rights, data location restrictions and exit notice periods. All three are easy to promise upstream and expensive to discover missing downstream.
Source partners who can evidence back-to-back supplier terms are listed in the Outsource Accelerator hub directory.
Independent
