Free ScopeDue tool

Freelance Change Request Generator

Use this change request generator when a client asks for extra work and you need a clear, priced approval record before the work continues. Add what changed, why it is outside the original scope, the price, timeline impact, and whether payment is required before work starts. You can copy the message now, then turn it into a client approval link in ScopeDue.

Tool page · Built for U.S. freelancers, solo studios, and small service providers

Scope
What changed from the original agreement.
Price
What the extra work costs before approval.
Payment rule
Whether payment is required before work.
Proof
What should be saved to the approval trail.
Keep it professional, not confrontational. A change request is not a legal threat. It is a clear business record that helps the client understand what changed, what it costs, and what must happen before you continue.

Interactive preview

Generate a client-ready change request

Fill in the basics below. The preview creates a calm message you can copy into email, send as a note, or save as a ScopeDue approval link. The generated text is useful before signup; saving a reusable approval trail happens inside ScopeDue.

Create approval link

Privacy note: avoid entering sensitive client, payment, or confidential project details into any public tool page. In a full ScopeDue workspace, client/project records should stay private and not be indexed as public pages.

Pain

Extra work starts from a vague message

A client asks for “one quick thing,” but the request adds a new deliverable, more revisions, or a different deadline. If you start from chat alone, the price and timeline can stay unclear.

ScopeDue workflow

Create the record before work starts

  1. Create a priced change request.
  2. Send the client approval link.
  3. Let the client approve, decline, or ask a question.
  4. Track payment if required before work.
  5. Save the approval and payment history.

What gets recorded

A clear approval trail

  • Change title and description
  • Original scope note
  • Price and timeline impact
  • Client approval status
  • Payment status and proof
  • Freelancer confirmation

Why this matters

Approved does not always mean ready to work

A clean change request should separate approval from payment. The client may approve the extra work, but if the request says payment is required before work starts, the change should remain approved but unpaid until payment is confirmed by the freelancer.

Status What it means Recommended next step
Draft The request is being written and has not been sent. Clarify scope, price, timeline impact, and payment rule.
Sent The client has the approval link but has not responded. Wait for approval, decline, or a client question.
Approved, payment required The client approved, but payment is still required before work. Use a payment ledger to track client marked paid, proof uploaded, and freelancer confirmed received.
Ready to start Required approval and payment conditions are complete. Start the extra work and keep the event history for the Proof Pack.

Quality checklist

Before you send a change request

Include these details

  • The exact extra work the client asked for.
  • The part of the original scope it changes or adds to.
  • The price, currency, and any tax/invoice note you normally use.
  • The timeline impact or delivery tradeoff.
  • The payment condition before work or handoff.
  • What happens after the client approves.

Avoid these mistakes

  • Do not start from “sure, I can do that” without a price.
  • Do not bury the cost in a long emotional explanation.
  • Do not let “client marked paid” count as final payment confirmation.
  • Do not promise that a change request guarantees payment or replaces legal advice.

Common freelancer situations

Use this generator when the client asks for extra work

Web design change

“Can you add another page?” Create a priced approval request with the page scope, cost, and launch impact.

Design revision

“Can we try one more version?” Turn the extra revision into a written approval instead of a vague favor.

Source file request

“Can you send the editable files?” Use a source file release request if the source files were not included.

  • extra page
  • new deliverable
  • rush change
  • third revision
  • source files
  • new export size
  • added copy
  • extra report

Use this when

The request changes scope, price, or timing

  • The client asks for a deliverable not listed in the original scope.
  • The client wants an extra revision round.
  • The change affects launch, handoff, or delivery timing.
  • You need payment confirmed before starting the extra work.

Do not use this as

A contract, legal opinion, or accounting system

ScopeDue helps create a clear business record of approvals, payment events, and handoff decisions. It is not a substitute for legal, tax, or accounting advice. For contract language, collections, taxes, or legal disputes, contact a qualified professional.

Read the product disclaimer.

Reusable message

Copyable change request structure

Firm-but-friendly version

Hi [Client Name],

I can help with [Change Request]. Since this is outside the currently approved scope, I created a short change request with the details, price, and timeline impact.

Please review and approve it here: [Approval Link]

Once it is approved and any required payment is confirmed, I’ll add it to the work queue.

For a fuller reusable script, use the freelance change request template. For a more general boundary response, try the scope creep email generator.

Create the record before work continues

The next client change should not live only in chat

Generate the message, send a client approval link, track the payment rule, and keep a clear Proof Pack trail for the change.

Questions

Change request generator FAQ

Is this the same as an invoice?

No. A change request explains what changed, the price, the timeline impact, and the approval/payment condition. An invoice may still be used for billing, while ScopeDue focuses on the approval trail and payment status history.

Can the client mark a request as paid?

The client can mark payment sent and upload proof, but the freelancer should confirm receipt before the item counts as paid. That keeps “client says paid” separate from “payment confirmed.”

Should I use this for every small change?

Use it when the request changes scope, cost, timing, handoff, or revision limits. For tiny included edits, a full priced request may not be necessary.

Does this replace a contract?

No. ScopeDue helps document approvals, payments, and handoff events as a business record. It does not replace legal, tax, or accounting advice.