Write a project closure report
Formally closes a project: results vs. objectives, handover, open items, and lessons.
The prompt
Write a project closure report.
Project: [NAME, objective, sponsor]
Planned vs. actual: [scope, schedule, budget]
Results and deliverables: [WHAT WAS DELIVERED, metrics]
Open items and handover: [WHAT REMAINS, who owns it]
Lessons: [NOTES]
Sections: executive summary; objectives vs. outcomes (table); scope, schedule, and budget performance with variance explanations; benefits realized and still to come; handover and support arrangements; open risks and issues; lessons learned; formal sign-off.
Use only my data; mark gaps [TO CONFIRM].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- NAME, objective, sponsor
- scope, schedule, budget
- WHAT WAS DELIVERED, metrics
- WHAT REMAINS, who owns it
- NOTES
- TO CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a banquet event order for a wedding or functionA complete BEO that tells kitchen, banquet, AV, and setup teams exactly what to deliver and when.
- Investigate a truck crash and write the internal incident reportA structured crash investigation covering evidence, timeline, root cause, preventability, and corrective actions, written factually.
- Write a change request that gets through the change boardDrafts a complete change request with risk, testing, rollback, and communication so approvers can say yes quickly.
- Write a corrective action plan for a recurring quality problemA CAPA plan that contains the problem, finds the root cause, fixes it, and proves the fix worked.