Post-Project Review Template for Agencies

Post-project reviews are where agencies actually improve. Without them, you repeat the same mistakes every project. With them, each project makes you smarter.

A post-project review isn't complicated. It's a structured conversation about what went well, what didn't, and what you'll do differently next time.

Timing

Do the review within a week of project completion, while everything's fresh. Wait too long and details fade. Do it too early and you don't have perspective yet.

Include the team that worked on the project plus a facilitator from outside the team if possible. An outside perspective prevents group consensus and honesty erosion.

Project Overview

Start with basic facts, so you have context.

• Project name and client
• Project duration
• Team size
• Budget and actual spend
• Timeline and whether you hit it
• Primary objectives

This isn't analysis yet. Just context-setting.

What Went Well

Start positive. What actually worked on this project?

• What am I most proud of?
• What went smoother than expected?
• What did the team do really well?
• What did the client appreciate most?
• What would we want to do the same way next time?

Let people celebrate. Morale matters. You're building a culture where good work is recognized.

What Didn't Go Well

Now the harder part. What could have been better?

• What caused the most friction?
• What took longer than expected?
• Where did we miss deadlines or expectations?
• What surprised us negatively?
• Where did communication break down?
• What's the biggest thing we'd change?

Be honest. This is for learning, not blame. Create psychological safety. "What would have helped us deliver better?" not "Who screwed up?"

Root Cause Analysis

For things that didn't go well, dig deeper.

• Why did that happen?
• What processes or decisions led to it?
• Was it avoidable or just bad luck?
• How much of this is on us versus external factors?

This is where you find patterns. "We're always late on design because we don't get clear feedback from the client early." Now you can fix it.

Client Feedback

Get their perspective if possible.

• How satisfied was the client?
• Are they likely to work with us again?
• What would they do differently?
• What did they value most?
• What did they wish we'd done differently?

This is different from internal perspective. They might say "Your communication was great" when your team thought it was chaotic. Their perception is reality for selling more work.

Business Metrics

Evaluate the project economically.

• Was it profitable?
• Did we estimate the effort correctly?
• Did the timeline hold?
• Did scope creep happen? How much?
• What was our utilization rate?
• Was the client profitable to work with long-term?

This is important. Some projects are great work but bad business. You need to know which is which.

Lessons Learned

Summarize the concrete things you're taking away.

• What's one thing we'll do differently next time?
• What process or tool should we implement?
• What should we stop doing?
• What should we do more of?
• How do we train the team on what we learned?

These should be specific and actionable. "Communication was better" is not actionable. "We'll have a weekly client call and share written updates on Slack" is actionable.

Action Items

Assign ownership for the lessons learned.

• What's the one change we need to make?
• Who owns implementing it?
• When will it be done?
• How will we know we did it?

Without action items, post-project reviews are just venting. With them, you actually improve.

Retention Questions

If you want the client back, ask yourself:

• Will this client hire us again?
• Should we want them to?
• What would it take to have them hire us for another project?
• How should we nurture this relationship?

Some clients are great but low-margin. Some are profitable but annoying. Be honest about which is which.

Post-Project Review Meeting Flow

1. Opening (5 min) - Frame the purpose. This is learning, not blame.
2. Overview (5 min) - Facts about the project.
3. What Went Well (10 min) - Celebrate wins.
4. What Didn't Go Well (15 min) - Honest conversation.
5. Root Causes (10 min) - Dig deeper on problems.
6. Lessons Learned (10 min) - Specific takeaways.
7. Action Items (5 min) - Assign owners and dates.

Total time: 60 minutes. Keep it tight.

Documentation

Write it up and make it searchable. Future projects should learn from this. If you didn't document it, it didn't happen.

Store project reviews in a central place your team can search. Over time, you'll see patterns. "We always underestimate design work" becomes obvious if you have data.

FAQ

How honest should we be? Completely. If people know they'll get blamed, they'll hide problems. Make it safe to be honest by focusing on learning.

Should the client be in the post-project review? Not the internal debrief. But definitely get client feedback separately. Their perspective is valuable but different.

What if we can't find a root cause? That's okay. Sometimes things just don't go smoothly and there's no single reason. Document it and move on.

How do we actually implement the action items? Ownership and deadline. "Sarah owns implementing weekly status updates, starting with the next project." Without clear ownership, nothing changes.

What if the same problems come up project after project? That means you're not actually implementing the action items. Either the lessons aren't real or the change isn't sticking. Address that.

How often should we review our post-project reviews? Quarterly. Look at the last few projects. What patterns do you see? Are the action items being implemented? Are your processes improving?