1---2name: compare-closing-documents-against-restructuring-conditions3task_id: banking-finance/compare-closing-documents-against-restructuring-conditions4description: Reviews restructuring closing documents against closing conditions from the relevant restructuring support and related transaction documents from an ad hoc lender’s perspective, flagging discrepancies with severity calibration and recommended remedial actions.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/compare-closing-documents-against-restructuring-conditions8---910# Skill: Restructuring Closing Documents Gap Report1112## 2. Failure modes the skill is correcting1314- Checking the package against deal expectations in the abstract instead of matching each closing condition to the executed documents, certificates, and exhibits actually delivered15- Missing a mismatch because the closing package is internally consistent on its face but inconsistent with the RSA, term sheet, or operative definitions elsewhere in the source set16- Treating borrower-favorable drift as acceptable when the lender group did not authorize the change17- Failing to separate true closing blockers from lesser administrative gaps and economic deviations18- Ignoring the scale of the deviation, the related document interaction, and the consequence for the lender group19- Reporting issues without a concrete cure, responsible party, and urgency tie-back2021## 3. Legal frameworks / domain conventions that apply2223- Restructuring closing conditions must be tested against the operative condition language, not a summary of the transaction24- Ad hoc lender perspective requires strict comparison to the lender group’s bargained-for economics, control rights, and deliverables25- Any required deliverable should be checked for existence, form, and conformity to the stated condition or exhibit list26- Economic terms must be compared across the RSA, term sheet, draft closing documents, schedules, definitions, and any side letters or certificates in the source set27- If a condition turns on priority, intercreditor, or related protections, verify both execution status and whether the deliverable is referenced where the documents require28- If the package includes maturity, interest, liquidity, or proceeds conditions, check the operative figure, date, formula, or threshold against the controlling document language29- If the source set contains legal opinions or officer certificates, confirm each required topic or assertion is covered and not contradicted elsewhere30- Use a uniform ordinal severity scale across all issues, and define it once at the outset31- Cite the controlling provision or authority for every legal or transactional proposition relied on32- When the source documents identify roles or deadlines, carry those through into remedial guidance3334## 4. Analytical scaffolds35361. Identify the governing closing conditions, defined terms, and any document hierarchy language before checking the package.372. Compare each closing document to the specific condition it is meant to satisfy; do not infer satisfaction from general deal alignment.383. For each monetary, date-based, percentage-based, or formula-based condition, use the actual source values and check for deviations, however small.394. For any issue involving multiple documents, reconcile the closing package against the RSA, term sheet, draft operative documents, schedules, and certificates together.405. When an economic or structural term appears in more than one place, treat inconsistency itself as a discrete issue even if no single provision is facially broken.416. For any proceeds, liquidity, or similar threshold, calculate the relevant closing metric from the transaction documents and compare it to the stated requirement.427. For any required deliverable, verify both that it exists and that it matches the required content, signatory, form, or attachment status.438. For any interest, maturity, priority, or covenant term, compare the executed formulation to the agreed formulation and flag unauthorized drift in either direction.449. For every issue, state: the controlling provision, the closing document reviewed, the specific deviation, the scale of the deviation, the cross-document interaction, the consequence to the lender group, the severity, and a recommended cure.4510. Calibrate severity using an explicit ordinal scale, with the most serious items reserved for conditions that block closing or fundamentally alter lender economics or control.4611. Where the record is unclear, say so and identify the missing document or fact needed to complete the comparison rather than assuming compliance.4712. Tie the recommendation to the role that should act and, where available, to the milestone or timing trigger in the source documents.4849## 5. Vertical / structural / temporal relationships5051- Compare the RSA, term sheet, and closing package in a document-hierarchy-aware sequence so later operative documents are not read in isolation from earlier deal constraints52- Track whether a condition precedent is satisfied as of signing, funding, or effectiveness, since timing can control whether a deviation is curable or already a breach53- Distinguish terms that are required to be identical across documents from terms that may vary by drafting convention but still must preserve the same economic effect54- If a deliverable depends on another deliverable, note the dependency and whether the failure cascades into a broader closing failure55- If a mismatch affects ongoing post-closing rights, flag the downstream governance, economic, or enforcement consequence separately from the closing defect itself5657## 6. Output structure conventions5859- Produce a compliance gap report organized by issue number60- Open with a brief executive summary that identifies the most serious gaps first61- State the ordinal severity scale once at the top and apply it consistently to every issue62- For each issue, include:63 - severity64 - controlling provision or authority65 - closing document reviewed66 - specific deviation67 - scale or metric, if applicable68 - cross-reference to the interacting clause, schedule, or document69 - downstream consequence to the lender group70 - recommended remedial action71- Use plain, lender-facing language; do not narrate your process or hedge with internal deliberation72- Close with a Recommended Actions section that lists the immediate steps, the responsible role, and the urgency or deadline anchor drawn from the source documents73- If no discrepancy is found on a given condition, say so affirmatively rather than omitting the condition74- Keep the report self-contained and suitable for conversion directly into `compliance-gap-report.docx`