All topics

Project Closeout

Category: Project Management

Project closeout / lessons-learned capture: outcomes vs objectives, what worked, what did not, knowledge assets, recognition.

When to use this template

Use it at the end of a project - the wrap-up meeting where the team captures what shipped, what was left undone, what to do differently next time, and who needs to be recognized. For the start of a project, see Project Kickoff. For a retro during the project, see Retrospective.

Fields captured

Project name - the working title of the project.
Original objectives - what the project set out to do.
Outcomes vs objectives - how the team did against each objective.
What went well - patterns and wins to repeat.
What didn't go well - friction and pain points to address.
Insights & root causes - why things went or did not go well.
Recommendations - suggestions for future projects.
Process improvements - concrete changes for the team's process.
Knowledge assets - runbooks, docs, models, code, or other artifacts created.
Outstanding items - what did not get done or is handed off.
Recognition - people to thank and the why.
Next steps - concrete tasks (handoffs, follow-ups) with optional owner and due date.
Key takeaways - the AI's prioritized summary points.

The standard summary, attendees, and per-section summaries also apply.

Sub-views, role views, and artifacts

Sub-views: none.
Role views: Sales Engineer, Project Manager, Executive Sponsor.
Artifacts: Email draft (recipient, tone, optional subject hint).
Study mode: not available.

Exports

PDF, DOCX, and Markdown include the outcomes-vs-objectives table, lessons learned in the standard "Went well / Didn't / Insights" order, and dedicated blocks for knowledge assets, outstanding items, and recognition. Approved role views and email drafts appear in exports too.

See also: All templates, Project Kickoff.