Change Order: How Agencies Handle Out-of-Scope Requests

What a change order is

A change order is a written amendment to the original project scope. It documents a specific piece of new work the client has requested, states the additional cost, explains the timeline impact, and requires the client's signature before any of that work starts. It is not a new contract. It is a one-page addendum to the agreement you already have.

The purpose is straightforward: protect both sides. The agency gets a written commitment that additional work will be paid for. The client gets a clear picture of what they are approving, what it costs, and how it affects the rest of the project. Without a change order, scope creep builds up silently until someone realizes they have done 30 hours of unbilled work, or the client realizes they are being billed for something they thought was included.

Use a change order any time a client requests work that falls outside the original scope of work. That includes small requests. Especially small requests. The "quick" additions that take "five minutes" are exactly the ones that accumulate into unpaid weeks. If it is not in the SOW, it gets a change order.

What goes in a change order

Keep it short. A change order is not a new contract, and it should not read like one. One page is usually enough. If you are writing more than two pages, you probably need a full SOW amendment instead.

Five required fields

Description of the change

What new work is being added. Be specific: 'Add a filterable portfolio gallery to the Services page' is useful. 'Update website' is not.

Impact on timeline

How many days or weeks does this add to the project schedule? If it shifts the launch date, say so explicitly.

Additional cost

State the fee as a fixed amount or an hourly estimate with a cap. Do not leave this open-ended.

Effect on original deliverables

Does this new work delay anything that was already promised? If adding a gallery pushes the homepage revisions back by a week, the client needs to know.

Approval signature line

A place for the client's name, signature, and date. Digital signatures work fine. The point is a written record, not a ceremony.

Reference the original SOW: Every change order should name the original scope of work it amends, including the project name and SOW date. This creates a clean paper trail if there are multiple change orders over the life of a project.

How to issue a change order without killing the relationship

This is where most agencies get stuck. The work is clearly out of scope, but the conversation feels uncomfortable, so they either do the work for free or send a defensive email that damages the relationship. Neither outcome is good. The goal is a tone that is helpful and action-oriented, not legalistic.

The framing that works

"I want to make sure we can fit this in properly." That single sentence reframes the change order from a bureaucratic hurdle into a quality measure. You are not blocking the request. You are making space for it. Clients respond well when they feel like you are taking their request seriously enough to plan for it.

Tone: helpful, not defensive

You are protecting the client's project, not just your revenue. If you add unplanned work without adjusting the timeline, something else slips. The change order makes that trade-off visible. When you frame it that way, the client sees you as organized and transparent, not difficult.

Timing: before the work, not after

Issue the change order before starting the additional work. Always. Sending a change order after you have already done the work puts you in a weak position: the client has the deliverable and no incentive to sign. The moment a request comes in, respond with the change order. Speed matters here.

When the client pushes back

Acknowledge the request. Explain the impact on what is already in progress. Then offer options: "We can add this and push the launch by a week, or we can swap it in for the testimonials section and keep the same deadline." Giving the client a choice keeps them in control. Saying "no" without alternatives creates friction.

The phrase to retire: "That's not in scope" is technically accurate and relationally destructive. Replace it with "Let me send you a change order for that so we can get it scheduled." Same outcome, completely different energy. One is a wall. The other is a door.

Change order vs. SOW amendment

A change order and a statement of work amendment serve different purposes, and using the wrong one creates confusion.

Change order

Covers a single addition or modification
Fast to issue (one page, same day)
Does not rewrite the original SOW
Best for additions under ~20% of the original project value

SOW amendment

Rewrites the broader engagement terms
Takes longer to draft and negotiate
Replaces or substantially modifies the original SOW
Necessary when the overall project direction has shifted

Rule of thumb: If the change is under 20% of the original project value and does not alter the core deliverables, use a change order. If the project has fundamentally shifted (new target audience, different platform, doubled page count), rewrite the SOW.

Keeping a record: why email is not enough

Verbal approvals vanish the moment someone remembers the conversation differently. Slack messages get buried. Email threads with 14 replies and three forwarded attachments are not a clean record of what was agreed. When a dispute happens six weeks later (and it will), you need a single document with a signature and a date.

A signed change order removes ambiguity. The client cannot claim they did not approve additional work if their name is on the document. You cannot claim the client agreed to a fee if there is no written record. Both sides benefit from the clarity, which is why framing it as "protection for the project" is accurate, not a sales pitch.

What counts as a sign-off

A signed PDF (digital or wet signature)
Approval logged in a client portal with a timestamp
A reply email explicitly confirming the change order terms

What does not count

A thumbs-up emoji in Slack
"Yeah that sounds fine" on a phone call
A forwarded email chain where someone said "OK" to something else entirely

Structured approval workflows: If your agency handles multiple projects with frequent scope changes, a structured approval system (like Sagely) replaces the email-and-PDF shuffle with a single place to submit, review, and approve changes. Every approval is timestamped and tied to the right project. No more searching inboxes. During website delivery, when scope requests tend to peak, this kind of structure pays for itself.

Frequently Asked Questions

What is a change order?

A change order is a written amendment to a project's original scope of work. It documents what new work has been requested, what it costs, and how it affects the timeline, and requires client sign-off before the work begins.

When should I issue a change order?

Issue a change order any time a client requests work that is not covered by the original scope of work or statement of work. Issue it before starting the additional work, not after.

Can a client refuse to sign a change order?

Yes. If a client refuses, the agency should not do the out-of-scope work. Discuss the request, understand the urgency, and either negotiate the scope or decline. Never do additional work on a verbal agreement.

What is the difference between a change order and a SOW amendment?

A change order covers a single addition or modification. A SOW amendment rewrites the broader engagement terms. Use a change order for small additions; use an amendment when the overall project has significantly changed.

How do I write a change order?

Include a description of the new work, the additional cost, the timeline impact, any effect on existing deliverables, and a signature line. Keep it short: one page is usually enough.

Related Terms

Website Project Delivery

The structured process of running a client walkthrough, collecting formal sign-off, and handing off a completed website — covering pre-launch checks, the delivery call, and post-launch documentation.