If you’ve been freelancing as a web designer for more than a few months, you already know the truth: the design work is rarely the hard part. The hard part is managing what comes after you hit “send” on that first preview link. Endless tweaks, vague feedback, contradicting stakeholders, and the dreaded “Can we just try one more version?” message at 11 PM on a Friday.
This guide is a practical playbook on how to handle client revisions without losing sleep, money, or your sanity. No fluff, just the workflows, contract clauses, and exact scripts I use with my own clients at Designer Renji.
Why Revision Rounds Spiral Out of Control
Before fixing the problem, it helps to understand why it happens. In my experience, runaway revisions almost always come from one of these root causes:
- No clear revision cap in the contract (or no contract at all)
- Too many decision-makers giving conflicting feedback
- Vague briefs that never defined what “done” looks like
- Feedback collected in scattered channels (email, Slack, voice notes, text messages)
- Designer-side issues: skipping discovery, presenting work without context, or hiding from tough conversations
Fix these upstream, and you fix 80% of the revision drama downstream.
Step 1: Set the Rules Before the Project Starts
Put a Revision Cap in Your Contract
This is non-negotiable. Every proposal and contract I send includes a clear, plain-English revision policy. Here’s the kind of clause I recommend:
“This project includes two (2) rounds of revisions per design phase (wireframes, visual design, development). A revision round is defined as a single, consolidated set of feedback submitted via [tool]. Additional rounds are billed at $[X]/hour with a one-hour minimum.”
Three things matter in that clause:
- The number of rounds is specific
- What counts as a “round” is defined
- The cost of extra rounds is stated upfront
Identify the Single Point of Contact
Before kickoff, ask: “Who is the final decision-maker on this project, and who will consolidate feedback from the team?” Get one name. Put it in the contract. If feedback starts coming from three different people, you have a contractual reason to push back.
Step 2: Run a Real Discovery Phase
Most revision nightmares are born in a weak brief. A 30-minute discovery call isn’t enough. I send a written questionnaire plus hold a 60-minute call covering:
- Business goals and target audience
- Three competitor sites they like (and why)
- Three sites they dislike (and why)
- Must-have features vs. nice-to-have
- Brand assets, tone, and visual references
- Success metrics: how will we know this redesign worked?
At the end, I write a design brief recap and get it signed off in writing. That document becomes the reference point any time a revision request drifts off-scope.
Step 3: Structure How Feedback Is Collected
One of the fastest ways to reduce revisions is to control how clients give them. I never accept feedback through random emails or DMs. Instead:
| Deliverable | Feedback Tool | Why |
|---|---|---|
| Wireframes & mockups | Figma comments | Pinned to exact elements |
| Live staging site | Markup.io or Pastel | Annotated screenshots |
| Copy & content | Google Docs (suggest mode) | Trackable changes |
| Strategic decisions | Recorded video call | Big questions deserve real conversation |
Tell the client upfront: “All feedback must come through [tool] within 5 business days. Anything outside that channel will be moved there before I action it.”
Step 4: Present Work the Right Way
How you deliver a design directly impacts the type of feedback you get. Never just send a Figma link and say “let me know your thoughts.” That’s an open invitation for chaos.
Instead, do a guided walkthrough, either live or as a Loom video. Cover:
- What problem this design solves (tying back to the brief)
- The reasoning behind key decisions
- What you specifically want feedback on at this stage
- What is not open for change in this round (e.g., “colors are locked, focus on layout”)
This last point is the secret weapon. Framing feedback narrows the scope and prevents clients from re-opening decisions you already settled.
Step 5: Turn Vague Feedback Into Actionable Tasks
“Make it pop.” “It feels off.” “Can we make it more modern?” Every freelance designer has heard these. Your job is to translate them into concrete actions before touching the design.
The Clarification Script
When you get vague feedback, respond with something like:
“Thanks for the feedback. To make sure I address this correctly, can you help me understand what ‘more modern’ means to you? Is it the typography, the spacing, the color palette, or something else? If you have a reference site that captures the feel you’re after, that would be incredibly helpful.”
This does three things: it shows you took the feedback seriously, it forces specificity, and it gets a reference you can actually design against.
Step 6: Handle Out-of-Scope Requests Diplomatically
When a client asks for something outside the brief (a new page, a new feature, a redesign of an already-approved element), do not just do it. Even if it’s small. Especially if it’s small, because those are the requests that compound.
The Scope Shield Script
“Great idea. That wasn’t part of the original scope, but I’d love to include it. Adding [request] would take approximately [X hours] and cost $[Y]. Want me to send a quick change order, or should we park this for phase two?”
Notice the tone: collaborative, not defensive. You’re not refusing, you’re presenting options. Most clients will either approve the change order or drop the request. Either way, you win.
Step 7: Know When to Push Back on Revisions
Sometimes a client’s revision is genuinely a bad idea: it’ll hurt conversions, break accessibility, or contradict the goals we agreed on. In those cases, my job is to give a professional opinion, not just say yes.
Try this format:
- Acknowledge: “I understand why you want to add a slider to the homepage.”
- Explain: “In my experience, sliders reduce conversions by around 30% because users rarely wait through them.”
- Recommend: “I’d suggest a static hero with a clear CTA instead, but if you still want to test the slider, I can build it.”
- Defer: “It’s your site, you make the final call.”
This positions you as a consultant, not a button-pusher. Clients respect designers who push back with reasoning.
Step 8: Lock Things Down at Sign-Off
After each phase, send a written sign-off request:
“Please reply with ‘approved’ to confirm the homepage design is finalized. Any changes after this point will be treated as new scope and billed accordingly.”
Save that email. Pin it. Reference it the next time someone wants to “just tweak the header one more time” after development has started.
Quick-Reference Cheat Sheet
| Situation | Your Move |
|---|---|
| Vague feedback (“make it pop”) | Ask for specifics + references |
| Out-of-scope request | Send a change order with cost and timeline |
| Conflicting stakeholders | Require one consolidated feedback document |
| Revisions exceed contract cap | Invoice for extra rounds at your hourly rate |
| Client wants something you disagree with | Acknowledge, explain, recommend, defer |
| Feedback in random channels | Redirect to your approved tool every time |
The Mindset Shift That Changes Everything
The freelancers who handle revisions well aren’t the ones with the toughest contracts. They’re the ones who treat revisions as part of the design process, not an obstacle to it. Feedback is data. Your job is to collect it cleanly, interpret it intelligently, and channel it into a stronger final product.
When you stop viewing clients as adversaries trying to squeeze free work out of you, and start viewing them as collaborators who haven’t been trained in how to give good feedback, everything shifts. Most of them aren’t being difficult. They just don’t know how the process works. That’s your job to teach them, gently, from day one.
FAQ: Handling Client Revisions
How many rounds of revisions should I include?
For most web design projects, two rounds per phase (wireframes, design, development) is reasonable. Anything more becomes inefficient for both you and the client.
What if a client refuses to pay for extra revisions?
This is why you put the policy in writing before starting. If they push back, point them to the signed contract and offer to find a compromise (e.g., dropping a feature in exchange for the extra round). Never work for free out of guilt.
How do I handle revisions after final delivery?
Once the project is signed off and delivered, any changes fall under a separate maintenance retainer or hourly rate. State this clearly in your contract under a “post-launch support” section.
What’s the best tool to manage client feedback?
For visual feedback on live sites, Markup.io and Pastel work well. For design files, Figma’s native commenting is hard to beat. For written content, Google Docs in suggest mode keeps everything trackable.
Should I charge a flat rate or hourly for extra revisions?
Hourly with a one-hour minimum is fairest for both parties. It discourages tiny nitpicks while keeping you compensated for real work. Some designers prefer flat-rate “revision packs” sold in bundles of 3 or 5 hours.
How do I tell a client their revision idea is bad?
Use the Acknowledge-Explain-Recommend-Defer framework. Respect their authority as the client while giving them the benefit of your professional expertise. Document your recommendation in writing in case the change backfires later.
Handling revisions well is one of the highest-leverage skills you can build as a freelance web designer. It protects your time, your income, and your relationships. Set the rules early, communicate often, and never let a project drift without structure. Your future self will thank you.