Identify Disclosure Schedule Issues

---
name: identify-disclosure-schedule-issues
task_id: corporate-ma/identify-disclosure-schedule-issues
description: Guides cross-referencing of disclosure schedules against transaction representations, diligence materials, and source documents to identify gaps, inconsistencies, and incompleteness requiring remediation.
activates_for: [planner, solver, checker]
---

# Skill: Disclosure Schedule Issues Identification

## 1. Subject-matter triage
- Use this skill when the task is to compare disclosure schedules to merger-agreement representations, the data room index, diligence notes, and financial materials, then prepare an issues memo with remediation.
- Identify the universe of schedules and representations first; if multiple schedules, exhibits, financial periods, entities, or diligence sources are in scope, enumerate them before analyzing so each can be checked once and only once.
- Treat the memo as an advisory deliverable: the goal is not merely to spot omissions, but to state why each gap matters and what should be done next.

## 2. Failure modes the skill is correcting
- The review confirms that schedules exist in a formal sense without testing whether they actually capture all known exceptions to the relevant reps as of signing.
- Materials surfaced in the data room or diligence memo are not systematically matched to the corresponding schedule entry, so obvious omissions survive.
- Schedule text, exhibits, and financial materials are read in isolation, allowing internal inconsistencies to go unnoticed.
- Issues are described without severity, cross-reference, consequence, or a concrete fix.
- The memo stops at identification and does not convert findings into a practical remediation plan.
- The analysis assumes one pass over the schedules is enough even where multiple reps, periods, or document sets require separate review.

## 3. Legal frameworks / domain conventions that apply
- Disclosure schedules are exceptions lists, not generic background summaries; assess whether each schedule captures the known carve-outs required by the corresponding representation.
- A schedule must be read in light of the specific rep it qualifies, the knowledge qualifier if any, and any defined terms that narrow or expand the disclosure burden.
- Common issue buckets include contracts, litigation, regulatory matters, real property, IP, employee/benefit matters, compliance exceptions, indebtedness, related-party items, and other rep-specific carve-outs.
- Data room indexing is a disclosure cross-check tool: if a document falls within the scope of a rep and is present in the source set, test whether the matching schedule discloses it.
- Diligence findings are a second cross-check source: if the diligence memo flags a fact within the scope of a rep, the absence of corresponding disclosure is a potential gap.
- Financial statements, management accounts, and schedule exhibits must be checked for internal consistency on dates, categories, amounts, and classifications; reconcile narrative disclosures to the underlying financial presentation.
- Apply the governing transaction document framework and any expressly referenced standards in the source materials; do not assume a disclosure is sufficient just because it is technically mentioned if the rep calls for fuller disclosure.
- Remediation should be framed in transaction terms: supplement, correct, expand, or add disclosure; if facts are incomplete, flag the need for further verification before finalizing the schedule.

## 4. Analytical scaffolds
- Build a rep-by-rep matrix: representation, corresponding schedule, source documents to compare, gap assessment, severity, consequence, and remediation.
- For each rep:
  - confirm the schedule section exists;
  - identify the disclosure standard the rep imposes;
  - compare the schedule against the data room index;
  - compare the schedule against diligence findings;
  - compare any financial exhibit or schedule narrative against the financial materials.
- For each issue, close the analysis with three moves:
  - anchor the issue to a specific scale, date, amount, period, or scope element drawn from the source set;
  - cross-reference the interacting schedule, rep, exhibit, or document that creates the discrepancy;
  - state the downstream consequence for the client, including transactional, economic, operational, regulatory, or litigation impact.
- Assign a severity level to every issue using a single ordinal scale defined at the outset, and apply it consistently across the memo.
- If only one schedule, one period, or one entity is actually in scope, say so expressly; otherwise, do not collapse distinct items into one generalized finding.
- Separate true omissions from drafting imprecision: a missing disclosure, an incomplete disclosure, and a mismatch between documents are different defects and should be labeled distinctly.

## 5. Vertical / structural / temporal relationships
- Check temporal alignment: disclosures should be assessed as of the signing snapshot reflected in the source materials, not based on later events unless the documents make later updates relevant.
- Where the source set includes multiple versions or cutoffs, identify which version governs each comparison and note any date drift that could make a disclosure stale.
- Where schedules refer to affiliates, subsidiaries, contracts, locations, matters, or personnel, trace the disclosure one level down to the underlying item in the source set rather than stopping at the umbrella label.
- Where financial data is presented on a different basis than the schedules, state the basis mismatch and whether the discrepancy is one of timing, classification, or amount.
- If a representation is qualified by knowledge, evaluate whether the source set suggests the matter would fall within the knowledge set even if no express admission appears in the schedules.

## 6. Output structure conventions
- Produce a single disclosure-schedule-issues memorandum.
- Begin with a concise executive summary that flags the most material gaps and the overall risk picture.
- Define the severity scale once near the top, then use it uniformly throughout the issues list.
- Follow with an organized issue analysis section arranged by transaction rep or schedule group, not by source document alone.
- For each issue entry, include: severity; related rep or schedule; issue description; source cross-references; impact or consequence; and recommended remediation.
- End with a standalone Recommended Actions section that uses imperative verbs, names the responsible role from the source set where possible, and includes a timing anchor tied to the signing, disclosure update, or closing process.
- Use conventional legal drafting headings and compact tables where helpful, but do not mimic any hidden rubric structure or rely on unlabeled narrative alone.
- Keep the memorandum action-oriented: every material issue should be paired with a fix, a reviewer path, or a request for further fact development before finalization.