How to get feedback on a style guide
To get useful feedback on a style guide, send clients a structured review — not the raw PDF. Break it into sections (color, type, imagery) and ask one specific question per section. Give reviewers a way to point at the exact element they're reacting to rather than describe it in words. Email attachments create version chaos; a shared link with anchored comments keeps every note in context.
Break the guide into reviewable sections
A full brand style guide can run 20–40 pages. If you send it as one PDF and ask 'what do you think?', you'll get silence or a call. Break the review into logical sections — color palette, typography, logo usage, imagery, tone of voice — and send each one separately. Most clients engage with a focused 5-page color review; very few will sit down with a 40-page document unprompted.
Ask one specific question per section
Vague questions produce vague feedback. 'Does this feel on-brand?' is unanswerable for most clients. Swap it for questions tied to the brief: 'Does this primary blue read as trustworthy to your target customer?' or 'Could your team use these font pairings without asking a designer?' One question per section — more than that and clients skip all of them.
Give reviewers a way to point, not describe
The single biggest source of bad style guide feedback is clients who can't describe what they mean spatially. 'The blue on page 4' could mean the swatch, the headline, or the border. When reviewers can click the exact element and pin a note to it, the feedback gets useful fast. Share a link they can annotate in the browser, not a file they'll mark up in Preview and re-email — every note on the same artifact, no version confusion.
Set a deadline and a round limit
Style guide reviews drift without a deadline. Give clients a specific date — five to ten business days is standard. Make clear this is round one of two, so they consolidate feedback rather than trickling it in. One reminder two days before the deadline; more than that trains them that the deadline is soft. A stakeholder who misses the round waits for round two.
Distinguish direction changes from clarifications
Sort incoming feedback before you act: notes that clarify what you built (a hex code that's slightly off, a typo in a font name) versus notes that change direction. Fix the first quietly. The second is out-of-scope work — put it in writing before you open the file to revise, not after you've done the work and need to explain the invoice.
If your client is the one reviewing — not you making edits yourself — drop the style guide export (PDF, PNG spreads, or a Figma share link screenshot) into Drafty and share the URL. Your client clicks the exact swatch, typeface, or layout section they're reacting to and pins a note right there. No email attachment, no 'the blue on page 4.' Every comment lands anchored to the element they meant, in one thread you can reply to and resolve. When you push a revised version, it lives on the same link — no re-emailing the file.
Open a live demoQuestions
- How do I ask a client to review a style guide?
- Send the guide with a specific question per section rather than an open-ended 'what do you think?' Frame questions around the brief's goals — for example, 'Does this type pairing feel appropriate for a B2B audience?' Give a deadline of five to ten business days and specify how many rounds of revisions are included.
- How do you get client approval on brand guidelines?
- Share a link they can annotate directly, not just a PDF attachment. Ask for section-by-section sign-off rather than a single all-or-nothing approval. Document each sign-off in writing so the scope of future changes is clear.
- What format should I send a style guide for client feedback?
- A shareable link beats an email attachment every time. PDFs get downloaded, renamed, and re-emailed back as 'Style Guide FINAL v3 John edits.pdf.' A shared link keeps all feedback on one artifact, prevents version confusion, and lets you push revisions without re-sending the file.
- How many rounds of revisions are normal for a style guide?
- Two structured rounds is standard for most freelance brand projects. Round one captures big directional changes (a color that's wrong, a typeface that doesn't fit); round two addresses refinements. Anything beyond that is typically billed as additional work. State this in your contract before the first review goes out.
- Why do clients give vague feedback on style guides?
- Usually because they can't point at what they mean. 'Make it feel more premium' is the only language available when you can't click the specific element. Giving clients a way to pin a comment directly to a color swatch or typographic example produces more actionable notes than asking for written feedback on a static PDF.
- How do I get a client to actually look at the style guide?
- Make the review feel small. Send one section at a time, ask one specific question, and set a clear deadline. Sending a 40-page PDF with 'let me know what you think' is a request most clients quietly defer. A focused five-page color review with a single question gets a response.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.