The Scope I Added and Never Wrote Down

It started with a call. The client asked if I could add one more thing while I was in there. It would only take a minute. I said sure. I did not write it down, did not create a change order, and did not add it to the project in my time tracker.

That was not the last time it happened on that project. It was just the first.

How verbal agreements disappear

When someone asks you to add something on a call and you say yes, that agreement exists in your memory and their memory. Those are two different things. Your memory of what you agreed to do is not the same as their memory of what they asked for. And three weeks later, neither version is reliable.

By the time the project closed, I had a list of client requests that never made it to the invoice. Some were genuinely small. One or two were not. I only discovered this when I was reviewing my time logs before sending the final bill and noticed entries that didn't match any line item in my original scope.

Hours logged. Tasks completed. Work done. Invoice total unchanged.

The specific damage

I went through the logs carefully. Time-Trak showed me every entry by project. I could see exactly what tasks I had worked on and when. When I compared those entries to the original scope document, the gaps were visible.

There were twelve hours of logged work that didn't map to anything I had originally agreed to do. At my rate, that was real money sitting outside the invoice.

Some of it I could still add. I went back to the client, explained what had come up during the project, and added a scope adjustment to the final bill. They were fine with it. They remembered the additions. There was no argument.

The rest I wrote off because I had no documentation and the conversation had happened too long ago to reconstruct cleanly. That part hurt. Not because the client was difficult but because I had made it impossible to invoice properly by not writing anything down.

The pattern underneath it

This was not a single mistake. It was a habit. I would get on calls, things would evolve, I would agree to things verbally, and I would do the work. Then at invoice time I would reconstruct the project from memory instead of from records.

Memory is not a billing system. It is a story you tell yourself about what happened. It leaves out things that feel small and overweights things that were stressful. It is not accurate enough to build an invoice on.

What I do now

Anytime something is added or changed on a project, I log it before I do the work. Not after. Before. I open a new time entry, note what the new task is and where it came from, and then start the timer.

That creates a record that exists before my memory of it gets fuzzy. If the task came from a verbal request on a call, I note that too. Two weeks later when I'm building the invoice, the log tells me exactly what happened and I can make a clear decision about whether and how to bill it.

I also started sending a short follow-up email after every call where something was added. Not a formal document. Just a one-line reply confirming what we agreed to. That takes ninety seconds and it removes all the ambiguity.

The invoice you send reflects the records you kept

If you don't log it, you can't bill it cleanly. You might forget it entirely. You might remember it but have no documentation to back up the charge. Either way, the work happens and the invoice doesn't reflect it.

Your time tracker is only as useful as the habit behind it. Log things when they happen, including the things that come up mid-project on a call. Especially those.

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