Draft Disclosure Schedule Preparation

---
name: draft-disclosure-schedule-preparation
task_id: corporate-ma/draft-disclosure-schedule-preparation
description: Guides preparation of a complete disclosure schedule package keyed to the acquisition agreement, with a master table of contents, individual schedules for each representation, and an Outstanding Items Memo tracking pre-closing actions including IP chain-of-title gaps, regulatory notice requirements, and open-source copyleft issues.
activates_for: [planner, solver, checker]
---

# Skill: Draft Disclosure Schedule Preparation

## 1. Subject-matter triage (only if applicable)

- Treat the agreement as the organizing instrument: identify every representation, warranty, covenant, and definition that requires disclosure support before drafting any schedule.
- Separate items that are purely responsive disclosures from items that are remediation tasks; do not bury pre-closing fixes inside a generic schedule entry.
- Build the package only from the source record in the data room and the acquisition agreement; if an item cannot be grounded in a document, flag it as needing confirmation rather than inventing detail.
- When multiple subsidiaries, contracts, employees, policies, filings, or assets are implicated, enumerate them first and then allocate each to the proper schedule or workstream.

## 2. Failure modes the skill is correcting

- Treating disclosure schedules as a naming exercise instead of a controlled cross-reference system tied to specific agreement sections.
- Omitting material exceptions, qualifications, or carveouts because the reviewer looked only for obvious deal blockers rather than all responsive facts.
- Misclassifying a remediation item as a disclosure item, especially where title, recording, notice, consent, or filing steps remain open.
- Collapsing distinct legal categories into one omnibus entry, which obscures whether a fact belongs on the IP, tax, employment, contracts, insurance, regulatory, or real-estate schedule.
- Failing to carry the same fact consistently across the master package, individual schedules, closing checklist, and outstanding-items memo.
- Describing a status issue as if it were already cured, particularly for filings, assignments, consents, notices, or certificates that are still pending.
- Drafting the package without a clear hierarchy of what is disclosed, what is reserved, what is excluded, and what requires post-signing action.
- Leaving the reader unable to tell whether an item is informational, a bring-down issue, a closing condition, or a pre-closing covenant.

## 3. Legal frameworks / domain conventions that apply

- Disclosure schedules function as section-specific qualifications to acquisition agreement representations; each disclosure should be mapped to the correct section and should not be assumed to qualify unrelated provisions.
- The master schedule should operate as a table of contents plus incorporation convention, stating that a disclosure in one place may qualify every responsive section unless the agreement requires a narrower linkage.
- Chain-of-title issues in IP and other registered assets require special care: executed-but-unrecorded or incomplete assignments should be treated as defect items that may require cure before closing, not merely as background facts.
- Open-source and similar software compliance issues should be identified at the component level when they affect proprietary code, distribution obligations, or source-code disclosure risk.
- Tax disclosures must distinguish filed returns from returns in preparation, open audits, elections, and nexus/registration positions; do not imply completion where only preparation exists.
- Regulatory and permits disclosures should capture notice, approval, registration, and waiting-period requirements where a change of control or asset transfer may trigger them.
- Employment and equity disclosures should show the full compensation structure, including pool authorization, grants, vesting status, and any contingent obligations that affect post-closing economics.
- Material contracts should be grouped by category and should identify amendment, renewal, termination, consent, anti-assignment, and change-of-control issues where relevant.
- Insurance disclosures should reflect coverage type, carrier, limits, exclusions, claims status, and any lapse or notice obligations.
- Real-estate and landlord matters should capture lease consent, estoppel, recognition, or waiver requirements if the transaction implicates occupancy or transfer rights.
- Use controlling authority only where the proposition is legal rather than factual; when the source materials identify a statute, regulation, or other authority, cite it in the schedule or memo rather than implying it.

## 4. Analytical scaffolds

