How many revision rounds should I include in a design contract?

Two rounds is standard for logo and brand identity work; three for web or UI design. What matters as much as the number is how you define a round: one consolidated batch of feedback, submitted by a deadline, not a rolling stream of changes. Build in a rate for additional rounds so the client knows the boundary before they hit it.

What counts as a revision versus a new request?

A revision refines or corrects something in the agreed brief — adjusting the colour, moving a heading, resizing an element. A new request changes the scope: a new page, a different layout direction, or something not mentioned in the original brief. When a client asks for something outside scope mid-round, name it: 'That's a new deliverable rather than a revision — here's what it would cost to add it.' Staying quiet and absorbing it sets a precedent.

How do I stop feedback from arriving one comment at a time instead of all at once?

Set a feedback deadline when you open the round and explicitly ask for all comments at once: 'Please review and send everything by Thursday.' Then hold the boundary — don't action individual comments that arrive before the deadline. Let the client know you'll pick them up when the deadline closes so they have an incentive to gather all their notes first, including from any stakeholders they need to consult.

What do I do when a client ignores the revision limit and keeps requesting changes?

Reference the contract clause calmly — don't avoid it. 'We've completed the two rounds included in the project. I'm happy to keep going — here's what an additional round costs.' Have the rate ready so the response is one message, not a negotiation. Most clients who push past the limit aren't being difficult; they just haven't been reminded where the limit is. A written reminder with a clear next-step price usually resolves it.

How do I get better feedback from clients who say things like 'make it pop'?

Ask them to annotate the actual design rather than describe it in words. A comment pinned to the headline that says 'this feels small against the body text' is actionable; 'the hierarchy is off' sent in an email is not. You can also send a feedback prompt alongside the link: 'Tell me what to change, where it is, and what you'd like instead.' Giving clients a structure produces more specific feedback and shorter rounds.

Should I start revisions as soon as I get client feedback?

No — confirm the complete list first. Reply and enumerate every change you're reading: 'I'm picking up three changes: [A], [B], [C] — is that everything?' Wait for confirmation before opening the file. This catches feedback the client forgot to include and creates a written record of what was agreed. A round you start before the list is confirmed is a round that can reopen.

drafty

How to handle client revision rounds

Quick answer

Handle each revision round by opening it with a clear deadline for feedback, collecting all comments directly on the design (not in email), confirming the complete list in writing before making a single change, then delivering the revised version and formally closing the round. Most revision spirals happen when rounds aren't opened or closed — feedback trickles in indefinitely and no one knows whether round one is actually done.

Step 1

Open each round with a deadline and a single shared link

When you send a deliverable for review, don't just drop the file in an email — open the round explicitly. Name it ('This is Round 1 of 2') and give a feedback deadline ('Please send all changes by Thursday at 5 pm'). A deadline matters because clients often haven't consulted their manager or business partner yet. Without one, feedback arrives over a week in drips, and you end up making changes on a version the stakeholder hasn't seen. Share the design as a link, not a file attachment. A link means every reviewer is looking at the same version; a PDF attachment means you'll be reconciling four annotated copies emailed back to you at different times.

Step 2

Collect all feedback on the design itself, not in a separate thread

Ask clients to comment directly on the artifact rather than describing changes in a separate email. 'The hero image feels off' takes three follow-up messages to action. 'This image — the contrast is too low for mobile' takes none. Figma lets collaborators comment in-canvas. For documents, PDFs, and anything outside Figma, share a review link the client can open in any browser and pin notes without an account. The gotcha most designers miss: a Figma view-only link prevents commenting for anyone without a Figma account — they fall back to emailing. Check your share settings before the review starts.

Step 3

Confirm the complete list before touching anything

When feedback arrives — even if the deadline has passed — don't start the revisions immediately. Reply first and list every change you're reading: 'I'm picking up four changes from this round: [A], [B], [C], [D] — is that the full list?' This catches the client who forgot to include their director's notes and would have come back with three more requests after you'd already made the first four. It also creates a written record. If a dispute comes up later ('I thought I asked you to change X'), you have a reply where the client confirmed the list and X wasn't on it. Only once they reply confirming 'yes, that's everything' do you open the file.

