Skip to content
GanttPal
Log in Get started

How to Run a Project Post Mortem: Meeting Guide and Report Template

A project post mortem turns the experience of a finished project into practical lessons. This guide explains how to prepare for the meeting, facilitate a focused discussion, and convert feedback into owned actions that can improve the next project.

What a post mortem is for

A post mortem gathers key contributors after delivery to review both successes and problems. The discussion should celebrate individual and team achievements while examining workflow, collaboration and client management. The facilitator then helps turn feedback into positive change and passes recognition to leadership and the wider team. Done well, the meeting improves communication, builds empathy for different perspectives, and gives people a constructive way to close out difficult work.

Prepare before the meeting

Hold the session soon after the project finishes so details remain fresh. A 45 to 50 minute meeting is usually enough to agree tangible next steps without losing attention. Invite people from early phases as well as delivery, contractors who may work with the team again, and sales colleagues who can hear scope or contract concerns directly. Send an agenda in advance listing attendees, the meeting goal, the format, and a short recap covering original goals, budget, timeline, major scope changes, new tools or processes, and client feedback. Attendees can prepare through a brief survey or by blocking 15 minutes to reflect on the questions in advance.

Run a focused discussion

Choose a moderator who knows the project well and can engage everyone, keep the pace steady, and handle disagreement constructively. If the moderator is also facilitating, appoint a separate notetaker. Open with clear ground rules: participate when called upon, value every voice, be honest without blame, avoid interruptions, use cameras in virtual meetings, and silence notifications. A simple flow works well: what worked well, what did not work, what needs improvement, and what happens next. An interactive board can help the group collect, group and prioritise comments, with labels for teams, priorities, owners and deadlines.

Turn discussion into a report

Start with the project name, meeting date, attendees, timeframe, budget and team members. Then create one row for each issue, record every solution proposed, and convert the solutions the team chooses into clear actions that state what completion looks like. Assign a named owner to each action so responsibility is visible. Use notes for context such as a first use of Scrum or a new communication tool. Finally, share the report with attendees and wider stakeholders so agreed changes can be adopted across future projects.

Use templates as a checklist

Use the survey to gather views before the meeting and the report template to capture decisions afterwards. A short survey can ask what worked and what did not, or rate teamwork, stakeholder collaboration, expectations, goals, deliverables and quality. The report template keeps the outcome practical by linking each issue to a solution, action, owner and notes. Before the meeting, check that every action has an owner and a clear definition of done; after the meeting, check that the report has been shared with everyone who needs to act on it.

Post mortem vs retrospective
Post mortemRetrospective
TimingEnd of a fully completed projectEnd of each sprint or iteration
ScopeReviews the entire projectReviews the most recent sprint
AttendeesAll team members and stakeholders involved across the projectProject team on the current sprint
FocusWhat went wrong and how to fix it for the next projectImproving quality and effectiveness for the next sprint

Comparison based on timing, scope, attendees and focus described in the guide.

Frequently asked questions

What is a project post mortem?

It is a structured review held after a project ends, bringing together people who contributed across the work to recognise successes, examine problems, and agree practical changes for future projects.

How does a post mortem differ from a retrospective?

A post mortem reviews the whole completed project, while a retrospective usually reviews one sprint or iteration. Post mortems tend to involve a wider group, including stakeholders, whereas retrospectives focus on the current delivery team.

How should a team prepare for a post mortem?

Schedule it soon after completion, invite contributors from every phase, share an agenda and brief project recap in advance, and ask attendees to spend a short period reflecting on what worked and what did not.

What should a post mortem report contain?

Record the project and meeting details, list each issue, capture possible solutions, convert chosen solutions into specific actions, name an owner for every action, add useful context in notes, and share the finished report with attendees.