TweakTick
FeaturesFormatsIntegrationsBlog
PricingFoundingFree toolsSign inStart free
  1. Home
  2. /
  3. Free tools
  4. /
  5. Design feedback examples

Copy & feedback

Design feedback examples, from clients and to clients

Runs in your browser. Nothing is uploaded.Last updated 7 Nov 2026

Show
Topic

28 examples

  • Layout · From the client

    The page feels flat

    Vague: “Can you make it pop more?”

    Clear: “The “Book a table” button gets lost next to the photo. Can it stand out more, so it is the first thing people see?”

    Names the element and the goal (be seen first), so the designer can choose how instead of guessing what “pop” means.

  • Layout · From the client

    Too much on one screen

    Vague: “It feels too busy.”

    Clear: “The home page has three offers above the fold. Our main one is the free trial; the other two can move lower down.”

    Gives the priority order, which is the real decision the designer needs from the client.

  • Layout · From the client

    Something is in the wrong place

    Vague: “I don’t like where the reviews are.”

    Clear: “Please move the reviews section above the price table. Most buyers ask us about reviews before price.”

    Says where it should go and why. The reason helps the designer handle other pages the same way.

  • Colour · From the client

    A colour feels wrong

    Vague: “The colours are off.”

    Clear: “The green on the buttons looks lighter than our brand green. Please use the green from our brand guide (page 4).”

    Points to one colour, one place and the source of the right value.

  • Colour · From the client

    The mood is wrong

    Vague: “It’s too dark and gloomy.”

    Clear: “The dark grey background makes the site feel serious. We want it to feel friendly. Could we try a light background with the grey only in the footer?”

    Describes the feeling it should have and offers a direction, while leaving the final choice to the designer.

  • Type · From the client

    The font does not feel right

    Vague: “Can the font be more modern?”

    Clear: “The headline font feels old-fashioned to us. We like the simpler, rounder letters on the menu sample we sent. Can the headlines move closer to that?”

    Says which text, what it feels like now, and gives a reference to aim at.

  • Type · From the client

    Text is hard to read

    Vague: “I can’t read this.”

    Clear: “On my phone the grey text under each price is too small and too light to read. Can it be larger or darker?”

    Names the device, the exact text and the two problems (size and contrast).

  • Copy · From the client

    A sentence is not right

    Vague: “The wording isn’t us.”

    Clear: “In the About section, please change “We leverage synergies” to “We help small shops sell online”. We never use business jargon.”

    Gives the exact replacement text and the rule behind it, so the same fix spreads to other pages.

  • Copy · From the client

    A spelling mistake

    Vague: “There are some typos.”

    Clear: “Page 2, second paragraph: “anual” should be “annual”. Page 5 caption: “recieve” should be “receive”.”

    Every typo has a location and the correct spelling. Nobody has to hunt for it.

  • Images · From the client

    A photo feels generic

    Vague: “The photos look like stock.”

    Clear: “The team photo on the home page looks like stock. Please use our own photos from the shared folder, ideally the one of the shop front.”

    Says which photo, the issue, and which replacement is preferred.

  • Images · From the client

    A crop cuts something off

    Vague: “The picture is weird.”

    Clear: “The chef’s head is cut off in the banner photo on tablets. Can the crop keep his face in view on every screen size?”

    Explains what is cut off and on which screen, which is often the part the designer cannot see.

  • Brand · From the client

    The logo feels too small

    Vague: “Make the logo bigger.”

    Clear: “In the desktop header the logo looks small next to the menu. Can it be a little larger there? On phones it is fine as it is.”

    Separates desktop from phone, which avoids the common back-and-forth of a logo growing everywhere.

  • Brand · From the client

    It does not feel like the brand

    Vague: “This doesn’t feel like our brand.”

    Clear: “The rounded icons feel playful, but our brand is calm and precise. Can the icons use straight lines like the ones in our brochure?”

    Names the gap between what it is and what the brand is, and points to an example that is on brand.

  • Process · From the client

    Praise that helps the next round

    Vague: “Looks great!”

    Clear: “The checkout page is exactly right: short, clear and the total is easy to find. Please keep that style for the account pages.”

    Positive feedback that says what to keep is as useful as a change request. It stops good parts being changed later.

  • Process · From the client

    Something feels wrong but you cannot say what

    Vague: “I’m not sure about it.”

    Clear: “Something about the pricing page does not feel right and I cannot say what. Could we look at it together for 15 minutes before you change anything?”

    Honest, and it asks for a short call instead of starting a round of guesswork changes.

  • Process · From the client

    Several people have opinions

    Vague: “Here are everyone’s thoughts (forwarding five emails).”

    Clear: “I collected the team’s notes into this one list. Where people disagreed, I chose: keep the blue header. These are our final comments for round 2.”

    One consolidated list with conflicts already settled is the fastest way to a good next round.

  • Process · To the client

    Confirming what you heard

    Vague: “Got it, will do!”

    Clear: “Thanks. Here is what I will change in round 3: 1) larger logo on desktop only, 2) brand green on the buttons, 3) reviews above prices. Reply if I missed anything; I will send round 3 on Thursday.”

    A numbered summary catches misunderstandings before the work is done, not after.

  • Layout · To the client

    The feedback is vague

    Vague: “What do you mean by “pop”?”

    Clear: “Happy to make it stand out more. Is it the headline, the button or the photo that feels flat? If you can point to one part, I will try two options for it.”

    Asks a narrow question with choices, which is easier to answer than an open “what do you mean?”.

  • Type · To the client

    A request would hurt the result

    Vague: “That won’t work.”

    Clear: “I can make all the text bold, but then nothing stands out, including the prices. Could we make the prices bold and keep the rest as it is? I have mocked up both so you can compare.”

    Agrees with the goal, explains the cost in the client’s terms, and shows an alternative instead of a flat no.

  • Brand · To the client

    Two people on the client side disagree

    Vague: “Your team can’t agree, so I’ll wait.”

    Clear: “Maria asked for a bigger logo and Tom asked for a smaller one on phones. Which should I follow? If it helps, I can do bigger on desktop and keep phones as they are.”

    Names both requests neutrally, asks the approver to choose, and offers a way to satisfy both.

  • Process · To the client

    A request is outside the agreed scope

    Vague: “That’s not included.”

    Clear: “A blog section is a great idea. It is not part of the current scope, so I will send a short quote for it today. The rest of your round 2 notes are all in hand.”

    Says yes to the idea, separates it from the current round, and keeps the price conversation calm.

  • Process · To the client

    Reminding about the rounds left

    Vague: “This is your last round.”

    Clear: “This is round 2 of the 3 included, so there is one more round after this. It helps to send every comment from your team together this time.”

    States the count without sounding like a warning, and asks for the behaviour that makes rounds count.

  • Colour · To the client

    Explaining a design choice

    Vague: “Trust me, it’s better this way.”

    Clear: “I used the darker green on the buttons because the lighter one is hard to read with white text, especially on phones. If you prefer the lighter green, I can use it with dark text instead.”

    Gives the reason in plain words and still leaves the client a real choice.

  • Copy · To the client

    Waiting on the client’s text

    Vague: “Still waiting on your copy.”

    Clear: “The design is ready for your text. Could you send the About and Services wording by Tuesday? Until then I will use placeholder text marked in yellow so nothing goes live by mistake.”

    Names what is missing, gives a date, and explains how the gap is handled meanwhile.

  • Images · To the client

    A requested image cannot be used

    Vague: “We can’t use that photo.”

    Clear: “The photo you linked belongs to another company, so we cannot use it. I have picked three similar photos we are allowed to use; tell me which one you prefer.”

    Explains the reason and arrives with options, so the client can decide in one reply.

  • Process · To the client

    Asking for a clear approval

    Vague: “So are we good?”

    Clear: “All round 3 changes are done. If you are happy, please reply “approved” and I will prepare the final files. Anything after approval will be a new request.”

    Makes the yes easy, says what happens next and what approval covers.

  • Layout · To the client

    Offering options instead of one answer

    Vague: “Here’s the new version.”

    Clear: “For the pricing page I made two layouts: A keeps three plans side by side, B shows one plan with a switch. A is easier to compare; B is calmer on phones. Which fits your customers better?”

    Two labelled options with one honest trade-off each lead to a faster decision than one take-it-or-leave-it version.

  • Brand · To the client

    A change would break the brand guide

    Vague: “That’s off-brand.”

    Clear: “Your brand guide keeps the logo on white or navy only. A photo behind it would break that rule. Would a navy band behind the logo give you the look you want?”

    Points to the client’s own rule, not your taste, and offers a version that respects it.

