The Revision Round That Was Never in the Contract

The email comes in friendly. "Just a few small tweaks." You read it and see six comments, two of which require rebuilding something you already finished.

You do it. You do not add it to the invoice. You tell yourself it is part of the relationship.

Multiply that by every project this year. That is the number worth thinking about.

What a Revision Round Actually Costs

Most freelancers do not track revision time separately from delivery time. It all goes under the same project. Which means when the project closes, you just see a total. You cannot see how many hours were planned work versus how many were changes after the fact.

Once you start logging revision rounds as a separate task type, the picture changes fast. You will see that some clients use far more revision time than others. You will see that some project types generate revision hours that match or exceed the original build time. You will see where your time is actually going.

The Agreement That Did Not Say What You Thought

Most freelance contracts include something about revisions. Two rounds, three rounds, unlimited within reason. The problem is that "a round" is almost never defined precisely enough.

A client reads "two rounds of revisions" as two opportunities to send feedback. You read it as two structured review sessions on the full deliverable. These are not the same thing, and you will only discover the difference when feedback arrives after you thought the project was closed.

Your time log will document what happened regardless of what the contract said. That documentation matters when you need to have the conversation about additional charges. "I have logged four separate sessions of revisions here" is a much cleaner thing to say than "it feels like we have gone over the agreed amount."

How Scope Creep Lives in Revision Rounds

Scope creep does not always arrive as a new project requirement. Often it arrives inside a revision request. "While you are making those changes, could you also adjust..." That sentence has cost freelancers billions of hours over time.

The adjustment feels small. It probably is small, by itself. But revisions attract additions. Once a client is in feedback mode, they notice other things. The revision round becomes a second pass at the brief.

Tracking the specific time on each revision session helps you see how far individual rounds drift from the original scope. A revision round that takes four hours on a project scoped for fifteen is worth noticing. You can decide what to do about it. You cannot decide if you do not see it.

The Habit That Changes the Pattern

Start a separate timer for every revision session. Label it clearly. "Round two revisions" or "post-delivery changes" or whatever makes sense for your workflow.

With Time-Trak, the floating widget is always accessible, so starting a new task entry takes seconds. You do not have to stop what you are doing or switch applications. The timer is just there.

After a few months of this, pull the report. Look at what percentage of your total project time is going into revision and post-delivery work. If that number is high, your revision allowance in your contracts and your pricing is too low.

The Conversation Gets Easier With Data

When you need to tell a client that additional revision rounds are outside the scope, the worst position to be in is vague. "I think we have done more rounds than agreed" invites disagreement. "I have six hours of logged revision time here beyond the two rounds in our agreement" does not.

The data is on your side. You just have to collect it.

Revision rounds feel like part of the job because they are part of the job. That does not mean they are free. Tracking them is how you find out which ones you should have been billing for.

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.

macOS + Windows · Floating widget · Auto screenshots