How to Write a Change Order Email Clients Actually Approve

A change order is a simple document: it names a request, confirms it falls outside the current scope, and states what it costs to add. In practice, the email carrying that message is where most agencies get stuck — not because the ask is unreasonable, but because the email is written defensively, and defensiveness reads as friction to the client on the other end.

Why most change-order emails land badly

The common failure mode is leading with justification: three sentences explaining why this is extra work, followed by the price, followed by an apology-shaped closing line. That ordering puts the client in a position to argue with your reasoning before they've even seen what they're getting. It also implies the request itself was somehow inappropriate to make, when usually it wasn't — it just fell outside a scope line the client never saw in detail.

A structure that works better

The emails that get quick approvals tend to follow the same shape, in this order:

• Confirm the request — restate exactly what was asked for, so the client knows you understood it correctly.
• Name the original scope, neutrally— one line referencing what was agreed ("the current contract covers 6 pages and 2 rounds of revisions"), without editorializing.
• State the price, plainly— no hedging, no "if that's okay," just the number and what it includes.
• Offer the next step— a one-line call to action: "Reply 'approved' and we'll start today," or similar.

Example

Happy to add the careers page — that's outside the 6 pages scoped in the current agreement, so it'd be an additional $650, delivered alongside the rest of the site. Reply "approved" and we'll get it into this sprint.

Notice what's missing: no apology, no over-explanation, no framing the request as a problem. It treats the ask as normal — because it is — while still being precise about what was and wasn't included originally.

Where the evidence comes from matters

The hardest part of writing this email usually isn't the wording — it's knowing, confidently, that the request really is outside scope, and being able to point to exactly where the contract says so. That's the piece MarginFlow automates: it flags the request against the parsed contract and drafts the first version of this email for you, evidence included, so you're editing a draft instead of starting from a blank page under time pressure.