Step 4

Deliver the revision and close the round in writing

After making the confirmed changes, deliver on the same link (not a new file) and close the round explicitly: 'Round 1 is complete — here's the updated version. Round 2 opens on [date].' Delivering on the same link means there's only one URL to reference. Closing in writing prevents Round 1 feedback from reappearing as 'new' in Round 2. If the client surfaces a forgotten change, note it for the next round: 'I'll pick that up in Round 2.' The round is closed; hold that line.

Step 5

When rounds run out: name it, quote it, move on

If the client hits the revision limit in your contract and wants more changes, don't go quiet or start delivering extra work unpaid. Reference the agreed scope plainly: 'We've completed the two rounds included in the project — happy to continue, here's what an additional round costs.' Keep the tone factual, not confrontational. Have the rate ready (hourly or flat per round) so you can respond in one sentence. Most clients don't realise they've hit the limit; a clear message lands better than a terse 'that's out of scope.' If the extra request is genuinely small — a hex code swap, a typo — use your judgment. But if it's a layout change, it's billable.

The faster way

The fastest way to run a clean revision round is to share the design as a link and have the client annotate it directly — not describe changes in email. Drafty turns any design, doc, or PDF into a reviewable link: your client pins comments to the exact spot without needing an account, and every note lands in one threaded place. When you push the revised version, it goes on the same link — no new files, no 'which PDF are we on?' You can see all the feedback at once, confirm the list before starting, and mark each comment resolved as you go.

Open a live demo

Questions

How many revision rounds should I include in a design contract?: Two rounds is standard for logo and brand identity work; three for web or UI design. What matters as much as the number is how you define a round: one consolidated batch of feedback, submitted by a deadline, not a rolling stream of changes. Build in a rate for additional rounds so the client knows the boundary before they hit it.
What counts as a revision versus a new request?: A revision refines or corrects something in the agreed brief — adjusting the colour, moving a heading, resizing an element. A new request changes the scope: a new page, a different layout direction, or something not mentioned in the original brief. When a client asks for something outside scope mid-round, name it: 'That's a new deliverable rather than a revision — here's what it would cost to add it.' Staying quiet and absorbing it sets a precedent.
How do I stop feedback from arriving one comment at a time instead of all at once?: Set a feedback deadline when you open the round and explicitly ask for all comments at once: 'Please review and send everything by Thursday.' Then hold the boundary — don't action individual comments that arrive before the deadline. Let the client know you'll pick them up when the deadline closes so they have an incentive to gather all their notes first, including from any stakeholders they need to consult.
What do I do when a client ignores the revision limit and keeps requesting changes?: Reference the contract clause calmly — don't avoid it. 'We've completed the two rounds included in the project. I'm happy to keep going — here's what an additional round costs.' Have the rate ready so the response is one message, not a negotiation. Most clients who push past the limit aren't being difficult; they just haven't been reminded where the limit is. A written reminder with a clear next-step price usually resolves it.
How do I get better feedback from clients who say things like 'make it pop'?: Ask them to annotate the actual design rather than describe it in words. A comment pinned to the headline that says 'this feels small against the body text' is actionable; 'the hierarchy is off' sent in an email is not. You can also send a feedback prompt alongside the link: 'Tell me what to change, where it is, and what you'd like instead.' Giving clients a structure produces more specific feedback and shorter rounds.
Should I start revisions as soon as I get client feedback?: No — confirm the complete list first. Reply and enumerate every change you're reading: 'I'm picking up three changes: [A], [B], [C] — is that everything?' Wait for confirmation before opening the file. This catches feedback the client forgot to include and creates a written record of what was agreed. A round you start before the list is confirmed is a round that can reopen.

Keep exploring

How to manage client revisions Client feedback tool Review a website

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo