How many rounds of revisions are normal for design approval?

Two structured rounds is the standard when feedback is anchored to the brief and collected in one place. The first round covers the overall direction; the second covers refinements. Projects that run to four or five rounds almost always share the same root cause: feedback arrived from multiple stakeholders across different channels (email, Slack, a call), so no single round was ever truly closed before the next one started.

How do I ask a client for design approval without sounding pushy?

Tie your ask to the next step, not to your schedule. 'Once you've had a chance to look at this, let me know if the direction is approved and I'll move to final production' is a clear, professional close that frames approval as unblocking the client's own project — not rushing them. Include a specific window: 'I'll plan to start production on [date] unless I hear otherwise.' Clients who are going to say no rarely do so late; most delays are simply the approval sitting in a full inbox.

What if the client keeps asking for revisions without ever approving?

This is almost always a contract problem, not a design problem. If your proposal defines a fixed number of revision rounds, point to it. If it doesn't, define it now: 'We've done two rounds — I want to make sure we're using the remaining scope well. Can you consolidate the remaining notes into one final list?' Structuring feedback as a named round (rather than an ongoing conversation) makes approval feel like a natural next step rather than a gatekeeping move.

How do I get design approval from multiple stakeholders?

Share one link and make it the only place for notes — not email, not Slack, not a Zoom where someone screenshots their screen. When all reviewers comment on the same artifact, conflicting opinions are visible to each other and the person with final authority can resolve them in the thread rather than you receiving two contradictory emails. Establish the approval hierarchy before you send: one person consolidates or one person has sign-off authority. 'Reply all' feedback loops between stakeholders are not your job to referee.

Do I need a design approval form or contract sign-off?

A formal sign-off document is worth adding for large projects or clients who have requested changes after previously approving work. A written 'I approve this for production' email is often sufficient and faster. The more important thing is that approval is explicit — a non-reply does not count as sign-off, and continuing to production without it is a risk you're absorbing alone.

How do I handle 'I'll know it when I see it' clients?

Present multiple directions early — even rough ones — rather than a single polished concept. Clients who can't articulate what they want in advance can usually point at a direction once they see options side by side. Frame it as: 'These three are different bets on the brief. Which direction feels right, and we refine from there.' This approach turns a vague initial approval into a clear direction without burning revision rounds on a misaligned concept.

drafty

How to get design approval from a client

Quick answer

To get design approval, share the work in a way that makes sign-off easy — not just the file. That means: tie the presentation to the brief rather than personal taste, give your client a way to mark up the exact element they mean (not describe it in an email), and collect all feedback in one place before you revise. Most stalled approvals come from scattered notes and unclear authority, not from a design that's actually wrong.

Step 1

Brief your client before you show the design

Walk your client through the brief and the specific goals the design had to solve before you reveal anything. 'We needed the hero to read as premium on mobile' gives them a frame for looking at it. Skipping this step is the single biggest source of late-stage 'can we try something completely different' feedback — because the client had no shared criteria and evaluated purely on instinct. Keep it to two or three sentences. You're not selling; you're giving them the vocabulary to approve it. If you have a written brief they signed off on, paste the three most relevant lines at the top of your presentation.

Step 2

Share the design as a link, not an attachment

An emailed file invites a reply with a marked-up screenshot, a PDF export with comments, and a voice note all covering different things. A link — whether a Figma view, an exported image in a browser-based review tool, or a live page — keeps every reviewer on the same version. In Figma, click Share → 'Anyone with the link can view' → Copy link. For a Figma export, a PDF, or a design built outside Figma, a browser-based tool wraps it in an annotation layer. The key detail: Figma commenting requires a Figma account. Many clients hit the login prompt and email you instead — plan for that if your client isn't already a Figma user. For a client who hasn't touched Figma, a review link that opens in any browser with no login is often faster.

Step 3

Ask your client to click the exact element, not describe it

