The Client Who Paid Half Upfront and Redefined Done

You got a deposit. You felt good about it.

Then the project started moving. Slowly at first. A revision here, a new requirement there. Nothing big enough to flag. Nothing small enough to ignore.

By the time you hit the original scope, the client had quietly rewritten what "done" meant. And because you never tracked any of it, you had no way to show the distance between what you agreed to and where you actually ended up.

The Deposit Doesn't Protect You

A lot of freelancers treat the upfront payment like a safety net. It isn't. It covers your early hours. It doesn't cover the version of the project that exists three weeks in, after the brief has been reinterpreted four times.

What protects you is a time log that shows exactly when the scope changed and what you did after it did.

If you tracked the original deliverables separately from everything that came after, you have something concrete to point to. If you didn't, you're just arguing about feelings.

The Redefinition Usually Happens in One Conversation

Watch for the phrase "can we also just."

That's where scope creep lives. Not in dramatic change requests. In small conversational additions that feel like nothing in the moment and compound into hours by the end.

When you hear that phrase, start a new time entry. Label it something specific. "Revision round two" or "added deliverable, date" or literally anything that creates a record that this was not part of the original agreement.

You don't have to make it a confrontation. You just have to make it documented.

The Second Half of the Invoice Is Where It Falls Apart

Most billing problems don't show up at the start of a project. They show up when you go to collect the second payment.

By then, the client has forgotten the original scope. They remember the project as the thing that exists now, not the thing you agreed to build. And if your time log looks like one big undifferentiated block of hours, you can't show them the difference.

But if your entries are labeled by phase, by deliverable, by request, the invoice tells a story. It shows what was planned, what was added, and what that cost. The client can follow it. They might not love it, but they can't argue with the sequence.

What to Do Before the Next Project Starts

Before you touch any work, set up the project structure so that new scope has somewhere to live.

Create a task or category for original deliverables. Create a separate one for additions. When something new comes in that wasn't in the brief, it goes in the additions bucket. You track it, you label it, you keep it separate.

When you go to invoice, you can clearly show what was included in the original price and what wasn't. That conversation is a lot easier when you have the data.

The Floating Timer Helps More Than You Think

One reason scope creep goes untracked is that the extra work happens in the middle of a session. You're working on one thing, the client sends a message, you switch over and handle it, then go back.

You log it all under the same entry.

A floating timer widget that stays visible keeps you honest. You can see you're still running on the original task. You can stop, switch entries, log the addition separately, then go back. It takes ten seconds and it changes what you can prove later.

You Agreed to a Project. Not to a Moving Target.

Clients don't always redefined scope maliciously. Sometimes they genuinely don't realize they're doing it. But that doesn't change what it costs you.

The deposit got you started. The time log gets you paid accurately at the end.

Track the gap between what you agreed to and what you actually built. That gap is billable. But only if you can show it exists.

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