The Scope Question You Forget to Ask at the Start

You ask about the deadline. You ask about the budget. You ask who the decision-maker is and what success looks like. These are good questions. You have learned them from experience.

But there is one question most freelancers skip, and it is the one that determines whether the project stays the size it was quoted or quietly doubles by the time you close it out.

The question is this: what does done actually mean to you?

Why This Question Matters More Than the Brief

Clients write briefs from their best-case version of the project. Everything in the brief assumes smooth handoffs, quick approvals, and clear feedback. The brief does not account for what happens when the stakeholder changes their mind, or when a third party needs to sign off, or when the client says the word "just" before adding something significant.

If you start work without a shared definition of done, you are building on a foundation neither of you has actually agreed to. You are both working from a different mental model of the finish line.

This is where scope creep begins. Not in bad faith. In ambiguity.

What the Question Surfaces

When you ask a client to describe what done looks like in concrete terms, a few things happen.

Some clients immediately clarify details they had not mentioned in the brief. New stakeholders appear. An extra deliverable surfaces. A review process comes up that adds two rounds you had not priced.

Other clients struggle to answer because they have not actually thought it through yet. That is important information. It means the project is not ready to start, or that you need to build more discovery time into the estimate.

Either way, you learn something that protects you.

How to Track This From Day One

Once you have a shared definition of done, your time tracking structure should reflect it. Set up your project with phases or categories that map directly to the agreed deliverables. If something comes in that does not fit any of those categories, that is your signal that the scope has shifted.

Log everything from the first day. Not just deep work time. Meetings, feedback reviews, revision rounds, clarification calls. All of it. A floating timer helps with this because you can start it before a call, not ten minutes after you hang up when you have already lost track of how long it ran.

When scope creep does happen, and it usually does even on well-defined projects, you have a clean record. You can show exactly when the new work appeared and how many hours it consumed. That is a much easier conversation than trying to reconstruct what happened from memory three weeks later.

Revisions Are the Most Common Trap

The brief will often say something like "two rounds of revisions included." But it almost never defines what a revision round is. Is a revision round one set of consolidated feedback? Or does each comment count separately? What happens if the client sends feedback, you implement it, and then they revisit something from round one?

Ask this at the start. Write it down. Put it in the contract.

When you have a time tracker capturing every revision session with timestamps and screenshots, you can show exactly what happened in each round. That removes the gray area from the conversation.

The Ten Minutes That Saves the Project

Asking the done question takes ten minutes at the start. So does setting up your project structure in your time tracker before work begins.

Those ten minutes tend to return themselves many times over by the time you send the final invoice. Not because the project runs perfectly, but because you have the data to know what changed and the documentation to support whatever conversation needs to happen.

The scope you agreed to at the start is only protected if you can see exactly where it ended and something else began.

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