The Estimate You Update Mid-Project and Never Document

The original estimate was solid. You quoted twelve hours for the content audit, client agreed, work started. Then two weeks in, they asked you to include the blog archive too. You said sure. You did not update the quote. You did not log it as a separate scope item. You just absorbed it and kept working.

At invoice time, you billed the original number. Because that is what the agreement said. And because by then you had already done the extra work and writing a new invoice felt awkward.

This is not a rare situation. It is the default pattern for most freelancers.

Why Mid-Project Changes Are the Hardest to Catch

Project kickoffs have structure. You quote, the client approves, work begins. But the middle of a project has no natural structure. Things shift. Scope grows in small increments. Each addition feels minor enough to absorb in the moment.

The problem is that minor additions compound. Three small scope changes across a four-week project might add up to eight hours you never planned for and never charged. That is real money left on the table, and you have no record that it happened.

The Note You Never Write

When a client emails mid-project with a small addition, most freelancers respond immediately and start the work. The request gets handled. The thread gets archived. And the connection between that request and your tracked hours disappears.

If you are using a time tracker, this is where a single habit saves you repeatedly. When you start work on something that was not in the original scope, log it under a separate entry and note the reason. "Blog archive review, added 2/14 per client request." That entry takes fifteen seconds. It gives you a searchable record of what changed and when.

At invoice time you can pull all entries flagged as additions and decide how to handle them. Sometimes you charge for them. Sometimes you offer one as a gesture of goodwill but document it anyway so the client knows the value. Either way, you are making a deliberate choice instead of just letting hours disappear.

When to Have the Estimate Conversation

Not every scope addition needs a formal change order. But every scope addition needs a conversation before the work starts, not after.

"That is doable. Before I add it to this week's work, I want to flag that it falls outside what I originally quoted. I can either fold it in and adjust the invoice or we can keep it separate. What works for you?"

That is not a confrontational message. It is a professional one. It tells the client that you track what you do and that additions are visible to you. Most clients respond well. The ones who do not were going to be a problem regardless.

How Your Logs Show You the Pattern

If you have been tracking time consistently, you can run a report at the end of any project and compare logged hours to the original estimate. When those numbers are far apart, that gap is worth understanding.

Some of it might be your own underestimation. Some of it might be legitimate scope additions. Some of it might be client-driven rework that you absorbed without question. The log does not lie. It shows you exactly where the time went.

Once you see the pattern across multiple projects, you stop being surprised by it. You start building buffers into estimates. You start flagging additions before you absorb them. You stop invoicing from memory and start invoicing from data.

The Invoice Is a Report

Every invoice you send is a reflection of how well you tracked what happened. If your tracking is loose in the middle of a project, your invoice will be loose too. And loose invoices undercharge.

Log the additions when they happen. Note the reason. Let the record catch what your memory will miss.

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