How to Catch Unpaid Revision Rounds Before They Stack
Revisions are where fixed-price projects quietly bleed out. Here's how to track them before they become a loss.
Most project scopes include a revision round or two. That's normal. What's not normal, but very common, is what happens when those rounds multiply and nobody says anything.
Round one is in scope. Round two is a stretch but you do it. Round three is definitely outside the original agreement. By round four, you're just doing it because stopping feels harder than finishing.
At no point did anyone formally change the project. The client didn't ask for more scope. You didn't approve a change order. The project just quietly expanded, and your effective hourly rate quietly collapsed.
Why Revision Creep Is Hard to See in the Moment
Each revision feels small when you're inside it. The client sends feedback. You make changes. You send it back. That cycle feels like normal project work, so your brain files it under "expected."
But there's a difference between refining work toward an agreed standard and repeatedly reworking deliverables because the direction keeps changing. The first is part of the job. The second is new work.
You can only tell the difference if you're tracking how much time each round is actually consuming.
Tag Your Revision Entries
This is the simplest habit change that makes the biggest difference. When you log time for revision work, label it clearly. Use a consistent tag like "revision round 2" or "feedback cycle 3" so you can filter for it later.
At a glance, you'll be able to see how much of a fixed-price project was spent on revision versus original production. That breakdown tells you everything.
If your project was scoped at twenty hours and you've spent twelve of them on revisions across four rounds, you have a problem worth naming. Without the tags, you just have a vague sense that the project took longer than expected. With the tags, you have a conversation starter.
What to Do With the Data
You have a few options once you can see the revision hours clearly.
If the project is still active, you can flag it early. A message to the client that says you're approaching the included revision limit is easier to send after round two than after round five. The earlier you send it, the less awkward it is.
If the project is already done and you're looking at the numbers in retrospect, the data still matters. It tells you how to price the next similar project. If revision work reliably doubles your hours on a certain type of deliverable, your fixed price needs to reflect that.
And if you're renewing a contract with the same client, you can use the history to have an honest conversation about how revisions are scoped going forward.
The Floating Timer Keeps the Data Honest
The problem with tracking revision rounds is that you have to actually track them. It sounds obvious, but revision work is exactly the kind of task that gets absorbed without logging. You open the file, make a quick change, close it. No timer started.
Having a timer widget that's always visible removes most of that friction. You see it. You start it. The session gets logged. The revision round gets counted.
That's the only way the data you need actually exists when you go to look for it.
Revisions Are Not the Problem
Good clients give feedback. That's part of the process and it usually makes the work better. Revisions only become a problem when there's no limit on them and no mechanism for catching when you've crossed it.
A clear scope, labeled time entries, and a habit of checking your hours before you send another round of changes gives you everything you need to manage this well.
You don't have to be rigid about it. You just have to be watching.
Track your time, bill every minute.
Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.
Free during beta.
Download Time-Trak →macOS + Windows · Floating widget · Auto screenshots