Handling scope changes with change orders

A change order is a short written agreement, approved before the extra work starts, that records what is changing in a project's scope, what it costs and how it moves the schedule. Log every request, price it, get it signed, then update the budget and the plan.

Client projects rarely end exactly as they were sold. A client sees the work and asks for one more page, a second language or an extra round of revisions. Each request sounds small. Together they turn a profitable project into a loss, and the conversation about money happens weeks too late. A change order process moves that conversation to the moment the request arrives, while it is still easy to say yes, no or "yes, at this price".

Change request, change order and scope creep

• Change request: the ask. A client, or someone on your own team, proposes doing something differently from the agreed scope.
• Change order: the result. The request has been described, priced and approved, and it now changes the scope, the price or the dates of the project.
• Scope creep: what happens without the step in between. Work grows through informal requests that nobody priced or approved.

Scope is easier to defend when it is written down in pieces the client recognizes. If the original proposal splits the work into phases with clear deliverables, a request either fits inside a phase or it does not. The guide to structuring a project into phases and tasks covers that groundwork.

What to put in a change order

Field	What to write	Why it matters
Reference and date	A number in sequence and the date of the request	Lets both sides refer to it later
Requested by	The person who asked	Shows the change came from the client
Description	What changes, in plain words, and what does not	Prevents a second argument about what was agreed
Reason	Why the change is needed	Helps when the budget is reviewed later
Price impact	The extra fee, or the extra hours and rates	The part people most often skip
Schedule impact	New dates for the affected deliverables	Extra work rarely fits in the old timeline

Finish with an approval line: the name of the person who can approve spend on the client side, their decision and the date. One page is usually enough. A change order that takes an afternoon to write will not get written.

A six-step change order process

1. Log every request. Keep one list per project, even for requests you plan to absorb for free. A list of small favors is useful evidence when a larger one arrives.
2. Check it against the scope. Read the proposal or contract. If the work is already included, say so and carry on. If not, it is a change.
3. Estimate the impact. Ask the people who will do the work how long it will take and what it moves. Include knock-on effects such as testing, revisions and project management time.
4. Send the change order. Describe the change, the price and the new dates, and ask for a decision by a set date.
5. Wait for approval before starting. Work done before approval is work you may not be paid for. Whether an email reply counts as written approval depends on your contract and local law, so agree on the form in advance.
6. Update the budget and the plan. Add the approved amount and hours to the project budget, move the dates, and tell the team what changed.

Pricing a change

How you price a change follows from how the project is priced. On a fixed-fee project, a change is usually quoted as a fixed amount, because the client agreed to a fixed price and expects the same certainty for the extra work. On a time and materials project, a change is usually an estimate of extra hours at the agreed rates, with a cap if the client needs one. The guide to fixed fee and time and materials pricing explains the trade-offs between the two.

Not every change adds cost. A client may drop a feature to make room for a new one. Record that swap as a change order too, with a price impact of zero, so the scope on paper still matches the work.

Keep the budget honest after approval

An approved change order is worth little if the budget still shows the old numbers. Add each approved change as its own budget line, rather than quietly raising the original figure, so you can still see how the original estimate performed. Then watch actual hours against the new total. The guide to project budget tracking for small teams lists what to check and how often, and what a budget vs actual view should show covers the report itself.

Review the change log at the end of the project. If one client accounts for most of the changes, the next proposal for that client may need a larger contingency or a clearer scope. If one type of change keeps appearing across clients, it may belong in your standard offer.

Saying no without souring the relationship

• Set the rule at the start. Explain the change process in the kickoff meeting, so the change order that follows is expected, not a surprise.
• Offer options. "This can be added for this price and two extra weeks, or swapped for the reporting page" is easier to hear than a flat no.
• Batch small requests. Collect minor changes and send them as one change order every week or two, instead of a stream of tiny ones.
• Absorb some, but say so. If you choose to do something for free, note it on the log as a no-charge change. The client sees the goodwill, and you keep the record.

Frequently asked questions

What is the difference between a change request and a change order?

A change request is the proposal to do something differently. A change order is the approved version, with a price and dates attached, that formally changes the scope. Some contracts use the two terms interchangeably, so check how yours defines them.

Who should sign a change order?

Someone on the client side who can approve the extra spend, and someone on your side who can commit the team. The person who asked for the change is not always the person who can pay for it, so confirm who holds the budget early in the project.

Do small changes need a change order?

They need to be logged, even if you do not charge for them. Many teams set a threshold, such as a number of hours, below which changes are batched or absorbed. Above it, the work waits for a signed change order.

Can I refuse a change request?

Yes, unless your contract says otherwise. You can decline a change that does not fit the project, the timeline or your skills, ideally with an alternative. Many client contracts include a change clause that sets out how requests are raised and decided.