What Is a Liability Cap, and Why Your SOW Needs One
A liability cap bounds how much one party can be forced to pay the other if something goes wrong -- here is what it covers, what it typically excludes, and why the exclusions matter as much as the number.
July 20, 2026 · By ScopeWise Team
What a liability cap does
A liability cap is a contract clause that sets a ceiling on the total amount one party can be required to pay the other in damages. It usually applies as a multiple of fees paid (twelve months of fees is common) or as a fixed dollar figure. Without one, a party is in theory exposed to the full extent of a claimed loss -- lost profits, delay costs, rework -- however large that turns out to be. The cap does not eliminate risk, it bounds it to a known, negotiated number.
Why the carve-outs matter more than the number
Almost every liability cap comes with a list of carve-outs -- categories of loss that stay uncapped regardless of the headline number. Common carve-outs include confidentiality breaches, gross negligence, willful misconduct, IP infringement, and indemnification obligations. A cap of "12 months of fees" sounds protective until you notice indemnification is carved out entirely, at which point the real exposure is whatever the indemnification clause covers, uncapped. Reading the cap amount without reading the carve-out list gives a false sense of the actual protection in place.
Mutuality: does it run both ways?
A liability cap that only protects one party is a red flag worth raising even if the number looks reasonable. In a healthy SOW, the cap applies symmetrically -- both the vendor and the client are protected by the same ceiling, with the same carve-outs. One-sided caps usually show up when one party's legal team drafted the document and the other side did not push back during negotiation, which is common when a SOW is reviewed quickly by whoever needs the project started rather than by legal counsel.
What a missing liability cap means
If a SOW has no liability cap at all, both parties are exposed to unbounded damages claims for anything that goes wrong on the engagement -- a missed deadline that cascades into a client's own downstream losses, a security incident, a defect that causes business disruption. This is more common in smaller or rushed engagements than most people expect, precisely because a missing clause does not visually stand out the way a bad clause does. It has to be actively checked for, not just read past.
How to review one
Check three things in order: is there a cap at all, what is the amount and how is it calculated (fixed figure vs. multiple of fees), and what is carved out. Then check mutuality -- does the same cap and carve-out list apply to both parties. ScopeWise's Commercial agent runs this exact check on every SOW it reviews, flagging missing caps, unusually asymmetric terms, and carve-out lists broad enough to functionally uncap the clause -- alongside the five other review agents (Scope, Delivery, Security, PMO, Legal) and the rule engine that scan the rest of the document.