ArticlesScope

Scope Creep: Change-Request Email Template (AU Freelancers)

Affiliate disclosure: This article may contain affiliate links (including Amazon Associates) and links to products sold by the site owner (Andrew / NDYT on Gumroad). As an Amazon Associate I earn from qualifying purchases. If you buy through affiliate links, we may earn a commission at no extra cost to you. This is not financial, tax, or legal advice.

Scope creep is usually an unpriced change wearing a friendly sentence: “While you’re in there, could you also…?” The fix is not a defensive speech. It is a short change request that records what changed, the effect on price and timing, and the approval needed before work starts.

Spot the change before you absorb it

Pause when the request adds a deliverable, audience, revision round, integration, meeting, or turnaround pressure that was not in the original brief. A small request still counts if it displaces booked work or creates a new acceptance test.

  • Compare the message with the signed proposal, SOW, or pricing one-pager.
  • Reply with acknowledgement, not an instant promise: “I’ll check the impact and come back with options.”
  • Record the request before discussing the solution in a scattered chat thread.

Three clean options

OptionUse whenWhat changes
SwapClient has a fixed budgetNew item replaces an existing item
AddBoth parties want the extra workPrice and/or milestone increases
DeferIt is useful but not urgentMove it to a later phase or retainer

Do not start the changed work until the option, price, and revised date are approved in writing. If the original project is not yet paid to start, use the deposit workflow before adding effort.

Copy-and-paste change-request email

Subject: Change request — [project] — [new item]

Hi [Name],

Thanks — I can add [plain-English description of request]. It is outside the current [proposal / SOW] because the agreed scope is [one-line boundary].

Here are the options:

A. Add: A$[amount] + [x] business days; revised delivery [date].
B. Swap: I can replace [existing item] with [new item] at the current fee; delivery remains [date].
C. Defer: I can quote this as phase two after [current milestone].

Reply with A, B, or C and I will update the change note. I will start the additional work once the option is approved in writing and, for option A, the additional invoice / deposit is arranged.

Thanks,
[Your name]

If the client says “it should be quick”

“It may be quick to discuss, but it adds a deliverable and a new acceptance check. I can either swap it for [existing item] or add A$[amount] and [x] business days. Which option works?”

If you already started the extra work

Do not pretend the ambiguity is free. Send a reset note while the facts are fresh:

“I started [item] based on our message, then noticed it changes the agreed deliverables. To keep us aligned, I have logged it as change CR-02: A$[amount] and [x] business days, or a swap for [item]. Please confirm the preferred option before I take it through final delivery.”

For a repeated pattern, pause new work and have the client approve a short SOW addendum. Large or disputed changes deserve contract and legal advice, not a stronger email.

A lightweight Notion change-request log

  • ID, date requested, client, and link to the original message
  • Request, in-scope boundary, and affected deliverable
  • Option: Swap / Add / Defer; price; hours; revised date
  • Status: Captured / Quoted / Awaiting approval / Approved / Delivered
  • Approval date, invoice number, and acceptance note

Link each change to the project and invoice. Your client onboarding checklist should point to the same source of truth, so the kickoff promise and the later request do not drift apart.

Keep the cash and delivery loop closed

Owned products

Do this today: make “swap, add, or defer” your default reply, then create one change-request row for the next extra ask instead of answering from memory.

Not legal, tax, or financial advice. For material contract changes or disputes, consult a qualified adviser.