1---2name: compare-indemnification-provisions-precedent3task_id: corporate-ma/compare-acquisition-agreement-indemnification-provisions-against-precedent-database4description: 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.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/compare-indemnification-provisions-precedent8---910# Skill: Compare Acquisition Agreement Indemnification Provisions Against Precedent Database1112## 1. Subject-matter triage1314- Treat this as a comparison and deviation-analysis task, not a full-form drafting task.15- Identify the draft indemnification article, the playbook standard, and the cited precedent baseline before analyzing any deviations.16- 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.17- 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.1819## 2. Failure modes the skill is correcting2021- Comparing indemnification provisions at a summary level without tracking how basket, cap, survival, scrape, knowledge, defense control, and special-rep treatment interact.22- Missing deal context that makes a deviation more or less consequential for buyer protection.23- Treating a tax survival issue as ordinary when the claims window can extend beyond a generic survival period.24- Failing to distinguish general representations from provisions that should receive separate survival or cap treatment because of their commercial importance.25- Describing a gap without tying it to the controlling authority, the cross-referencing clause, and the downstream exposure it creates.2627## 3. Legal frameworks / domain conventions that apply2829- 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.30- 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.31- A materiality scrape changes whether qualifiers are ignored for breach analysis, loss calculation, or both; the distinction is structural, not stylistic.32- Defense control and settlement authority determine whether the indemnified party can protect its position in third-party claims.33- In technology or IP-heavy deals, intellectual property reps often warrant separate attention because their treatment can shift both survival and cap economics.34- Tax representation survival should be compared against the applicable limitations period and any customary tail; a shorter survival can create a coverage gap.35- Title-to-equity-interest treatment should be tested for whether it receives fundamental-representation status when the target is an equity-holding entity.36- 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.3738## 4. Analytical scaffolds3940- Begin each issue with the draft position, then state the playbook position, then the precedent benchmark, then the deviation.41- For every deviation, identify:42 1. the affected provision and its exact function in the indemnity architecture;43 2. the scale of the issue using a number or threshold drawn from the source materials when available;44 3. the related clause, schedule, or document that changes the practical effect of the provision;45 4. the consequence for the client if the deviation remains.46- Run the analysis provision by provision for:47 - scope of indemnification and exclusions48 - basket type and amount49 - general cap50 - fundamental-rep cap treatment51 - survival periods for general, fundamental, IP, and tax reps52 - anti-sandbagging53 - materiality scrape54 - knowledge qualifier and knowledge group55 - defense control and settlement authority56 - IP rep treatment57 - title-to-interests treatment58 - escrow amount and release mechanics59- 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.60- 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.6162## 5. Vertical / structural / temporal relationships6364- Test how one provision affects another before calling a deviation harmless.65- Read basket, cap, carve-outs, and escrow together because changes in one can offset or amplify another.66- Read survival alongside the underlying claim window, especially for tax and special representations.67- Read knowledge qualifiers alongside anti-sandbagging, because a narrower knowledge group can materially expand seller protection.68- Read defense control alongside settlement authority and any notice timing mechanics, because control without consent rights can eliminate practical leverage.69- Read special-representation treatment alongside cap and survival because a rep can be substantively important even if it is not labeled fundamental.70- If the source set gives only one applicable period, claim, or class of representation, say so affirmatively before analyzing it.7172## 6. Output structure conventions7374- Produce a deviation analysis memo organized by provision, using industry-conventional headings rather than the rubric’s internal checklist language.75- For each provision, include:76 - current draft language77 - playbook position78 - precedent benchmark79 - gap analysis80 - recommended revision81 - severity using a uniform ordinal scale defined once at the top82- Each issue entry must close the loop by tying the deviation to its scale, any interacting clause or document, and the downstream consequence.83- Include an explicit priority matrix that ranks the deviations by practical importance.84- End with a concise Recommended Actions section that assigns an imperative, a responsible role, and a timing anchor tied to the transaction timeline.85- 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.