Identify Issues In Closing Checklist

---
name: identify-issues-in-closing-checklist
task_id: banking-finance/identify-issues-in-closing-checklist
description: Cross-references a closing checklist against the governing credit documentation and submitted deliverables, then produces a severity-organized closing issues memo with remediation steps.
activates_for: [planner, solver, checker]
---

# Skill: Closing Checklist Issues Memo — Revolving Credit Facility

## 1. Subject-matter triage
- Determine whether the package is a single-facility closing, an amendment-and-restatement, or a multi-party rollover with new money, because the governing checklist items and failure points change with the transaction shape.
- Identify the operative source set first: the credit agreement, the closing checklist, the submitted deliverables, the flow of funds materials, payoff letters, certificates, and any ancillary closing conditions.
- If the record contains multiple obligors, collateral providers, properties, or funding legs, enumerate them before analysis and assess each separately; do not use one representative review for the whole package.
- If a required item is missing from the source set, flag the gap as a closing issue rather than assuming it will be cured off-record.

## 2. Failure modes the skill is correcting
- Reviewing the checklist without tying each item to the controlling closing condition in the credit documents and the submitted package.
- Missing mismatches between the checklist, the credit agreement, and the delivered forms, especially where one document requires more than the others.
- Accepting a payoff, funds flow, or disbursement package that does not reconcile across the deal documents, creating a closing shortfall or incorrect release.
- Overlooking obligor-specific or collateral-specific requirements that vary by entity, asset class, or jurisdiction.
- Treating a signed certificate, consent, or opinion as sufficient without checking whether it addresses every condition it is supposed to satisfy.
- Collapsing all defects into one bucket instead of grading them by how directly they affect closing, perfection, or post-closing cure risk.

## 3. Legal frameworks / domain conventions that apply
- Use the credit agreement as the primary governing standard for conditions precedent, required deliveries, and defined terms; then test the checklist against any more specific closing instruction that supplements it.
- Read the checklist as an operational control document, not as the source of substantive obligations; where it conflicts with the credit documents, identify the mismatch and note which document controls.
- For perfection and filing items, verify the relevant debtor, collateral type, and jurisdiction-specific deliverable against the closing package; do not assume a filing in one place satisfies another place or another asset class.
- For guarantees, collateral grants, and control agreements, confirm that the delivered documents match the required obligors and secured property described in the source set.
- For payoff and release items, compare the payoff letter, allocation instructions, and any release conditions against the funds flow and closing disbursement schedule.
- For compliance certificates, verify that the certificate addresses each covenant that is live at closing and that the support ties back to the figures used in the certificate.
- For insurance, environmental, leasing, and related property-level conditions, test freshness, scope, naming conventions, and consistency with the mortgaged-property or collateral package requirements.
- Apply ordinary contract-interpretation principles: specific controls over general, later-dated supplements can refine earlier instructions, and a condition is not satisfied by a document that omits an express required element.
- Cite the controlling authority or operative document language for each legal proposition relied on, using the credit document section, applicable statute, rule, or standard-form convention as reflected in the source set or generally recognized practice.

## 4. Analytical scaffolds
1. Build a source map: checklist item, corresponding credit-document requirement, and actual submitted deliverable.
2. For each checklist line item, determine whether the requirement is fully satisfied, partially satisfied, or missing.
3. For each potential issue, state the scale of the problem using a source-derived figure or transaction feature where available, and tie it to the interacting document or clause.
4. Test for cross-document inconsistencies: checklist vs. credit agreement, checklist vs. certificate/opinion, payoff vs. funds flow, and any document vs. closing instructions.
5. Assess downstream effect: whether the issue blocks closing, threatens perfection or enforceability, creates a funding discrepancy, or is a post-closing cleanup item.
6. Assign severity using a uniform ordinal scale and define that scale once at the outset of the memo.
7. Where one issue can be fixed by simple substitution or supplemental delivery, distinguish that from a true missing-condition problem.
8. Close each issue with three elements: the relevant scale or scope, the interacting source reference, and the consequence for the client.
9. End with concrete remedial steps tied to the responsible party and the closing timeline.

## 5. Vertical / structural / temporal relationships
- Review requirements in the order they affect closing: satisfaction of conditions precedent, execution deliveries, filing/perfection actions, funding mechanics, and post-closing cures.
- Distinguish pre-closing conditions from post-closing undertakings; a post-closing covenant should not be scored as a closing defect unless the record shows it was wrongly treated as satisfied.
- Where the package includes multiple obligors or collateral owners, track each entity’s role vertically: borrower, guarantor, pledgor, account party, landlord, issuer, or property owner.
- Where the package includes staged funding or multiple disbursements, compare each funding leg against the related document set rather than against the transaction as a whole.
- If a requirement depends on another document first being effective, note the dependency explicitly and analyze the sequence.

## 6. Output structure conventions
- Produce a closing issues memo organized by severity from highest to lowest, using an explicit ordinal scale defined in the memo.
- Use conventional severity labels such as Critical, Significant, and Administrative, or an equivalent ordinal scale stated once and applied uniformly.
- Begin with a short executive summary that states the overall closing posture and the issue distribution by severity.
- Include a compact table or bullet inventory of issues before the narrative discussion if that improves readability.
- For each issue, include:
  - the checklist item or document tested,
  - the governing requirement,
  - the specific deficiency or inconsistency,
  - the source cross-reference(s),
  - the downstream consequence,
  - the recommended remediation.
- Each issue entry must be self-contained and must end with a concrete fix, not merely a diagnosis.
- If a document appears to satisfy the requirement only by implication, say so and explain why that is risky.
- Include a Recommended Actions section at the end with imperative steps, the responsible role, and a timing anchor tied to the closing sequence or applicable deadline.
- If the memo references a legal or documentary proposition, cite the controlling authority or operative document section inline rather than leaving the proposition unsupported.