Key Takeaways
- Useful feedback identifies the exact element, explains the concern, and describes the desired result.
- Keep comments in one shared place and identify the current design version in every review request.
- Choose a client decision owner to consolidate conflicting stakeholder requests.
- Agree on review scope, priorities, and deadlines before the first round.
- Check revisions against the requests and ask for explicit approval of the identified version.

A client says, “Make it pop.” Another stakeholder asks you to shorten the page while a third wants more detail. Then someone sends notes on a version you replaced last week.
These client feedback problems do more than make a project frustrating. They leave the designer guessing what to change and the agency uncertain about when the review is finished. A visual feedback tool can help organize the work, but it cannot replace clear instructions and an agreed decision process.
Here are ten common problems creative teams and agencies encounter, with a practical fix and wording you can adapt for your next client review.
1. Vague Feedback That Gives the Designer Nothing to Fix
“Make it pop” and “something feels off” describe a reaction, but they do not identify a problem. The designer has to guess whether the concern is the layout, copy, imagery, or visual hierarchy. A revision based on that guess can create another round of equally vague feedback.
The Fix
Ask the reviewer to name the exact element, explain the concern, and describe the result they want. They do not need to prescribe the design solution. A business goal gives the designer a useful starting point.
What to Say
““The headline blends into the supporting copy. Please make the main message easier to notice when someone first opens the page.””
If the client cannot explain the concern, offer a focused question: “Is the issue that the offer is unclear, or that the page feels too busy?” Clarify the request before revising.
For a reusable comment structure, see our guide to giving design feedback your team can actually use.
2. Comments Scattered Across Email, Chat, and Screenshots
One stakeholder emails a paragraph, another sends a chat message, and a third annotates an old screenshot. Now someone has to collect the notes, match them to the work, and check that nothing was missed. The longer the review runs, the easier it is to lose the original context.
The Fix
Agree on one place for design feedback. Keep each comment attached to the relevant area of the work, and move requests from other channels into that shared record. Use email or chat to coordinate timing rather than maintain competing change lists.
What to Say
““Please add design changes to the shared review so we can track each request against the current version. We’ll use this email thread for scheduling.””
Jottrly supports numbered pins, annotations, and per-mark comment threads. Those features help keep the location and discussion together; the team still needs to agree to use that shared process.

3. Stakeholders Asking for Opposite Changes
The marketing manager wants a shorter page. The sales manager wants three more sections. Both requests may have a reasonable purpose, but implementing them without a decision can leave the designer working in circles.
The Fix
Name one client decision owner who consolidates stakeholder input. Describe the tradeoff against the brief and ask for one agreed direction before making the change. This is a project responsibility you agree with the client, regardless of the software you use.
What to Say
““A shorter page will make the main offer quicker to scan. Adding all three sections will give more detail but extend the page. Which outcome matters most for this audience?””
Record the chosen direction with the feedback. That gives the next reviewer a clear reason for the design decision instead of reopening the same debate.
Our client design approval process explains how to set responsibilities and carry those decisions through to handoff.
4. Personal Preferences Replacing the Project Goal
“I don’t like orange” may be a sincere reaction, but it does not establish that a design fails. Reviews become difficult when every stakeholder treats their own taste as the deciding standard.
The Fix
Return to the agreed audience, brand requirements, and intended action. Separate a required brand correction from a personal preference. Where the outcome is uncertain, identify what evidence would help rather than claiming a design choice is automatically better.
What to Say
““Our brand guidelines require navy for primary navigation. Please update that area. The orange accent elsewhere is a preference question, so let’s assess it against the campaign brief.””
A useful reviewer can dislike a visual choice and still recognize that it serves the brief. Give the team a shared standard before discussing individual opinions.
5. Feedback on an Outdated Design Version
A client opens last week’s attachment and requests a change that the designer has already made. Another reviewer comments on the latest file. The team cannot reliably close the round until it knows which version each person assessed.
The Fix
Identify one current version in every review request. Use descriptive names and a short change summary. Keep older versions for reference, but clearly tell reviewers which one needs feedback now.
What to Say
““Please review homepage version 3, uploaded October 9. The headline and contact section have changed. Earlier versions are reference material for this round.””
Jottrly’s version history helps keep revisions together. Pair that history with clear instructions so reviewers do not mistake an earlier file for the current decision.
Give Client Feedback a Clear Home
Bring annotations, discussions, and design versions into one review workflow. Explore Jottrly’s pricing page to see the plans currently presented.
Explore Jottrly Pricing6. A Change List With No Priorities
A broken contact detail and a minor spacing suggestion arrive in the same list. If everything is presented as equally urgent, the designer may spend time polishing a detail while an essential correction remains unresolved.
The Fix
Label requests by their effect on the agreed goal. Use plain categories such as required correction, improvement, and optional suggestion. Resolve conflicting priorities with the decision owner before the next round starts.
What to Say
““Required: correct the phone number before handoff. Improvement: make the service headings easier to scan. Optional: try a slightly tighter image crop if time allows.””
These categories can be written directly into a comment. They do not require a dedicated priority feature. The important part is that the whole team understands what must be checked before approval.
7. New Stakeholders Joining After the Review Is Nearly Finished
The design has been revised twice when a previously uninvolved stakeholder requests a new direction. That may reveal a real requirement, but it also means the original review group was incomplete.
The Fix
Ask who needs to contribute before the first review and who has final approval authority. Agree on a feedback window. If a new stakeholder joins later, assess their request against the brief and explain its effect on scope and timing.
What to Say
““This request changes the approved page structure. We can include it, but we need to agree on the additional work and a revised handoff date before starting.””
Avoid dismissing late input automatically. A factual error still needs attention. Distinguish a necessary correction from a new creative direction so the response fits the actual request.

