The 5 Biggest Mistakes Freelancers Make with Client Feedback
Most freelance web designers get client feedback all wrong. Not because they're careless — but because nobody taught them how to do it right. You're juggling feedback across WhatsApp, email, screenshots with red arrows, and voice notes. Your clients aren't sure where to click. Revisions pile up. Everyone's frustrated. It doesn't have to be this way.
This guide walks through the five biggest mistakes freelancers make with client feedback — and exactly how to fix them. By the end, you'll have a feedback process that saves you hours and actually improves your designs.
Mistake #1: Letting Feedback Scatter Across Multiple Channels
This is the #1 reason freelancers waste time on revisions.
You send the design to your client. They reply via WhatsApp. Their business partner comments in email. You get a voice note from another stakeholder. A week later, you're searching through three different apps trying to figure out which feedback is current, which is outdated, and which contradicts something else entirely.
What happens:
- You miss comments because they're buried in message threads
- The same issue gets reported twice in two different channels — you think it's new feedback
- You implement feedback from version 2, but meanwhile your client is on version 5
- You spend 30 minutes every morning just collecting and organizing feedback
Why this happens:
You probably hand over your design link via email with something like: "Here's the link — let me know if you have questions." No guidance. No structure. Your clients do what's easiest for them: text you on WhatsApp, email you, ask their team members to reply-all.
How to fix it:
Create a single source of truth for all feedback. Tell your client: "I've set up a feedback page specifically for this project. It takes 30 seconds to leave a comment. Please use this instead of email or WhatsApp — it keeps everything organized, and I won't miss anything."
When you use a dedicated feedback tool:
- All comments are in one place, chronologically ordered
- You can see which version each comment refers to
- Comments stay attached to the exact element — no ambiguity
- You can mark comments as resolved and track what's done vs. pending
This alone cuts revision time by 40–50% because you're not hunting for feedback anymore. You're implementing it.
Mistake #2: Skipping the Briefing — Clients Don't Know How to Give Feedback
Your client opens the design. They stare at it. They have some reaction, but they don't know what to click on or how to describe what they want.
So they send you a vague email: "Hmm, the design feels a bit off. Can you make it better?"
Or worse, they complain to their business partner instead of telling you, and you find out three weeks later that they were unhappy the whole time.
Why this happens:
Giving good feedback is a skill. Most clients have never done it before. They don't know the difference between "I don't like the color" and "I don't like the energy the color gives me." They might not even realize they can click on specific elements.
How to fix it:
Send a feedback briefing with every design review. It takes 3 minutes to write and saves 10 hours of confusion.
Example:
"Hi [Client], I've set up the design for feedback. Here's what helps me most:
>
1. Click directly on the thing you want to comment on — no need to describe where it is
2. Be specific: instead of "doesn't feel right," try "the headline feels too small" or "the blue is too dark"
3. Mention the impact: "this makes it hard to scan" or "this doesn't feel premium enough"
4. One comment per issue — keeps things organized
>
Questions? Just ask. I want to get this right."
Add a example screenshot or 30-second video showing where to click and how to leave a comment. Most clients will actually follow instructions if the process feels simple.
Result: Instead of vague feedback, you get actionable comments. Instead of surprises, you get clarity.
Mistake #3: Not Providing Enough Context
You send over the design. What your client doesn't see:
- What they asked for originally
- Which sections are complete vs. work-in-progress
- What the design is supposed to solve
- Why you made certain decisions
So they comment on parts that were intentionally left rough. They suggest changes that contradict their own brief. They focus on polish when they should be focusing on structure.
Why this happens:
You've been living with this project for weeks. Everything in your head makes sense. You forget that your client is seeing it fresh, with no context.
How to fix it:
Add a context note at the top of your feedback page. Keep it brief:
"This review focuses on [the homepage and pricing page]. The blog is coming next week. Please focus on:
- Does the headline communicate what we do?
- Is the pricing clear?
>
Don't worry about exact copy yet — that's next. Just let me know if the structure makes sense."
Give them permission to ignore certain things. Tell them what to focus on. Frame the review around their goals, not your to-do list.
Bonus: Add a "before & after" screenshot in your brief so they see what changed. Clients who understand the direction give better feedback.
Mistake #4: Treating All Feedback As Equal Priority
Your client leaves 22 comments. One says "logo is too big." Another says "the blue doesn't match our brand guide." A third says "I like the concept, just make it punchier."
You start implementing everything in order, spending 4 hours on minor tweaks while the major issues stay in the backlog.
Why this happens:
Clients don't triage. They don't know which feedback is critical vs. nice-to-have. They just comment as they go.
How to fix it:
After you collect feedback, create a triage list before you start designing:
Priority · Comment · Action
P1 (Critical) · Logo is too big — breaks the layout on mobile · Resize logo, test on mobile
P1 (Critical) · Blue doesn't match brand guide (should be #003D82) · Update color across site
P2 (Nice-to-have) · Could the intro text be punchier? · Review copy, consider rewrite
P2 (Nice-to-have) · Spacing between sections feels tight · Adjust padding if time allows
You reply to the client: "Thanks for the feedback. I'm prioritizing [critical items] first, then we'll tackle [nice-to-haves]. I'll send an updated version by Friday."
Now they know what's getting done when. You're not wasting time on polish while ignoring structural feedback.
Mistake #5: Not Closing the Loop — Clients Don't Know What You Actually Did
You get feedback. You implement it. You send a new version. Silence.
Three weeks later, the client asks about one of the items you already fixed. Or they complain about something you actually addressed, but they missed it in the new file.
You end up re-explaining your work because they didn't realize you'd already made the change.
Why this happens:
You assume the client will re-review everything. They don't. They skim it, see some changes, assume you ignored half the feedback.
How to fix it:
Send a revision summary with every updated version:
"Hi [Client], I've made the following updates based on your feedback:
>
✅ Resized the logo (it was 140px, now 80px)
✅ Updated the blue to match your brand guide (#003D82)
✅ Adjusted section spacing — should feel less cramped now
✅ Rewrote the intro headline to be punchier
>
Not included (will do next round): exact button labels and footer copy
>
The new version is ready for review at [link]. Let me know what you think."
This tells them exactly what changed. They can re-review with confidence. They know you listened.
If they still have feedback, repeat the process. Don't move forward until you're aligned.
Why dotts Fixes All of This
All five of these mistakes stem from the same root: scattered feedback + unclear process = wasted time.
When you use dotts:
- All feedback lives in one place (no more WhatsApp hunting)
- Clients click directly on elements (no ambiguity about what they mean)
- You can add context and briefing right on the feedback page
- You can see what's resolved vs. pending
- The revision history is clear — everyone knows what was changed and why
dotts isn't another tool your clients have to learn. They just get a link. They click where it matters. You get actionable, organized feedback. No login, no confusion, no lost email threads.
Real-World Example: Sarah's Chaos-to-Process Transformation
Sarah is a freelance Webflow designer. She'd been using the scattered-feedback approach for three years. Here's what her typical project looked like:
Before dotts:
- Monday: Client gets the design link via email
- Tuesday: Client WhatsApps her: "logo seems too big?"
- Wednesday: Client's business partner emails: "colors don't match the brand"
- Thursday: Sarah's clarifying which feedback is current. The client has already moved on to version thinking
- Friday: Sarah implements everything in random order, misses two comments in a Slack thread
- The following Monday: Client says "I thought you were going to fix the spacing?" (She did, but they didn't notice)
- Time spent on actual design revision: 3 hours. Time spent hunting and organizing feedback: 7 hours.
After dotts:
- Monday: Client gets the feedback link with a 2-sentence briefing ("focus on structure, not copy")
- All comments land in one feed. Sarah sees them in real-time
- By Thursday, Sarah sends a revision summary: "Fixed 4 items, holding off on copy until next week"
- Client reviews the new version, sees exactly what changed
- Time spent on actual design revision: 3 hours. Time spent on feedback admin: 30 minutes.
Same design. Same client. Fraction of the chaos.
Summary
The biggest feedback mistakes aren't about being a bad designer — they're about process. You're probably fighting against:
- Scattered channels (email, WhatsApp, Slack, voice notes)
- Unclear direction (clients don't know what feedback to give)
- No triage (you're treating minor tweaks like major revisions)
- No closing of the loop (clients don't realize you fixed things)
Fix these five mistakes, and you'll cut revision cycles in half. Your clients will feel heard. Your projects will move faster. You'll actually have time to do the design work you got into this field for.
The easiest starting point: consolidate your feedback into one tool. Everything else follows from there.
FAQ
Q: How do I convince clients to use a new tool instead of email/WhatsApp?
A: Frame it as making their life easier. "I've set up a feedback page so you don't have to type out long descriptions — just click and comment. Takes 10 seconds." Most clients prefer clicking over typing long explanations.
Q: What if the client keeps sending feedback via WhatsApp anyway?
A: Politely redirect: "Great point — can you add that to the feedback page as well? That way I can track everything in one place and make sure nothing gets missed." Don't shame them, just guide them.
Q: How many revision rounds is normal?
A: For a typical website: 2–3 rounds of feedback is healthy. If you're doing 5+, your briefing (Mistake #2) probably needs work — they're not clear on scope or direction. Spend an extra 15 minutes upfront clarifying, and you'll cut revision rounds.
Q: What about clients who say "just make it look better"?
A: This is Mistake #2 — lack of context. Reply: "I want to get this right. Can you tell me specifically what 'better' means? Is it the color, the size, the energy, the layout?" Force them to be specific. It'll change their feedback quality instantly.
Q: Should I charge extra for unlimited revision rounds?
A: Define "rounds" upfront in your contract. Something like: "3 rounds of revisions included. Additional rounds: $200 each." Scope creep disappears when clients know the boundary. Use your triage list to manage what fits in each round.
Q: How do I handle feedback that contradicts earlier feedback?
A: Document both in your triage list and ask for clarification. "You asked me to make the headline bigger last week, but now to make it smaller. Which direction should we go?" This is actually gold — it shows you're paying attention and prevents wasted work.
Ready to fix your feedback process? [Try dotts free →](https://dotts.se)
Further reading
Start Collecting Feedback in Seconds with dotts
Forget messy email threads and unclear revision requests. dotts makes feedback fast, clear, and organized so you can focus on what matters—getting work done.