Project Closure Checklist
Close a project completely and cleanly.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create a project closure checklist. Project type and deliverables: [PROJECT_TYPE]. Contracts and vendors: [CONTRACTS_AND_VENDORS]. Handover recipients: [HANDOVER_RECIPIENTS]. Produce a checklist grouped as: deliverables (accepted in writing, documentation complete, training done); handover (operations team briefed, support contacts, known issues list); contracts (final invoices, supplier closure, warranty periods noted, return of equipment and access); finance (budget reconciliation with variance, remaining funds released, final report); people (recognition, feedback, reassignment); records (archive documents, retention periods to confirm [VERIFY]); lessons (retrospective held, register updated); and communication (closure announcement). For each item: Owner | Date | Evidence | Done. Include a closure report outline (1 page) and a draft announcement (100 words) thanking the team. Add a section on benefits tracking after closure: who measures them, when, and how. Mark the five items that cannot be skipped (acceptance in writing, final invoices, access removal, handover, archive), and add a rule that the project is not closed until each has a date and an owner who confirms it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.