Most freelancers only find out what a client thought when they don't get rehired. The silence after a project can mean "perfect, we'll be back in spring" or "fine, but we're trying someone else next time," and you can't tell which. A short feedback form asked at the right moment turns that guess into data, catches small problems while they can still be fixed, and gives you testimonials in the client's own words.
This template has two versions: a quick mid-project check-in and a fuller end-of-project review. Both are designed to be finished in under five minutes.
TL;DR
The client feedback form template has a mid-project check-in and an end-of-project review, with 1-5 ratings for results, communication, timeliness and value, a 0-10 likelihood-to-recommend score, open questions on what worked and what to improve, and testimonial permission. Send the check-in at the project midpoint and the review within two weeks of delivery. Keep it under five minutes so clients actually finish it.
What's inside
- Mid-project check-in — four quick ratings and one open question about what to adjust.
- Project details — client, project and completion date.
- Ratings — results, communication, responsiveness, timeliness, value and overall experience.
- Likelihood to recommend — a 0-10 score with a follow-up "why."
- Open questions — what worked, what could improve, what nearly stopped them hiring you.
- Future work — whether they expect to need help again, and with what.
- Testimonial permission — consent to quote, and how to be named.
When to use it
Send the check-in on projects longer than about four weeks, around the halfway point. It's short enough to send by chat or email, and it often surfaces a mismatch in expectations (too many updates, too few, the wrong person being copied) that would otherwise come out at the end.
Send the full review as part of your offboarding, after final delivery and once the final invoice is settled, so the feedback isn't mixed with the payment conversation. The client offboarding checklist and project handoff checklist show where it fits among the closing steps.
Questions that produce useful answers
"What nearly stopped you from hiring us?" This tells you about friction in your sales process: price, response time, a missing case study. Answers here are often more actionable than any rating.
"If you could change one thing about working with us, what would it be?" Limiting it to one thing gets a specific answer instead of a polite "nothing."
The 0-10 recommend score. Track it across projects rather than reading too much into any single score. Clients who answer 9 or 10 are the ones to ask for referrals and testimonials; anyone at 6 or below deserves a follow-up call.
Testimonial permission inside the form. Asking "may we quote you?" alongside the feedback means you don't need a separate awkward request. Always confirm the exact wording before publishing.
What to do with the results
Read every response within a day and reply personally to each one, even if it's two lines. For any rating of 2 or below, call or message to understand what happened. Every quarter, look across all responses for themes: if three clients mention slow replies, the fix is a process change, not an apology.
Clients who score you highly and expect more work are your best source of repeat business. That's a good moment to mention upcoming availability or a retainer option. If you're planning a rate change, consistently strong feedback is useful context for the rate increase letter.
Customize it in your COLO workspace
COLO doesn't host feedback forms, so download this template and send it as a file or paste the questions into an email. You can send the mid-project check-in in project chat where the client already talks to you. For your own analysis, COLO reports on projects and customers, exportable to CSV, Excel or PDF, give you the delivery and payment side to read alongside what clients said.
Common mistakes
- Sending it with the final invoice. Payment and feedback in the same message muddy both.
- Too many questions. Response rates fall sharply after five minutes.
- Only asking happy clients. You learn the most from the projects that felt difficult.
- Publishing quotes without approval. Always confirm wording and how the client wants to be named.
FAQ
Q: When should I ask clients for feedback?
At two points: a short check-in around the midpoint of a longer project, while there's still time to fix problems, and a fuller review within a week or two of final delivery, while the experience is fresh.
Q: How long should a client feedback form be?
Five minutes or less. Eight to twelve questions, mostly ratings with two or three open questions, gets far more responses than a long survey.
Q: What questions should a client feedback form ask?
Ask about the result, communication, timeliness, value for money and the likelihood of recommending you, plus open questions on what worked, what could be better, and what nearly stopped them from hiring you.
Q: How do I turn feedback into a testimonial?
Include a permission question asking whether you may quote their comments, and whether they want to be named with their company or anonymously. Then send them the exact wording for approval before publishing.
Q: What should I do with negative feedback?
Thank the client, acknowledge the specific issue, and say what you'll change. If the problem can still be fixed, offer to fix it. Track repeated themes across projects; one complaint is an anecdote, three are a process problem.