How do I get a client to actually approve creative work instead of just saying "looks good"?

Ask for a written reply to a specific version — not a verbal yes on a call. Once all changes are in, send: "Here's the current version — please confirm you're happy to proceed." A reply to that message, about that version, is your sign-off.

How do I avoid endless revision rounds?

Two things cause most loops: vague feedback and acting on it without clarifying. Convert every comment to change, question, or decline before touching the file. "Make it pop more" needs a clarifying question, not a redesign. Present the work alongside the brief so clients evaluate rather than react.

What should I send a client to approve creative work?

A link to the current version (not a file), a one-paragraph context note, one or two targeted questions for this round, and a clear ask for written confirmation. A link keeps feedback on one artifact; a file spawns competing versions the moment they save it.

Do I need a contract clause for creative approval?

At minimum: define what counts as approval (written confirmation), how many revision rounds are included, and what happens after sign-off. For day-to-day review, a reply to an email or comment thread is sufficient — you don't need a formal form every round.

How do I handle a client who changes their mind after approving?

Point them to the approval record — the email or thread where they confirmed that version — and treat the new request as a change order. That written record is what makes the conversation straightforward rather than contested.

How do I avoid contradictory feedback from multiple stakeholders?

Ask the client to nominate one person to consolidate internal notes. Two stakeholders with conflicting views is an authority problem on their side — acting on both wastes a round. Ask which notes are decisions and which are optional before you start.

drafty

How to approve creative with clients

Quick answer

To get a client to approve creative work: present the piece with the brief beside it, ask one targeted question per round rather than "what do you think?", collect feedback pinned to the exact element, resolve each note explicitly, then ask for written confirmation on the final version — not a verbal yes on a call. A vague "looks good" isn't sign-off; a reply to a specific version is.

Step 1

Present the work alongside the brief — not just the file

Send the deliverable with a short context note: what the brief asked for, any constraints, and the one decision you most want their input on. Clients who see a design cold anchor on whatever catches their eye; clients who read the goal first evaluate against it. "The brief called for a trust-first tone aimed at first-time buyers, so I led with social proof. What I'd most like your read on is whether the hero headline lands for that audience." One focused question beats "let us know your thoughts."

Step 2

Collect feedback pinned to the exact spot

The version-file trap: the client downloads the PDF, marks it up in Preview, re-saves it with their initials, and emails it back. Now you have a disconnected file with comments that aren't tied to the live version. Share a link instead — they click the exact element and leave a pinned comment there. "The font on the CTA" is now a pin, not a sentence to decode. Feedback lands on the shared artifact, not in a parallel thread.

Step 3

Resolve every note explicitly before opening the file

Sort every comment into three buckets: change, question, or decline. Reply to each one before touching the design. Acting on "make it more premium" without asking what that means in context is the most common way to burn a revision round. Mark each comment resolved once the change is in — a thread of resolved notes is a checklist both parties can read, and it documents that you addressed everything.

Step 4

Push the revision on the same link

Update the same URL rather than sending a new attachment. The client opens the link they bookmarked and sees the current version — no searching through email for which file has which edits. If your tool shows version history, they can compare v2 and v3 side by side to confirm their change is in. Without that, clients re-raise notes they think weren't actioned — because they found the wrong file.

Step 5

Ask for written confirmation — not a verbal yes

Once all notes are resolved, send one final message: "All changes from round 2 are in — here's the current version. Please confirm you're happy to proceed." A reply to that message, about that version, is your written sign-off. A verbal "looks fine" on a call is not. If the client later says "I thought we changed the logo," the thread shows the logo was approved unchanged. Keep the confirmation — it's the record of what was agreed and when.

The faster way

The email-attachment trap — client re-saves the file with their initials, now you have three versions floating around — disappears if you share a Drafty link instead. They click the exact element they mean, leave a pinned comment, and you see every note in one thread. Push a revision on the same link; the history stays. No more "v3 FINAL (2) Sarah edits.pdf". No account needed. Works on mockups, PDFs, design docs, or any URL.

Open a live demo

Questions

How do I get a client to actually approve creative work instead of just saying "looks good"?: Ask for a written reply to a specific version — not a verbal yes on a call. Once all changes are in, send: "Here's the current version — please confirm you're happy to proceed." A reply to that message, about that version, is your sign-off.
How do I avoid endless revision rounds?: Two things cause most loops: vague feedback and acting on it without clarifying. Convert every comment to change, question, or decline before touching the file. "Make it pop more" needs a clarifying question, not a redesign. Present the work alongside the brief so clients evaluate rather than react.
What should I send a client to approve creative work?: A link to the current version (not a file), a one-paragraph context note, one or two targeted questions for this round, and a clear ask for written confirmation. A link keeps feedback on one artifact; a file spawns competing versions the moment they save it.
Do I need a contract clause for creative approval?: At minimum: define what counts as approval (written confirmation), how many revision rounds are included, and what happens after sign-off. For day-to-day review, a reply to an email or comment thread is sufficient — you don't need a formal form every round.
How do I handle a client who changes their mind after approving?: Point them to the approval record — the email or thread where they confirmed that version — and treat the new request as a change order. That written record is what makes the conversation straightforward rather than contested.
How do I avoid contradictory feedback from multiple stakeholders?: Ask the client to nominate one person to consolidate internal notes. Two stakeholders with conflicting views is an authority problem on their side — acting on both wastes a round. Ask which notes are decisions and which are optional before you start.

Keep exploring

How to collect client feedback Client feedback tool Design feedback tool

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