Small extra asks add up faster than any one request looks.
11 min readWhy these requests are risky
One extra inbox. One quick report. One small edit.
Each one feels fine alone. Together they eat your week.
Clients often do not mean to abuse you. They forget what you agreed. You forget to push back. Nobody wrote it down.
That is how a 20-hour retainer becomes 35 hours at the same rate.
What "while you are at it" usually means
| Phrase | What they might really want |
|---|---|
| "While you are at it..." | A new task bundled with current work |
| "Can you also..." | Scope growth without a rate talk |
| "This should be quick" | Your time treated as free |
| "Just one more thing" | A pattern starting |
If it was not in your kickoff email or contract, treat it as out of scope until you confirm.
What to do in the moment
- Pause. Do not auto-yes on Slack.
- Check your scope doc. What did you both agree on?
- Reply with options. In scope swap, change order, or next cycle.
- Wait for written OK before you start the extra.
- Log it. Note date, ask, and what you agreed.
This takes two minutes. Skipping it costs hours.
Scripts you can copy
First time (friendly)
Thanks for this. Our current scope covers [list]. [New task] is outside that. I can add it at [rate], swap it for [other task] this week, or slot it for [date]. Which works?
Second or third time (pattern forming)
I want to keep things smooth. We have had a few adds lately ([list]). Going forward, anything outside [scope doc] needs a quick written OK before I start. Happy to send options for [new ask].
When they say it is small
Small tasks add up on a retainer. I can do it if we reprioritize, or I can quote [time] at [rate].
See also out-of-scope request scripts for more copy-paste lines.
GUARD Protocol in plain terms
Salag's GUARD Protocol is a simple five-step habit:
- Capture what was asked and by whom.
- Compare to your written agreement.
- Name tradeoffs (time, cost, what slips).
- Confirm in email before work.
- Archive the decision in your project folder.
You are not being difficult. You are being clear.
Common mistakes
| Mistake | What happens |
|---|---|
| Saying yes to avoid awkwardness | Client learns your time is free |
| No written scope at kickoff | Nothing to point to later |
| Invoicing surprise extras | Trust drops fast |
| Arguing in chat without facts | You look reactive, not pro |
How Salag helps
- Request Clarifier: turn vague asks into clear written tasks.
- Client Red Flag Checklist: spot patterns before they grow.
- Payment Method Risk Check: know how you get paid if scope fights start.
Structure keeps good projects on track.
Move safer. Not faster.
In short
"While you are at it" sounds small. It rarely is.
When a client adds a task that way, stop and check your written scope. Acknowledge the ask, say what is already included, and offer a path: swap priorities, bill extra, or schedule it later. Confirm in email before you do the work.
Common questions
"While you are at it" sounds small. It rarely is. When a client adds a task that way, stop and check your written scope. Acknowledge the ask, say what is already included, and offer a path: swap priorities, bill extra, or schedule it later. Confirm in email before you do the work.
Write down what they asked, what you already agreed, and what is new. Do not start until the extra work is clear.
Stay polite and clear. Send a short email that lists what is in scope and what is extra. Good clients respect that.
For project work, yes. Put tasks and limits in your agreement or kickoff email before you bill hours. Bigger jobs need fuller terms.
Offer choices: swap tasks, add a change order, or move the extra to next week. Structure helps you both, not just you.
GUARD means: capture facts, check your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
When extras keep coming unpaid, approvals stall, or they will not confirm in writing. Escalate means document, not argue.
Yes. A short email with task, timeline, price, and limits beats a verbal yes every time.
Salag has tools like the scope creep detector and agreement builder so you catch extras before they pile up.
Use written scope, change orders, and Salag tools like the request clarifier and scope creep detector.
About five minutes after a call. That small step saves hours of fights later.
Yes. Retainers need a weekly task list and hour cap. Projects need milestone gates. Check every new ask against what is written.
Pause the extra work. Send a one-line summary of what you will do and wait for reply. Save the thread.