Draft Plan Effective Date Checklist

---
name: draft-plan-effective-date-checklist
task_id: bankruptcy-restructuring/draft-plan-effective-date-checklist
description: Ensures a plan effective date checklist provides a dashboard summary, condition-level detail with responsible party and risk rating, and proactive identification of practical risks that are not formal conditions precedent but can still delay the effective date.
activates_for: [planner, solver, checker]
---

# Skill: Draft Plan Effective Date Conditions Precedent Checklist

## 1. Subject-matter triage

- Treat the plan, confirmation order, and related transaction documents as a single effectiveness package.
- Identify whether there is one target effective date framework or multiple timing tracks tied to different signings, approvals, filings, or funding steps.
- Separate formal conditions precedent from practical blockers that can delay effectiveness even if they are not labeled as conditions.
- If the source set includes several open conditions, enumerate them first and then assess each one on its own terms; do not collapse distinct items into a generic summary.

## 2. Failure modes the skill is correcting

- Agent lists formal conditions from the plan but misses practical risks that are not conditions precedent and yet threaten the effective date timeline, such as outstanding appeals, regulatory approvals, or documentation gaps.
- Agent does not produce a summary dashboard showing the overall feasibility of the target effective date at a glance.
- Agent treats multiple open conditions as a single blended issue instead of tracking each condition, owner, deadline, and status separately.
- Agent identifies a problem but does not tie it to the governing plan language, confirmation order, or transaction document that creates the obligation.
- Agent omits a concrete next step, making the checklist diagnostic rather than actionable.
- Agent fails to verify arithmetic for financial items such as incentive plan participant savings from forfeitures, professional fee escrow adequacy, or cure cost estimates.

## 3. Legal frameworks / domain conventions that apply

- Conditions precedent: Read the plan effectiveness provisions, the confirmation order, and any implementing documents together; every condition should become a checklist item with a responsible party and required evidentiary support.
- Bankruptcy effectiveness mechanics: Track the sequencing of confirmation, appeal finality, entry of ancillary orders, funding, restructuring transactions, and document delivery that must occur before effectiveness.
- Appeal risk: Confirm whether any notice of appeal, stay motion, or similar challenge remains outstanding and whether effectiveness is conditioned on finality, waiver, or expiration of appellate timing.
- Third-party approvals and consents: Flag regulatory approvals, lender consents, counterparties’ approvals, and other third-party signoffs that are not always formal plan conditions but can still block closing.
- Equity, incentive, and governance deliverables: Watch for organizational documents, officer certificates, director appointments, plan reserve documentation, and incentive program mechanics that must be ready by the effective date.
- Tax and attributes timing: If the restructuring turns on ownership composition or other post-effective-date facts, flag any timing sensitivity that could change tax or attributes analysis before effectiveness.
- Escrow and payment mechanics: Confirm that funding sources, reserve accounts, professional fee escrows, and distribution mechanics match the operative documents and actual accruals.
- Governing authority: Where a checklist item depends on a legal rule or approval standard, cite the operative document provision and the applicable statute, rule, or order language reflected in the source set.

## 4. Analytical scaffolds

- Produce a summary dashboard before the itemized checklist:
  - total conditions tracked;
  - count of complete, in progress, and at-risk items;
  - overall assessment of readiness for the target effective date.
- Define one ordinal risk scale and use it consistently for every item, with a short rationale:
  - Critical;
  - High;
  - Medium;
  - Low.
- For each formal condition, capture:
  - condition description;
  - source provision or document reference;
  - responsible party;
  - evidence or deliverable required;
  - deadline or timing trigger;
  - status;
  - risk level;
  - open issues and recommended action.
- For each item, close the analysis by tying the issue to:
  - the operative source document or provision;
  - the practical effect on closing timing or certainty;
  - the downstream consequence if the item remains open.
- For financial checklist items, verify figures against the source documents and reconcile them to the operative mechanics before marking them complete.
- For every open or at-risk item, give a concrete next step with a named role and a timing anchor.

## 5. Vertical / structural / temporal relationships

- Map the sequence from confirmation to effectiveness to post-effective administration so the checklist reflects what must happen before, on, and immediately after the effective date.
- Distinguish items that are true conditions to effectiveness from items that are prerequisites to an implementing step, even if both appear in the same transaction package.
- Note dependencies among conditions, such as one approval enabling another filing, one certificate supporting another closing deliverable, or one funding step unlocking distributions.
- If a document requires a certificate, officer deliverable, or notice to be delivered by a deadline, show whether the deadline is absolute, relative to entry of an order, or relative to satisfaction of another condition.
- Where timing is uncertain, flag the risk as such and identify the earliest point at which the uncertainty must be resolved.

## 6. Output structure conventions

- Deliver a checklist document with a dashboard summary at the top and condition-by-condition detail below.
- Use a conventional status dashboard with a brief narrative assessment, then a table or matrix for the detailed items.
- Each checklist row should include, at minimum: Description | Source Reference | Responsible Party | Evidence Required | Deadline / Timing Trigger | Status | Risk Level | Open Issues / Recommended Actions.
- Include a separate section for practical risks and non-condition items using the same or a materially similar column structure.
- Use concise, operative phrasing; write each item so a business or legal reviewer can act on it immediately.
- If a target effective date is stated in the source set, assess readiness against that date; if not, assess readiness against the next workable milestone identified in the documents.
- End with a short Recommended Actions block that lists the immediate steps, the role responsible, and the timing anchor for each step.