Scope creep almost never shows up as a big ask. It's "one quick tweak," then another, then a new page nobody priced. The fix isn't saying no more often. It's having a calm, repeatable way to turn extra requests into paid work. Here's the process I use.
1. Write scope as a list, not a paragraph
Vague scope ("website redesign") invites creep. A numbered list doesn't:
- 5 page templates (Home, About, Services, Blog index, Contact)
- 2 rounds of revisions per template
- Launch support for 7 days after go-live
Add one line most people skip: "Anything not listed here is quoted separately."
2. Name revision rounds and what counts as one
"Two rounds of revisions" means nothing until you define a round: one consolidated list of feedback, delivered at once. Five emails over three days is still one round only if you say so up front.
3. Use a neutral script when a new request lands
Happy to do that! It's outside the original scope, so I'll send a quick change order with the cost and timeline. Once you approve it, I'll slot it in.
No apology, no debate about whether it's "small." You're just routing it to the right process.
4. Send a one-page change order
Keep it short so it's easy to approve:
- Request: add a pricing page
- Cost: $450 (fixed)
- Timeline impact: launch moves from May 3 to May 7
- Approval: reply "approved" to this email
Clients rarely push back on a clear number. They push back on surprises at invoice time.
5. Track everything in one log
A simple table (date, request, status, cost, approved by) ends the "but you said it was included" argument, and it shows you which clients creep the most so you can price them properly next time.
Want the templates?
I packaged a scope baseline, a change-request triage guide, an impact brief, trade-off options, client email scripts, a revision log, and a one-page approval form as the Scope & Change Order Kit ($19, instant download): https://buy.stripe.com/dRm6oIbQdfPIgf68hUfEk02
There's also a free scope-creep guide at https://opspack.vercel.app/scope-creep, and the full set of freelance ops kits lives at https://opspack.vercel.app.
Top comments (2)
The line about defining what counts as a round is the one that saves me most. One thing I'd add: when you send the change order, state the timeline impact the same way you did here, because clients tend to accept the price faster once they see the launch date move. I also like to send the revised date even for small extras, so "quick tweaks" stop feeling free. And if a client keeps approving change orders without pushback, that's usually a sign the original quote was too tight, so it's worth pricing the next project with a bit more buffer.
What stops the quick-tweak pile-up for us is batching: small extras go on a running list and get quoted together once a week, so the client sees the total instead of approving five small changes nobody questions. It also keeps the log in step 5 honest.