Construction Change Order Process: How to Write One Clients Actually Sign

Sound Familiar?

Signs your change order process is costing you money:

• You're doing extra work and not billing for it because you don't want the conflict — then resenting the client by the end of the project
• Change orders get signed late (or not at all) because clients feel blindsided by the cost
• You're negotiating change order prices after you've already done the work, from the weakest possible position
• Your contract has a change order clause but you almost never actually use it
• Projects routinely finish $5,000–$15,000 over budget on scope items that were never formally authorized

What We Found

Why Most Builder Change Order Processes Fail

The fundamental problem with how most builders handle change orders isn't the paperwork — it's the timing and the framing. The change order process typically fails in one of three ways:

Failure Mode 1: Doing the work first, billing later

This is the most common pattern. The client asks for something extra, the builder says yes to avoid awkwardness, the work gets done, and then a line item appears on the next invoice. The client is surprised. The amount feels higher than expected. A negotiation begins. The builder ends up absorbing part of the cost to preserve the relationship.

The problem with this approach isn't that clients are unreasonable — it's that the builder put themselves in the worst possible negotiating position. Once work is complete, the client has received the value. The motivation to agree to full payment is lower. If the builder had issued a written change order before starting the work, the conversation happens at the right time: when the client is deciding whether they want the additional scope, not after they've already gotten it.

Failure Mode 2: Issuing change orders without context

A change order that says "Framing modifications — $3,200" creates questions. What modifications? Why $3,200? Why is this a change at all? Clients who are confused ask questions. Questions become negotiations. Negotiations erode your final number.

A change order that says "Framing modifications to accommodate homeowner-requested addition of window in master bedroom per site meeting 4/11 — 8 hours carpenter labor at $95/hr, $350 lumber, $125 window frame rough opening reinforcement" is self-explanatory. The client remembers the conversation. They understand what they're paying for. The likelihood of signing without pushback is dramatically higher.

Failure Mode 3: Treating the change order as confrontational

Builders who hate issuing change orders often frame them as adversarial — either apologetically ("I hate to ask but...") or confrontationally ("Per the contract, this is additional scope"). Both framings create friction. The change order is not a confrontation. It's documentation of a mutual decision. Frame it that way and the signature comes faster.

The Change Order Process That Gets Signatures

The change order process that works has five steps, and all of them happen before the additional work starts.

Step 1: Identify the scope change immediately

The moment a client requests something outside the original contract scope — verbally, in a text, in a site walkthrough — that item goes on a "pending change order" list. Not into your mental backlog. Not onto a notepad you'll find later. Into a running list that gets reviewed daily.

In JobTread, the cleanest way to manage this is with a pending change order line item in the project. Every scope item outside contract becomes a line in that section until it's either approved and added to contract or explicitly declined. Nothing falls through the cracks.

Step 2: Price it before you commit

Never give a price verbally at the site and then formalize it later. The client remembers the verbal number. If your written change order comes in higher (even by $200) because you missed something when you were estimating on the spot, the discrepancy becomes a dispute. Take 30 minutes to price it properly, then present the written number.

Step 3: Write the change order with full context

A complete change order includes:

• Reference to the original contract and date
• Description of what changed and why (including reference to the client conversation that triggered it)
• Itemized cost breakdown — not a lump sum, but labor hours, material costs, and any subcontractor costs called out separately
• Schedule impact, if any — "This work will add approximately 2 business days to the project schedule"
• Payment terms — when the change order cost is due
• Signature line with "Work will not proceed until this change order is approved"

Step 4: Present it before any work begins

This is the non-negotiable. The change order goes to the client the same day the scope change is identified, or the next morning at the latest. If you're using JobTread's client portal, the change order routes directly to the client for digital signature. If you're not using the portal, email it with a clear subject line: "Change Order #3 — [project name] — Signature Required."

Step 5: Follow up within 24 hours if unsigned

Change orders that sit unsigned for more than 24 hours are change orders that will be disputed at close. One follow-up call or text — "I need your signature on CO #3 before we can start the window work tomorrow" — closes the loop. Builders who send change orders and wait for clients to respond on their own timeline are creating their own collection problems.

The JobTread allowances post covers how to set up allowance tracking alongside your change order process — because allowance overages are the other major source of unbilled scope in residential projects.

Change Order Language That Reduces Client Pushback

The exact language in a change order affects signing speed more than most builders realize. Here's the framing that consistently produces faster signatures:

Lead with context, not cost

Start every change order description with the client's request or the site condition that created the change — not the price. "At your request during the April 11 walkthrough, we are adding a window in the master bedroom. This change requires structural modifications to the framing. The cost is as follows:" reads differently than "Window addition and framing modifications: $3,850." Same numbers, different reception.

Show the breakdown

Itemized change orders get signed faster than lump-sum change orders, consistently. When clients can see 8 hours of labor at $95/hr, plus $350 in lumber, plus $125 in hardware, the $1,235 total makes intuitive sense. A lump sum of $1,235 feels arbitrary. Same amount. Different conversion rate.

Acknowledge the schedule impact

A change order that says "This work will add 1 day to the project schedule" signals to the client that you're managing the project actively and thinking about their timeline. Clients who understand the schedule implications of their requests are less likely to add more changes impulsively — and more likely to respect the billing because they understand the full cost of the decision, not just the dollar amount.

Make signing easy

A change order that requires printing, signing, scanning, and emailing back gets signed in two days, if at all. A change order in JobTread's client portal that requires one click on a mobile phone gets signed in two hours. Reduce the friction in the signing process and signing speed increases automatically.

If your change order approval rate is below 90%, or if you routinely absorb unbilled scope at project close, the change order process is where the margin is leaking. A strategy session with Go First can walk you through the exact JobTread configuration and template language that closes that gap.

Frequently Asked Questions