
When a Revision Is Actually a New Project
Clients call it a revision. Your time logs call it something else entirely. Here is how to tell the difference before you eat the cost.
The word revision sounds small. It sounds like a tweak. A polish. Ten minutes, maybe thirty.
Then you sit down and realize the client wants the whole thing reconceived from a different angle, with new copy, a different structure, and a tone that was never in the original brief.
That is not a revision. That is a new project wearing a revision's clothes.
And if you do not catch it fast, you will do the work, finish the work, and send an invoice that does not reflect any of it.
Why This Keeps Happening
Clients are not usually trying to cheat you. Most of the time they genuinely do not understand what they are asking for. They see the output, not the process. To them, changing the direction feels like adjusting something that already exists.
To you, it means starting over.
The problem is that without clean time data, you cannot prove the difference. You cannot show them what the first version cost, what the revision cost, and why the second number is not a small rounding error.
When you track time by phase or by task, that gap becomes visible. The original concept was four hours. The revision that changed everything was six more. That is a ten-hour project, not a four-hour one with a note at the end.
What to Watch For
A revision is contained. It works within the existing framework. You adjust, you refine, you fix.
A new project breaks the framework. The goal shifts. The audience changes. The format gets reconsidered. You are not improving what exists, you are replacing it.
If you feel yourself opening a blank document, you are probably not revising.
If you are re-reading the brief to figure out what the project actually is now, that is a signal.
If your time log for the revision ends up longer than your time log for the original work, that is a number you cannot ignore.
How to Handle the Conversation
You do not have to be combative. You do not have to accuse anyone of scope creep. You just need data.
Pull your time entries. Show what the original scope looked like in hours. Then show what the revision request requires. Let the numbers carry the conversation.
Something like: "The original brief took me eight hours across research, drafting, and revisions. What you are describing now is a different direction entirely. Based on what I am seeing, this will take another six to eight hours. I want to make sure we handle that correctly before I start."
That is not a confrontation. That is a professional with receipts.
What Accurate Tracking Makes Possible
If you are running a timer during every work session, and labeling entries by task type, you will always have this data ready. You do not have to reconstruct it from memory. You do not have to guess.
When the client sends the revision request on a Tuesday afternoon, you can look at the project in your time tracker within five minutes and know exactly where you stand.
That kind of clarity changes how you respond. Instead of feeling cornered or unsure, you feel grounded. You know what the work cost. You know what the new work will cost. You can speak to both.
The Habit That Protects You
Start every project with clear phase labels. Discovery. Draft one. Client feedback. Revisions. Final delivery.
When a client comes back with something that does not fit neatly into the revision phase, that mismatch is your first signal. Your time tracker is not just a billing tool. It is a record of what you actually built.
And when a revision walks in pretending to be small, your logs will be the first thing that tells you the truth.
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