Start with the project fact
Before responding, compare the request with the written deliverables, exclusions, revision rules, and approval history. A neutral fact is stronger than a feeling that the client is asking too much.
- Find the approved scope
- Identify the exact difference
- Estimate effort and schedule effect
- Decide which options you can offer
Make the change visible
Use plain language to state what changed and what happens next. Avoid accusations and long justifications. The client needs a decision they can understand: swap work, add it for a fee, move it to a later phase, or keep the original plan.
Document the decision
Record the request, fee, timing impact, and approval in the same place as the current project plan. This prevents memory disputes and helps new stakeholders understand why the schedule or budget changed.
Worked scenario
A client asks for an additional deliverable after approving the current phase. The request sounds minor, but it changes the work, review time, and delivery sequence. The freelancer checks the agreement before replying instead of deciding from memory.
I can help with that. The approved scope currently covers [included work], while this request adds [new work]. I can add it for [fee], with delivery moving to [date], or we can swap [existing item] to keep the current plan. Which option works best?
Action plan
- Locate the latest approved scope and decision history
- Describe the exact difference in one sentence
- Estimate production, review, and schedule impact
- Offer no more than three concrete options
- Record approval before updating the project plan
Completion checklist
- The original scope is quoted accurately
- The request is described without blame
- Fee and timing are both visible
- The approver and approval channel are clear
- The project plan reflects the final decision
Frequently asked questions
- What is the first step when handling scope creep retainer?
- Return to the approved scope and identify the exact difference before discussing price or responsibility.
- Do I need a formal document?
- Not always. A clear written message can be enough for a small request, provided it includes impact and approval.
Continue with the next decision
Client boundaries for freelancers
Boundaries are not about saying no; they are sequencing and communication rules that keep projects predictable. This pillar covers revisions, availability, approvals, and hard conversations.
Free editable artifactOut-of-Scope Email Template for Freelancers
An out-of-scope email identifies the difference between the approved deliverable and a new request, then offers a priced addition, a scope swap, or a later phase. Send it before starting the extra work and retain written approval.
Next stepScopeShield Toolkit — $39
Review the editable text inventory, what it does, and what it does not do before buying.