How to Set Revision Rounds and Feedback Rules for Creative Agency Projects

Revisions are part of creative work. A client may need to see a design in context, hear a script aloud, or compare two routes before they can make a confident decision. The problem is not that clients ask for changes; it is when nobody agrees on what a revision includes, who can request one, or what happens when the brief changes halfway through.

If you are figuring out how to manage revisions in creative projects, start by treating feedback as a planned stage of delivery—not an informal favor. A useful policy gives clients room to refine the work while protecting the agency from unpriced rounds of new direction. It also gives your team a clear next step when feedback arrives late, conflicts, or expands the scope.

There is no universal number of rounds that fits every project. A logo engagement, a campaign concept, and a multi-page website carry different kinds of uncertainty. The goal is to define a process that matches the work, then make the rules visible before production starts.

Define what a revision round actually means

“Two rounds of revisions” sounds clear until a client sends a list on Monday, another list from a different stakeholder on Wednesday, and a new direction the following week. Define a round as a single, consolidated set of feedback on a specific deliverable, submitted by an agreed deadline by the client’s decision-maker or designated lead.

Then clarify what the agency does with it. A round might include reviewing the feedback, making changes within the approved brief, and presenting the updated work once. It should not mean unlimited back-and-forth until everyone feels finished.

Separate refinement from a change in direction

A revision is a change that improves or adjusts the work while keeping the original objective and agreed scope intact. Examples include correcting copy, adjusting a color choice within the selected identity direction, or changing the order of sections on a landing page.

A change in direction alters the underlying assignment. Examples include replacing the approved concept, adding a new audience, asking for a second campaign route after one was selected, or adding pages that were not in the estimate. Those requests may be reasonable, but they need a scope conversation—not a quiet addition to the revision list.

Put the distinction in plain language in your proposal or statement of work. For instance: “Included revisions refine the selected direction against the approved brief. A new direction, additional deliverable, or material change to the brief may require a revised fee and timeline.” For more on drawing that line, see our guide to scope creep warning signs on agency projects.

Choose the number of rounds based on the work

There is no magic number. Two rounds may be sensible for a tightly scoped deliverable with a strong brief; three may be appropriate when the project includes exploration or several stakeholder groups. A high-uncertainty project may need a paid discovery or concept phase before the production scope is fixed.

Estimate the effort behind the rounds, not just the number. A “round” could take 30 minutes for a small graphic or several days for a site redesign with design, copy, and development changes. Include the expected review and implementation time in your estimate, and make clear which deliverables the allowance covers.

Use decision gates for larger projects

For a website, you might set a review point for sitemap and structure, another for visual design, and a final one for content and functional QA. At each gate, the client approves a defined piece of work before the team moves on. This is more useful than saying “three rounds for the whole website,” because it identifies what is being reviewed and reduces the chance that an early decision is reopened at launch.

For brand work, the gates could be discovery findings, selected creative direction, and final identity applications. For a campaign, they might be concept, key creative, and channel adaptations. The right stages depend on how your team works, but decisions should be made in an order that limits expensive rework.

Set feedback rules that help clients respond well

Clients are often asked to review work while also managing their own jobs. A vague request to “send any thoughts” makes it harder for them to give useful feedback and harder for your team to act on it. Explain what you need, where to send it, and who is responsible for consolidating it.

  • Name one feedback owner. Ask the client to gather comments from relevant stakeholders and send one approved response. If several people need to contribute, agree who resolves conflicts.
  • Set a deadline. Specify a date or a number of business days after presentation. State that late feedback may move the delivery date or affect team availability.
  • Use one channel. Choose a shared document, project workspace, or annotated proof. Avoid splitting comments across email, chat, and meetings.
  • Ask for prioritized, actionable notes. Encourage clients to identify the issue, explain why it matters, and point to the relevant section or screen.
  • Confirm approval in writing. Record who approved what and when, especially at stage gates.

At kickoff, cover these mechanics alongside objectives, roles, and approvals. A structured agency project kickoff agenda can help make feedback responsibilities explicit before the first presentation.

