Scope creep rarely starts with a dramatic request. It’s often one extra field, one more version, or another review round. The request itself isn’t the problem; the problem is doing it before both sides agree what changes.
A simple habit helps:
- Check the request against the latest approved scope. Separate a clarification or correction from a new deliverable or revision.
- Name the change plainly: what’s being added, how many revisions it involves, and whether it affects timing or dependencies.
- Offer clear options: swap it for something already in scope, add it for an agreed fee and schedule, or move it to a later phase.
- Get written approval before starting, then update the project record.
A reply could be:
“Thanks for asking. I checked this against [scope/version]. [Request] is outside [agreed item]. I can swap it for [item] within the current plan, add it for [fee] and move delivery to [date], or put it in a later phase. Which works best? I’ll update the plan once we agree.”
This isn’t about turning every small request into bureaucracy. It’s about making the trade-off clear before either person is surprised.
Disclosure: I sell a project-boundaries toolkit on Gumroad. Its free 2-page sample includes a client email, a change-request record, and a checklist. It’s an educational workflow aid, not a contract or legal advice.
Top comments (2)
The part that saves me most is the last step, updating the project record. I keep a simple log with one line per request: the date, what was asked, the estimate in hours and cost, and the date the client approved it. When a client later says they thought something was included, I can point to the line instead of arguing from memory. It also helps to flag a new request as a change the same day it comes in, because the longer you wait, the more it feels like part of the original job.
That’s a solid system—especially logging the request the same day. I’d add a simple status (pending, approved, or declined) and a link to the client’s written approval, so the record makes clear what was discussed versus what was authorized. Even a shared spreadsheet is enough.