Key Takeaways
- Define the deliverables, inputs, review boundaries, and included rounds before the first review.
- Distinguish improvements to agreed work from new deliverables or changes to an agreed direction.
- Collect one consolidated set of feedback on the identified current version.
- Assess additional requests and confirm their effect on scope and timing before starting.
- Check the revised work and record explicit approval of the file and version.

A client asks for a small change. Then another stakeholder requests a new section. By the next review, the homepage project includes an extra landing page and a different visual direction, but the deadline has stayed the same.
Design revisions are part of creative work. Scope creep happens when the work expands without a clear decision about what changed and how the team will handle it. The goal is to make room for useful feedback while keeping the deliverables, effort, and next decision visible.
You do not need to reject every new idea. You need a consistent way to assess it. This workflow helps creative teams and agencies set review boundaries, separate revisions from new requests, and close each round clearly.
1. Define the Deliverables Before the First Review
Scope creep often begins before a client leaves the first comment. “Website design” sounds clear until the client expects six page layouts, the designer expects three, and nobody has decided who supplies the copy.
Write down the deliverables in concrete terms: which pages or assets are included, the formats you will provide, what the client supplies, and which decisions this stage covers. A homepage design, a mobile layout, development, and copywriting are different tasks. Identify the ones your team has agreed to deliver.
Also record the assumptions that affect the work. If you are designing around approved copy, a request to rewrite that copy may change the layout and the schedule. If brand direction is already agreed, a new visual identity is more than a small adjustment to a button.
A More Useful Scope Statement
“This stage includes the homepage and contact page designs for desktop and mobile, using the supplied brand assets and approved copy. Development, additional page layouts, and new brand exploration are separate tasks.”
Keep this brief accessible during review. It gives both sides something specific to refer to when a request is unclear.
2. Agree on What Counts as a Revision
A revision improves an agreed deliverable within the agreed direction. A new request adds a deliverable, reopens an earlier decision, or changes an input the team was relying on. The distinction depends on your project agreement, not how small the request sounds.
For example, adjusting the spacing on an included page is usually a revision. Designing an additional landing page is new work. Replacing a headline might be a simple edit, but rewriting every section could create a larger task. Assess the actual work and its dependencies rather than classifying everything by the number of words in the request.
There is no universal number of revision rounds that works for every agency. Agree on the included rounds and explain what one round means. A practical definition is one consolidated set of client feedback followed by one revised submission.
Define the Review Round
“Each round begins with one consolidated set of feedback on the current version. We review the requests, confirm the direction, and submit one updated version for the next decision.”
Clarify how you will handle corrections separately from optional changes. If your team missed an agreed requirement, assess and address that gap instead of automatically treating it as an extra.

3. Give Every Review Round a Clear Purpose
A general “let us know what you think” request opens every decision at once. A focused review asks the client to assess a specific part of the work against a specific goal.
Early rounds might focus on structure and visual direction. Later rounds can check the agreed copy, imagery, and final details. Tell reviewers which decisions are open and which have already been agreed. If a later concern reveals a real problem with an earlier choice, discuss its effect rather than pretending the decision can never change.
Name the current file and version, the feedback deadline, and the person who will consolidate the response. Ask the client to include the stakeholders who need to contribute before the round starts.
A Focused Review Request
“Please review homepage version 2 for content order and the visibility of the enquiry action. Add specific comments by Thursday. Morgan will consolidate stakeholder input before we prepare the next version.”
The deadline should be an agreement, not a surprise. Explain how delayed feedback may affect the next review or handoff date.
4. Consolidate Feedback Before Making Changes
Three reviewers can produce three reasonable requests that do not work together. If the designer starts implementing each comment as it arrives, the next version can inherit the contradictions.
Agree on one client decision owner who settles conflicting input. Keep feedback attached to the relevant part of the design, then sort it into required corrections, improvements, questions, and optional suggestions. These can be simple labels in the comment text.
Ask reviewers to explain the concern and the desired outcome. A designer can solve “the primary action is difficult to find” in several ways. They have less useful information when the request only says “make the button bigger.”
Before revising, confirm the direction on requests that conflict or lack context. A short clarification now can prevent a round built around the wrong assumption.
Clarify the Tradeoff
“One request removes the testimonials to shorten the page; another asks for more proof near the enquiry form. Should we keep a shorter proof section there? Please confirm the direction before we revise.”
The decision owner is a role in your agreed workflow. Do not assume a software permission automatically identifies who can make the client’s final decision.
If a review is already getting difficult, our guide to common client feedback problems and how to fix them includes examples for vague comments, conflicting requests, and outdated versions.
5. Assess New Requests Before Committing to Them
When a request arrives outside the agreed scope, pause long enough to understand it. A quick “sure” can commit the team to work nobody has estimated. An automatic rejection can also miss a useful idea or a necessary correction.
Check what the request changes, which deliverables it affects, and whether it reopens an approved decision. Then estimate the effort and dependencies. A new section may need copy, imagery, a mobile layout, and another review, even if the client describes it as “just one more box.”
Give the client a clear choice. They can approve the additional task and its effect on cost and timing, replace another agreed task if that is workable, or save the idea for a later phase. Confirm the selected option before starting.
A Calm Response to Additional Work
“The campaign page is outside the two layouts in this stage. We can estimate it as an additional task, discuss replacing a planned deliverable, or schedule it for phase two. Which option would you like us to assess?”
Describe the work, not the client’s behavior. “This adds a page layout and review round” is more useful than accusing someone of causing scope creep.
Keep the Work and Feedback Connected
Jottrly brings annotations, discussions, and design versions into one review workflow. Explore the pricing page to see the plans currently presented.
Explore Jottrly Pricing6. Record the Scope Decision Where the Team Can Find It
A conversation can resolve a request, but the agreement needs to be clear to the people doing the work. Record the chosen option, the deliverable affected, the version or brief it changes, and the agreed effect on the schedule.
Use your normal project agreement and approval process for commercial changes. A comment thread can preserve design context, but it should not replace whatever process your business uses to authorize additional work.
Keep a short change summary alongside the review instructions. This helps a colleague or a returning stakeholder understand why the next version differs from the original brief.
A Simple Change Record
“Requested change: add a campaign landing page. Decision: estimate as an additional deliverable. Dependency: client supplies campaign copy. Next step: confirm the estimate and schedule before design starts.”
If the decision is still pending, make that visible. Do not quietly include the request in the next revision and hope the scope conversation will work itself out.
7. Check the Revised Version Against the Agreed Requests
Once the designer submits an update, review it against the consolidated change list. Check the actual outcome instead of assuming that an upload means every issue is resolved.
Keep the review focused on what changed and whether it meets the agreed goal. If a reviewer introduces a new direction, assess it through the same scope process. If a correction has not solved the original concern, explain what remains in the existing discussion.
Jottrly supports version history, per-mark comment threads, resolved comments, and a Next unresolved button. Those features help a team organize the work and review individual issues. They do not determine whether an additional request is included in your project.
A Useful Revision Summary
“Version 3 shortens the headline, moves the approved proof section beside the enquiry form, and corrects the contact details. Please check these changes against the agreed feedback before the final decision.”
Keep the original concern and the resolution connected. That makes it easier to distinguish an unfinished fix from an unrelated new request.

