How Do I Explain a Change Order to a Customer?

Explain what changed before asking the customer to approve a different price. Connect the request or condition to the original scope, show the cost and schedule effect, offer workable choices, then put the decision in writing. A measurable original scope is the foundation, so fix that first if the real problem is scope creep in the quote.

Do it when the change is requested or discovered. A customer should not first learn about extra work when the invoice arrives.

How to explain a change order in six steps

1. Acknowledge the request or condition. Repeat what the customer wants or show what the crew found.
2. Reference the original scope. Point to the quantity, task, assumption, allowance, or exclusion affected.
3. Explain the impact. State the changed work, price or credit, and schedule effect.
4. Offer clear paths. Let the customer approve the change, keep the original scope, choose an alternative, or pause the affected work when feasible.
5. Send the written change order. Record the changed scope, amount, schedule, and approval.
6. Wait for the required approval. Continue only the unaffected work that can proceed safely and under the contract.

This order matters. Starting with “That will cost another $2,000” makes the price sound detached from the decision. Starting with a factual change lets the customer understand what the number buys.

Change-order script for a customer-requested addition

Use this when the customer asks the crew to add an item:

We can add that. It is outside the scope we originally priced, which covers [original work]. I’ll document the added [task or quantity], the price, and any schedule effect in a change order. You can approve the addition, choose an alternative, or keep the original job unchanged. We will not add the work until you approve it in writing.

For a small request, do not say, “No problem,” before checking it. Small tasks still consume labor, material, and schedule. If you decide to include one at no charge, document that choice so it does not silently redefine the remaining scope.

Change-order script for a concealed condition

Show the condition before discussing the solution. Use photos, measurements, test results you are qualified to provide, or an on-site walkthrough.

After we removed [item], we found [observable condition]. The original price was based on [stated assumption or visible condition], so repairing this is not included in the approved scope. We have stopped work in this area. Option A is [repair] for [price and time impact]. Option B is [alternative], with [price and time impact]. I’ll send the photos and written change order so you can decide before we proceed here.

Describe what you observed. Do not exaggerate the condition or assign blame without evidence. If the issue needs an engineer, licensed specialist, testing company, or other qualified party, say that the affected work is paused pending that review.

Change-order script for a material substitution or delay

The customer needs to know whether the original choice remains possible, what the alternatives change, and who bears the effect under the agreement.

The specified [material] is now [unavailable/delayed until date] according to the supplier. We can keep the original selection and move the affected work to [timing], or substitute [alternative] for a [price difference or credit] and a revised completion date of [date]. The rest of the approved scope [can/cannot] continue meanwhile. I’ll send both options in writing; we will order the substitute only after you approve it.

Do not present your preferred substitution as the only option unless the original is genuinely unavailable and the contract gives you that authority. State differences in performance, appearance, warranty, or lead time that matter to the customer’s decision.

Show the original scope, evidence, impact, and choices

Bring the conversation back to four facts:

The customer may ask whether the change is necessary. Answer precisely. Separate work required to complete the agreed result from an optional upgrade. Separate a code or safety issue identified by a qualified source from your recommendation. Do not use urgency to force approval when the affected work can safely wait.

If the customer declines, confirm what happens next:

Understood. We will keep the original scope unchanged and will not perform [requested addition]. The affected area will [remain as described/be paused], and the current completion date is [date]. I’ll send that confirmation with the change marked declined.

What to include in a written change order

The written change order should show at least:

• Project and change-order number
• Reference to the original agreement
• Description and reason for the change
• Added and deleted work
• Price increase, credit, or no-price change
• Added days or revised completion date
• Any effect on selections, warranties, or responsibilities
• Approval or rejection, name, and date
• Updated contract amount when applicable

Build the amount from the net cost and credit created by the change. The change-order pricing guide covers labor burden, materials, remobilization, overhead, profit, tax, and deleted work.

Follow the form, notice method, and approval path in your contract. Requirements also vary by project and location. For example, the California Contractors State License Board says that for covered California home-improvement contracts, a change to contract price or scope must be made in a written change order signed by the customer and contractor before the change. That is a California rule, not a universal US standard. Check the rules that apply where you work.

Do not treat a texted “looks good” as sufficient when the contract or law requires a particular signed form. Keep the approval with the job record and give the crew the updated scope.

What not to say when explaining a change order

Do not say:

• “We already did it, so I just need your signature.”
• “It is only a little extra.”
• “You have no choice.”
• “That was obviously not included.”
• “The office makes us charge for this.”
• “We will settle the price at the end.”

Use the record instead:

The approved scope includes [work]. This request changes it by [difference]. The written change is [amount] and [schedule effect]. Here are the available options. We will proceed after the required approval.

That explanation is firm without being defensive. The customer sees the original promise, the new decision, and control over what happens next.

Clear change communication helps preserve trust through the end of the job. A Google review management process can then place a simple request for honest feedback into the existing job-close instead of adding another manual follow-up.

Frequently asked questions

When should I tell a customer about a change order?

Tell them as soon as the request or changed condition is identified and before the affected work proceeds. Early notice gives the customer time to review the evidence, price, schedule effect, and alternatives.

What if the customer refuses a change order?

Do not perform the changed work. Continue the original scope where that remains practical and permitted, or pause the affected area when the original work cannot proceed without a decision. Confirm the customer’s choice in writing.

Is a text message enough to approve a change order?

It depends on the contract and the rules that apply to the job. Use the specified form and approval method when one is required, and keep the complete approval with the project record.