Learn essential IT contract vocabulary: liability caps, indemnification, hold harmless clauses, consequential damages, force majeure, and liquidated damages.
0 / 5 completed
1 / 5
A SaaS contract states: 'Provider's total aggregate liability shall not exceed the fees paid in the preceding 12 months.' What type of contractual provision is this?
A liability cap (also called a limitation of liability) sets a ceiling on the total financial exposure one party can face under the contract. In IT contracts, caps are commonly tied to fees paid (e.g., 'fees paid in last 12 months' or '2x annual contract value'). This protects vendors from catastrophic claims while giving clients a known recovery ceiling.
2 / 5
A vendor's software breach exposes a client's customer data. The contract requires the vendor to defend the client against third-party lawsuits and cover legal costs. What is this obligation called?
Indemnification is a contractual obligation where one party (the indemnitor) agrees to compensate the other (the indemnitee) for specified losses, including third-party claims, legal defence costs, and settlements. In IT contracts, common indemnification triggers include IP infringement claims, data breaches caused by the vendor, and gross negligence.
3 / 5
A contract clause states: 'Client shall hold vendor harmless from any claims arising from Client's use of the software in violation of applicable law.' What does 'hold harmless' mean here?
A hold harmless clause means the protected party (vendor here) will not be held responsible for losses arising from a specified situation. It is often paired with indemnification — the indemnification covers third-party claims while hold harmless covers direct claims between the contracting parties. Together they form a comprehensive liability shield for the specified trigger.
4 / 5
Which category of damages — commonly excluded in IT contracts — covers losses like lost profits, lost business opportunities, and reputational harm that flow indirectly from a breach?
Consequential damages (also called indirect or special damages) are losses that don't flow directly from a breach but are a downstream consequence — e.g., a client losing a major deal because the vendor's software was down. IT vendors routinely disclaim consequential damages to avoid open-ended liability. Courts require these to be 'foreseeable' at the time of contracting (Hadley v Baxendale rule).
5 / 5
A cloud hosting contract specifies: 'If uptime falls below 99.5% in any month, Client is entitled to a service credit equal to 10% of that month's fees.' This is an example of:
Liquidated damages (LDs) are a pre-agreed sum payable upon a specific breach (such as missing an SLA). Unlike actual damages, they are fixed in advance and meant to represent a genuine pre-estimate of loss. In IT contracts, LDs often appear as service credits for SLA misses. Courts will enforce LDs only if they represent a genuine estimate — not a penalty.