Identify Regulatory And Methodological Issues In Expert Damages Report

---
name: identify-regulatory-and-methodological-issues-in-expert-damages-report
task_id: corporate-governance/identify-regulatory-and-methodological-issues-in-expert-damages-report
description: Agents identify general methodology weaknesses without addressing a potentially dispositive contractual damages waiver as a threshold issue, verifying arithmetic in discount-rate or margin calculations, applying the reasonable-certainty standard to separate damages periods, or identifying a duty-to-mitigate provision as an independent basis for damages reduction.
activates_for: [planner, solver, checker]
---

# Skill: Identify Issues in an Expert Damages Report — Defense Perspective Memorandum

## 1. Subject-matter triage
- Treat the work as an issues memorandum, not a rebuttal report and not a damages re-computation.
- Start by scanning for any threshold contractual limitation on damages, then move to admissibility and methodology, then to quantum-reduction arguments, then to cross-examination points.
- If the source set contains multiple damages theories, periods, models, or scenarios, enumerate them first and analyze each separately rather than collapsing them into one blended critique.

## 2. Failure modes the skill is correcting
- Baseline treats all defects as equal and misses threshold bars that may defeat or narrow the claimed damages category before methodology matters.
- Baseline critiques assumptions without tying each issue to the specific report section, the governing rule, and the downstream effect on recoverability or quantum.
- Baseline flags discount rates, margins, or present-value calculations without independently checking the arithmetic for concrete error.
- Baseline fails to segment damages by period, especially where one period is more speculative or less supportable than another.
- Baseline overlooks mitigation evidence as an independent reduction argument.
- Baseline gives descriptive criticisms without indicating whether each issue is exclusionary, weight-only, or best reserved for cross-examination.

## 3. Legal frameworks / domain conventions that apply
- **Contractual damages limitations first:** Review the agreement and related operative documents for clauses limiting or waiving consequential, indirect, special, punitive, or similar damages, plus any language that affects lost-profits recovery. Apply the governing contract-interpretation rule from the relevant jurisdiction and treat any such clause as a threshold issue.
- **Expert admissibility:** Under the applicable evidence rule or gatekeeping standard, expert opinions must rest on sufficient facts or data, use reliable principles and methods, and apply those methods reliably. Identify defects that may support exclusion, not just impeachment.
- **Reasonable certainty:** Lost profits and similar damages must be proven with reasonable certainty under the governing damages doctrine. Evaluate that standard separately for each time period or scenario the expert addresses.
- **Mitigation:** Where the record shows plausible loss-reduction opportunities, evaluate the duty to mitigate under the controlling contract clause or common-law doctrine as a standalone reduction theory.
- **Discounting and present value:** Future losses generally must be discounted to present value using a rate justified by the business, industry, and risk profile. Unsupported rate selection or inconsistent compounding methodology is a material weakness.
- **Margin selection:** Distinguish incremental contribution margin from net income or other broader margin measures, and test whether the chosen margin matches the loss theory and excluded-fixed-cost assumptions.
- **Benchmark selection:** If the report relies on peers, industry data, or comparator companies, assess whether the benchmark set is representative and free from cherry-picking or survivorship bias.
- **Authority citation discipline:** Every legal proposition should be anchored to a controlling statute, rule, regulation, or case, rather than stated as a bare conclusion.

## 4. Analytical scaffolds
- **Threshold issue screen:** Identify any damages waiver, limitation-of-liability clause, exclusion, cap, or mitigation language that may bar or narrow the claim before analyzing methodology.
- **Report-map by section:** For each issue, identify the exact report section, assumption, table, or model input implicated.
- **Period-by-period review:** Break the claim into discrete periods or scenarios and test reasonable certainty separately for each one.
- **Arithmetic verification:** Recompute stated projections, margins, discounting, and present-value steps where the source materials permit, and note any specific computational error.
- **Admissibility vs. weight:** Classify each issue by whether it is a likely exclusion argument, a weaker admissibility challenge, or a credibility point for cross-examination.
- **Mitigation lens:** Look for evidence of alternative sourcing, substitute transactions, offsetting revenue, or other practical steps that would have reduced losses.
- **Benchmark audit:** Test whether comparator selection is internally consistent, representative, and free from post hoc filtering.
- **Issue-closing discipline:** For each issue, tie the point to a scale drawn from the source record, cross-reference the related clause, schedule, or report exhibit, and state the practical consequence for the defense.

## 5. Vertical / structural / temporal relationships
- Analyze the damages claim in a hierarchy: contract-level limits, then expert methodology, then line-item computation, then period-specific certainty, then mitigation and residual cross-examination points.
- Where the report uses a forecast across time, distinguish historical actuals, transition periods, and forward-looking periods, because certainty and causation often weaken as the timeline extends.
- Where multiple business units, products, or revenue streams are involved, keep them separate unless the report itself aggregates them with a defensible common methodology.
- Where a dispute spans pre-breach, breach-period, and post-breach or post-expiration losses, do not apply one standard uniformly without noting the varying proof burden.

## 6. Output structure conventions
- Write the memo as a defense-side issues memorandum with a short executive summary, a prioritized issue discussion, and a concise closing recommendations section.
- Define one ordinal severity scale at the outset and apply it uniformly to every issue entry.
- For each issue, include:
  - severity;
  - the report section or model input affected;
  - the governing authority or methodological rule;
  - the factual basis from the source materials;
  - the scale of exposure or period affected, using only figures that appear in the source set;
  - the interacting clause, exhibit, schedule, or document, if any;
  - the consequence for the defense, including exclusion, reduction, or impeachment value.
- Do not present only abstract commentary; each issue should end with the practical litigation consequence.
- Include a brief table or bullets that rank issues by severity and likely impact.
- End with a **Recommended Actions** block that gives concrete next steps in imperative form, assigns the responsible role where available, and ties timing to the litigation or expert-discovery schedule if the source materials provide one.