Compare Acquisition Agreement Indemnification Provisions Against Precedent Database

---
name: compare-indemnification-provisions-precedent
task_id: corporate-ma/compare-acquisition-agreement-indemnification-provisions-against-precedent-database
description: Guides provision-by-provision comparison of draft indemnification terms against a firm playbook and precedent, assessing structural gaps in basket type, materiality scrape, knowledge qualifier, defense control, survival periods, and special representation treatment.
activates_for: [planner, solver, checker]
---

# Skill: Compare Acquisition Agreement Indemnification Provisions Against Precedent Database

## 1. Subject-matter triage

- Treat this as a comparison and deviation-analysis task, not a full-form drafting task.
- Identify the draft indemnification article, the playbook standard, and the cited precedent baseline before analyzing any deviations.
- If multiple provisions, survival periods, or claim types are in scope, enumerate them first and analyze each separately; do not collapse distinct items into one generic pass.
- Preserve the transactional context supplied by the term sheet and use it only to interpret why a deviation matters, not to replace the provision-by-provision comparison.

## 2. Failure modes the skill is correcting

- Comparing indemnification provisions at a summary level without tracking how basket, cap, survival, scrape, knowledge, defense control, and special-rep treatment interact.
- Missing deal context that makes a deviation more or less consequential for buyer protection.
- Treating a tax survival issue as ordinary when the claims window can extend beyond a generic survival period.
- Failing to distinguish general representations from provisions that should receive separate survival or cap treatment because of their commercial importance.
- Describing a gap without tying it to the controlling authority, the cross-referencing clause, and the downstream exposure it creates.

## 3. Legal frameworks / domain conventions that apply

- Indemnification mechanics should be read as a system: scope, basket, cap, survival, carve-outs, escrow, knowledge qualifiers, scrape, and defense provisions must be assessed together.
- Anti-sandbagging principles matter because buyer knowledge at closing can change whether a breach is recoverable; the knowledge standard and knowledge group define the imputation risk.
- A materiality scrape changes whether qualifiers are ignored for breach analysis, loss calculation, or both; the distinction is structural, not stylistic.
- Defense control and settlement authority determine whether the indemnified party can protect its position in third-party claims.
- In technology or IP-heavy deals, intellectual property reps often warrant separate attention because their treatment can shift both survival and cap economics.
- Tax representation survival should be compared against the applicable limitations period and any customary tail; a shorter survival can create a coverage gap.
- Title-to-equity-interest treatment should be tested for whether it receives fundamental-representation status when the target is an equity-holding entity.
- Cite the controlling legal or transactional authority for each proposition relied on, including the relevant provision in the source set, the playbook rule, or a generally recognized M&A drafting convention.

## 4. Analytical scaffolds

- Begin each issue with the draft position, then state the playbook position, then the precedent benchmark, then the deviation.
- For every deviation, identify:
  1. the affected provision and its exact function in the indemnity architecture;
  2. the scale of the issue using a number or threshold drawn from the source materials when available;
  3. the related clause, schedule, or document that changes the practical effect of the provision;
  4. the consequence for the client if the deviation remains.
- Run the analysis provision by provision for:
  - scope of indemnification and exclusions
  - basket type and amount
  - general cap
  - fundamental-rep cap treatment
  - survival periods for general, fundamental, IP, and tax reps
  - anti-sandbagging
  - materiality scrape
  - knowledge qualifier and knowledge group
  - defense control and settlement authority
  - IP rep treatment
  - title-to-interests treatment
  - escrow amount and release mechanics
- When comparing a provision to precedent, specify whether the deviation is more favorable to buyer or seller and why that matters in the deal context.
- Use authority-based reasoning rather than conclusory labels; each legal or drafting proposition should be tied to the governing document, playbook rule, or recognized drafting norm.

## 5. Vertical / structural / temporal relationships

- Test how one provision affects another before calling a deviation harmless.
- Read basket, cap, carve-outs, and escrow together because changes in one can offset or amplify another.
- Read survival alongside the underlying claim window, especially for tax and special representations.
- Read knowledge qualifiers alongside anti-sandbagging, because a narrower knowledge group can materially expand seller protection.
- Read defense control alongside settlement authority and any notice timing mechanics, because control without consent rights can eliminate practical leverage.
- Read special-representation treatment alongside cap and survival because a rep can be substantively important even if it is not labeled fundamental.
- If the source set gives only one applicable period, claim, or class of representation, say so affirmatively before analyzing it.

## 6. Output structure conventions

- Produce a deviation analysis memo organized by provision, using industry-conventional headings rather than the rubric’s internal checklist language.
- For each provision, include:
  - current draft language
  - playbook position
  - precedent benchmark
  - gap analysis
  - recommended revision
  - severity using a uniform ordinal scale defined once at the top
- Each issue entry must close the loop by tying the deviation to its scale, any interacting clause or document, and the downstream consequence.
- Include an explicit priority matrix that ranks the deviations by practical importance.
- End with a concise Recommended Actions section that assigns an imperative, a responsible role, and a timing anchor tied to the transaction timeline.
- If the task requires a file, ensure the named deliverable is the operative output and not merely a summary of it; the memo should be the finished product.