Liability caps, exclusions and insurance: adding up the losses your contracts make you keep

Ask a business owner a simple question: if each of your key suppliers failed badly, how much of the resulting loss would you have to carry yourself? Few can answer. Yet the figure exists. It is the sum, across every contract, of the gap between what a supplier’s failure would cost and what the business could actually recover. Much of that gap is created deliberately, by liability caps and exclusion clauses that someone accepted when signing.

Those clauses are often treated as fine print, or as the other side’s lawyers trying to avoid responsibility. They are better understood as economic decisions about who carries a loss. A supplier that caps its liability at the fees it is paid is offering a lower price than it would charge if it carried the full risk. That trade can be perfectly sensible. But it is a decision, and the loss above the cap does not disappear. It stays with you, funded by whatever cash and insurance you happen to have on the day it arrives.

This article explains how caps and exclusions shrink what you can recover, why the gaps add up across contracts, how to compare suppliers once their liability terms are counted, and how to make insurance match what you have actually agreed to keep. It is general information. Whether a clause is enforceable depends on its wording, how it became part of the contract and the law that applies, including consumer and unfair contract terms protections, so get legal advice on significant contracts, and insurance advice from a broker.

A cap is a decision by the buyer

It is natural to read a liability cap as a term about the supplier. It is just as much a term about the buyer. The supplier gets certainty about its maximum exposure; the buyer gets a lower price, or simply gets the deal done. Whether that is a good trade depends on how large the loss above the cap could be, and almost nobody measures it.

Caps are usually anchored to the contract, not to the loss: the fees paid in the last twelve months, a multiple of the price, a fixed sum. The loss is anchored to your operations. A small contract for a service you depend on completely can have a cap of a few thousand dollars and a potential loss of hundreds of thousands. Those are often the contracts that get the least negotiating attention, because attention follows spend.

Three ways recovery shrinks

A liability regime usually reduces what you can recover in three steps, and most people only notice the last:

1. Excluded classes of loss. Many contracts exclude “consequential” or “indirect” loss, loss of profit, loss of revenue or loss of data. In many operational failures, those excluded classes are the largest part of the cost, because the cost of fixing the faulty item is small compared with what it stopped.
2. Notice periods. Claims must often be notified within a set time after the event. If a failure is not discovered until weeks or months later, the window may have closed before anyone knew there was something to notify.
3. The cap itself. Whatever survives the first two steps is limited to the capped amount.

So the honest way to read a liability clause is: what is the plausible worst-case loss, what classes are excluded, how quickly would we discover the problem, and what is the cap? The residue, the loss you would keep, is what remains after all three.

The gaps add up

Each cap is usually accepted on its own, by whoever is negotiating that contract at the time: an office manager renewing a software subscription, a project lead accepting standard terms to keep to a date, an owner trading a warranty for a discount. None of them is thinking about the total. But the residues accumulate, and a single event can trigger several at once. A regional power outage could hit your refrigeration, your systems and your security monitoring simultaneously. A cyber incident at a shared platform could affect several services together.

So it is worth building a simple table for contracts that matter:

Then three tests:

• Capacity test. Group residues that could be triggered by the same event, take the largest group and compare it with what the business could absorb from cash and insurance.
• Concentration test. Which single supplier leaves the largest residue, and which supplier appears in several?
• Authority test. Who is allowed to accept a cap? Many businesses set approval limits by contract value. A better rule sets them by residue: above a certain retained loss, the person negotiating may not accept the cap without approval from whoever would have to fund the loss.

Compare bids with their liability terms included

Consider two quotes for the same work. Supplier A is cheaper but excludes most downstream loss and caps liability at a low figure. Supplier B costs more but accepts meaningful responsibility for the failures that matter most. A comparison on price alone favours A. A comparison that includes the risk being handed back to you may not.

For any significant contract, ask:

• What failure is this clause allocating?
• Who is best placed to prevent, control or insure it?
• What is the plausible maximum loss?
• How much of the price difference reflects the different liability terms?
• What practical recovery options remain if the excluded event happens?
• Could we reduce the risk ourselves, for example with a backup, an inspection or a second source?

It also helps to know where the terms are. Important exclusions often sit in schedules, linked standard terms, quotes, delivery dockets or purchase-order conditions that nobody reconciles. Whether those terms form part of the contract depends on how they were brought to the other party’s attention and on the law, which is a question for a lawyer. Commercially, the question is whether the risk was allocated deliberately or by accident.

None of this means suppliers should carry unlimited liability. A small supplier cannot carry the full value of your business on its balance sheet, and if forced to would price accordingly or decline the work. The point is to know what you are keeping and to choose it. The passing a risk on does not remove it article covers testing whether a supplier could actually absorb what it agrees to.

Insurance should follow responsibility

Insurance is often handled as a compliance exercise: collect certificates of currency, file them, move on. That misses its purpose. Insurance is a way of financing selected consequences when defined events happen. It should sit underneath the contract’s allocation of responsibility, not alongside it.

A sensible sequence:

1. Risk map. What could go wrong: damage to property or work, injury to workers, harm to third parties, design or advice errors, data loss, stock spoilage, business interruption?
2. Responsibility map. Under each contract, who is responsible for each of those?
3. Policy map. Which policy, yours or the other party’s, is meant to respond to each?
4. Gaps. What is excluded, capped or subject to large excesses? Which retained residues from your contracts are not insured at all?
5. Timing. When does each cover start, change and end? Responsibility often shifts at milestones such as site possession, handover or the end of a defects period.
6. Evidence. What proof do you need, and who checks it?

