Client Feedback Form Template
End-of-project debrief for agencies and freelancers — outcome versus expectation, communication quality, and whether the next project is yours.
The project is wrapped — before we archive the folder, tell us how it really went. Candor now makes the next engagement better.
Agencies lose clients in the gap between "the deliverable was fine" and "the experience was exhausting". A client feedback form exists to measure that gap while the project is still warm, because by the time the next RFP goes out, it is too late to learn why you were not on it. This template is a structured debrief, not a satisfaction survey — it is built to be filled in thoughtfully at a desk, which is why it ships in document mode.
Why these fields. The outcome question is scored against "what you hoped for" rather than "the brief", deliberately: clients judge results against the picture in their head, and the distance between that picture and your deliverable is the real quality metric. Communication gets its own rating because it is the number-one silent killer of agency relationships — projects with great outcomes and murky status updates still end. The deadline question offers "mostly, with slips" as a middle answer because that is the honest reality of most engagements, and forcing yes/no would hide it. Best-part and friction are the retro pair; friction names the specific surfaces — handoffs, revisions, invoicing — to give permission to complain about the unglamorous parts clients usually swallow. The next-project question is the only number your pipeline cares about, and its "consider this a heads-up" option has directly booked revenue for teams using it.
What we left out. Hourly-rate satisfaction (pricing conversations belong in a meeting, not a form), team-member-by-name ratings (feedback should land on the process, not individuals), and referral requests — asking for referrals inside a feedback form contaminates the candor you are trying to collect.
Who uses this. Design studios and dev shops send it with the final invoice, freelancers attach it to the handover email, and consultancies run it at every engagement close as part of their delivery checklist.
Make it yours. Add your project phases as a multi-select if you want friction localized by stage. Set the form to notify you by email on each response, and paste the best-part answers — with permission — into your proposals. If you run retainers, send the same form quarterly instead of at close; the CSV export turns those into a relationship health trendline per client.
Patterns across engagements. One debrief is an anecdote; five are an audit of how you run projects. Read the friction answers side by side across clients and mark every surface named twice — if revisions come up on three different engagements, the problem is your revision process, not those clients. The same goes for the deadline question: scattered "mostly, with slips" answers are project noise, but a straight column of them is a scoping habit. Treat the outcome scores as your quality floor and the repeated friction words as your operations backlog, revisited whenever you refine how the studio works.
Frequently asked questions
When is the right moment to send this?
With or just after the final deliverable, while details are fresh — ideally before the final invoice conversation so feedback does not tangle with billing.
Will clients be honest if the form is not anonymous?
Client debriefs are relational, not anonymous, by nature. The framing does the work: specific, low-stakes questions about friction get honest answers where "rate us" would get politeness.
Can I reuse the answers as testimonials?
Ask first — the best-part answers are often testimonial-grade, but they were given as private feedback. A separate testimonial form with explicit permission keeps it clean.
How do I track this across many clients?
One form for all engagements, with the project-name field as your join key. The CSV export gives you outcome, communication, and next-project intent per client in one table.