Guides preparation of a gap analysis memorandum for an acquisition transaction by cross-referencing disclosure schedules against diligence findings and relevant representations to identify omissions, inconsistencies, and disclosure concerns.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill synthesize-disclosure-schedules-against-diligence-findings --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Synthesize Disclosure Schedules Against Diligence Findings?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-synthesize-disclosure-schedules-against-diligence)More formats (shields.io, HTML) on the badges page.
---
name: synthesize-disclosure-schedules-against-diligence-findings
task_id: corporate-ma/synthesize-disclosure-schedules-against-diligence-findings
description: Guides preparation of a gap analysis memorandum for an acquisition transaction by cross-referencing disclosure schedules against diligence findings and relevant representations to identify omissions, inconsistencies, and disclosure concerns.
activates_for: [planner, solver, checker]
---
# Skill: Disclosure Schedule and Diligence Findings Gap Analysis (Pharma)
## 2. Failure modes the skill is correcting
- The analysis stops at comparing schedules to the SPA and fails to sweep the full diligence record, so omissions that appear only in diligence are missed.
- The review treats the target as a generic acquisition target and misses pharma-specific disclosure pressure points: IP ownership and licensing, regulatory status, clinical and development issues, product liability, commercialization, and key supply or collaboration dependencies.
- Informal counsel assessments, diligence call notes, and working summaries are discounted even when they are the most current source on litigation, regulatory, or operational exposure.
- Newly added schedule disclosures are noted but not tested for internal consistency, transactional impact, or bring-down risk.
- A finding is described as a “gap” without tying it back to the governing representation, the intersecting diligence source, and the practical consequence for the deal.
- The memo reads as a narrative summary instead of an issue-spotting work product with consistent severity, a traceable source set, and actionable recommendations.
## 3. Legal frameworks / domain conventions that apply
- Map each diligence topic to the most specific SPA representation, not merely to a broad catchall disclosure concept.
- In a pharma acquisition, prioritize disclosures that bear on patents, patent applications, licenses, data rights, regulatory approvals, clinical trials, adverse events, product complaints, recalls, safety reporting, governmental correspondence, and commercialization restrictions.
- Test litigation disclosures against the most current litigation-risk source available in the record, including outside counsel assessments and informal status updates where relevant.
- Cross-check capitalization disclosures against the cap table, option ledger, convertible or derivative securities records, and any equity grant history reflected in diligence.
- Cross-check environmental disclosures against environmental diligence findings where the target owns or operates facilities or uses regulated materials.
- Treat the schedules as part of the bring-down analysis: any omission or late-added disclosure may affect whether the reps are true and correct at signing and closing and whether a closing condition is satisfied.
- Apply ordinary contract interpretation principles to the SPA: read the representation, its qualifications, and its disclosure schedule together; assess whether the schedule actually cures the rep or merely mentions the topic.
- Where a legal proposition is stated, anchor it to the governing authority reflected in the source set or the generally applicable transaction-law rule the proposition depends on.
## 4. Analytical scaffolds
- Enumerate the source set before analysis:
1. SPA representations and warranties.
2. Disclosure schedules.
3. Diligence summaries and issue lists.
4. Specialist diligence materials for IP, regulatory, litigation, environmental, capitalization, and commercial matters.
5. Any later updates, addenda, or counsel communications.
- For each representation group, identify the disclosures required by the text of the rep, then test whether the corresponding schedule section is complete, internally consistent, and supported by the diligence record.
- For each diligence finding, determine whether it is:
- fully disclosed,
- partially disclosed,
- disclosed in the wrong schedule,
- missing from the schedules, or
- newly disclosed without prior diligence flagging.
- For each gap, complete the triad:
- scale the issue using a figure, range, count, timing point, or other source-based magnitude;
- cross-reference the interacting schedule, diligence item, or agreement provision;
- state the downstream consequence for the transaction, closing condition, indemnity, pricing, or regulatory posture.
- For each new disclosure, test whether it broadens the risk profile, narrows a rep, triggers a bring-down concern, or suggests a diligence miss requiring follow-up.
- Treat current, concrete sources as more probative than generalized summaries when they conflict, but flag the inconsistency rather than silently harmonizing it.
- Separate substantive omissions from drafting noise: incomplete cross-references, misplaced entries, vague carve-outs, and topic-only disclosures should be flagged only when they impair the rep’s accuracy or completeness.
- Use a uniform severity scale for every issue and apply it consistently:
- Critical: likely deal-impacting or bring-down relevant;
- High: material omission or significant inconsistency requiring correction;
- Medium: meaningful but likely curable;
- Low: completeness or clarity issue with limited immediate impact.
- When multiple issuers, facilities, products, programs, claims, or time periods are in scope, analyze each one individually rather than collapsing them into a single representative item.
- If the source set supports only one item in a category, say so explicitly and explain why no broader inventory is warranted.
## 5. Vertical / structural / temporal relationships (only if applicable)
- Track how later-in-time disclosures change earlier diligence conclusions; if a schedule was updated after diligence, identify the delta and its deal significance.
- Compare issue materiality across levels: program, product, facility, subsidiary, contract, claim, and representation.
- Distinguish present obligations from historical facts and contingent risks; a past event may matter only if it creates a current rep failure, disclosure obligation, or closing-condition issue.
- Where a topic appears in multiple places, determine whether the overlap is cumulative disclosure, duplicative disclosure, or an unresolved inconsistency.
- If the target has multiple products or regulatory filings, trace whether the omission is isolated to one item or reflects a broader schedule-wide pattern.
## 6. Output structure conventions
- Produce a single gap analysis memorandum, not a diligence summary and not a markup.
- Start with a concise executive summary that identifies the highest-severity gaps, the most important new disclosures, and the overall deal-risk readout.
- Follow with issue sections organized by subject area, using conventional M&A headings such as:
- Intellectual property and licensing
- Regulatory and compliance
- Litigation and claims
- Environmental
- Capitalization and equity
- Commercial and operational matters
- Other rep-specific gaps
- Newly disclosed items
- In each issue entry, include:
- the governing representation or schedule topic;
- the source comparison that exposed the issue;
- the severity label;
- the gap or inconsistency;
- the transaction consequence;
- the recommendation.
- End with a Recommended Actions section that gives imperative next steps, names the responsible role or team, and ties each step to a transactional milestone or immediate follow-up need.
- Keep the prose analytical and source-driven; do not turn the memo into a broad business summary or an abstract legal treatise.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!