How do I get real written approval when a client changes the scope mid-project?

This page may contain affiliate links from which Blur Studio earns commissions.

This is one of the more common and more expensive disputes in service businesses: a client asks for something extra mid-project, you both agree over email or a phone call, you do the work, and then the client says they never actually approved it, or didn't realize it would cost that much. You're not wrong that they agreed. You're just stuck without a clean way to prove it, which in a dispute is functionally the same problem.

The no-tool way first

For a small, low-dollar change, a clear email thread, where you stated the price and timeline plainly and the client replied with an unambiguous "yes, go ahead," is genuinely defensible. Under the U.S. ESIGN Act and most states' UETA, that kind of exchange counts as a valid electronic agreement as long as both sides intended it as acceptance. The actual weakness isn't legal, it's practical: email threads get buried, replies get vague ("ok" means a lot of different things), and when a dispute happens weeks later, scrolling through a thread trying to reconstruct exactly what was agreed to is a bad position to be arguing from. The bigger the dollar amount of the change, the less I'd rely on this.

Options, from least to most effort

Paper, by hand. If you're meeting the client in person anyway, having them initial a short change note on paper works fine and costs nothing.

A WhatsApp photo of a signed paper. Print a one-page change order, have the client sign it, and photograph it. This is a real, legitimate step up from a vague email reply, since it captures an actual signature on an actual document, even if the "document" is a photo rather than a clean digital file. The honest downside is organization: photos scattered across phone camera rolls and chat threads are hard to find again when you need them, and a blurry photo is occasionally hard to read.

SignWell. SignWell is an e-signature platform built around flat, predictable pricing rather than per-signer fees. Its Free plan, confirmed live on signwell.com, covers 3 documents a month with 1 sender and 1 template, which is plenty for occasional change orders. Light runs $10 a month annually ($12 month-to-month) for unlimited documents, and Business runs $30 a month annually ($36 month-to-month) with 3 senders and unlimited templates.

PandaDoc. PandaDoc is a document platform built for proposals and quotes with real-time tracking of whether the client has opened and viewed the document, which is itself useful evidence in a dispute (you can show not just that it was sent, but that it was opened). Confirmed live on its pricing page: Free covers 5 documents a month with a basic editor, Starter runs $19 a month per seat for unlimited uploads and e-signatures, and Business runs $49 a month per seat and adds approval workflows, useful if your change orders need a second person's sign-off before going to the client.

QuickSigner. QuickSigner is an e-signature tool for uploading a PDF or Word document, placing signature and date fields, and sending it as a link the client opens and signs in their browser, no account needed. Confirmed live on its pricing page: Free covers 5 documents a month, 3 signers, PDF only, up to 5 MB. Business runs $5 a month per user (or $48 a year annually) for unlimited documents, 10 signers, Word support, 10 MB files and 10 saved templates, which matters here since a one-page change order template is exactly the kind of document worth saving and reusing every time scope shifts. Professional runs $15 a month per user ($144 a year annually) with higher limits and OTP phone verification.

The actual steps

1. Write the change in one short page. What's changing, the new price, and the new timeline if it affects the deadline. Keep it to one page so there's no excuse not to read it.
2. Send it for signature. Not a reply-to-this-email request. An actual document with a place to sign. Sending is simple even without a printer: seehow to get contracts signed online without printing.
3. Start the extra work only after it's signed. This is the step people skip because the client is waiting and the work feels urgent. It's also the step that actually protects you, so skipping it defeats the entire point.
4. Save the signed copy with the project. Not in a random email folder. Wherever your project files already live, so it's findable months later when you've forgotten the details. Proving later what the change said is covered inproving the exact wording of a signed change order.

When a clear email thread is genuinely enough

For small, low-dollar changes, like adding one extra hour to a job already scoped in hours, a clear email thread with an explicit price and an explicit "yes" is a reasonable amount of friction for the stakes involved. The honest line: once a change adds more than roughly a day's worth of work or meaningfully shifts the deadline, the ten minutes it takes to send a proper signed change order is worth it, because that's exactly the size of change most likely to become a dispute later.

A worked example

Say you're a freelance designer on a $3,000 website project, and the client asks mid-project for two extra landing pages that weren't in the original scope. You quote an extra $600 and a one-week extension over email, the client replies "sounds good, let's do it," and you build the pages. Three weeks later, at invoice time, the client says they thought the extra pages were part of the original $3,000 and refuses to pay the $600. You have the email thread, which is genuinely useful, but "sounds good, let's do it" is vague enough that the client can argue it was agreement to a concept, not a specific $600 line item. A one-page change order stating "$600, two additional landing pages, one-week extension, signed by [client name] on [date]" removes almost all of that wiggle room, because there's no ambiguity left about what was agreed to.

The part everyone glosses over

A signed change order protects you on the scope and the price. It does almost nothing for you if the original contract itself was vague about what was in scope to begin with, because then the argument just shifts to whether the "change" was actually a change at all, or something that should have been included from the start. I've seen clients dispute a change order by arguing the item was implied in the original agreement. The real fix for that isn't a better change-order process, it's a tighter original scope of work, with explicit exclusions listed, not just inclusions. A change order is a patch on a leak, not a substitute for sealing the original agreement properly. A tighter original document helps: see thisscope of work template for agencies.

There's a second version of this problem worth naming: scope creep that arrives in small pieces rather than one obvious request. "Can you just also move this button" five separate times never individually feels big enough to justify a formal change order, but five small asks can easily add up to real unpaid hours. I'd set a personal rule, maybe three small unscoped requests in a week triggers a short change order covering all of them together, rather than letting each one slide because it felt too small on its own.

How I'd approach this

When I write a contract for my own work, I spend more time on what's explicitly excluded than on what's included, because exclusions are what prevent the "wait, I thought that was part of it" conversation later. If you're finding yourself writing change orders constantly, more than once or twice a project, that's usually a sign the original scope document needs tightening, not a sign you need a faster signature tool. Get in touch if you want help building out a standard contract and change-order process that actually holds up rather than patching the same leak project after project. Starter wording is available infree contract templates for small jobs.