How many rounds should a design review take?

One or two rounds is the target. Email-based review adds rounds because clients describe feedback rather than point at it — resolving 'the section near the top' takes at least one extra exchange before you know what to fix. Anchored annotation (where a client clicks the exact element) plus a pre-call written-notes window typically gets a design to approval in one or two rounds instead of three or four.

How do I get more specific feedback from my client?

Give them a way to point at the exact element rather than describe it. Specific feedback comes from specific pointing — when a client can click the headline and type a note tied right there, the note is about the headline. When they're writing an email, they're translating a visual reaction into words, and something gets lost. Also helps: send two specific questions with the design link. 'What do you think?' gets impressions. 'Does the hierarchy make the offer immediately clear?' gets answers.

Should I present the design on a call or let the client review it async?

Both, in sequence. Share the link for async notes first (48-hour window), then use the call only to resolve what needs discussion. Presenting a design live for the first time on a call puts the client in a reaction mode — they respond to what you're talking about, not to the design itself. Clients who've already read and annotated come to the call knowing what they want to discuss; the meeting is shorter and the feedback is more considered.

What should I tell my client to look for in the design review?

Keep it to three things: whether the design matches the goal you agreed on (does the hierarchy push the right action?), whether it fits the brand (in feeling, not just in colour), and whether there's anything that would stop their audience from acting. Avoid open-ended prompts like 'let me know your thoughts' — they invite impressionistic feedback. Two focused questions produce more actionable notes than a general invitation to react.

How long should a design review meeting take?

30 minutes if the client has reviewed the design in advance and left written notes. 60 minutes if you're presenting it for the first time on the call. The 30-minute version is only possible when feedback is already anchored to specific elements before the meeting — the call is resolution, not discovery. If you're regularly running 90-minute review meetings, the bottleneck is usually that the client is seeing the design for the first time and reacting in real time.

How do I share a design with a client who doesn't have Figma?

Export it as a PNG or PDF and share it as an annotated review link — not a raw Figma share. A Figma view link prompts the client to log in or request access; most fall back to email. A browser-openable link with anchored commenting removes that wall entirely.

drafty

How to run a design review with a client

Quick answer

To run a design review, share the design as an annotated link (not a file), give the client two specific questions to answer, set a 48-hour window for written notes, then hold a 30-minute call to resolve anything that needs discussion. The most common reason reviews drag across three rounds is that clients describe feedback in email instead of pointing at the exact element — anchored comments fix that before the first exchange.

Step 1

Share a link, not a file — and frame what you're asking for

The single change that cuts review rounds: send a shareable link the client opens in their browser, not a Figma file that hits them with a login wall, and not a screenshot they'll annotate in Preview and email back. Before you send, write two specific questions at the top of your message: one about the goal ('Does the hierarchy make the main action immediately obvious?') and one about the constraint you're most worried about ('Does this feel on-brand given what we agreed in the brief?'). Specific questions get specific answers. 'What do you think?' gets 'Can you make it pop?'

Step 2

Give them a 48-hour window for written feedback — before any call

Most designers schedule the review call first, then share the design. Reverse it. Send the link 48 hours before the call with a deadline: 'Please leave your notes before Thursday noon — I'll read everything before we meet.' Clients who annotate before the call come to the meeting with specific notes already pinned to the design, not half-formed impressions they're trying to articulate on the spot. The call becomes a resolution session, not a discovery session. 48 hours is long enough for a considered read; beyond that, notes accumulate without real thinking behind them.

Step 3

Ask for notes anchored to the element — not email summaries

The pattern that creates 'the bit near the top' feedback: the client can't point at the actual element, so they describe it. Descriptions are imprecise. When a client clicks the exact headline and types 'too long — audience won't read this on mobile,' you know what to fix and why, without an extra exchange. If you're running the review async (common for freelancers with clients in different time zones), anchored notes replace the entire discovery phase of the call. One note per element, pinned to the spot, is more actionable than a three-paragraph email summarising the whole design.

Step 4

On the call: resolve, don't re-present

When you've seen the feedback before the call, the agenda writes itself: go through each open note, confirm the fix or explain the constraint, and mark it done. Keep the call under 30 minutes by skipping anything both parties already agree on — only surface the notes that need discussion or a decision. At the end, close with two explicit outputs: a list of approved elements ('header layout, colour palette — locked') and a list of changes with who owns each one ('hero copy — I'll revise by Friday'). Leaving the call with 'I'll make a few tweaks' is how you end up at round four.

The faster way

If the design is a Figma export, a live preview, or a PDF — drop it into Drafty and share the link. Your client opens it in any browser, clicks the exact element they mean, and leaves an anchored note. No Figma account, no extension, no screenshots emailed back. Every note lands in one thread, pinned to the spot they pointed at. When you push a revised version, the same link updates — one URL through every round.

Open a live demo

Questions

How many rounds should a design review take?: One or two rounds is the target. Email-based review adds rounds because clients describe feedback rather than point at it — resolving 'the section near the top' takes at least one extra exchange before you know what to fix. Anchored annotation (where a client clicks the exact element) plus a pre-call written-notes window typically gets a design to approval in one or two rounds instead of three or four.
How do I get more specific feedback from my client?: Give them a way to point at the exact element rather than describe it. Specific feedback comes from specific pointing — when a client can click the headline and type a note tied right there, the note is about the headline. When they're writing an email, they're translating a visual reaction into words, and something gets lost. Also helps: send two specific questions with the design link. 'What do you think?' gets impressions. 'Does the hierarchy make the offer immediately clear?' gets answers.
Should I present the design on a call or let the client review it async?: Both, in sequence. Share the link for async notes first (48-hour window), then use the call only to resolve what needs discussion. Presenting a design live for the first time on a call puts the client in a reaction mode — they respond to what you're talking about, not to the design itself. Clients who've already read and annotated come to the call knowing what they want to discuss; the meeting is shorter and the feedback is more considered.
What should I tell my client to look for in the design review?: Keep it to three things: whether the design matches the goal you agreed on (does the hierarchy push the right action?), whether it fits the brand (in feeling, not just in colour), and whether there's anything that would stop their audience from acting. Avoid open-ended prompts like 'let me know your thoughts' — they invite impressionistic feedback. Two focused questions produce more actionable notes than a general invitation to react.
How long should a design review meeting take?: 30 minutes if the client has reviewed the design in advance and left written notes. 60 minutes if you're presenting it for the first time on the call. The 30-minute version is only possible when feedback is already anchored to specific elements before the meeting — the call is resolution, not discovery. If you're regularly running 90-minute review meetings, the bottleneck is usually that the client is seeing the design for the first time and reacting in real time.
How do I share a design with a client who doesn't have Figma?: Export it as a PNG or PDF and share it as an annotated review link — not a raw Figma share. A Figma view link prompts the client to log in or request access; most fall back to email. A browser-openable link with anchored commenting removes that wall entirely.

Keep exploring

How to review a design Design feedback tool BugHerd alternative

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