Change Order Management: How to Handle Change Orders Without Losing the Client

Change order management is how a change goes from “the customer asked for something extra” to “it’s priced, approved, scheduled and on the invoice.” Done well, it follows the same five steps every time: capture the change, work out its impact, get the right approval, update the job and bill it. Done badly, the work gets done and the money doesn’t.

This guide covers those five steps for a job that’s already running, who owns each one, a worked example, and a simple change order log that shows you, at any moment, which changes still aren’t approved or billed. For what goes into the change order document itself, see what a change order is and why it matters.

Most contractors who skip a formal change order aren’t careless. It feels awkward, it slows the job down, and nobody wants to upset a customer they worked hard to win. So the work gets done, a note gets made somewhere, and by the time the final invoice goes out, the contractor is either eating the cost or arguing with a customer who doesn’t remember agreeing to anything.

In a growing business there’s a second problem: the person who hears about the change isn’t the person who prices it, schedules it or bills it. The crew lead says yes on site, the office never hears, and the extra never reaches the invoice. That’s not a people problem. It’s a missing process.

The easiest change orders are the ones the customer expected. Put one clear sentence in your contract: any work beyond the agreed scope will be documented, priced and signed before it’s done. When a change comes up mid-job, it doesn’t feel like a surprise. It feels like the process working.

Then decide, before the first change happens, who on your team can approve what. A crew lead might be able to agree to small extras from your price list up to a set amount; anything bigger goes to the estimator or the owner. Write it down so the crew isn’t guessing.

Two rules hold it together:

• No work before approval. A verbal “yes” is not a change order, and an email saying “sounds good” is borderline. A signed document, even a digital one signed on site, is.
• No change without a status. Every change on the job is either waiting for approval, approved and not yet billed, billed, or declined. Nothing sits in “we talked about it.”

A three-day fence install, day 2. The numbers are made up to show the method. The customer walks out and asks the crew to add 24 feet along the side yard.

1. Capture. The crew lead adds it to the job: “Customer asked for 24 ft extra along the east side, same style. Photo of the line attached.” The crew carries on with the original scope.
2. Impact. The estimator prices it from the price list: 4 more posts, 3 panels, concrete, and one extra day for the crew. That pushes the next customer’s start from Thursday to Friday. Price: $1,850.
3. Approval. The change is over the crew lead’s limit, so the estimator sends the change order. The customer signs that afternoon.
4. Update. The office orders the extra materials for next-morning delivery, moves the next job to Friday, tells that customer, and updates the crew’s instructions.
5. Bill. The $1,850 is added to the final invoice, and the change order shows “approved, not yet billed” until it goes out.

Nobody had to remember anything. Every step had an owner, and the change order log showed exactly where the change stood.

A change means extra labor, extra materials, and often extra scheduling and coordination time. Price it the same way you’d price new work. Example: a customer who’s already spending $40,000 with you isn’t a reason to discount a $1,850 extension. A properly priced change order also shows that your original price was fair, not padded to absorb extras.

Don’t forget the schedule. A change that adds a day affects the next customer too. Put the time impact on the change order, not just the price.

• The “while you’re at it” extra. A different outlet location, one more fixture, a small patch in the next room. It sounds too small for paperwork. Treat every one as a change order trigger, whatever the size.
• The material upgrade. The customer switches to a more expensive product mid-order. The difference seems easy to absorb; across a big job, several of them add up.
• The hidden condition. Rot behind the wall, an old wiring problem, buried rock or old concrete where you need to dig. Photograph it, stop the affected work and price it before going on.
• The schedule-only change. A change that costs nothing but time still needs writing down, so nobody expects the original finish date.

One list, per job or for the whole company, that shows every change and its status. Review it once a week.

Example rows, made up. The weekly look is simple: anything without an approval, anything approved but not billed, and anything waiting more than a couple of days. Those are the changes that turn into lost money or arguments.

The way you present a change matters. If you apologize for it or over-explain, it sounds like something unusual. Present it as a normal part of a professional job. Something like:

“We found rot in the ledger board during demo. It’s outside the original scope, so I’ve written up a change order: $640 and half a day. If you can sign it now, we’ll keep moving.”

That’s it. Clear, calm, and the customer knows exactly what they’re agreeing to.

1. Pull up your two or three most active jobs. List every change that was done or agreed verbally and isn’t on a signed change order. Get them documented this week.
2. Pick your most common kind of change (extras the customer asks for on site, usually) and write the five steps for it: who captures, who prices, who approves up to what amount, who updates the job, who bills.
3. Start a change order log and review it every week.

What to review each week: changes without documented scope, without approval, or approved but not yet billed. That number should be zero by the end of each job.

Next lesson: close jobs with complete information, so every approved change actually reaches the invoice.

The process for handling changes to a job’s scope once it’s underway: capturing the change, working out its cost and schedule impact, getting the customer’s signature and your own internal approval, updating the job records and billing it. A change order log keeps track of where each change stands.

The customer always signs. On your side, set limits: a crew lead might approve small extras from your price list up to an amount you choose, while larger or unusual changes go to the estimator or the owner. Write the limits down so the crew doesn’t have to call for every one.

No. Document and price the change, get the signature, then do the work. If something is unsafe or would cause damage if left, make it safe, document what you did and get the change order signed as soon as possible.

For each change: the job, what changed, who asked and when, the price and schedule impact, who approved it and when, whether the job records were updated, and the billing status. Review it weekly and look for anything unapproved or unbilled.

In MotionOps, change orders live inside the work order, so they can’t get lost on the way to the invoice:

• Change Order Requests: field technicians and account managers start and manage the change order process with the customer, inside the work order, so the full cost gets collected.
• Signatures and Approvals: collect the customer’s signature, or upload proof of approval such as an email or text screenshot.
• Proposal History: the job’s full record, from the first proposal to every change order and update.
• Close Work Order: close the job once it’s really done, after checking that the full approved amount is invoiced.

Related: what a change order is, with a template. See plans and pricing, or try MotionOps free.