Got a long thread of feedback already? Pull it into one list with the feedback consolidator.

Next, send your design as a TweakTick review link, so clients pin each comment where it belongs and every round gives you one list.

Get feedback on the spot – free

What next in TweakTick

  1. 1Sign up, then paste the page address or upload the draft.
  2. 2The client comments next to the exact words they mean, one pin per point.
  3. 3Every round is counted, and the final wording is approved with a code sent to their email.
Get feedback on the spot – free

What makes design feedback examples clear

A design feedback example shows the same comment written two ways, vague and clear: for example, “Can you make it pop more?” becomes “The Book a table button gets lost next to the photo; can it stand out more, so it is the first thing people see?”, which tells the designer what to change and why.

Most review rounds that go wrong start with a comment that sounded clear to the person who wrote it. The examples here come in two sets. The first is feedback from clients, which you can share as a short guide before the first round. The second is what you write back to a client: confirming, asking, pushing back and asking for approval. Filter by topic or search for a word, then copy what you need.

Location
Where the comment applies: the page, the section, the element, and the screen size if it matters. “The logo in the desktop header” is a location; “the logo” is not, because it might mean every page, every size and every file.
Problem before fix
Saying what is wrong, or how something should feel, before suggesting a solution. “The prices are hard to find” lets the designer pick the best fix. “Make the prices red” locks in one fix that may not solve it.
Reason
A short “because” after the request: “because most buyers ask about reviews first”. A reason lets the designer apply the same rule elsewhere, and it makes push-back easier to discuss.
Keep list
Praise that names what is working, such as “the checkout page is exactly right, keep that style”. It protects the good parts from being changed in a later round.
One voice
All comments from the client’s side sent together by one person, with disagreements already settled. It is the single biggest thing a client can do to cut the number of rounds.
Confirming reply
Your numbered summary of what you will change, sent before you start. It turns a loose email into a list both sides agreed to, and catches misunderstandings early.

