Calm language routes extras through your change process.
11 min readScript 1: first time
Thanks for sending this over. Our agreed scope covers [list]. [New request] sits outside that. I can add it at [rate/hours], swap it for [task] this week, or schedule for [date]. Which works best?
Script 2: pattern forming
I want to keep delivery smooth. We have had a few adds this month ([list]). Going forward, anything outside [scope doc dated X] needs a quick written OK before I start. Happy to send options for [new ask].
Script 3: deadline squeeze
I can hit [original deadline] for [in-scope work]. [New ask] needs about [X hours]. If we do both, something slips or we add rush terms. Which priority should I use?
Script 4: "I thought that was included"
I hear you. Our kickoff email on [date] listed [scope]. [New item] was not on that list. I can add it at [rate] or we can do a 15-minute scope sync so we are aligned going forward.
Script 5: Slack ping (short)
Logging this. [Ask] is outside current scope. OK to add via change order or swap for [task]?
FRAME reminder
Facts Reference scope Assess hours Message options Execute after confirm
Full guide: VA scope creep.
Common mistakes
| Mistake | Fix |
|---|---|
| Long apology | Three sentences |
| Yes in chat, fight in invoice | Confirm first |
| No scope link in thread | Reply on kickoff thread |
| Angry tone | Options always |
How Salag helps
- Agreement Builder: scope to reference in scripts.
- Rate Calculator: numbers for change orders.
- Request Clarifier: clarify vague asks before quoting.
Move safer. Not faster.
In short
Copy-paste beats blank-page panic. These scripts say no without sounding mean. Always offer options: swap, bill extra, or schedule later.
Confirm in writing before extra work.
Common questions
Copy-paste beats blank-page panic. These scripts say no without sounding mean. Always offer options: swap, bill extra, or schedule later. Confirm in writing before extra work.
Pause. Open scope doc. Reply with acknowledge + options, not instant yes.
Polite English, same email thread as original scope. Facts beat feelings.
Change process line in scope makes scripts expected, not surprise.
Repeat options calmly. Pattern forming script on repeat asks.
Facts, Reference, Assess, Message, Execute after confirm. Maps to scripts.
Third unpaid extra in a month. Firm change order rule.
Yes. Script replies are documentation.
Scope creep detector before you paste script.
Saved snippets, scope doc, change order template.
Two minutes to paste and edit brackets.
Retainer: swap priority script. Project: change order script.
Do not do extra until OK in writing.