To track client revision rounds, keep one log per deliverable. Write the running count on every version you send (for example, "Homepage, 2 of 3 used"). When the included rounds are gone, stop until the next one is approved.
A number in the contract only works if you and the client can both see the same count.
Why limits fail without a log
A revision limit only works if both sides can point to the same number.
Say the scope includes two rounds. Feedback arrives in five messages, a voice note and a comment in the file. You count more than one round. The client calls it all "the first set of notes." Nobody can prove either side, so the extra pass gets done for free.
That unpaid pass is a form of scope creep: extra work that slips in without a new agreement. A log doesn't make the client difficult. It gives you both one place to look.
PMI's Margaret Love, writing about project change logs, says decisions that aren't clearly documented and approved are "subject to rehash" later. Her advice is to keep a log of the key facts and update it while the work is still in motion.
Put the rules in writing first
Before the first file goes out, write down:
- how many rounds each deliverable includes
- what one round is
- who sends the feedback
- what happens after the last included round
What is a round, and when does it open and close?
A round is one consolidated list of changes, from the named approver, on one deliverable. You action it in one pass.
It opens when the approver sends that list on the current version. It closes when you send the revised file back and mark the log closed. Feedback that arrives after you start work belongs in the next round.
If you start on the first email and then accept three more messages, you have quietly agreed that round 1 never ends. So confirm the list before you start:
Thanks, I've got these changes for homepage round 1:
1. New headline on the hero
2. Swap the two testimonials
3. More space above the footer on mobile
Is that everything for this round? I'll start once you confirm,
and I'll send version 2 back with the count updated to 1 of 2 used.
The first delivery is not a revision. Label it "Homepage, first version, 0 of 2 revision rounds used."
What goes in the log
One row per round is enough. Individual comments belong in the feedback list, not as extra rows.
| Column | What to enter |
|---|---|
| Deliverable | Homepage, logo, article, video cut |
| Included rounds | The number in the scope, such as 2 |
| Round | 1, 2, or Extra 1 |
| Opened / closed | Date the confirmed list arrived, date you sent the new version |
| Version sent | File name or link |
| Feedback summary | A short list, or a link to the confirmed list |
| Included or extra | Included until the cap is used, extra after that |
| Approval | Who signed off, and when, or "pending" |
| Evidence | The email or thread where the list and the yes live |
Show the client "2 of 3 used"
A private spreadsheet they never see doesn't count. Put the count where the client already looks:
-
File name:
homepage-v2-1-of-2.pdfis harder to misread thanhomepage-FINAL-revised-v2.pdf. - Subject line and first sentence: "Homepage, version 2, 1 of 2 revision rounds used. One included round remains."
- A view-only copy of the log, or a status line at the top of the shared folder: "Home 1/2, Menu 0/2, Reservations 0/2."
Say the count from the first delivery, when it is still 0 of 2. People accept a limit they have been looking at. They push back on one they first hear about on round 3.
On the last included round, add one plain sentence: "This is the last included round on the homepage. If you'd like another pass after this, I'll send a short quote before starting." That is a heads-up, not a threat.
Several deliverables
Give each deliverable its own counter and its own rows. The homepage can be on 2 of 2 while the about page is still at 0 of 2.
If you use one project-wide number, one talkative page burns the rounds meant for the rest. Add a one-line summary:
Current revision count: Homepage 2 of 2 used. Menu page 1 of 2. Reservations page 0 of 2.
Drip feedback and extra stakeholders
Pick one official channel for feedback on a deliverable: the comment thread, a request link, or a single email chain. When a note arrives somewhere else, copy it into that channel and reply there.
When two people disagree, pause. Note in the log that the round is waiting on a decision, and ask the approver to pick. Doing both, or just the later email, is how you redo the same work in the next round.
If new people join mid-project and want to reopen approved work, that is usually a change, not a fresh set of included rounds. The log is how you show the earlier approval.
Retainers
A monthly retainer can hide revision creep, because there is no single end date to force a count. Use the same per-deliverable log, and decide in the agreement what you are capping:
- rounds per deliverable per month
- a shared monthly round cap (show "5 of 8 monthly rounds used")
- hours, if the retainer is an hours bank
Reset the visible count on the first day of the cycle. Say whether unused rounds expire, and don't invent a rollover later.
At the limit: quote first, then wait for a yes
When the included rounds are used, stop work on that deliverable. Tell the client, point to the log, and send the price for an extra round.
Wait for a written yes before you start. Starting "while they think about it" is how the limit quietly disappears.
Once the extra round is approved, add a row labelled "Extra 1" and name the next file to match.
Originally published at creepless.online. This version was drafted with AI assistance.
Top comments (0)