Liability cap
A contractual limitation on the total financial liability one party can face to the other under the agreement, typically expressed as a multiple of contract fees or an absolute monetary amount. In AI vendor agreements, buyers must negotiate carve-outs from the general liability cap for regulatory-compliance and data-protection indemnities, because the default cap may be far below the actual regulatory penalty exposure.
Defined in 2 GAGE programs, which carry 2 distinct definitions of it. The wording above is taught in EU AI Act Implementation Expert.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
A contractual limitation on the total financial liability one party can face to the other under the agreement, typically expressed as a multiple of contract fees or an absolute monetary amount. In AI vendor agreements, buyers must negotiate carve-outs from the general liability cap for regulatory-compliance and data-protection indemnities, because the default cap may be far below the actual regulatory penalty exposure.
The contractual ceiling on what a party can be made to pay, typically tied to fees paid over a defined period, sitting atop categorical exclusions (consequential damages, lost profits, lost data). It allocates the tail of the risk, and AI's correlated failures make the tail long.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- The AI contract: the clauses that protect you when the vendor's model fails · Shipping AI and Surviving the Incident, Certified AI Governance Professional (CAIGP)
- Contractual Risk Allocation with AI Vendors · Regulatory Interplay and Liability, EU AI Act Implementation Expert
Where it shows up at work
A definition is where Liability cap starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Turns controls into enforceable obligations: data use, change notice, audit rights, incident duties, subcontractors, IP, exit and deletion.
2 lessons on this page teach it as a primary outcome.
Tiers vendors by use and impact, requests evidence instead of promises, tests in the customer's context, and plans monitoring and exit.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- AI Vendor Risk Managerneeds it at depth
- Third-Party Cyber Risk Managerneeds it at depth
- Third-Party AI Risk Analystneeds it at depth
- AI Regulatory Counselneeds it at depth · 14 open postings this week
- Chief Information Officer, technology leadership editionneeds it at depth
- Chief Audit Executive, AI audit editionneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: GDPR Article 28; EU AI Act value-chain obligations; NIST AI RMF GOVERN 6 and MANAGE 3; ISO/IEC 42001 Annex A supplier controls.
One interview question about it
Which contract terms would you insist on before a vendor's model touches customer data, and what happens when the vendor changes the model?
Asked of candidates for contract terms that allocate ai risk. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Legal and paralegal work carries it as work you can show: Contract terms are your product.
- A law degree (JD, LLB or LLM), no AI work yet carries it as a claim to back up: Contract terms that move risk are a first-year subject.
- Privacy and data protection carries it as a claim to back up: Processor and vendor review is routine privacy work.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.