Design feedback examples, vague and clear

These rows come from the same library as the filter above. Each one shows a comment that is common in client reviews, and a clearer version that says where, what and why. The client-side rows are written in the client’s voice; the reply rows are yours. The clear versions are longer, but they save a whole round of guessing.

SituationDirectionVague versionClearer version
The page feels flatFrom the clientCan you make it pop more?The “Book a table” button gets lost next to the photo. Can it stand out more, so it is the first thing people see?
A colour feels wrongFrom the clientThe colours are off.The green on the buttons looks lighter than our brand green. Please use the green from our brand guide (page 4).
The logo feels too smallFrom the clientMake the logo bigger.In the desktop header the logo looks small next to the menu. Can it be a little larger there? On phones it is fine as it is.
Praise that helps the next roundFrom the clientLooks great!The checkout page is exactly right: short, clear and the total is easy to find. Please keep that style for the account pages.
Two people on the client side disagreeTo the clientYour team can’t agree, so I’ll wait.Maria asked for a bigger logo and Tom asked for a smaller one on phones. Which should I follow? If it helps, I can do bigger on desktop and keep phones as they are.
A request is outside the agreed scopeTo the clientThat’s not included.A blog section is a great idea. It is not part of the current scope, so I will send a short quote for it today. The rest of your round 2 notes are all in hand.
Asking for a clear approvalTo the clientSo are we good?All round 3 changes are done. If you are happy, please reply “approved” and I will prepare the final files. Anything after approval will be a new request.

