Scope creep and change requests: how to handle extra work as a freelancer (with a change order to copy)

Scope creep is the slow pile-up of "can you just…" requests that weren't in the job you priced. Here's how to spot it early, what a change request and a change order are, what to put in a change order, how to re-quote extra work on fixed-price and hourly jobs, how to keep track of what the client approved, and email and change-order wording you can copy.

The few legal rules mentioned (written-contract laws in New York City, New York State and Illinois) were checked against official pages on 2026-10-13. What scope creep, change requests and change orders mean, and the advice here, is general practice, not something those pages define. Not written by a lawyer.

The short answer

• Scope creep is extra work that drifts into a project without an agreed change to the price or the dates. It's easiest to stop when the original scope is countable and lists what isn't included (see our guide to writing a proposal).
• When a request is outside the scope, say so kindly and give options: add it with a price and a new date, swap it for something of the same size, or park it for later.
• Put an agreed change in a short change order: what's added or removed, the price, how it's invoiced, the new delivery date, and the client's approval, before you start the extra work.
• Fixed-price jobs get a price for the change and a new total; hourly jobs get an estimate of the extra hours at the agreed rate, so the client isn't surprised by the invoice.
• Keep a simple change log and the client's written approval with the original agreement. In some places a written contract is required by law: for example New York City for freelance work worth $800 or more (counting all work for the same client over 120 days) and Illinois for work worth $500 or more in a 120-day period (NYC DCWP; Illinois DOL), so a change can tip a small job over the line.

