The Revision You Approved Without a Change Order

How It Starts

The client sends feedback. It's reasonable. You read it and think, "This is only going to take an hour, I'll just do it."

You don't create a change order. You don't log it as a separate scope item. You open the file, do the work, and move on.

That's not generosity. That's an undocumented cost you absorbed.

The Issue Is the Pattern, Not the Instance

A single absorbed revision probably won't break a project. But freelancers who say yes without a change order once will say yes without a change order twenty times on the same project.

The client learns that revisions are included. You never said they were, but your behavior confirmed it. By the third or fourth round, you have a client who expects unlimited refinement and a project that no longer resembles the one you quoted.

The billing records show the original invoice. They don't show the six hours of post-close revision you absorbed over three weeks.

Your Time Log Sees What Your Inbox Doesn't

Email threads make everything feel conversational. A revision request buried in a long thread doesn't look like a billing event. It looks like a message you need to respond to.

Your time tracker doesn't make that distinction. It records hours. When you log a session tagged to a project that you've already invoiced, that entry is a signal.

At the end of the month, if you run a report and see four hours of logged time on a closed project, that's four hours of uncompensated work you did after the final invoice. That's not hypothetical. That's a real number you can see.

What a Change Order Actually Does

A change order is not an aggressive document. It's a clarification.

It says: this is outside the original scope, here's what it covers, here's the cost, let's confirm before I start.

Most clients who are acting in good faith will not object. They may not even realize the revision was outside scope. The change order makes that visible to both of you at the right time, before the work happens, not after.

Clients who object to every change order are telling you something about the relationship. That's useful information to have.

How to Build the Habit

The simplest version of this habit has two steps.

First, keep the timer running on everything. If you touch a project, log it. Don't make exceptions for small favors. If you log it, you can see it. If you can't see it, it doesn't exist in your billing record.

Second, before you start any session on a project you've already invoiced, ask yourself one question: is this covered? If yes, log it and work. If no, send a one-paragraph change order first.

The change order doesn't have to be formal. It can be a short email. "Hey, I want to flag that this revision is outside our original scope. Happy to take it on. Here's the additional cost. Let me know and I'll get started."

That sentence takes two minutes to write. It can recover hundreds of dollars per project.

Screenshots Help Document the Extra Work

If a client ever questions why they're seeing a change order for something they thought was included, your time log and screenshots give you a clear record. You can show when the original project closed, when the new session started, and what was being worked on during that session.

That's not a fight. That's a transparent record that protects both parties.

The Real Cost of the Unbilled Revision

You don't feel the cost of one absorbed revision. You feel the cost of forty of them across a year.

That's the money that should have been in your invoices and wasn't. That's the margin that disappeared because yes was easier than a two-minute email.

Track everything. Log after close. Send the change order. Your future self will have a better rate than your past self did.

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