How to Revise an Estimate When a Customer Changes the Scope

A customer calls you back two days after you sent a quote. "Actually, can we do the whole fence instead of just the back section?" Or they text you a photo of a tile they saw on Pinterest that costs three times what you priced. Or the walk-through where you measured 1,200 square feet turns into "oh, we also want the hallway and the stairs."

None of that is a change order. A change order happens mid-job, after the customer has already signed off and your crew is on site. What happens before work starts — when the scope shifts while the estimate is still sitting in the customer's inbox — is a revision. Treat it like one, or you'll end up doing work nobody agreed to pay for.

{"h2":"Why verbal yeses on scope changes bite you later"}

The instinct is to handle it like a normal conversation. The customer mentions the extra section of fence, you do some mental math, you say "yeah, that's probably another $600 or so," and you move on. Three weeks later you invoice for the job and the customer is shocked the price went up. They remember you saying "probably" and "around." You remember quoting a hard number. Neither of you has it in writing.

This is the same trap covered in giving an estimate range without making a firm promise — a ballpark number spoken out loud turns into a promise in the customer's memory, even when you never meant it that way. Scope changes make this worse because now there are two numbers floating around: the original estimate and whatever you said on the phone. When the invoice doesn't match either one, you're the one explaining yourself.

{"h2":"Revise, don't verbally amend"}

When a customer changes the scope before work begins, the estimate needs to change too — as a new, numbered document, not a mental adjustment. That means:

{"ul":["Pull up the original estimate and create Revision 2 (or 3, or however many it takes). Keep the same job number so it's clearly tied to the same project.","Show the delta, not just the new total. List what was added or removed and what it costs, separate from the line items that didn't change.","Reset the validity date. The original 30-day window doesn't carry over to a bigger job with different material costs.","Get approval again, in writing, before you schedule or order anything."]}

Each of those steps closes a specific gap. Let's go through them.

{"h2":"Keep the revision numbered and tied to the original"}

Don't delete the first estimate and start fresh — version it. Estimate #1042 becomes Estimate #1042 Rev. 2. This matters for two reasons. First, if the customer ever asks "wait, what did you originally quote me for just the fence?" you can pull it up instead of reconstructing it from memory. Second, if there's ever a dispute, a numbered revision history shows you documented the change as it happened rather than padding the price after the fact. A single, unversioned document that keeps getting edited looks exactly like that to a skeptical customer, even when it isn't.

{"h2":"Show what changed and what it costs"}

A revised estimate that just shows a new bottom-line total is the fastest way to trigger a "why did it go up so much?" phone call. Instead, make the change visible:

{"ul":["Line items removed: show them struck through or in a clearly labeled \u201cremoved\u201d section, with the dollar amount they take off the total.","Line items added: list them the same way you'd list any other item on the price book \u2014 quantity, unit price, extension \u2014 so the customer can see it's not a made-up number.","A short note at the top: \u201cRevised 3/14 to add 40 linear feet of fence and upgrade from pressure-treated pine to cedar, per phone conversation.\u201d"]}

That note matters more than it looks like it should. It's the difference between a customer feeling informed and a customer feeling like the price crept up on them. If you're estimating off a contractor price book instead of guessing, the added or removed items should already have real unit costs attached, which makes this step fast instead of another round of manual math.

{"h2":"Reset the validity date"}

Most written estimates carry an expiration date for good reason, as covered in whether to put an expiration date on an estimate — material costs move, your schedule fills up, and a 45-day-old number isn't a number you want to be held to. A scope change is a natural reset point. If the original estimate was good through the end of the month, the revision should get its own fresh window from the day you send it, not the leftover days from the original. This also gives you a clean reason to re-check material pricing on anything that's volatile, which matters if you're pricing a job where material costs keep changing.

{"h2":"Get approval again before anything moves"}

This is the step people skip because it feels redundant — "they already said yes on the phone, why do I need another signature?" Because a phone call isn't a record. Send the revised estimate the same way you'd send the first one, through an online approval flow if you have one, and don't schedule the crew or order the upgraded materials until it's approved. This isn't about distrust — it's about making sure the number the customer sees is the number they're committing to, with no gap between a phone conversation and an invoice.

{"h2":"Where the revision line stops and the change order starts"}

The cutoff is simple: if the crew hasn't started the job yet, it's a revision to the estimate. If the crew is mid-demo and the customer decides they want recessed lighting added, that's a change order, and it gets priced and documented differently — including how it affects a job that's already using labor and materials on site. That process is covered in change orders 101, including how to price mid-job additions without eating the cost yourself. Mixing the two up is how contractors end up either under-pricing a pre-job change because it felt informal, or over-complicating a simple revision with change-order paperwork it doesn't need yet.

{"h2":"Why this is worth the extra five minutes"}

A revised, numbered estimate with a clear delta takes maybe five minutes longer than just saying "sure, I'll add that in" on the phone. What it buys you: a customer who can't claim they didn't know the price changed, a document trail if a dispute ever comes up, and a number you're actually confident charging instead of one you half-remember agreeing to during a jobsite walk-through.

In Trusso, a scope change on an unapproved estimate works this way by default — editing line items creates a new revision with the old version preserved, the validity date resets automatically, and the customer has to approve the updated total before the job moves to scheduling. You're not maintaining two versions of the truth in a text thread and a quote; there's one document, and it's always the current one.