Skip to content
ScopeShield

Practical guide

A Simple Client Change Request Process for Freelancers

A change process makes additions visible without burying a small project in paperwork.

By ScopeShield EditorialPublished 2026-07-26Reviewed 2026-07-26Practical guidance; no fabricated ratings

Direct answer

What you need to know

A change process makes additions visible without burying a small project in paperwork.

Key takeaways

  • Start with the project fact
  • Make the change visible
  • Document the decision

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.

A response you can adapt
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

  1. Locate the latest approved scope and decision history
  2. Describe the exact difference in one sentence
  3. Estimate production, review, and schedule impact
  4. Offer no more than three concrete options
  5. 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

Put this guide into practice

  • Apply “Start with the project fact” to one active or upcoming client project.
  • Apply “Make the change visible” to one active or upcoming client project.
  • Apply “Document the decision” to one active or upcoming client project.

Frequently asked questions

What is the first step when handling client change request process?

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 through this topic

Pillar guide

Change requests and change control

A change process is what turns scope creep into billable, approved work. This pillar covers documenting requests, pricing them, getting approval, and controlling change over the life of a project.

Free template

Out-of-Scope Email Template

A ready-to-customize out of scope email template with practical guidance for using it professionally and keeping the client relationship intact.

Educational information only; not legal advice. Review contract language for your jurisdiction and circumstances.

ScopeShield

$39 · instant access