- Start with a representation-by-representation map of the acquisition agreement and identify which schedules, if any, support each section.
- For each source document or data-room cluster, ask: what fact does this support, which representation does it qualify, and whether it creates a disclosure, a qualification, or a cure item.
- For each issue, determine: the precise asset, contract, filing, employee, policy, or claim involved; the legal or transactional consequence; and whether the item must appear in the schedule, the closing checklist, or the outstanding-items memo.
- When a fact touches more than one schedule, repeat it consistently in each implicated place rather than assuming one reference will suffice.
- Where timing matters, distinguish past, current, pending, and future statuses so the package does not misstate the present record.
- Where the data room shows an open item, pair the disclosure with a short action description and identify the responsible functional owner if the record supports one.

### Master package drafting logic

- Begin with a cover page identifying the transaction, parties, and date.
- Follow with a table of contents keyed to the agreement’s section numbering and schedule titles.
- Include a cross-reference convention explaining how a disclosure in one schedule may qualify other responsive sections and how incorporated references should be read.
- Keep the master document as the routing document; do not use it to restate all substantive disclosures.

### Individual schedule drafting logic

- Use one schedule per agreement section or related topic cluster, with a title that mirrors the underlying subject matter.
- Put the most specific, document-supported facts first: names, dates, scope, status, and any exception or carveout.
- For contract schedules, capture material terms that matter for risk allocation, including renewal, termination, consent, exclusivity, assignment, and change-of-control features.
- For IP schedules, organize by registered rights, unregistered rights, licensing, development arrangements, open-source components, assignment status, and recordation gaps.
- For tax schedules, organize by filing status, audits, elections, jurisdictions, nexus, and unpaid or pending matters.
- For employment schedules, organize by employee, role, compensation, benefits, incentives, restrictive covenants, and contingent obligations.
- For insurance schedules, organize by policy, coverage, limit, exclusions, claims, and notice obligations.
- For real-estate schedules, organize by property, lease status, consents, defaults, and occupancy rights.
- For regulatory schedules, organize by regime, notice or approval requirement, current status, and expected timing.
- For each schedule entry, state the responsive representation section and the fact that qualifies it.

### Outstanding items and closing support

- Maintain a separate action-oriented memo for unresolved items that must be tracked through signing and closing.
- Rank each item by a uniform severity scale defined once at the top of the memo.
- For each item, include the issue, why it matters, the linked schedule or agreement section, the owner, and the expected completion point.
- Distinguish issues that require immediate cure from issues that can be disclosed and monitored through closing.
- Carry the same unresolved item into the closing checklist when it affects a condition, deliverable, consent, certificate, or bring-down step.

## 5. Vertical / structural / temporal relationships (only if applicable)

- Apply the package vertically: agreement section → schedule entry → supporting source document → closing action item.
- Preserve structural consistency across the master index, individual schedules, checklist, and memo so that a reviewer can trace a fact from source to output without inference.
- Preserve temporal accuracy:
  - past events should be drafted as completed facts,
  - current facts as existing conditions,
  - pending items as open matters,
  - future actions as obligations or expected steps.
- When an item changes status across documents, ensure the package reflects the latest status everywhere and does not mix pre-signing, pre-closing, and post-closing states.
- If a disclosure is intended to qualify multiple agreement provisions, make that relationship explicit in the schedule text and the master cross-reference convention.

## 6. Output structure conventions

- Produce the primary schedule package first, then the support workbooks and memos.
- The package should include a master disclosure schedule document plus individual schedule files aligned to the agreement’s numbered sections.
- Use industry-conventional titles rather than a rubric-shaped checklist; each document should be self-explanatory from its title and contents.
- Keep disclosures concise but complete: enough detail to identify the item, its status, and its deal significance without over-arguing the point.
- Use consistent names, dates, and terminology across all files, and reconcile discrepancies before finalizing.
- Include a separate closing checklist and outstanding-items memo so that unresolved matters do not disappear into the schedules.
- If the source record supports it, include supporting matrices or workbooks for contracts, employees, insurance, tax nexus, debt, financial statements, patents, working capital, and other diligence categories.
- Ensure every primary deliverable exists and contains operative content before ending; secondary memos should supplement, not replace, the schedule package.
- When a legal proposition is stated in the package, identify the governing authority by name and citation if the source materials or standard practice supply one.
- Final review should confirm that each schedule maps to the correct agreement section, each open item has a tracked action, and no disclosed fact is stranded without a home in the package.