Give clients prompts, not just a deadline

Useful review prompts can focus feedback on the brief: “Does this speak to the audience we agreed on?” “Which part feels least clear?” “What evidence supports changing this?” For visual work, ask reviewers to distinguish preference from a concern about audience, usability, or business goals. That does not mean every creative decision needs a spreadsheet; it means the team can understand what a comment is trying to solve.

Some requirements are not matters of taste. For example, if a deliverable must meet accessibility criteria, evaluate it against the relevant requirements rather than treating compliance feedback as a subjective revision request. The W3C Web Content Accessibility Guidelines provide testable success criteria for web accessibility.

Make timing and approval consequences explicit

Revision limits do little to protect a schedule if the client can take three weeks to respond without any effect on the delivery plan. Include review windows in the project timeline and explain what happens when a deadline is missed. A practical rule is that the schedule shifts by the delay, subject to the team’s next available production slot. Avoid promising an immediate restart if your staff have already moved to other work.

Set an approval point before work becomes costly to change. If the client approves a homepage design and later requests a different navigation structure, that may affect approved layouts, copy, and development—not just one screen. Record the decision and its consequences as they happen. A status dashboard can make open approvals, owners, and due dates visible; see how to build an agency client project status dashboard.

Do not treat silence as approval unless your agreement clearly says so and that approach is appropriate for the engagement. In most cases, a written approval request and a revised schedule are cleaner than assuming the client accepted work they have not reviewed.

Handle out-of-scope feedback without creating friction

When feedback exceeds the agreed allowance, respond promptly and specifically. Avoid a blunt “that’s out of scope” with no explanation. Identify which request changes the brief, estimate the added effort, and give the client a choice: approve extra work, defer it to a later phase, or proceed with the current scope.

For example: “The requested second visual direction is outside the two refinement rounds for the selected concept. We can develop it as an additional option for an estimated 10–14 hours, which would move presentation by about a week. Would you like us to quote that, or should we continue refining the approved direction?” The estimate should reflect your actual team and dependencies; do not use the example as a standard rate or time allowance.

When the change is material, document the revised deliverables, fee, schedule, and approval before doing the work. A simple agency change order process can prevent an informal request from becoming disputed work later.

A practical revision policy checklist

Before sending a proposal or starting production, check that the client and team can answer these questions:

  • Which deliverables have revision rounds, and how many are included for each?
  • What counts as one round, and what does the agency return after receiving it?
  • Who gathers feedback and has authority to approve it?
  • How many business days does the client have to respond?
  • What happens to the schedule when feedback is late?
  • Which kinds of requests count as new scope or a change in direction?
  • How will additional work be estimated and approved?
  • At which stages does client approval lock a decision?

Use wording that suits the project rather than copying a generic clause into every contract. A short brand engagement may need a compact explanation; a complex digital build may need separate rules for content, design, functionality, and testing. If a contract term has legal consequences, have a qualified lawyer review it for your jurisdiction.

FAQ

How many revision rounds should an agency include?

Choose a number based on the deliverable, uncertainty, stakeholder load, and estimated production effort. Two or three rounds can be a starting point, not a universal rule. Define what each round covers and estimate the work involved.

Should agencies charge for every change after the included rounds?

Not automatically. First determine whether the request is an in-scope refinement or a new direction, added deliverable, or changed requirement. Explain the impact and get approval for additional work before proceeding.

What if a client gives conflicting feedback?

Pause implementation and ask the designated client lead to resolve the conflict into one consolidated set of comments. If the disagreement changes the approved direction, clarify the decision and any effect on cost or timing before continuing.

Can a client request revisions after final approval?

They can ask, but whether the request is included depends on your agreement and the type of change. A correction to agency work that does not match the approved brief is different from a new preference after sign-off; document the distinction and agree on next steps.

How should an agency handle feedback that arrives late?

Tell the client how the delay affects the schedule and when the team can resume. Update the delivery plan rather than squeezing unplanned work into already committed capacity, and confirm the revised dates in writing.

Similar Posts