Change orders for scope creep: how to handle it in writing

Handle scope creep with a written change order that you send before the extra work starts. It states what is being added, why it falls outside the agreement, the extra fee, the effect on the delivery date and a line the client approves. Nothing begins until they say yes in writing. Done calmly, it protects your margin and your relationship at the same time.

What scope creep looks like in a service business

Scope creep is the slow growth of a project beyond what was agreed, without a matching change in price or time. It is rarely one big demand. It is a "small" extra page, one more round of edits, a second language, "can you also quickly...".

The size of the problem is documented. In the Teamwork.com research quoted in its handoff guide, 27% of teams named clients changing budgets or timelines mid-project as their biggest frustration. That is one survey from a software vendor, but anyone who has run client projects recognizes the pattern.

Most scope creep is not malicious. Clients do not know what is hard. They see a small change and assume it is small. The fix is not to argue, it is to have a process that makes each extra visible, priced and agreed.

What a change order is

A change order is a written change to an agreement. The term comes from construction, where it is standard. The American Institute of Architects explains that a change order is a written modification to the contract that changes the work, the contract sum or the contract time, and that, once signed, it becomes part of the contract documents and binds the parties to the revised terms. AIA's own guidance says it should record the change to the work, the contract sum adjustment and the contract time adjustment, and that the parties should execute it once they have agreed on the change. Its checklist says the change should be in writing and that no work should proceed on a verbal instruction alone.

You do not need construction paperwork for a branding project, a coaching package or a photo shoot. You need the same three ideas: describe the change, price it, and get a yes before you begin.

Build the groundwork before the project starts

A change order is easy when the original scope is clear. Do three things at the start.

Write the scope as a list of deliverables. "Three launch emails" is clear. "Email support" is not. Also list the exclusions: "Translation, photography and ad copy are not included."

Limit revisions in the contract. A common pattern is two rounds of changes, where a round means one consolidated set of feedback sent in a single document. Extra rounds are billed. Grey's guide to freelance scope creep suggests this wording, along with a clause that any work not listed is out of scope and subject to a separate agreement. Our earlier posts on how to stop scope creep and scope changes in freelance contracts cover the contract side. This one is about the written change itself.

Agree a rate for extras. Put an hourly or day rate in the contract so you do not negotiate it mid-project. Add a clause that says work on a change will not begin until a revised fee and timeline are agreed in writing by both parties. That sentence is the whole system in one line.

Decide what counts as a change

Not every request needs paperwork. A short test, adapted from the practical advice in Twine's scope creep guide: treat a request as a scope change unless it takes only a few minutes, is clearly one-off, will not set a future expectation and leaves your margin intact. Fixing a typo is a favour. Adding a page is a change.

When you do a free favour, say so: "Happy to do this one as a courtesy. Future additions of this type will go through a change order." That sets the line without a fight.

The conversation: say it in four steps

Most scope creep is solved by one calm message. Use four steps.

1. Acknowledge the need. "That makes sense, the team will want to see the Arabic version too."
2. Point to the agreement. "The current scope covers the English site only. Arabic pages are listed as out of scope in section 2."
3. Offer two options. "I can add the Arabic version for 600, which moves delivery by four days. Or, if the budget is fixed, we can drop the blog section to make room."
4. Confirm in writing. "I will send a short change order today. Once you approve it, I will start."

Never say "no" flatly and never say "sure" in passing. A verbal yes in a call is the start of the problem, because it creates an expectation without a price. If a client approves something verbally and will not confirm it in writing, Grey's guide calls that a red flag worth taking seriously. It is, and it is a reason to pause.

A simple change order template

Copy this. Fill it in. Send it as a message, a PDF or a page the client can approve. Keep it to one screen.

Change order [number] for [project name]

• Date: [date]
• Requested by: [client contact]
• What is being added or changed: [one or two lines, specific]
• Original scope reference: [deliverables list or section number]
• Why it is outside the agreed scope: [one line]
• Additional fee: [amount and currency, and whether tax applies]
• Effect on the schedule: [number of working days, new delivery date]
• Effect on other deliverables: [none, or what moves]
• Payment: [due with the next invoice, or a deposit of X% now]
• Approval: "Reply 'approved' or sign below to confirm. Work on this change starts once approval is received."

Twine's example change request shows how little it takes: the requested addition (5 extra email variants), the original scope (3 launch emails), the additional fee, the timeline impact (plus 3 business days) and an approval by written reply. Its advice, "simple beats fancy", is right. What matters is that the new work becomes explicit and billable.

Number your change orders in order. They become a record. If the client later disputes the final invoice, you can show each agreed addition with its date and approval.

Pricing a change

Price from your rate for extras, not from a feeling. Estimate the hours, add the cost of anything you must buy, and add a small buffer for the extra coordination. Show the amount, not the working. If the extra work affects the schedule, say by how much. A change of two hours may move nothing. A new section may move the date a week.

Collect payment sensibly. For small changes, add them to the next invoice. For larger ones, ask for a deposit before you start. That keeps you from carrying unpaid extras to the end of the project. If the project has a payment schedule, amend it in the change order so the due dates still make sense.

When the client pushes back

Some clients say, "I thought this was included." Do not argue about intent. Go back to the document: "I understand. The scope document lists what is included, and this wasn't on the list. I want you to get this done properly, so here is what it takes." Offer the swap option again.

If the extra really was your mistake, such as a deliverable listed in the quote that you missed, fix it and say so plainly. Your reputation is worth more than the hour.

If the client refuses all change orders and keeps adding work, treat it as a pattern. The next step is a conversation about ending the project at its current milestone, or moving to a retainer or hourly basis. This is where the contract clauses on termination and kill fees earn their keep. Check the wording with a lawyer for your country.

Small changes in the portal, big changes in a new agreement

For a big change, such as a doubled scope, do not stack change orders. Write a new agreement or amendment and treat it as a new project phase. This article's template is for additions, not for reshaping the whole job.

Also keep your communication in one place. A change requested in a chat thread, approved by emoji and priced in a phone call is hard to prove. Put requests and approvals on the project record.

How Delivvo keeps scope changes in writing

Delivvo does not have a separate form called a change order. It gives you the pieces to run one, all attached to the same client and project, so the request, the price, the approval and the payment sit together.

The client portal holds one message thread per project. When a client asks for something extra, the request lives there, with a date, instead of in a text message you have to find later. You reply in the same thread with the change order text from the template above.

For the price and approval, send a short quote for the extra work to the same client. The client opens it from a link, accepts it online and can sign on the same page, and the accepted quote and signing record stay on the project. Contracts are templates you edit and issue yourself, so your original agreement can already contain the sentence that work on a change starts after written approval, and the revision limits and the rate for extras.

For the money, send a deposit invoice or add the amount to the next invoice. Payments go through your own gateway, with up to 12 instalments if you want to spread a larger addition. Reminders run before and after the due date, so you do not chase the extra. Delivvo takes 0% of the payment, and the final invoice shows the deposits already received.

Every quote, contract and invoice carries a verification code, so if a client or their accountant later wants to check what was agreed, the document confirms itself.

See the client portal page, the proposals and quotes and the contracts and e-signatures pages.

Read more about Delivvo for teams, or start with the CRM and client portal.

FAQ