Business Tips
How to Say No to Extra Scope Using Last Week’s Time Data
Scope creep for freelancers does not usually arrive as a villain speech. It arrives as a reasonable sentence: “Can you also…?” on a Thursday, when you are already late, and when saying yes feels cheaper than a conflict. By invoice time the week has two personalities: the work you quoted and the work you performed.
You do not need a new personality to say no. You need last week’s numbers in a form a client can see without feeling surveilled. This is not tax or legal advice, and it is not a dare to be rude. It is a script that treats extra work as extra work — named, estimated, or declined — instead of as unpaid overlay on a task that was already too fat.
The working rule: if you cannot point at a task and a date range, you are negotiating from mood. Mood loses to a client who is not in a hurry. A report is slower to open than a Slack reply, and that delay is a feature.
Why “I’ll squeeze it in” is a pricing decision
Squeezing is how sticker rate and real hourly rate diverge. You still did the hours. You just refused to put them on a line the client has to acknowledge. That is a discount you did not invoice and a precedent you will be asked to repeat.
- Hourly projects: extra scope without a new task becomes a surprise total. The fight moves to Friday.
- Fixed-price projects: extra scope without a new task becomes a silent overrun. The fight moves to the retrospective you will never schedule.
- Retainers: extra scope without a capacity check becomes a retainer that is actually an all-you-can-eat buffet. See also how retainers fail when the week is not visible.
If you already use time data to decide which clients to keep, you already know the pattern. Saying no is the same data, earlier, while the relationship is still worth keeping.
Build the evidence before you need the sentence
You cannot summon a calm no from an empty timesheet. The week before the ask, do three unglamorous things:
- Name leaf work. “Website” is not a task. “Revisions R2 — homepage” is. Extra asks need a place to land that is not the original delivery task.
- Close or lock finished phases. If Discovery is done, stop letting new pixels accrue there. Locked tasks prevent further tracking — which makes “this is new work” visible instead of philosophical.
- Keep a report habit. One What × Who × When pass in the week (not only at invoice) so you know whether you are already over the hours you mentally sold.
If the project is fixed-price or a fat retainer, a tracker on the project or a critical task — estimate plus % milestone emails, or budget plus % of cost consumed — is how you notice 50% consumed with 80% of the wish list remaining. That is not a timer. That is a tripwire. The trackers guide is the setup; the script below is the conversation.
Do not send a client a surveillance vibe. Do not send screenshots of your desktop. Send a named task, a date range, and a number of hours (or a % of estimate). Adults can disagree about priority. They should not have to guess whether you are “being difficult.”
Scripts that use hours instead of adjectives
Pick the version that matches the contract. Replace the bracketed bits with last week’s report — clients or projects, optional tasks, a date range. Pivot by task if they will ask what the hours were for.
1. The delay (still a no to “this week”)
“I can do [extra page / extra revision round], and it is not in [Project X] as scoped. Last week I already tracked [N] hours on [task list]. If we add it this week I will miss [agreed delivery]. I can start it [date] as a new task, or we can swap it for [named item] still in the queue.”
2. The paid add (hourly or a new fixed chunk)
“That’s additional to [original task]. I estimate [range] and I would track it under a new task, [name]. If you want it this cycle, I’ll send the extra line on the next invoice from the same report I already use for [Project X]. If not, we leave it in the parking lot.”
3. The hard no (capacity or fit)
“I don’t have the hours. Last week’s billable time on your work was [N]; the rest of my week is already committed. I can refer someone, or we can put this on [next sprint / next month] after [current milestone] is closed.”
Notice what these scripts do not do: they do not apologize for having a calendar. They do not claim you are “at capacity” as a mood. They cite a week that already happened. If you cannot cite it, run the report first — What × Who × When — and then reply. The extra hour of delay is cheaper than a month of precedent.
Where extra work should live in the tree
If you say yes, do not put the new work on the old task “so the invoice stays simple.” Simple invoices that hide scope teach clients to keep asking. Use the hierarchy:
Workspace → Client → Project → Task → Subtask
New ask → new task (or a subtask under a clearly named Revisions phase). Time is tracked on the task. The invoice can still group by project.
- Designers: Revision R3 is a phase, not a feeling. If R2 was locked, R3 is a new yes.
- Developers: “Also make it work in Outlook” is not Implementation. It is a new task, possibly with its own estimate.
- Strategists: An extra workshop is not “the retainer.” It is a task with a date. If the retainer is already full, the tracker should have told you before the email.
Duplicate safeguards and clear names matter more than poetry. A 60-character project name is enough to keep “Website Redesign v2 (scope add)” from colliding with the original. Tasks can be closed so they stop collecting time. That closure is part of the no: the old container is full.
When the data says you should have said no last month
Sometimes you already did the extra work. Saying no going forward still needs a number: hours already spent versus estimate, or cost consumed versus budget. A post-mortem is allowed to be boring. The project audit post covers the after-the-fact version. This post is the during-the-fact version: answer while the extra ask is still a message, not a regret.
What to pull from MinuteShark before you reply
Open Reports. Set What (this client or project, optional tasks), Who (you), When (last week or this billing period). Generate. Look at the grand total and, if you use rounding, the BILLABLE total. Pivot by task. If you set a tracker on the project or a key task, check whether you have crossed a % of estimate or budget — those emails exist so you do not discover the overrun in the invoice preview.
If History is messy, fix the obvious wrong tasks first; then generate. If you want the invoice to show the extra work as its own line, it has to be its own task. Generate Invoice from the same report and a cost profile when you are actually billing — including extra flat or hourly lines for things that are not time. James P., Solo Consultant, said the bar: “Simple enough to use every day, powerful enough to trust.” Trust, here, is a number you can read aloud without flinching.
A 15-minute weekly pre-mortem so the no is ready
- Scan History for timers that outlived the meeting. Fix while you remember.
- One report for each active client (or one report pivoted by client). Circle anything already near the estimate.
- List the asks sitting in Slack that are not yet tasks. Either create the task and estimate it, or write the delay script now, before they ping again.
- If a tracker is near a milestone percentage, decide the sentence this week — not after the milestone email fires and you are already defensive. MinuteShark’s tracker emails are a tripwire, not a personality test.
Saying no is a freelance business skill, not a time-tracker feature. MinuteShark only makes the skill less theatrical: tasks you can name, a report you can cite, a tracker you can believe. You still have to send the message. Send it with last week attached.