Client revision request examples that get you clear answers

You open a Figma file and the client has left a single comment: “Make it pop.” You laugh, but not out loud. You know how many rounds of guesswork that'll take. If you want fewer ambiguous emails, you need better client revision request examples — phrasing they can actually copy and send.

This post gives you templates clients can use (and examples you can paste into an email or a ClientMarkup link). Use them as-is or tweak for tone. Each template says what to attach, what to expect, and the acceptance criteria so you and the designer stop playing phone tag.

client revision request examples you can copy

Before the templates: two quick rules that change everything.

• Point at the thing. Frame name, screenshot with a pin, or a link to a comment in Figma. Don’t say "the header" unless you name the artboard.
• Say exactly what you want changed and why. If it’s to match brand, include the hex code or the brand doc.

Bad: “Change the blue — make it pop.”

>

Better: “Change primary button color to #4F6EF7 (brand swatch). Use white text, keep 16px padding. Goal: increase CTA contrast to meet AA accessibility.”

1) Quick tweak (1–2 small changes)

Use when: color swap, copy edit, spacing tweak.

What to attach: screenshot with annotated pin or a direct Figma comment on the component.

Template:

Hi — small tweaks:

1) Change primary button color to #4F6EF7; keep white text. 2) On the hero, update headline from “Grow fast” to “Grow smarter” (see attached screenshot pin).

Please implement and push a new version by EOD Wednesday. Accept when the buttons pass AA contrast and the headline reads exactly as above.

Why it works: Two items, exact values, deadline, acceptance criteria.

2) Copy change across multiple screens

Use when: label/CTA/copy needs consistent edits across many pages (signup flows, pricing, etc.).

What to attach: spreadsheet or list of frames + Figma link.

Template:

Hi — update copy across all signup screens:

• Change CTA from “Start free” to “Create account” on frames: Signup_v1, Signup_v2, Pricing_Signup.
• Update microcopy under email field to: “We’ll never share your email.”

Attached: a CSV with frame names. Please confirm when you’ve updated all instances. Mark as done when all frames show the new CTA text.

Why it works: You avoid scattered messages and ensure consistency.

3) Layout restructure (moves beyond a tweak)

Use when: you want a new grid, different hierarchy, or a mobile-first rework.

What to attach: annotated PDF or Figma prototype with examples and at least one inspirational link.

Template:

We want a layout restructure for the product detail page to improve scannability. Goals:

• Move the buy box to the right column on desktop (see mockup attached).
• Collapse specs under an accordion on mobile.
• Keep the existing color palette and fonts.

Priority: medium. Please provide two layout options by next Tuesday. I’ll choose one and expect one round of refinement. Done when the chosen option is implemented across desktop and mobile breakpoints.

Why it works: It sets expectations for deliverables (two options) and rounds.

4) Urgent visual bug or legal copy change

Use when: something is broken or legally required and needs a fast patch.

What to attach: screenshot and severity (blocker / high / medium).

Template:

Urgent: The footer legal link is missing on all pages (see screenshot). This is a blocker. Please restore the footer link and push a hotfix within 4 hours. Confirm completion with a screenshot of the live page.

Why it works: Short, urgent, and requires confirmation.

5) Scope change or new request (billable)

Use when: the ask is beyond original scope.

What to attach: a short brief and why it’s new.

Template:

Request: Add a knowledge base section with 6 article templates to the marketing site. This wasn’t in the original scope. Please estimate time and cost for: wireframe, UI, and content templates. Don’t start until I approve the estimate.

Why it works: It prevents surprise work and keeps approvals documented.

6) Final approval with minor edits

Use when: you've gone through rounds and want to sign-off.

What to attach: the final artboard and a ClientMarkup link if you want a typed signature.

Template:

Looks good overall. Two minor edits: change testimonial copy on the homepage (see pin) and reduce hero image crop by 10% on the left. If those are done, I approve the design. Please send final assets and a signed handoff PDF.

Why it works: It’s binary — either done or you get the two tiny things fixed.

Quick anti-templates: what not to write

• “Looks off.” — No.
• “Make it better.” — No.
• “Can you follow brand?” — OK if you link the brand pack and list the exact deviations.

If a client can’t describe what they want, give them two annotated options and ask them to pick. It removes the burden of description.

Tools and workflow notes

• Figma comments work if both of you are in the file and name frames consistently. Use frame names like ProductPage_v3 to avoid ambiguity.
• PDFs can get messy — use annotated pages with numbered pins and a short list in the email.
• If you want clients to record their screen and draw on the design, use ClientMarkup. Clients open a link with no account, pin/draw annotations, screen-record feedback, and approve with a typed signature. It’s great when clients prefer visual explanation.

Give these templates to clients. Paste them into an email or your agency intake form. Stop decoding vague requests. Your next round should be the one that actually ships.