The Revision You Did Not Log Because It Felt Small
Small revisions feel too minor to clock, but they are where your project budget quietly bleeds out every single time.
It Was Just a Quick Fix
Fifteen minutes. Maybe twenty. You opened the file, made the change, sent it back.
You did not start a timer because it felt silly to log something so small. You would remember it. It was not worth the friction.
Then it happened again the next day. And three more times that week. And twice the week after.
By the time the project closed, you had done somewhere between four and eight hours of unlogged revisions. Gone. No record. No invoice line. Just time you gave away.
Why Small Tasks Are the Hardest to Track
Large work blocks are easy to log. You sit down, start the timer, work for two hours, stop the timer.
Small reactive tasks are different. They interrupt other work. They happen in the gaps. They feel too minor to formalize.
But small tasks are where most project budgets actually bleed out. Not on the big deliverables. On the drip of tiny changes that accumulate invisibly.
If you review your time log at the end of a project and it looks clean and neat, that is usually a warning sign. Real projects are messy. If your log does not reflect that messiness, the hours are still there. You just did not capture them.
The Habit That Closes the Gap
The fix is not more discipline. It is lowering the friction of logging small tasks.
A floating timer widget helps because it is always visible. You do not have to open an app, navigate to a project, find the right code. You click and the clock starts. When you are done, you stop it and add a note.
That process takes ten seconds. That is a low enough bar that you will actually do it for a fifteen-minute revision.
If you have to open a browser tab, log in, find your project, and select a task category just to record twenty minutes, you will skip it. The system is slower than the work.
What This Looks Like on an Invoice
You have two options when it comes to logging small revision work.
One: you track it, include it in your hours, and bill for it. If the contract includes a revision limit, this is how you know when you have hit it.
Two: you track it, do not bill for it in this round, but use it to price the next project differently.
Either way, logging the work gives you a choice. Not logging it removes the choice entirely.
The client who keeps requesting small changes after delivery is not necessarily doing anything wrong. But if you have no record of how many times it has happened, you cannot have a conversation about it. You just quietly absorb it.
The Bigger Pattern
Freelancers who consistently undercharge for revision work usually have one of two problems.
First, they did not define revision rounds in the contract. So every change feels like an obligation.
Second, they did not track the changes, so they cannot quantify what the obligation actually cost them.
Fix both. Write a scope that specifies revision rounds and what counts as a revision. And log every change, no matter how small.
After a few projects, you will have real data on how many hours revisions consume per project type. That data should change how you quote.
One Rule That Helps
If a task takes more than five minutes, it gets logged. No exceptions.
Five minutes is the threshold, not thirty. If you set it at thirty, you lose all the fifteen and twenty minute tasks that add up to half a day over a week.
That one rule, applied consistently, will change what your invoices look like inside a month.
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