Learn essential IT contract vocabulary: liability caps, indemnification, hold harmless clauses, consequential damages, force majeure, and liquidated damages.
0 / 10 completed
1 / 10
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 / 10
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 / 10
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 / 10
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 / 10
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.
6 / 10
During a code review, Sarah from Legal comments on the draft API terms: 'We need to ensure that our liability is capped at $50,000 per incident. This protects us against potentially large claims.' What legal principle is Sarah primarily referencing?
Indemnification refers to one party agreeing to protect another from financial loss or legal liability. Sarah's statement is a specific example of this – the company (the 'provider') promises to cover the other's losses up to a defined amount. 'Breach of contract' concerns violating an agreement, while 'force majeure' deals with unforeseen events and 'negligence' relates to carelessness.
7 / 10
Mark, the DevOps engineer, sends a Slack message to the team: 'Just deployed the new server – let's hope this doesn't lead to any claims against us if there's a data breach. The SLA covers a lot, but we need to be careful.' What is Mark primarily concerned about?
Mark's message highlights the importance of an SLA (Service Level Agreement). An SLA outlines the terms of service, including liability limitations and remedies for downtime or failures. While compliance, audits, and risk assessments are important, Mark's immediate concern is with the contractual obligations protecting his company from potential claims arising from a service disruption.
8 / 10
A PR description for a new feature states: 'This update includes enhanced logging to support forensic investigations in the event of a security incident. We've taken steps to mitigate potential liability related to data access.' What does this phrase – 'mitigate potential liability' – suggest about the development team's approach?
The phrase 'mitigate potential liability' indicates a proactive effort to reduce the company's exposure to financial or legal consequences. This means they are taking steps – in this case, enhanced logging – to demonstrate due diligence and minimize the chances of a claim being successfully pursued. It's not accepting full responsibility, nor is it ignoring best practices.
9 / 10
During a standup meeting, David, the product manager, asks: 'Has anyone reviewed the indemnification clause in the new payment gateway contract? We need to ensure we're not overly exposed if there are fraudulent transactions.' What is David asking about specifically regarding this clause?
David is focused on the 'limits of liability' section within the indemnification clause. This part of the contract defines the maximum amount one party (the vendor) will be responsible for covering if claims arise due to breaches or errors in their service. The other options relate to different aspects of the contract, but not the core question of liability exposure.
10 / 10
An API response from a third-party service states: 'Rate limiting applied – exceeding 100 requests per minute will result in temporary suspension and potential legal action.' What type of clause is this example illustrating?
This response demonstrates a limitation of liability clause. It establishes the conditions under which the third-party service provider can take legal action against the user for violating their terms of service – in this case, exceeding rate limits. It's not an exclusivity or service level agreement (although it contains elements of SLA), nor is it directly about indemnification.
What will I practise in "Liability & Indemnification Vocabulary"?
Learn essential IT contract vocabulary: liability caps, indemnification, hold harmless clauses, consequential damages, force majeure, and liquidated damages.
How many exercises are in this module?
This module has 10 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Legal Contracts exercises?
Browse the full Legal Contracts hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.