Revision rounds
What's the best way to track revision rounds with clients?
Short answer
Write the number of included rounds into the scope the client approves, then count each round in the same place the client can see it. When the included rounds are used, the next one goes on a change order the client signs, so the extra work is paid instead of absorbed. PaloWorks does all three in one project.
Free for 1 client, 3 active projects. No card to start. Updated by PaloWorks.
What to look for
Rounds agreed before work starts
A round limit in an email thread is a suggestion. One in the approved scope is a term the client agreed to.
In PaloWorks
Every scope has an included-rounds field (two by default) that the client approves with the rest of the terms.
One count both sides can see
Disputes start when the studio thinks it is round four and the client thinks it is round two.
In PaloWorks
Each round is recorded with its number. The client portal and status link show rounds used against rounds included.
Clients can ask without email ping-pong
Feedback scattered across email, chat and calls is how rounds go uncounted.
In PaloWorks
From the approved scope page the client sends change requests, which open a round, or join the round already open.
A clear next step when rounds run out
Without one, the extra round becomes a favour.
In PaloWorks
Logging a round past the allowance drafts a change order priced from your scope. You send it; the client signs it.
A second opinion on borderline requests
"Is this a revision or new work?" is the question that costs the most money.
In PaloWorks
On Pro and Studio, an AI referee suggests whether a request is in scope, an extra round or out of scope. You keep or discard its verdict; it never bills anything.
How it works in PaloWorks
Step 1
Set the rounds in the scope
Write deliverables, exclusions, the timeline, the price and the number of included rounds.
Step 2
The client approves it
They open the signing link emailed to them, tick the consent box and type their name. No account.
Step 3
Each round is counted
Rounds you log and changes the client requests are numbered, and both sides see how many are left.
Step 4
Round three becomes a change order
Past the allowance, a draft change order is ready. Send it, and invoice it once the client approves.
When PaloWorks is the wrong pick
- If you only need to collect comments on images or PDFs, a dedicated proofing tool that annotates files is a better fit. PaloWorks counts rounds; it does not mark up artwork.
- If your contracts never limit revisions, the round counter has nothing to count.
Comparing tools? Read PaloWorks compared, including what the others are better at.
Questions people ask
- How many revision rounds should a project include?
- Two is the most common starting point for design work, and it is PaloWorks' default. The number matters less than agreeing to it before work starts, and defining what counts as one round.
- Can the client see how many rounds are left?
- Yes. The client portal and the project status link show rounds used against rounds included, unless the studio turns that meter off.
- What happens when the client asks for another round?
- Logging a round past the allowance drafts a change order for the extra round, priced from your scope. Nothing is sent or billed until you send it and the client approves it.
- Does it work on the free plan?
- Scopes, round counting and change orders are on every plan, Free included. The AI referee is on Pro and Studio.