# Draft Compliance Audit Memorandum > Guides drafting of a pre-acquisition environmental compliance audit memorandum by organizing findings facility-by-facility and medium-by-medium, with assessment of open regulatory matters and their implications for the transaction, using only generic categories and procedural analysis. - Skill: `finchipaiorg/draft-compliance-audit-memorandum` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-compliance-audit-memorandum` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-compliance-audit-memorandum/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Security - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/draft-compliance-audit-memorandum --- # Skill: Draft Environmental Compliance Audit Memorandum for Pre-Acquisition Due Diligence ## 1. Subject-matter triage - Treat the project as a multi-site pre-acquisition compliance review, not a site-conditions survey; the core question is present legal compliance and transaction impact. - First identify each facility in scope, then map the source set to that facility before drawing any cross-site conclusions. - If the source materials contain only one facility or one regulatory medium, state that explicitly and do not imply a broader portfolio review. - Separate pure compliance findings from remediation, permitting, ownership-change, and enforcement issues; each has different timing and closing implications. ## 2. Failure modes the skill is correcting - Findings are blended across facilities, obscuring which site has which permit history, inspection record, or agency relationship. - Notices, letters, and agency correspondence are summarized without identifying current status, alleged violation, response posture, or transaction consequence. - The memo identifies problems but stops short of saying whether they are pre-closing items, post-closing follow-up items, or matters for contractual allocation. - Permit transfer, ownership change, and agency-notification obligations are treated as generic housekeeping rather than as transaction-sensitive requirements. - Corrective action, cleanup, or legacy liability matters are described without stating whether they may follow the buyer or require agency engagement before closing. - Conclusions are stated without tying them to the controlling environmental program or permit framework that makes the issue legally meaningful. - The memo is descriptive rather than decision-oriented: it does not tell the deal team what must be resolved, disclosed, reserved, or monitored. ## 3. Legal frameworks / domain conventions that apply - Pre-acquisition environmental diligence distinguishes between historical site condition and current regulatory compliance; both matter, but they answer different questions. - Air, water, waste, and land-related obligations should be analyzed under the specific permit, approval, order, or rule that governs the activity. - Ownership change can trigger notice, transfer, reapplication, or amendment obligations under the relevant permit or program rule. - Enforcement matters should be read against the governing statute, regulation, permit condition, or order, then assessed for status, exposure, and cure path. - Corrective action or remediation obligations may carry successor-liability implications depending on the governing program and transaction structure. - Transaction structure matters: stock acquisitions usually inherit existing obligations more directly than asset acquisitions, but successor-liability and permit-transfer risks may remain in either structure. - State or local requirements may be more demanding than baseline federal expectations; treat the most specific applicable source as controlling for the facility at issue. ## 4. Analytical scaffolds - Begin by enumerating the facilities in scope, then analyze each facility separately using the same internal sequence so the reader can compare sites cleanly. - For each facility, analyze by medium or program: permits/approvals, monitoring and reporting, inspections, notices and correspondence, enforcement, and cleanup/corrective-action items. - For each issue, identify: - the applicable permit, approval, order, or rule; - the current compliance posture based on the documents; - the open matter or gap, if any; - the transaction implication; and - whether the item calls for pre-closing action, closing-condition protection, or post-closing follow-up. - For open notices or agency communications, distinguish unresolved matters from closed matters and note whether a response, schedule, or corrective step is underway. - For permit and ownership-change issues, identify whether the source documents suggest advance notice, agency approval, or a transfer filing before or after closing. - For corrective action matters, identify the scope of the obligation, whether it appears continuing, and whether the transaction could require additional reporting or review. - For each finding, assign a qualitative severity that reflects deal impact and regulatory urgency, not a numeric score. - Where the source documents support it, tie the issue to the governing authority by naming the statute, regulation, permit condition, or order that makes the requirement operative. - Close each issue with a practical consequence for the transaction so the memo reads as a diligence tool, not a compliance inventory. ## 5. Vertical / structural / temporal relationships - Facility hierarchy controls the presentation: one site at a time, then one medium or program at a time within that site. - Temporal status matters: distinguish historical violations, ongoing compliance obligations, pending agency responses, and deadlines that may fall before closing. - Treat pre-closing, closing, and post-closing timing as different decision points; a matter that is manageable after closing may still require disclosure or a closing covenant. - Cross-document relationships matter: permit conditions, inspection findings, agency letters, and internal reports should be read together rather than in isolation. - If a matter appears in more than one document, reconcile the versions and explain whether later materials supersede earlier ones or merely supplement them. ## 6. Output structure conventions - Draft the memorandum in conventional legal-memo form with an executive summary, facility-by-facility analysis, transaction-specific issues, and recommendations. - Open with a concise severity legend using an ordinal scale such as Critical / Significant / Moderate / Minor, defined once and applied consistently. - In the executive summary, identify the facilities with the most material issues and flag any item that appears to warrant pre-closing resolution or special deal protection. - For each facility, use a compact findings table followed by narrative analysis. - Table fields should cover the governing permit or approval, the relevant requirement, compliance status, open matter, severity, and transaction implication. - Do not rely on headings copied from the source documents; use conventional legal-compliance framing. - In the narrative, address each facility-medium combination separately and state the applicable authority or program when it is clear from the record. - Include a transaction-specific section for ownership-change notices, permit transfers, required filings, and any regulatory approval or consent that appears tied to closing. - End with an explicit Recommended Actions section that uses imperative verbs, names the responsible role, and anchors timing to a regulatory or transactional milestone. - Use the file name exactly as instructed: `compliance-audit-memorandum.docx`.