Web Design Revision Process: How to Manage Client Revisions Without Losing Control
Web Design Revision Process: How to Manage Client Revisions Without Losing Control
A clear web design revision process is the single most important factor in keeping a project on budget, on time, and out of the revision spiral that turns a 4-week project into a 4-month one. The core structure: define the number of revision rounds in the contract, separate each round clearly, collect all feedback through a visual tool so nothing gets lost, and close each round with an explicit confirmation before opening the next one. This guide walks through the complete process from kickoff to sign-off.
Why Most Freelance Revision Processes Fail
Most freelance revision processes fail for one of three reasons:
1. No defined rounds. The contract says "revisions included" without specifying how many. The client treats the project as perpetually open-ended, and you don't have standing to push back.
2. No feedback structure. Feedback arrives across email, WhatsApp, phone calls, and the occasional Post-it photo. You spend hours aggregating it, misinterpret things, fix the wrong element, and create more rounds.
3. No explicit sign-off. Rounds close implicitly — you implement the feedback, send the updated version, and assume silence means approval. It doesn't. Six weeks later the client is still "reviewing" and you're not sure if the project is done.
All three failures are process failures, not client problems. A well-structured process makes all three avoidable.
Before the Project: Define Revisions in the Contract
The revision process starts before a single pixel is placed. Your contract needs to specify:
- How many revision rounds are included. Two is standard for most web design projects. Three for larger builds. One for small landing pages.
- What counts as a revision. A revision is a change to something already designed and approved. A new requirement is a scope addition and is billed separately.
- Who can request revisions. One named point of contact. Not "the team". Not "whoever emails first."
- What happens beyond included rounds. Additional revision rounds are billed at your hourly rate (state the rate).
This language isn't adversarial — it's professional. Clients who've worked with organized freelancers before expect it. Clients who haven't worked this way before appreciate the clarity once they understand it.
Setting Up Your Feedback System
Before you share anything for review, set up the tool that will collect feedback. The right tool for client website revisions is a visual feedback tool — software that lets clients click directly on elements and leave anchored comments, rather than describing them in emails.
dotts is built for exactly this. You paste the staging URL (or upload a PDF or image), get a shareable client link, and clients can click anywhere on the page to leave a comment. The comment is pinned to that element. You see a dashboard of everything they flagged, each one exactly where they meant it.
Important: set this up before round 1, not after the client has already sent you a 400-word email. Once the email habit is established, it's harder to redirect.
Round 1: Structure and Content
The first revision round should be exclusively about structure and content. Is the page architecture right? Is the hierarchy correct? Does the copy say what it needs to say? Is the right information on the right page?
Why scope it this tightly? Because visual refinements on top of wrong structure is wasted work. If the client approves a layout in round 1 and then changes the structure in round 2, you're essentially building twice.
When you share for round 1, say this explicitly:
"This is round 1 — please focus on structure, layout, and content. Is the right information in the right place? Is anything missing or in the wrong order? We're not finalising visual styling at this stage."
This framing prevents clients from obsessing over font weights and button colors when the page structure might still shift.
What to collect in round 1:
- Layout changes (move this section, remove this page, add this block)
- Content corrections (wrong copy, missing information, outdated details)
- Navigation and information architecture feedback
What to defer to round 2:
- Color adjustments
- Typography refinements
- Image choices (unless the image is in the wrong place structurally)
- Micro-interactions and animations
Closing Round 1 Properly
After you've addressed all round 1 feedback, don't just send the updated link. Close the round explicitly.
Send a brief summary: "I've addressed all [X] items from round 1. Here's the updated version for your confirmation: [link]. Please reply to confirm round 1 is complete so we can move to round 2."
Two things are happening here: you're documenting what was done, and you're asking for an active confirmation that round 1 is closed. That confirmation is your protection if something from round 1 resurfaces in round 3.
Round 2: Visual Refinement
Once the structure is locked, open round 2 for visual refinement. This is where color, typography, imagery, and styling details get addressed.
Your round 2 message:
"Round 2 is open. Structure is locked in from round 1. Please focus on visual styling — anything in the colors, fonts, imagery, or visual details that needs adjustment."
The "structure is locked" framing matters. It signals that structural changes are no longer in scope without you having to enforce it mid-review.
What to collect in round 2:
- Color adjustments (wrong brand color, contrast issues)
- Typography (font feels wrong, size or weight needs adjustment)
- Image feedback (wrong image, image quality, image placement)
- Spacing and visual balance issues
- Anything visually inconsistent
Handling New Requests Mid-Process
At some point in almost every project, a client will add something new during a revision round. A new section they forgot about. A page they didn't mention at kickoff. A feature that "just makes sense."
Handle this immediately and in writing. When a new item appears in a round 2 comment, reply directly in the feedback thread:
"This is a new addition outside our included revision rounds. Happy to scope it — I'll add it to the change log and we can discuss it separately."
Don't ignore it. Don't silently implement it and hope the client doesn't notice you've done extra work for free. Name it clearly, the first time, in the same thread where it was requested.
The client's reaction to this moment tells you a lot. Organized clients say "right, understood, let's scope it." Clients who push back might need a gentle reminder that your contract defines scope — which is why that contract language matters.
Pre-Launch QA Round
Before launch, run a final QA pass — ideally shared as a separate dotts link specifically scoped to:
- Copy accuracy (no typos, correct contact info, correct pricing if applicable)
- Broken links and 404s
- Mobile responsiveness on actual devices
- Forms working correctly
- Images loading at correct quality
- Page speed (basic)
This is not a new design round. It's a technical and accuracy check. Frame it that way:
"This is the pre-launch review. We're checking for anything broken, any copy errors, and anything that doesn't work correctly on your device. This is not a round for design changes — we're in sign-off mode."
The "sign-off mode" language sets the expectation clearly.
Getting the Final Sign-Off
Final sign-off should be explicit and in writing. Don't assume that silence after the pre-launch QA means approval.
Send a clear close message:
"Everything has been addressed and the site is ready for launch. Please reply with your sign-off and I'll prepare the launch checklist. Once confirmed, any additional changes will be scoped as new work."
That last sentence is important. It closes the revision process at the point of sign-off, so anything that comes up after launch (and something always does) is clearly a new engagement, not a leftover revision.
Managing Revision Creep in Real Time
Even with a perfect process, revision creep happens. Here's how to handle it in the moment:
New items in late rounds: Name them, log them, scope them. Don't implement silently.
Conflicting feedback from different stakeholders: "I'm seeing two different directions here — can you confirm which to follow before I proceed?"
Reopening something from a closed round: "We addressed this in round 1 and it was confirmed as resolved. If you'd like to revisit it, I can scope it as an additional round."
Scope erosion (lots of small additions that add up): Do a regular scope check. After a few rounds, compare what's been built to what was contracted. If you're consistently doing more than was agreed, address it directly: "I want to flag that we're approaching the edge of our original scope. Happy to continue — let's talk about how to handle the additional work."
Using dotts to Keep Revision Rounds Clean
A structured feedback tool makes the revision process significantly easier to manage:
- Every comment is timestamped — you know exactly when each piece of feedback arrived
- Comments are anchored — no ambiguity about which element a note refers to
- Resolved comments stay in the history — you have a record of everything that was addressed
- Separate projects per round — create a new dotts project for each round so feedback doesn't mix
- Reply in the thread — all communication around a specific change lives in one place
This doesn't just make your process better — it makes the process visible to the client. When they can see all their comments being addressed one by one, they feel confident the project is moving forward. That confidence reduces the anxiety that leads to off-channel messages and surprise requests.
Bottom Line
A web design revision process isn't about being rigid with clients — it's about creating a structure that makes the project better for everyone. Clear rounds, visual feedback collection, explicit sign-offs, and immediate scope management are the four pillars. Get those right and revision chaos becomes the exception rather than the rule.
FAQ
How many revision rounds should I include in a web design contract?
Two rounds is standard for most web design projects. Include one round for structure and content, one for visual refinement, and a separate pre-launch QA pass. Projects with more complex information architecture or multiple stakeholders may warrant three rounds.
What is the best tool for collecting web design revisions from clients?
dotts is the most efficient tool for freelancers. Clients click directly on the element they're commenting on, leave a pinned note, and browser/device data is captured automatically. No client account required. It works on live websites, PDFs, and images.
How do I handle clients who add new requests during revision rounds?
Name it immediately, in writing, in the feedback thread: "This is a new addition outside our included revision rounds." Log it, scope it separately, and refer to your contract. The key is to catch scope additions at the moment they appear — not after you've silently implemented three of them.
How do I close a revision round properly?
Send a brief summary of what was addressed and ask for explicit confirmation before opening the next round: "I've implemented all X items from round 1. Please confirm we're ready to proceed to round 2." Written confirmation at each round closing is the paper trail that protects you if something resurfaces later.
What should I do if a client keeps asking for revisions beyond the agreed rounds?
Refer to the contract, name it early, and scope additional rounds as paid work. A clear message: "We've completed our included revision rounds. I'm happy to continue — additional rounds are billed at [rate]. Want me to put together a change order?" Clients who have a defined contract language rarely push back hard.
How do I separate round 1 and round 2 feedback so they don't mix?
Use a separate dotts project or a new shared link for each round. When you send the round 2 link, state explicitly that round 1 is closed. Separate links make the separation tangible — clients see a fresh review interface, which reinforces that a new round has begun.
What goes into a pre-launch QA round?
Copy accuracy (no typos, correct contact info), broken links, mobile responsiveness on actual devices, form functionality, image loading, and basic page speed. Frame this explicitly as a technical and accuracy check — not a design round. No structural or visual changes at this stage.
Keep your revision process clean from day one. [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.