
Post-Event Review
Docs + Word8 pages
Free
Most retrospectives end as a list of complaints that nobody reads again. This document keeps the value where it belongs: findings grouped by theme, the root cause behind each one, and recommendations that carry a named owner and a due date. It runs over eight pages, from an answer-first summary to a RACI of who decides and who does.
The sample follows a pump station upgrade delivered by Marlowe Green Engineering, which finished 4.5% over budget after five late deliveries, three of them traced to an 18-day design sign-off against a plan of 7. Replace the project, figures, lessons and names with your own, and delete any recommendation you will not act on.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Replace the summary with your objectives, headline result and the four findings that matter most.
Move your lessons into went well and improve, and write the root cause behind each improvement before the fix.
Give every recommendation one owner and a date within 90 days, and update the RACI to match.
Delete the guide page, then share the document with the PMO and your sponsor or present it in the retrospective.
Yes. Make a copy in Google Docs and it is yours to edit, with no sign-up on this site and no cost. You can reuse it for every project you close.
No. Marlowe Green Engineering, the pump station project, every person and every figure are fictional and written only to show what good looks like. Replace them before sharing.
Aim for 8 to 20 lessons under 4 to 6 themes, and 5 to 8 recommendations. Each recommendation needs an owner and a due date within 30 to 90 days.

Docs + Word8 pages
Free
Docs + Word5 pages
Free
Slides + PowerPoint11 slides
Free
Slides + PowerPoint10 slides
Free
Docs + Word6 pages
Free