Swipe to see all columns →

Using these design feedback examples well

Adapt the design feedback examples to your own project

The clear versions use made-up details, such as a “Book a table” button or a brand guide on page 4. Swap in your own pages, elements and dates. A guide that mentions a café when your client sells software will feel pasted.

Share the client guide before the first round, not after a bad one

Sent at kickoff, a short feedback guide reads as helpful. Sent after a vague round, it can read as a telling-off. Send it with the first review link and keep it to a handful of examples.

Clear feedback does not replace a review process

Even well-written comments get lost when they arrive across email, chat and calls. Agree on one place for feedback, a deadline for each round and one person who approves.

Push-back still needs the client’s decision

The reply examples explain trade-offs, but the client owns the final choice on their project. If they still want the bolder version after hearing why not, do it, note the decision, and move on.

Questions about design feedback examples

How do I give design feedback to a client without sounding rude?+

Agree with the goal first, then explain the trade-off in their terms, then offer an option. “I can make all the text bold, but then the prices stop standing out. Could we make just the prices bold?” is firm without being a no.

Can I send these design feedback examples to my client?+

Yes. Filter to “Feedback from clients”, pick the topics that fit the project, and use Copy as a client guide. It writes a short note with three habits and the examples shown, ready to paste into your kickoff email.

What should I do when client feedback is too vague to act on?+

Ask a narrow question with choices instead of “what do you mean?”. For example: “Is it the headline, the button or the photo that feels flat?” A choice is easier to answer, and it gets you to a real request in one reply.

How should I reply when two people on the client side disagree?+

Name both requests neutrally, ask the person who approves the work to choose, and offer a version that might satisfy both. Do not pick a side yourself; you will end up redoing the work when the other person sees it.

Is positive feedback worth asking clients for?+

Yes. Praise that says what to keep, such as “the checkout page is exactly right”, stops good parts from being changed in a later round. Ask for it directly: “Which parts should stay exactly as they are?”

How do design feedback examples help with scope creep?+

The reply set includes how to say a request is outside the agreed scope while still welcoming the idea. Separating it from the current round, and offering a quote, keeps the round moving and the price conversation calm.

On this page

What makes design feedback examples clearDesign feedback examples, vague and clearUsing these design feedback examples wellQuestions about design feedback examples

Related free tools

  • Feedback consolidatorEmails, notes and chats in; one numbered to-do list out.
  • Approval email templatesThe four emails every review round needs.
  • Design brief generatorThe baseline that decides “revision or new scope?”.
  • Diff checkerCopy V1 vs V2, word by word and line by line.
  • Client feedback formA short survey on the result, the rounds and the value.

All free tools · See how TweakTick does this

Clients pin feedback on the real work, and approve each round with a code.

TweakTick counts the rounds and keeps a sign-off record you can prove.

Get feedback on the spot – free
TweakTick

Every tweak. Every tick.

Product

  • What’s new
  • All features
  • All formats
  • PDF proofing
  • Video review
  • Design feedback
  • Client approvals
  • Integrations
  • Support
  • What’s not supported yet

Resources

  • Blog
  • Help
  • Free tools
  • Compare
  • About

Free tools

  • Scope creep calculator
  • Change request form
  • Revision clause generator
  • Kill fee calculator
  • Freelance rate calculator
  • Sign-off form generator
  • Compare images
  • Screenshot annotator
  • PDF annotator
  • Approval email templates

Compare

  • TweakTick vs BugSmash
  • TweakTick vs MarkUp.io
  • TweakTick vs Pastel
  • TweakTick vs ruttl
  • TweakTick vs BugHerd
  • All comparisons

Legal

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement
  • Sub-processors
  • Refund Policy
  • Your privacy choices
  • Security

Secure checkout by Paddle

  • AMEX
  • GDPR READY: read our data processing agreement
  • CCPA READY: read the California section of our privacy policy
  • SOC 2 READY: read how our controls follow the SOC 2 Security criteria

© 2026 TweakTick

Photo credits