1---2name: identify-disclosure-requirements-based-on-ma3task_id: corporate-ma/identify-disclosure-requirements-based-on-ma-agreement4description: Guides preparation of a disclosure schedule checklist that maps each disclosure obligation in a merger agreement to the required content, responsible party, and information source.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/identify-disclosure-requirements-based-on-ma8---910# Skill: Disclosure Schedule Obligation Mapping Checklist1112## 1. Subject-matter triage13- Confirm the target output is a disclosure schedule checklist, not a legal memo or a schedule draft.14- Read the merger agreement first, then diligence materials, then any draft schedules; do not infer schedule content from diligence alone.15- Determine whether the agreement creates affirmative disclosure lists, exception schedules, or both; the drafting approach differs.16- Identify whether schedules are delivered at signing, closing, or both, and whether updates or supplements are permitted or required.1718## 2. Failure modes the skill is correcting19- The checklist names schedule sections without tying each one to the underlying representation, warranty, covenant, or definition that creates the obligation.20- Required content is stated too generally, so the team cannot tell what facts, documents, dates, parties, or exceptions must be gathered.21- No owner is assigned to each item, leaving legal, finance, tax, HR, operations, and external advisors to assume someone else is handling it.22- Available diligence sources are not mapped, so every item has to be re-sourced manually.23- The checklist fails to distinguish between schedules that list required items and schedules that disclose exceptions to a representation or warranty.24- The checklist ignores qualifiers such as knowledge, materiality, or specified disclosure standards, which changes how much detail must be included.25- Update mechanics are omitted, so the team misses whether a schedule may be brought down, supplemented, or updated before closing.2627## 3. Legal frameworks / domain conventions that apply28- Disclosure schedules typically operate either as required-item lists or as exception disclosures; treat each schedule according to the function the agreement assigns it.29- A disclosure obligation is read against the exact representation, warranty, covenant, definition, or qualification it modifies.30- Knowledge, materiality, and similar qualifiers affect the scope of information that must be disclosed and should be captured for each item.31- The relevant timing standard is the signing date, delivery date, or closing date specified in the agreement; note the operative date for each disclosure obligation.32- If the agreement allows updates or supplements, distinguish initial disclosure content from later bring-down changes and closing-delivery updates.33- Where the agreement points to a schedule or exhibit by designation, preserve that designation in the checklist so the drafting team can slot content into the correct place.3435## 4. Analytical scaffolds36- Start by enumerating every agreement section, definition, exhibit, and covenant that creates or references a disclosure obligation.37- For each item, extract four core elements: the schedule designation, the required content, the applicable qualifier, and the disclosure function.38- Then identify the source materials that appear to contain the needed facts; if no source exists, mark the item as unavailable or to be confirmed.39- Assign a responsible party for each item, using the actual workstream owner where possible and noting external counsel or advisors where they are the natural drafter.40- Compare any existing draft schedules against the extracted requirements and flag missing schedules, missing facts, and mismatched designations.41- Where multiple business units, entities, asset classes, or time periods are implicated, give each a separate row rather than collapsing them into one generalized entry.42- If the agreement requires updates between signing and closing, add a separate note for the initial draft obligation and the update/bring-down obligation.4344## 5. Vertical / structural / temporal relationships45- Map each disclosure item to the agreement hierarchy it sits within: main representation, related definitions, special disclosure carve-outs, and any linked covenant or closing condition.46- Note whether the obligation is upstream, contemporaneous, or downstream from signing, since timing often changes who owns the item and what materials are available.47- Where one schedule feeds another section, preserve the dependency so the drafting team understands which item controls if there is overlap.48- If an item depends on an external diligence artifact that may change before closing, flag that dependency and state the update trigger.49- Separate company-level disclosures from subsidiary-, project-, asset-, employee-, or contract-level disclosures so responsibility and source tracking stay accurate.5051## 6. Output structure conventions52- Produce a single disclosure schedule checklist intended to be pasted into the working draft document.53- Use industry-conventional table columns, such as:54 - agreement section / source clause55 - schedule or exhibit designation56 - required content57 - disclosure function58 - qualifier or timing59 - source document or diligence reference60 - responsible party61 - status or open point62- Keep the checklist organized by agreement section, with one row per distinct disclosure obligation.63- Use concise, operative descriptions rather than narrative summaries.64- Where the source material is incomplete, say so directly and identify the missing input needed to finish the item.65- Preserve the distinction between required disclosures and exceptions to representations; do not treat all schedule entries as the same drafting exercise.66- End with a short action-oriented completion note that identifies any items still awaiting source confirmation or owner assignment.