Ask ten designers how many revision rounds they include and most will say two or three. That’s a sensible default. But projects rarely spiral because the number was wrong. They spiral because nobody agreed on what a round is, what counts as a revision and what happens when the rounds run out.

Here’s how to set revision terms that clients understand and that still hold up in week six.

Why two or three is the usual answer

One round is rarely enough. The first presentation is when the client sees the work for real, and some of their best feedback only surfaces then. A second round lets you act on it. A third catches the small things that only show up once the big ones are fixed.

Past three, the returns drop quickly. If a project needs a fifth round, the problem is usually upstream: an unclear brief, a missing decision-maker or a change of direction dressed up as feedback.

Define what a round is

This is where most agreements fall short. “Three rounds of revisions” can mean three batches of feedback or three hundred emails, depending on who reads it. Spell it out:

• A round is one set of consolidated feedback. The client gathers input from their team and sends it together, not as a stream.

• A round has a deadline. Feedback that arrives after you’ve started on the changes rolls into the next round.

• A round covers the agreed scope. Changes to the brief aren’t revisions. They’re new work.

Revisions versus a change of direction

A revision adjusts the work you presented: tighter copy, a different photo, a color closer to the brand. A change of direction replaces it: a new concept, a new audience, a new message. The first is part of the project. The second needs a new estimate.

Clients don’t always know which one they’re asking for, so it helps to name it kindly when it happens. “This sounds like a new direction rather than a revision. We’re happy to do it, and here’s what it adds to the timeline and budget.” Said early, that sentence saves a lot of goodwill.

Match the rounds to the deliverable

Not every project needs the same structure. Some common patterns:

• Logo or identity: a concept round to pick a direction, then two rounds of refinement.

• Social ad set: one round on concept and copy, then one on the full set across placements.

• Website design: rounds per group of pages, starting with the homepage, so later pages build on approved ones.

• Email flow: one round on the structure of the flow, then one or two on the emails themselves.

• Photo retouching: a selection round, then one or two rounds of retouch notes.

Put it in writing, in plain language

You don’t need legal language for this. A short paragraph in the proposal does the job:

“This project includes two rounds of revisions after the first presentation. A round is one set of consolidated feedback from your team, sent within five working days. Changes outside the agreed brief, or extra rounds, are billed at our day rate, and we’ll always confirm the cost before starting.”

Change the numbers, keep the shape. The client knows what’s included, what isn’t and what happens next.

When the rounds run out

Bring it up before you’re out, not after. When you send the last included round, say so: “This is the final round included in the project. If anything else comes up, we can add a round at the agreed rate.” Most clients appreciate knowing where they stand, and many consolidate their feedback more carefully once they know.

If a project is clearly heading for extra rounds, look for the cause. Is the decision-maker seeing the work late? Is the brief changing? Fixing that is worth more than any number of extra rounds.

Track rounds so nobody has to argue

Disputes about rounds usually come down to memory. Was that the second round or the third? Did we agree to that change? Keep every version and every comment in one place, and the question answers itself.

In Honter, each new version goes to the same link with a version picker, and earlier comments stay with the version they were about. Clients approve or request changes on each deliverable with a review checklist, so the end of a round is a clear moment rather than a feeling. On Honter Pro, the pipeline board keeps track for you: a project moves to In revision after the client leaves feedback, back to Sent for review when you push a new version and to Approved when the client signs off.

For ways to need fewer rounds in the first place, see how to get client approval in fewer rounds.