The Client Who Never Reads the Proposal

You sent the proposal. They said it looked great. You started work.

Then three weeks in, they ask for something that was never in the scope. You reference the proposal. They say they don't remember that limitation. And now you're in a standoff where the document you wrote carefully means nothing to the person who signed off on it.

This happens more than it should. And every time it does, you pay for it.

The Proposal Is Your Protection, Until It Isn't

A well-written proposal lays out what's included, what isn't, and what happens when the work changes. Most freelancers put genuine effort into writing it. The problem is that some clients treat the proposal like terms and conditions. They scroll to the bottom and click agree.

They have a general sense of what they're getting. They do not have a specific sense of what they're not getting.

When the project starts, that gap becomes your problem.

What Logged Hours Actually Do Here

If you've been tracking time by task from day one, you have something concrete to point to when the conversation gets uncomfortable.

You're not saying "I think I've done a lot." You're showing a report. Here's what was scoped. Here's what got logged. Here's where we are against the original estimate.

That changes the dynamic. The client might still push back, but they're pushing back against real numbers, not your memory of how hard you worked.

The proposal tells them what was agreed. Your time log tells them where you are against it. Together, those two things make scope creep visible instead of invisible.

The Moment It Starts to Blur

Scope creep rarely arrives as one big ask. It comes in small ones. A tweak here. A revision there. An extra round of feedback that wasn't in the plan.

Each individual request feels minor. But in your logs, you can see them stacking up. You can see the extra hour you spent on the revision round that was supposed to be one pass. You can see the thirty minutes on a call that turned into an hour of follow-up work.

If you weren't tracking, you'd absorb all of that without a number attached to it. And when you go to invoice, you'd either undercharge because you forgot how much it grew, or you'd have a vague sense of being owed something with nothing to back it up.

When to Bring It Up

Earlier than feels comfortable. That's the answer.

If you wait until the invoice to surface the scope issue, you've already done the work. You have no leverage. The client has what they wanted and now you're asking for more money for something they've already received.

When you track by task and check in against your estimate weekly, you catch the drift while there's still time to have a real conversation. "Hey, we're at eighteen hours on a project I quoted for fifteen. Here's where the extra time went. Do you want to keep going or should we scope the remaining work separately?"

That is a professional conversation. Most clients respond to it reasonably when it happens before the invoice, not after.

The Client Who Never Reads the Proposal Will Happen Again

You won't screen them out perfectly. You'll have detailed kickoff calls and send clear documents and still end up working for someone who genuinely did not absorb the terms.

That's not fully fixable. What is fixable is your ability to show exactly what happened when the conversation eventually comes up.

Log your time. Label your tasks. Keep your project entries specific enough that a report tells the story without you having to narrate it from memory.

You can't make every client read what you send them. But you can make sure you have the receipts when they act like they didn't.

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