Vague feedback — 'can we make it more premium?' — comes from clients who can't point at what they mean, not from clients who don't know what they want. Solve this at the sharing step, not the revision step. A review link that lets clients click the specific element (the headline, the icon, the button colour) and pin a note there produces comments like 'this CTA doesn't stand out enough at this size' rather than 'it needs to pop more'. The designer reads the note, sees exactly what it's attached to, and makes one precise change — rather than making five guesses and sending another round. Tools that support this include Markup.io, GoVisually, Atarim, and Drafty. Each has a different focus (Atarim is built for WordPress agencies; Markup.io for general design review); none of them require the client to create an account.

Step 4

Establish one decision-maker before you present

The most common cause of a third or fourth revision round isn't a design problem — it's two stakeholders sending separate feedback, neither of whom has final authority. Before you send the design, ask: 'Who should have final sign-off — one person, or should I collect notes from multiple people and you consolidate them before sending?' If it's multiple people, collect their feedback on a single link (so the notes are visible to each other) and give the final decision-maker a thread they can resolve, not three separate emails to reconcile. Set a response window: 24–72 hours is the industry norm. Without a deadline, approval cycles can drag for weeks — and creative momentum is hard to restart after a two-week gap.

The faster way

If you're collecting approval on a design — not annotating it yourself — drop the exported file or canvas URL into Drafty and share the link. Your client clicks the exact element they're reacting to and leaves a note pinned there — no login, no extension. Every stakeholder comments on the same artifact. You see all the threads in one place, reply, resolve them, and push the revised version to the same URL. Your client opens the same link and sees v2, with resolved comments already closed. No re-emailed files, no 'can you send it again in a bigger format' replies.

Open a live demo

Questions

How many rounds of revisions are normal for design approval?: Two structured rounds is the standard when feedback is anchored to the brief and collected in one place. The first round covers the overall direction; the second covers refinements. Projects that run to four or five rounds almost always share the same root cause: feedback arrived from multiple stakeholders across different channels (email, Slack, a call), so no single round was ever truly closed before the next one started.
How do I ask a client for design approval without sounding pushy?: Tie your ask to the next step, not to your schedule. 'Once you've had a chance to look at this, let me know if the direction is approved and I'll move to final production' is a clear, professional close that frames approval as unblocking the client's own project — not rushing them. Include a specific window: 'I'll plan to start production on [date] unless I hear otherwise.' Clients who are going to say no rarely do so late; most delays are simply the approval sitting in a full inbox.
What if the client keeps asking for revisions without ever approving?: This is almost always a contract problem, not a design problem. If your proposal defines a fixed number of revision rounds, point to it. If it doesn't, define it now: 'We've done two rounds — I want to make sure we're using the remaining scope well. Can you consolidate the remaining notes into one final list?' Structuring feedback as a named round (rather than an ongoing conversation) makes approval feel like a natural next step rather than a gatekeeping move.
How do I get design approval from multiple stakeholders?: Share one link and make it the only place for notes — not email, not Slack, not a Zoom where someone screenshots their screen. When all reviewers comment on the same artifact, conflicting opinions are visible to each other and the person with final authority can resolve them in the thread rather than you receiving two contradictory emails. Establish the approval hierarchy before you send: one person consolidates or one person has sign-off authority. 'Reply all' feedback loops between stakeholders are not your job to referee.
Do I need a design approval form or contract sign-off?: A formal sign-off document is worth adding for large projects or clients who have requested changes after previously approving work. A written 'I approve this for production' email is often sufficient and faster. The more important thing is that approval is explicit — a non-reply does not count as sign-off, and continuing to production without it is a risk you're absorbing alone.
How do I handle 'I'll know it when I see it' clients?: Present multiple directions early — even rough ones — rather than a single polished concept. Clients who can't articulate what they want in advance can usually point at a direction once they see options side by side. Frame it as: 'These three are different bets on the brief. Which direction feels right, and we refine from there.' This approach turns a vague initial approval into a clear direction without burning revision rounds on a misaligned concept.

Keep exploring

How to get feedback on a logo How to get feedback on a Figma design Review a website Design review without BugHerd

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