How to Handle Verbal Scope That Never Made It Into the Contract

You are on a call. The client mentions something they want included. You nod. You might even say sure. Nobody writes it down. It does not make it into the contract or the project brief.

Four weeks later, they ask where that thing is. And now you have a problem.

Verbal scope is the source of more billing disputes than almost anything else in freelance work. Not because clients are dishonest, but because memory is unreliable and nothing was ever agreed in writing.

Why This Keeps Happening

Initial calls move fast. Clients mention ideas, preferences, and possibilities. Some of those are actual requirements. Some are thinking out loud. In the moment, neither party is clear on which is which.

You are trying to build rapport and show that you understand the project. You are not stopping to say, is that a formal requirement? You just absorb it and move on.

The problem is that clients absorb it differently. They leave the call thinking that thing is included. You leave the call thinking it was a nice idea that might come up later.

The Simple Habit That Prevents Most of It

After every client call, send a short follow-up email. Not a formal document. Just a few sentences. Something like: good call today. To recap, we agreed on these three deliverables. I will start with phase one next week.

That email does not have to cover everything. It just has to cover the things most likely to be misremembered. If something came up verbally that is not in the contract, this is the moment to either confirm it or flag it as out of scope.

The client does not need to reply. The fact that you sent it and they did not correct it creates a reasonable record of what was understood at that point.

When the Dispute Has Already Started

If a client is already citing something you never documented, stay calm. Do not get defensive. Ask them to point you to where that was confirmed in writing. Most of the time, they cannot. That does not end the conversation, but it shifts the footing.

Then go to your time logs. What work have you actually completed? What does your tracked time show in terms of phases and tasks? A clean time record helps here because it shows the client a picture of what was worked on and in what order. If the disputed item was never logged, that is a data point.

You may still have to make a judgment call about whether to absorb the work or charge for it. But you are making that call from a position of information rather than panic.

How to Protect Yourself Going Forward

Get comfortable saying let me add that to the scope document before we confirm it. You can be warm about it. You can even frame it as protecting the client. If it is in writing, there is no confusion later and we can both move forward with clarity.

Most clients appreciate this. The ones who push back on written scope confirmation are the ones who benefit from keeping things vague, and that is useful information.

Also consider tracking time from the very first call. Discovery and proposal time often gets lost, but it sets the frame for the entire project. If you have a time entry for the initial call with a note summarizing what was discussed, that log becomes part of your record even if it never made it into the contract.

The Bigger Pattern to Watch

If verbal scope disputes are happening more than once with the same client, that is a pattern, not a coincidence. Some clients habitually expand projects through conversation because they have learned that freelancers will absorb it.

Your time data will show this. If hours are climbing without corresponding change orders or invoice updates, the verbal scope is leaking into your work and not into your billing. That is the moment to have a direct conversation about process, not just the specific disputed item.

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