The Hours Between Revisions That Never Make It to the Invoice

You send the draft. The client goes quiet for a week. Feedback arrives. You open the file, re-read everything you wrote, check your notes, and spend twenty minutes getting back up to speed before you change a single word.

That twenty minutes is work. You almost certainly did not bill it.

The Gap Between Rounds Is Not Empty

Freelancers tend to think of a project in terms of active output. You wrote the copy. You built the feature. You designed the screen. That is the work, and that is what gets tracked.

But projects do not run in clean blocks. There is time before each round starts again. Time re-reading briefs, reviewing previous feedback, cross-checking earlier decisions, and reminding yourself what the client actually wanted.

None of that appears in most invoices. All of it is billable.

What Actually Happens Between Feedback Rounds

Here is a realistic picture of what goes on between rounds on a typical project:

You wait for feedback. While waiting, you get pulled into other work. When feedback arrives, you context-switch back. You re-read the original brief. You re-read your previous version. You re-read the client's feedback twice because it is vague. You send a clarifying question. They reply. You read that. Now you are ready to start.

Thirty to forty-five minutes have passed and you have not opened a new document yet.

If you are billing by the hour, that time counts. If you are billing flat rate and this is a fixed-scope project, it still tells you something important about how long projects like this actually take.

Why This Matters Even on Flat Rate Work

Fixed fee projects are not immune to this problem. Every hour you spend between revision rounds that you did not account for when quoting is an hour eating into your effective rate.

If you track time on flat rate projects and review the logs afterward, you will start to see patterns. Certain clients send fragmented feedback. Certain project types require more re-engagement time per round. Certain scopes that look clean upfront generate three rounds of revisions instead of one.

That data is how you quote better next time. You cannot get it if you only track the active output hours.

Make It a Habit to Log Re-Engagement Time

The simplest fix is to start your timer the moment you look at a project, not the moment you start producing something.

Opening the brief is work. Reading the feedback email is work. Writing the clarifying question is work. All of it belongs in the log.

A floating timer widget on your desktop makes this easier than you think. You do not have to navigate somewhere or log into a tool. You see the timer. You click it. You start reading. That is the habit.

Over a month, those small blocks of re-engagement time add up to hours. On some projects, they add up to a full day you never billed.

How to Label These Entries

Do not lump re-engagement time into a vague catch-all. Label it specifically.

"Reviewed prior draft and feedback before Round 2" is a real time entry. It shows the client that revision rounds have a startup cost. It shows you, over time, how much your revision process actually costs per project type.

When you build your next quote, you will have real data for how long a three-round revision project takes from first draft to final file. Not a guess. A number based on actual logged hours including the time that lives between the rounds.

That is how you stop undercharging for projects that should have been priced higher from the start.

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