Closing Checklist Manager
500 items across 12 parties — nothing falls through
Manages transaction closing checklists with real-time status tracking across all parties. Tracks document collection, signature coordination, and closing conditions. Sends automated reminders and generates status reports.
INGREDIENTS
PROMPT
Create a skill called "Closing Checklist Manager" for a transactional lawyer. When I start a new deal, generate a closing checklist from my template (or a prior deal I specify). Each checklist item includes: description, responsible party, target date, dependencies (items that must be completed first), status (not started/in progress/under review/final/ signed), and notes. Track status updates as I or team members mark items complete. Send automated reminder emails to responsible parties when items are approaching their target date. Generate a status report showing: total items, items complete vs. outstanding, overdue items, and next critical path items. Track signature pages separately — which parties have signed which documents. After closing, maintain a post-closing checklist for filings, deliveries, and follow-up items.
How It Works
Closings are coordination nightmares — dozens of documents, multiple parties,
cascading conditions. This skill tracks every item, chases every party, and
keeps everyone honest.
What You Get
- Auto-generated closing checklists from templates or prior deals
- Real-time item status tracking (not started, draft, under review, final, signed)
- Party responsibility assignment for each item
- Automated reminder emails to responsible parties
- Condition precedent tracking with dependency mapping
- Signature page coordination across all documents and parties
- Status report generation for distribution to deal team
- Post-closing item tracking
Setup Steps
- Select a checklist template or import from a prior deal
- Assign parties and responsibilities
- Set the target closing date
- Track, remind, and report as the deal progresses
Tips
- Start the checklist at LOI/term sheet stage, not the week before closing
- The dependency mapping prevents the "we can't close because item 47 depends on item 12" surprise
- Send daily status reports the week before closing — it creates accountability
- Don't forget post-closing items — they're easy to lose after the deal euphoria fades