Every services project has a moment, usually around week three, when someone says, “While you’re in there, could you just…” It is a friendly sentence. It is also how a fixed-price job quietly becomes a free one.
A change order is the cure, and it is less dramatic than it sounds: a short written agreement, made before the extra work starts, saying what is changing, what it costs and what it does to the schedule. This article covers who gets to say yes, what the paperwork has to contain, what happens if you skip it, and the odd case where the “change” is a head count rather than a scope. It is written for both chairs: the provider doing the work and the client asking for it.
The short version
Four things make a change order work. A named person on the client side who is allowed to approve. Five facts written down. A rule that nothing starts until it is approved. A price method agreed before anyone needs it. Miss one and “just a quick favour” turns into an argument about what was promised.
What Is a Change Order, and Why Does a Services Contract Need One?
A change order is a written agreement to alter one piece of work: it adds, removes or changes something in the scope, the price or the schedule, and it does so on paper instead of in a hallway. Some contracts call it a change request, and some use the two terms for two steps of the same process, which the FAQ below sorts out.
The law is relaxed about whether you may do this. The Legal Information Institute describes contract modification as parties changing terms that already exist, with price and delivery schedule as its examples (modification). The mechanism is open to everyone. The only question is whether you used it.
Why does a services contract need one more than most? Because a product has edges you can photograph and a service does not. “Set up email” can mean one mailbox or two hundred, and the contract that said “set up email” will not tell you which. Without a change process, every request becomes a debate about whether it was included all along, and there is no record on either side. Our guide to the statement of work covers writing the scope so there are fewer of those debates. This article is about what you do when the scope has to move anyway, which it will, because projects are the only things known to expand without being watered.
It protects the client as much as the provider. A client with no change process gets surprise invoices; a provider with none gets surprise freebies. Same hole, opposite ends.
A sensible home for the process is the master agreement, so every project inherits one procedure and each statement of work only fills in the names and the numbers (see the master services agreement guide for how the two documents divide the work).
Who Gets to Say Yes to Extra Work?
Suppose you run a small IT firm and the client’s office manager, friendly and overworked, emails: “Can you set up laptops for our three new hires this week? Thanks!” Your contract covers support for the machines the client already has. Is this a change? Almost certainly. Is the office manager allowed to buy it? Nobody knows, quite possibly including the office manager.
That second question is where this goes wrong. The person who asks for extra work and the person who can authorise paying for it are often different people, and the invoice lands on the second one. The office manager did not sign the contract. The office manager just lives with it.
The fix is a drafting fix, not a legal theory. Name the approvers in the contract:
- On the client side, list the people (or the one person) who may approve a change, by name or by role, and if you like, a dollar figure below which a listed person may approve by email and above which the owner signs.
- On the provider side, do the same. A technician who promises something on the phone is not the person who gets to change the price.
- Everyone else is a requester. A request from anyone not on the list is something to forward to an approver, not an instruction to start.
- Say whether email counts. For most small engagements it should, and the contract should say so in plain words rather than leaving it to be argued later.
Notice what this does not do. It does not promise how a court would treat a request from someone unlisted. It just means you never have to find out.
What Does a Change Order Have to Say?
Five facts, every time. A change order that carries all five is boring to read and very hard to argue with.
- What is changing, in countable terms. “Three laptops set up, joined to the company network, with the standard software list” is a change. “Laptop setup” is the start of an argument.
- The price, and how it is fixed. Either a fixed fee for this change, or a rate with a not-to-exceed ceiling. An estimate with no ceiling is a wish with a number on it.
- The effect on the schedule. Including “none”, which is a real answer and should be written down.
- The effect on everything else. Acceptance criteria, service levels, dependencies, other deliverables. If the change adds systems, ask whether the existing service levels and SLA credits cover them or whether the new things sit outside the promise.
- Who approved it, and when. Names, dates, and the signature or the email it came in on.
The clause that holds the process together can be short. Here is an original sample to adapt, with the numbers left for you to choose. It is an illustration, not a form to paste in blind.
Changes. Either party may ask for a change to the services, the schedule or the fees by sending a written request that describes the change. Within five business days the Provider will send a written estimate of the price and any effect on the schedule. A change takes effect only when a change order stating the work, the price, the schedule effect and any other affected terms has been approved in writing by an Authorised Approver of each party; an email from an Authorised Approver counts as writing. Until then the Provider will keep performing the services as already agreed and is not required to begin the change, and the Client is not required to pay for work outside the existing scope that no approved change order covers. If an Authorised Approver of the Client instructs the Provider by email to begin before the change order is signed, the Provider may do so at the rates in the rate card, up to the ceiling stated in that email, and the parties will sign the change order promptly.
Why each piece is there. The five-day clock stops a provider from sitting on a quote while the client assumes the work is happening. “Keeps performing as already agreed” stops a disagreement from becoming a work stoppage. The last sentence is the emergency exit: it lets work begin when the server is on fire, with a ceiling on what the fire can cost. And the rate card? Put it in the contract at signing. Negotiating a day rate while the client is waiting and needs the work is a poor place to bargain from, whichever side of it you sit on.
What Happens If the Work Starts Before the Paperwork?
It happens constantly. The client is anxious, the provider is helpful, and the paperwork feels like a speed bump on the way to being nice. Here are the three ways it can go, none of them fun.
The contract itself. If your contract says changes need an approved change order, extra work done without one sits outside the deal on its face. The provider has no agreed price, the client has no agreed scope, and each remembers the conversation differently.
Waiver. The Legal Information Institute describes a waiver as the intentional giving up of a right, and notes that it can be written down or implied from actions (waiver). Hold that next to a friendly habit. A provider who does three small extras for free may find it awkward to start charging for the fourth. A client who watches extra work happen for weeks without a word may find it awkward to say later that nobody asked for it. Whether either outcome actually follows depends on the facts and on the state, which is a question for a licensed attorney. The practical lesson needs no lawyer: silence reads as agreement, from both directions.
Quantum meruit. In some situations, where services were provided and the other side benefited, a court can award the reasonable value of the services even without an agreed price. The Institute’s entry describes this remedy, called quantum meruit, as compensation in a reasonable amount, and notes that courts keep discretion over how it is calculated (quantum meruit). Treat it as a safety net, not a plan. It means a stranger decides what your work was worth, after the relationship has already gone sour.
If work has already started, the way out is boring and quick. Stop adding to it. Send the written request and estimate today. Get the approval by email. Treat the paper as catching up, not as a gotcha. A late change order is clumsy. No change order is worse.
How Do Change Orders Work When the Change Is a Head Count, Not a Scope?
This is the case the construction-flavoured guides never reach. In a managed service, much of what changes is not what the work is but how many of it there are: more users, more devices, another site. The helpdesk is the same helpdesk. There are just more people calling it.
Providers often wave this through as “obviously covered,” and then find the contract has no rule for when the new people start paying.
Here is a hypothetical, with invented numbers. Suppose the rate card says $100 per user per month and the client has 25 users, so $2,500 a month. The client hires six people.
- New head count: 31 users, so $3,100 a month from then on.
- Say the six join with 20 days of a 30-day month left, and the contract prorates by the day. The first month’s extra is 6 x $100 x 20/30 = $400. After that it is $600 more a month.
Is that a full change order? It need not be. It needs a rule, written once, in the contract: head count adjusts by notice to a named address; the new price starts on a stated date; the proration method is stated. Then the client tells you about six new hires and nobody drafts anything. If you bill in advance, decide whether the mid-month addition is a small second invoice or waits for the next cycle (more on that in payment terms).
Write the downward rule too. A client who can add seats in a day but needs a year’s notice to remove them is paying for a chair to stay empty, which is a hard thing to be cheerful about.
Keep the full change order for changes that alter what the work is: a new office, a new line-of-business application, a server migration, a new service tier. Those get the five facts.
Does Any of This Change on a Trade or Construction Job?
Same bones, different pressure. On a job site the person asking for extra work is often standing right in front of you, and “I’ll need that in writing” feels rude. It is worth feeling slightly rude about.
I will keep this to general principle, because the rules differ so much by state. The person who tells you to do extra work may not be the person who can authorise paying for it. And on a subcontract, the party above you may not be paid for the change either, and your contract may tie your payment to theirs, which is what a pay-when-paid or pay-if-paid clause does. So:
- Find out from the contract who may order changes, on every level above you.
- Get the change in writing, with a price, before you start.
- If you must start on a verbal instruction, write down what you were told, by whom and when, and send it the same day.
- Pass the change order up the chain, not just along it.
Payment rights, lien rights and notice deadlines for extra work vary by state and can be strict. Check your state’s rules, or ask a local attorney, before the job rather than after the invoice is refused.
What Should You Ask For, From Each Chair?
If you are the provider:
- A rate card in the contract at signing, so extra work is priced before anyone needs it.
- A no-start rule, paired with a quote deadline you commit to, so the rule is fair to the client.
- A list of the client’s authorised approvers.
- Optionally, a small-favours allowance: a stated number of hours a month of minor adjustments inside the fee, tracked. It keeps the relationship warm and puts a visible number on goodwill.
If you are the client:
- A not-to-exceed figure on every estimate.
- A short approver list, so one tired colleague cannot commit the business.
- The right to decline a change without affecting the original scope.
- The estimate before the work, never after it.
For both of you, put the process in the master agreement and let each statement of work add its own names and rates. If the contract is for freelance creative work rather than a managed service, the same logic shows up as revision rounds, covered in our freelancer contract clauses guide.
It is a signed agreement that adds, removes or alters something about the work, the price or the schedule. It normally sits alongside the original contract instead of replacing it, and until it is approved the original terms still apply.
Whoever the contract says can. Good contracts name the approvers on each side, by name or role, and often set a dollar figure above which the owner has to sign. A request from anyone not on the list is a request to forward, not an instruction to start. If your contract names nobody, add a list before the next change arrives.
It depends on what the contract says and on the facts, and the answer varies by state, so for an amount that matters ask a licensed attorney. As a drafting matter, a clause making extra work payable only under an approved change order protects the client, and a rate card plus a quick written approval protects the provider. Silence is the expensive option for both.
In many contracts a change request is the ask, and the change order is the signed agreement that answers it with a scope, a price and a schedule effect. Some contracts use the two terms interchangeably, so check how yours defines them.
Describe the scope in countable terms, name who can approve changes, require written approval before the work begins, and price extras from a rate card agreed in advance. A small, tracked allowance of minor changes can keep the relationship friendly without leaving the cost open-ended.
Not always. If the contract prices by user, device or site, it can set a simple notice rule for adding or removing them, with a start date and a proration method, and keep full change orders for genuinely new work such as a new system or a new location.
The Bottom Line on Change Orders
Scope creep is not a character flaw in clients or providers. It is what happens when helpful people have no procedure. A change order is the procedure. Before you sign, be able to say who may approve a change, what the paper has to say, and what happens to work that starts before the paper does. If your contract cannot answer those three, adding the answers is among the cheapest edits you will ever make.
This article is general information, not legal advice, and does not create an attorney-client relationship. Contract law varies by state and by situation. For high-stakes agreements, have a licensed attorney review the document.