Some common misunderstandings:

• A certificate is not adequacy. It proves a policy exists, not that it responds to your risk, at the right limit, for the right parties.
• Not every contractual liability is insured. A supplier may agree to carry a risk its insurance does not cover.
• Copied requirements drift. Insurance requirements carried over from a previous job may not fit a different kind of work, design responsibility or location.
• Design changes responsibility. If a contractor or consultant takes on design work, professional indemnity cover may become relevant, and a variation that adds design work can change which policies matter.
• Insurance buys money, not outcomes. It can pay for a loss; it cannot return a lost customer or a missed season.

The pricing your risk controls article suggests recording each policy’s premium, excess, main exclusions and limits alongside your other controls, so its real cost and reach are visible.

A worked example

This is an illustration. A fresh produce wholesaler with a cold store and delivery fleet reviews four contracts it depends on. In each case it estimates a plausible bad failure, reads the liability terms and works out what it would realistically keep.

The residues total about $342,000. More importantly, a regional power outage could trigger three of them at once: refrigeration, software and security together leave about $299,000. The business has about $120,000 in cash. Its insurance package covers theft, but the owner is not sure whether it covers stock spoilage from a refrigeration breakdown or power failure.

The business takes several steps:

• It asks its broker about stock deterioration and business interruption cover, including power supply failure, and what excesses, limits and conditions apply.
• It installs a backup generator for the cool rooms, which changes the odds rather than who pays.
• It renegotiates the refrigeration contract, paying a higher fee for a faster response time and a higher cap, since that contract carries the largest residue relative to its price.
• It declares value or arranges transit insurance for high-value loads.
• It changes its approval rule: any contract leaving a residue above $50,000 must be approved by the owner, regardless of the contract’s price.

The review takes two afternoons. Before it, the business believed its suppliers “carried” most of these risks.

How this applies to a small Australian business

• List the contracts you depend on, including small ones such as software, maintenance and monitoring.
• Estimate the residue for each: failure cost, excluded losses, notice periods and caps.
• Group residues that one event could trigger together.
• Compare the largest group with your cash and insurance.
• Set approval rules by residue, not only by contract price.
• Compare quotes with their liability terms included.
• Map insurance to responsibility, and check what is excluded, capped or subject to large excesses.
• Review insurance when work changes, especially when design responsibility or site control changes.
• Get legal advice on important clauses. The Australian Consumer Law includes protections such as statutory guarantees and rules against unfair terms in some standard form contracts with small businesses, which may affect what a clause can do.

Signals worth watching

• Contracts approved by price with nobody reading the liability clause.
• Small contracts for services the business depends on completely.
• Certificates of currency filed but never checked for limits or exclusions.
• Insurance renewed on last year’s structure while contracts have changed.
• Notice periods shorter than the time it would take to discover a problem.
• Several suppliers relying on the same power, platform or site.

Common mistakes

• Treating liability clauses as fine print.
• Assuming the cap bears some relation to the loss.
• Forgetting excluded losses, which are often the largest part.
• Assessing contracts one at a time and never adding up the residues.
• Choosing the cheapest bid without counting the risk it hands back.
• Equating a certificate with adequate cover.

Frequently asked questions

Should we refuse contracts with liability caps? No. Caps are normal and often reasonable. The point is to know what you are keeping and to decide whether to accept, insure or reduce it.

What does “consequential loss” mean? Its meaning in a contract depends on the wording and how courts interpret it, and it can vary. Commercially, assume it may exclude much of the indirect cost of a failure, such as lost profit, and get legal advice on important contracts.

Can we negotiate caps with large suppliers? Sometimes. Large suppliers often have standard terms, but higher caps, service credits or specific carve-outs can be available, sometimes for a higher price.

Is our own insurance enough? It depends on what it covers. Ask your broker specifically about the residues you have identified, rather than asking whether you are “covered”.

Do these rules apply when we are the supplier? Yes, in reverse. Your own caps and exclusions protect you, and your customers will judge them. Make sure your insurance supports the liabilities you accept.

Questions to ask

• What is the total loss our contracts would leave us to carry?
• Which single event could trigger several of those losses at once?
• Who in the business is allowed to accept a liability cap?
• How do our supplier comparisons account for different liability terms?
• Which of our residues are insured, and which are not?
• When did we last check that our insurance matches our current contracts?

Bringing it together

Liability caps and exclusion clauses are not fine print. They are decisions about who carries the loss when something goes wrong, and the loss above the cap stays with you. Read each clause as a sequence of reductions: excluded losses, notice periods, then the cap. Add up what you keep across contracts, group the losses that one event could trigger together, and compare the total with what the business could absorb. Compare quotes with their liability terms included, set approval rules based on the loss retained rather than the price, and make insurance follow the responsibilities your contracts actually create. Accepting a cap can be a good trade, but only if someone has decided to make it.

---

Source: KEVOS notes, drawing on teaching material on exclusion and limitation clauses, contract insurance requirements and contract administration. Examples and figures in this article are illustrations. This article is general information, not legal, financial or insurance advice.