The Approval That Was Never in Writing

It Started With a Quick Call

The client called to talk through a new direction for the project. Twenty minutes. Casual. At the end they said, yeah, go ahead, let's do it that way.

I did. Three weeks of work under the new direction. Then the invoice landed and suddenly that call had not happened the way I remembered it.

Not according to them, anyway.

The Version of Events That Lives in an Email Thread

When a client pushes back on an invoice, the first thing they ask for is documentation. What was agreed, when, by whom.

If your only documentation is your own memory of a phone call, you are already behind.

This is not about clients being dishonest. Sometimes they genuinely do not remember what they approved. Sometimes they approved it without fully understanding what it would cost. Either way, you are the one holding an invoice for work they are now questioning.

What Your Time Log Captures That Memory Does Not

I use Time-Trak on every project. That day after the call, I opened a new time entry, noted the task as direction change per client call, and started the timer. Not because I was planning a dispute. Just because that is how I work.

When the client questioned the invoice, I sent them a time report. It showed the entry from that afternoon, the note I had written, and every hour logged under the new direction from that day forward.

It did not prove the conversation happened. But it showed exactly when my work shifted, and it matched the date of the call they claimed to not remember clearly.

That was enough. The invoice was paid.

The Habit That Changes Everything

Note your time entries like someone might read them later. Because sometimes they will.

Not a novel. Just enough context. Direction change per client call. Revised scope per Tuesday approval. Extra round of feedback, not in original brief.

A time entry with a clear note is worth ten times a time entry that just says meeting or design work. When a client questions something six weeks later, you will not remember the details. Your log will.

Scope Creep Is Invisible Without Records

Most scope creep does not arrive with a dramatic ask. It arrives as a quick call. A casual message. A yeah, go ahead that nobody wrote down.

If you are not logging what you are doing and when you started doing it, you cannot see the pattern. You just feel it as vague resentment, a project that is taking longer than expected, an invoice that does not feel right to send.

When you track consistently, scope creep shows up as data. A task that was not in the original estimate. Hours that belong to a request made after kickoff. A deliverable that materialized from a conversation neither party wrote down.

That data is useful in two ways. It tells you what to charge for. And it tells you when to stop and have the contract conversation before you keep going.

The Part You Cannot Outsource

A time tracker handles the logging. You still have to write down what you were doing and why.

That is three seconds of work per entry. A task name and one line of context. Done over a full project, it becomes a complete record of what was asked, what was approved, and what was delivered.

No client dispute survives a clean time log. Not because the log wins arguments. Because it answers questions before they become arguments.

Start your timer after every client call. Write one sentence about what you just agreed to. That habit has saved invoices I was not even sure I could defend.

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