1. What scope creep is (and isn't)

"Scope" is the work you agreed to do for the price and dates you agreed. Scope creep is when that work grows without the price or dates growing with it, usually one small, reasonable-sounding request at a time: "one more round of changes", "a quick extra page", "can you also send it as a…". Each one is small; together they can add days to a job you priced as a whole.

Not every change is creep. Clients are allowed to change their minds, and many good projects change as they go. The difference is whether the change is agreed, with its effect on price and time, or just absorbed. A change you agree to do for free, on purpose, is a favour; it only becomes creep when nobody decided.

2. How to spot it early

Signs a project is drifting past what you agreed:

• New words in requests: "also", "while you're at it", "just", "quick", "small tweak", "one last thing".
• Revision rounds that don't end: feedback arriving in pieces from different people, or new comments on parts already signed off.
• New people joining with their own wish list after the scope was agreed.
• Deliverables changing shape: a different format, extra sizes or versions, a second language, more pages or items than you counted.
• Work outside your role: being asked to write the copy, source the photos, set up hosting or manage someone else's supplier.
• Your hours running ahead of the plan, even though nothing big has been added. Logging time on fixed-price work too (our free timesheet does this) shows it early.
• Late inputs: content, access or feedback arriving after the date your timeline depends on.

The fix is the same each time: compare the request with the written scope. If it's in, do it. If it isn't, or you can't tell, treat it as a change request.

3. Change request or change order?

The words are used loosely, and neither is an official term on the pages we read. A common reading:

• Change request: the client asking for something different or extra. It can be an email, a call or a comment on a draft. On its own, it doesn't change the deal.
• Change order (also called a change note, variation or contract amendment): the short written record of a change you've both agreed: what changes, what it costs, how the dates move, and the client's approval. It adds to your original proposal or contract rather than replacing it.
• A new project: when the request is big or different enough, quote it as a separate job with its own proposal, rather than stretching the old one.

Your original proposal or contract should say how changes work. Our proposal outline has a "Changes" section: changes agreed in writing (email is fine) with their price and effect on the timeline, before the extra work starts.

4. What to put in a change order

Keep it to one page, or a short email. These parts cover most freelance changes:

A ready-to-fill version is in section 9.

5. Re-quoting the extra work

1. Restate the request in your own words, counted, and ask the client to confirm you've understood it.
2. Check what it touches: a "small" change to one part can mean re-doing parts that were finished. Price the knock-on work too.
3. Price it the way the job is priced (see section 6), at the rate in your original agreement unless it said otherwise. Our hourly rate calculator and free quote generator help with the numbers and a printable quote.
4. Work out the new dates, including anything you now need from the client.
5. Send the change order with options where you can: add it, swap something out, or park it for a later phase.
6. Wait for the approval before you start the extra work, and log the change (see section 7).

If the change is urgent, say what you can start on now (the parts already in scope) while the client decides, rather than starting the extra work on trust.

6. Fixed price or hourly: adjusting the price

How you adjust depends on how the job was priced. The examples use our own made-up numbers (any currency), not a rate or a recommendation:

• Hourly work creeps too. The client pays for every hour, but an invoice far above the estimate is a shock. Re-estimate in writing whenever the work grows.
• Tax. If you charge sales tax, VAT or GST/HST, say whether the change price includes or excludes it. If the extra work is a different kind of service from the original job, check with your accountant how it's taxed.
• Payment terms for the change normally follow the original agreement; if not, say so. Our invoice payment terms guide explains deposits, milestones and due dates.

7. Tracking extra work and approvals

A change log is a simple list, one row per change. These columns (our suggestion, not a rule) cover most projects:

• Get the approval in writing, even if it's a one-word email reply. If the client agreed on a call or in a meeting, send a short confirmation (in section 9) the same day.
• Keep it with the original agreement: the proposal or contract, each change order, and the approvals, in one folder per project. New York City's page on its freelance law, for example, says: "You and the hiring party must keep a copy of the written contract." (NYC DCWP).
• Log the hours for each change separately (a note or project code is enough), so you can see what the change really took and bill it.
• Bill it as agreed: show the change as its own line on the invoice with its change number, so the client's accounts team can match it. Our free invoice generator prints one in any currency.

8. Where written-contract laws come in

None of the official pages we read mention change orders as such, but some places require freelance agreements to be in writing, and a change can be part of that agreement. A few official examples, read on 2026-10-13:

• Changes add up. New York City counts all agreements with the same hiring party over 120 days, and Illinois counts the value of the work over a 120-day period, so several small changes, or a change added to a small job, can bring the total to the point where a written contract is required.
• Write the change so it fits the list. Where one of these laws applies, a change order that states the work, the pay and when it's paid (and, for Illinois, the dates of the work) keeps the written agreement complete.

These are examples, not a full list. We haven't checked other US states, Canadian provinces or other countries for this page. Consumer clients (people buying for themselves) often have extra rights; check your local consumer rules if you work for individuals.

9. Wording you can copy

Paste these into your email or document, replace everything in [brackets], and delete what doesn't apply.

Replying to a request that's outside the scope:

Subject: Re: [their subject]

Hi [first name],

Happy to help with [the new request]. It isn't part of the scope we agreed on [date of the proposal or contract], so here are the options:

- Add it: I'll send a short change order with the price and how it moves the delivery date. Nothing changes until you approve it.
- Swap it: we drop [an item of similar size] and do this instead, at no extra cost.
- Park it: we finish the current scope first, and I'll quote this as a separate piece of work afterwards.

Which would you prefer?

[Your name]

The change order:

CHANGE ORDER [change number] to [proposal / contract / quote number]
Project: [project name]    Client: [client name, company]    Date: [date]

What's changing
- Add: [what you'll do, counted: pages, rounds, hours, items]
- Remove: [anything dropped to make room, or "nothing"]
- Not included: [what this change still doesn't cover]

Price
- Pricing: [fixed price for this change / estimated hours at the agreed rate / no charge]
- Price of this change: [amount and currency], [plus or including sales tax, VAT or GST/HST]
- New project total: [amount], previously [amount]
- Invoiced: [with the next invoice / on its own invoice / with the final invoice]

Timeline
- New delivery date: [date], previously [date]
- Depends on: [content, access or feedback the client provides, and by when]

Everything else in the original [proposal / contract] stays the same.

Approved by: ____________________   Name: ____________________   Date: __________
(Or reply "Approved" to the email this came with.)

The signature line is optional. Whether a reply such as "Approved" is enough depends on the law where you and the client are; where a law requires a written contract, make sure the change order has everything that law lists (section 8).

Confirming an approval given by phone, chat or in a meeting:

Subject: Change order [change number] for [project name]: approved

Hi [first name],

Thanks for approving the change on [day]. To confirm what we agreed:

- Change: [one line on what's added or removed]
- Price: [amount and currency], invoiced [when]
- New delivery date: [date]

The rest of the [proposal / contract] is unchanged. If I've got any of this wrong, reply and I'll correct it before I start on it.

[Your name]

A small favour you do free, without making it the new normal:

Hi [first name],

I've made [the small change] as a one-off, at no charge. For anything else outside the scope we agreed, I'll send a short change order first, with the price and timing, so there are no surprises.

[Your name]

10. Checklist

• Before the job: the scope is countable, lists what isn't included, and says how changes are agreed and priced.
• When a request comes in: compare it with the written scope. In scope? Do it. Not sure? Ask, in writing.
• Outside the scope: reply with options (add, swap or park), not a flat no or a silent yes.
• Price it the way the job is priced, including knock-on work, tax and the new dates.
• Send a change order with a reference, what changes, price, invoicing, timeline and approval.
• Wait for the written approval before starting; confirm by email anything agreed out loud.
• Log it: change number, dates, price, status, who approved, and the hours it took.
• Bill it as its own line, with its change number, on the invoice you agreed.
• Check the law if you or the client are somewhere that requires written freelance contracts (section 8).

Free tools and kits

• Free quote and estimate generator: price a change as its own quote with a valid-until date and a printable PDF (runs in your browser; nothing is saved).
• Free timesheet: log the hours a change takes, separately from the original scope.
• Free invoice generator: bill the approved change as its own line.
• Freelance hourly rate calculator: the rate behind the price.
• Our paid Quote & Proposal Kit by Small Rows (US$12, one-time) prices a change from the same rate list as your original quote, prints it as its own short quote with a valid-until date (optional extras stay outside the total), and keeps it in a quote log with its status (sent, accepted, declined). It has no separate change-order form and doesn't decide what's in scope or what's binding.
• Freelance deposits and retainers explained: deposit vs retainer, how to invoice and credit a deposit, refundability, GST/HST and UK VAT notes.
• Our paid Client & Project Tracker by Small Rows (US$12, one-time) keeps each project's budget hours against the hours you log, with tasks, due dates and follow-ups, so an approved change can be a task with its own date and the budget hours raised by what was agreed. Its dashboard shows projects that have gone over their budget hours. It has no money tracking and no change-order form.
• To bill approved extra time, our paid Freelance Billing Kit by Small Rows (US$12, one-time) logs hours as billable or not, fills them into the client's next invoice and tracks what's been paid.
• All three kits together: the All-Kits Bundle by Small Rows (US$24, one-time).

Where the sources differ

We read the pages under Sources on 2026-10-13. A few details to watch:

• None of them defines a change order. They're about written freelance contracts in general; how a change fits into one is our reading, not theirs.
• The contract lists differ. NYC's page lists 3 things the contract must spell out, Illinois lists 5, and the New York State statute has its own list. If more than one could apply, include everything on all of them.
• What counts as "written". The Illinois FAQ says an email or text message both sides agreed to can be a contract; the NYC page doesn't say either way. Signed or not, keep the whole thread.

When to get legal advice

• a change is large, or turns the project into something quite different from what was signed;
• the client's own contract has a change or variation clause, or terms on ownership, liability or cancellation, you don't understand;
• the client disputes that a change was approved, or refuses to pay for extra work they asked for;
• you and the client are in different countries and it's unclear whose law applies;
• a client hasn't paid and you're thinking about a claim (see our Canadian late-payment guide).

Related free resources

• How to write a freelance proposal: scope that doesn't creep, starting with the original agreement.
• Invoice payment terms explained: deposits, milestones and due dates for the original job and its changes.
• Free quote and estimate generator.
• Free timesheet template.
• Getting paid on time as a freelancer in Canada: late fees and reminder emails.
• All free tools.

Sources

Official pages read on 2026-10-13. Check the live page before you rely on it.

• New York: NYC DCWP: Freelance workers · NYC model contract (PDF) · NY DOL: Freelance Isn't Free Act · NY DOL model agreement
• Illinois: Illinois DOL: Freelance Worker Protection Act · Illinois DOL: FAQ

Found something wrong or out of date? Tell us via Support and we'll fix it and note the change here.