Digital Product Power Factory

Change request template

Document extra client work before it becomes unpaid scope creep.

Use this structure when a client asks for an extra revision, a late change, a new page, another feature or a faster deadline.

ScopeWise Studio screenshot showing a project scope and change request workflow

Search intent

A change request is a written pause before extra work starts.

Freelancers need a change request when the client asks for work that was not part of the original agreement. The goal is not to sound defensive. The goal is to make the business decision visible before the work begins: what changed, why it is outside scope, what it costs and how it affects delivery.

Template

Copy this structure into your next client change request.

1. Requested change

Write the request in plain language: what is being added, removed, revised or accelerated.

2. Original scope reference

Point to the approved proposal, statement of work, brief, ticket or email that set the original deliverable.

3. Why it is outside scope

Explain the difference calmly: new deliverable, extra revision, changed requirement, new dependency or compressed timeline.

4. Price impact

List the additional fee, estimate range or decision needed before the work starts.

5. Timeline impact

State the current delivery date, the proposed new date and any dependency that could change the schedule.

6. Written approval

Ask for a written yes before starting. A short reply is enough if it clearly accepts price and schedule impact.

Example

A practical change request keeps the client conversation calm.

Instead of saying no, document the impact and ask for approval. That keeps the project collaborative while protecting your time.

Requested change

Add two extra landing page sections after the approved page scope.

Impact before approval

Extra work: 3.5 hours. Timeline impact: one additional working day. Price impact: requires written approval before work starts.

When to use it

Use a change request whenever the project decision changes.

  • A client asks for extra revisions after the included rounds are used.
  • A new page, feature, deliverable or service is added.
  • The deadline moves earlier and requires rescheduling other work.
  • The client changes a dependency after the project has started.
  • The approved scope was vague and the new request needs clarification before work continues.

Free download

Get the full Scope Creep Prevention Kit.

The free kit includes the checklist, included/excluded worksheet, change request template, client email wording, price/timeline impact sheet, quick guide, license and disclaimer.

Manual kit: copy-ready templates ScopeWise: offline workspace for repeat use No aggressive upsell or artificial scarcity