8. Revision Requests That Quietly Expand the Scope
A homepage review turns into a request for an additional landing page, a different brand direction, and new copy across the site. Calling every request a revision hides the difference between improving agreed work and adding new work.
The Fix
Define the deliverables and review boundaries before sharing a design. When a request falls outside them, describe the additional task and agree on cost, timing, or a replacement priority. Follow your project agreement rather than inventing a universal rule about revision limits.
What to Say
““The current round covers the homepage layout. A new campaign page is an additional deliverable. We can estimate that separately or discuss which existing task it would replace.””
Keep the original feedback and the new request visible. A clear record makes the conversation about specific work instead of whether the client is being difficult.
9. Closing Comments Before Checking the Revised Work
The designer marks a request complete after uploading a revision, but nobody checks whether the change solved the concern. A resolved thread can then be mistaken for proof that the work is ready.
The Fix
Review the updated element against the requested outcome before closing the issue. If the concern remains, explain what still needs attention in the same thread. Distinguish the completion of an individual comment from approval of the whole file.
What to Say
““The headline is larger now, but it still competes with the badge above it. Please check the hierarchy again before we resolve this comment.””
In Jottrly, resolved comments and the Next unresolved button support working through individual issues. File statuses such as Changes requested and Approved communicate the broader review decision.
10. “Looks Good” Without a Clear Final Approval
A stakeholder responds positively, but the designer does not know whether that means “I like the direction” or “this version is approved for handoff.” Silence creates the same uncertainty.
The Fix
Ask for an explicit decision that identifies the file, version, and purpose. Confirm who can make that decision. If there are remaining dependencies, record them alongside the approval instead of assuming they are understood.
What to Say
““Please confirm whether homepage version 4 is approved for development handoff, including the layout, imagery, and copy shown. If changes are still needed, add them before we proceed.””
Jottrly includes In review, Changes requested, and Approved file statuses. Keep the status aligned with the decision actually made, and review later changes before treating a newer version as approved.
A Short Review Request You Can Reuse
You do not need a long rulebook to improve the next round. Give the client the current version, a focused review question, a deadline, and a decision owner.
“Please review homepage version 3 for layout, imagery, and copy. Add location-specific comments to the shared review by Thursday. Label essential corrections separately from optional suggestions. Morgan will consolidate stakeholder input before we prepare the next version.”
Adapt the request to your project agreement and the client’s actual review responsibilities. Keep instructions short enough that people will use them.
Jottrly is a visual feedback and approval tool for creative teams and agencies. Explore the Jottrly product overview to see how annotations, comment threads, version history, and approval statuses support this process.
Frequently Asked Questions
How do you ask a client for more specific design feedback?
Ask them to identify the element, explain the concern, and describe the desired outcome. For example, replace “make it pop” with “the headline is difficult to notice; make the main message easier to scan.” Ask a focused follow-up question if the concern is still unclear.
What should an agency do with conflicting stakeholder feedback?
Ask the client decision owner to consolidate the requests into one direction. Explain the tradeoff against the project brief and record the decision before revising. Designers should not have to guess which stakeholder’s request takes priority.
How many design revision rounds should a project include?
There is no single number that suits every project. Agree on the included rounds, deliverables, and review boundaries before work starts. Explain how additional rounds or new deliverables will affect the scope, fee, and schedule.
How can you prevent clients from reviewing an old design?
Identify the current file and version in each review request, include a short change summary, and clearly label older work as reference material. Jottrly supports version history to keep revisions together.
What should you do when feedback arrives after the deadline?
Check whether it is a necessary correction or a new direction. Explain its effect on the agreed scope and handoff date, then confirm the next step with the decision owner. Do not assume every late request should be rejected or included without discussion.
Does resolving every comment mean a design is approved?
No. A resolved comment closes an individual issue. Approval is the decision about the identified file and version as a whole. Confirm the final decision explicitly and keep the file status aligned with it.
How does Jottrly help organize client feedback?
Jottrly supports designs, screenshots, and PDFs, with numbered pins, drawings, highlights, arrows, text annotations, and per-mark comment threads with @mentions. Version history, resolved comments, and file approval statuses help teams organize revisions and decisions.
Make Your Next Review Easier to Follow
Keep the work and feedback connected, then move toward a clear decision on the current version. Visit pricing to compare the plans shown for Jottrly.
Compare Jottrly Plans