8. Close the Round With Explicit Approval of the Current Version
“Looks good” can mean that someone likes the direction without authorizing the next stage. Ask the decision owner to confirm the specific file, version, and purpose of the approval.
Record any remaining dependencies, such as final image delivery or implementation work. A resolved comment is about an individual issue. Approval is the wider decision about the identified design.
Jottrly uses In review, Changes requested, and Approved file statuses. Keep those statuses aligned with the team’s actual decision. If the client requests another change later, identify the new work and review the updated version before treating it as approved.
Do not treat silence as approval. Follow up with the decision owner and agree on the next step. Any follow-up schedule is something your team arranges; this workflow does not depend on automated reminders.
An Explicit Approval Request
“Please confirm whether homepage version 3 is approved for development handoff, including the layout, copy, and imagery shown. If any required changes remain, add them to the review before we proceed.”
Closing a round clearly protects the client as well as the agency. Everyone can identify the work that was approved and the point at which a later request needs a new decision.
For the complete sequence from first brief to final handoff, see our client design approval process for creative agencies.
Your Design Revision Checklist
Before the next review starts, confirm these points with the team and client:
- The deliverables and client-supplied inputs are clear.
- The included rounds and the meaning of a round are agreed.
- Reviewers know the current file, version, and focus of the review.
- One decision owner consolidates stakeholder feedback.
- Requests are assessed against the agreed scope before work starts.
- Additional work has a recorded decision and next step.
- Required changes are checked on the revised design.
- Final approval identifies the version and the intended handoff.
The most useful boundary is one both sides understand. Explain what is included, assess new requests fairly, and keep the next decision clear. That creates a review process the client can follow and the designer can work from.
Jottrly is a visual feedback and approval tool for creative teams and agencies. The Jottrly product overview shows how annotations, comment threads, version history, and approval statuses support organized reviews.
Frequently Asked Questions
What is scope creep in a design project?
Scope creep is work expanding beyond the agreed deliverables or boundaries without a clear decision about the additional effort, cost, or schedule. It can involve new pages, extra assets, a different creative direction, or repeated review rounds that were not planned.
What is the difference between a revision and a new request?
A revision improves an agreed deliverable within the agreed direction. A new request adds a deliverable, changes an important input, or reopens an earlier decision. Assess the actual work against your project agreement rather than assuming a short request is a small task.
How many design revision rounds should you include?
There is no universal number. Choose a number that fits the project and explain what each round includes. One practical definition is a consolidated set of client feedback followed by one revised submission. Confirm how additional rounds will be handled before work begins.
How do you respond when a client asks for additional design work?
Identify what the request adds and assess its dependencies. Explain the effect on scope and timing, then offer workable options: estimate it as additional work, replace an agreed task where appropriate, or schedule it for a later phase. Confirm the decision before starting.
What if the designer missed an agreed requirement?
Assess the gap against the agreed brief and address the missed requirement. Do not automatically treat a correction to incomplete agreed work as an additional client request. Keep the correction and its review separate from unrelated new work.
Can a visual feedback tool prevent scope creep on its own?
No. A tool can keep annotations, discussions, versions, and review decisions organized, but the team still needs a clear brief, a decision owner, and a process for additional requests. Jottrly supports the review workflow; it does not set your commercial terms or revision limits.
How should you handle design changes after approval?
Identify the approved version and the proposed change. Assess the additional work and agree on the next scope and schedule decision. Review the updated design again before treating a newer version as approved, and keep the earlier approval record clear.
Give Your Next Revision Round a Clear Home
Keep feedback attached to the design and make the current version easy to identify. Visit pricing to compare the plans shown for Jottrly.
Compare Jottrly Plans