Post-Project Feedback Kit for Client Teams

Use a post-project feedback survey to understand the result, the working process, and what the client needs next. Keep the conversation practical and short enough to complete after delivery.

Before you send

Define the project milestone, the audience, and the decision that will follow. Send after the result is available, not while an unresolved issue is still blocking the client.

A compact question set

1. How well did the result match what you needed?
2. What helped most during the project?
3. Where did communication or speed fall short?
4. What would you change about the way we worked together?
5. What is the next problem we could help you understand?

The post-project survey template is ready to adapt.

How to read the answers

Separate outcome, process, communication, and scope. A delayed approval calls for a different action from a result that missed the original goal.

Keep a short evidence log with the theme, supporting responses, owner, and next review date. Share the summary with the team that can change the process.

Close the loop with the client

Thank people for the response and explain what you will keep, test, or investigate. Do not promise every requested change; be specific about the next step you can own.

Common mistakes

• Sending before the client can use the result.
• Asking only for a generic satisfaction score.
• Treating every comment as a project failure.
• Keeping the answers in a file with no owner.

Next step

Choose one recent project, send the five-question version, and schedule a 20-minute review with the delivery team.

Create my post-project survey