• The Three Paths for an Estimate Revision
  • The Change Order Decision Tree

Estimate revisions are the part of the workflow where small businesses lose the most margin. The original estimate sets the price, the client signs, work begins, then something changes. The way you handle that next 30 minutes determines whether the change comes out of your profit or the client's budget. This guide is the protocol.

Quick Answer Handle estimate revisions by routing them through three distinct paths based on timing: if the estimate has not been accepted yet, amend it directly with a new version number; if the estimate is signed and work has not started, issue a revised estimate that replaces the original (and re-collect signature); if work has started, never edit the estimate, issue a separate signed change order that adds to (or credits) the original. Every revision needs a clear "what changed, what it costs, what it does to the timeline" written down before any work proceeds.

Key Takeaways

  • Organizations with high-performing project management are 2.3 times more likely to prevent scope creep, per the PMI Pulse of the Profession 2024.
  • Projects without formal change management are 35 percent more likely to exceed costs or miss deadlines, per PMI data.
  • Change orders average 10 percent of contract value, with some reaching 25 percent, per Rhumbix's change order analysis.
  • The single most effective practice for handling revisions is naming the change order process in writing before the estimate is signed.
  • Cost increases of more than 10 to 15 percent usually warrant a new estimate, not a change order on the existing one.

This guide is built for service businesses, freelancers, and small contractors. The core protocol works in any industry where you quote scope and price up front.

The Three Paths for an Estimate Revision

Every revision belongs in one of three categories based on timing. Use the wrong path and you create a dispute.

Path A: Pre-Acceptance Revision (Estimate Not Yet Signed)

The estimate has been sent, the client has questions or wants changes, but they have not signed yet. This is the easiest case.

What to do:

  • Edit the estimate directly
  • Increment the version number (EST-2026-118 v1 becomes EST-2026-118 v2)
  • Save the old version
  • Send the new version with a one paragraph summary of what changed

Path A revisions are normal. They are part of selling. The discipline is to track version numbers so neither side gets confused about which estimate is the operative one.

Path B: Post-Acceptance, Pre-Work Revision

The estimate is signed but work has not started (the deposit may or may not be paid yet). The client wants a change.

What to do:

  • Treat the original estimate as canceled
  • Issue a new estimate (new number, not a v2) referencing the original
  • Re-collect signature
  • If the deposit has been paid, either apply it to the new estimate or refund it

This path is more sensitive because the client thought the agreement was settled. A short call before the new estimate goes out usually helps. Frame the new estimate as "let me build a fresh one so the math is clean."

Path C: Post-Work Revision (Change Order)

Work has started. The scope, the timing, or the price needs to change. This is the case where margin is most often lost.

What to do:

  • Never edit the original estimate
  • Never edit any invoice that has been issued
  • Write a separate change order document
  • Get it signed before doing the changed work

The change order is the protocol that protects both sides. It tells the client exactly what they are agreeing to, and it gives you a defensible record if the cost is disputed later.

The construction industry uses AIA Document G701 for this purpose. Service businesses can use a simpler one-page form. The principle is the same.

The Change Order Decision Tree

Within Path C, not every change should be a change order. Some changes are absorbed (your error, small adjustments) and some are renegotiations (the project structure changed). The decision tree:

Did the client request a change to scope, deliverables, or timeline?
├─ No → Continue under original estimate
└─ Yes → Is the cost impact more than 10 percent of original price?
   ├─ No → Issue a change order, work proceeds
   └─ Yes → Pause and discuss before any change order

Was the change caused by your error or omission?
├─ Yes → Absorb the cost. Do not issue a change order.
└─ No → Change order if scope, renegotiation if structure

Did the change make the original estimate no longer realistic?
├─ Yes → Renegotiate. Issue a new estimate or terminate cleanly.
└─ No → Change order, work proceeds

The 10 percent threshold is a rule of thumb. The principle is that a small change feels like an adjustment to the client; a large change feels like a new project. Trying to bolt a large change onto the existing estimate as a change order tends to break trust.

What Triggers a Revision

Not all changes are equal. Some are easy, some are hard. A clear list helps both sides agree on the trigger.

Triggers a Revision or Change Order

  • New deliverables added
  • Existing deliverables changed in size or complexity (the 5 page site becoming 12 pages)
  • New stakeholders requiring additional review rounds
  • Material or unit price changes outside the estimate's validity window
  • Schedule changes that affect the work (rush adds, hold periods)
  • New requirements (accessibility, compliance, integration)

Does Not Trigger a Revision

  • The order of work, if total scope is preserved
  • Minor process tweaks that do not change the deliverable
  • Schedule shifts caused by the client (but does require a written record)
  • Tool changes that produce the same outcome
  • Clarifications that do not expand scope

The principle is the same one from estimate vs invoice best practices: if either side wants a different outcome than the estimate described, revision or change order. If they want a different path to the same outcome, no revision needed.

A Communication Script for Cost Changes

The hardest part of an estimate revision is telling the client the price went up. The script below works in most cases. It has four steps.

Step 1: State What Changed (Neutral)

"We talked yesterday about adding the analytics integration. Here is what that adds to the project."

Step 2: State the Cost and Timeline Impact

"The integration adds 12 hours of work, which is $1,800, and pushes the launch by 3 business days."

Step 3: State the Options

"We have two paths: we can add this as a change order, or we can swap out the post-launch tweak window for the integration work, which keeps the price flat."

Step 4: Ask for the Decision

"What would you prefer?"

The reason this works: it does not apologize. It does not over-explain. It treats the cost change as a normal operational decision. Apologizing for a legitimate cost change trains the client to push back on every change.

Scope Creep Prevention

Scope creep is the slow drift where the project grows without anyone noticing until the budget is already gone. The PMI Pulse of the Profession 2024 found that organizations with high-performing project management are 2.3 times more likely to successfully prevent scope creep, and projects without formal change management are 35 percent more likely to exceed costs or miss deadlines.

Four practices that prevent scope creep:

1. Pre-name the Change Order Process in the Estimate

Add a sentence to every estimate: "Scope changes are documented in a signed change order before work proceeds. Out-of-scope work is billed at $X per hour, agreed in writing first."

This sentence does most of the work. When a change comes up, you reference the estimate clause. The client has already agreed to the process.

2. Define "Not Included" as Explicitly as "Included"

Most scope creep enters through the gaps in the original scope. List exclusions as carefully as inclusions:

  • Not included: paid ad creative
  • Not included: more than two rounds of revisions per deliverable
  • Not included: translations or localization
  • Not included: integrations beyond [list]

When something comes up that touches a "not included" item, the conversation is short.

3. Use the 24-Hour Rule

When a scope change request comes in, do not commit on the spot. Reply within 24 hours with a written assessment of the cost, timeline impact, and options. The 24-hour rule slows the conversation down enough for both sides to think.

4. Track Out-of-Scope Time

If you are doing fixed-price work, you still need to track hours internally. When out-of-scope requests show up, the tracker shows you exactly what they cost. A pattern of 5 hours of "quick favors" per week is 250 hours per year of unpaid work.

For the mechanics of tracking time on fixed-price work, see our guide to hourly invoicing.

Change Order Math

The change order has its own math, separate from the original estimate's. Two common approaches:

Approach 1: Cost Plus Markup

For change orders on construction or trade work, the convention is cost plus 15 to 25 percent markup. The change order line items reflect the additional materials and labor; the markup covers your overhead plus profit on the new work.

Example: a residential remodel adds a $4,000 plumbing scope.

Materials: $1,400
Labor: $2,000
Subtotal: $3,400
OH&P markup (18 percent): $612
Change order total: $4,012

Approach 2: Fixed Add

For service work, change orders are usually quoted as a fixed add. The math behind it can use the same logic, but the client sees a single number.

Example: a marketing project adds a 5-day support extension.

Add: 5 day post-launch support extension
Cost: $850
Timeline impact: launch unchanged

The fixed-add format is easier for clients to approve. Use it when the work scope is clearly defined.

Two Templates

Template A: Pre-Acceptance Revised Estimate

Estimate #EST-2026-203 v2
Issued: 22 May 2026
Replaces: EST-2026-203 v1 (issued 20 May 2026)
Expires: 5 June 2026

What changed in v2
- Added 7 day launch email sequence to the recommended option
- Reduced "Premium" support window from 90 days to 60 days
- Price impact: recommended option moves from $7,200 to $8,400

[Rest of estimate unchanged from v1]

The "What changed" block is the only essential addition. It makes the diff obvious so the client does not have to compare line by line.

Template B: Post-Work Change Order

Change Order #CO-2026-009
Issued: 12 June 2026
Project: Acme Co. Q3 launch microsite
Original estimate: EST-2026-203

Description of change
Add 5 business day support extension to handle the additional A/B testing
window requested by the client on 10 June 2026.

Cost impact
- Add: 5 day support extension          $850.00
- Net new charge: $850.00

Schedule impact
- No change to original launch date
- Support window now ends 14 August 2026 (vs 9 August in original)

Approval
By signing below, both parties agree to this change order. The original
estimate and any prior change orders remain in effect except as modified
here.

Client signature: _________________  Date: _______
Contractor signature: _____________  Date: _______

The signatures matter. An unsigned change order is an argument waiting to happen.

When to Issue a New Estimate Instead of a Change Order

The change order works for incremental changes. There comes a point where the project has changed enough that a new estimate is more honest. The threshold:

Change magnitude Use
Under 10 percent of original price Change order
10 to 25 percent of original price Change order, but pause and call first
Above 25 percent of original price Issue a new estimate, terminate the old one cleanly
Structural change to the project (different deliverable, different goal) New estimate regardless of dollar amount

The benefit of issuing a new estimate at the larger thresholds is that both sides re-evaluate the full project. The change-order route can hide the fact that the new project is no longer the project either party agreed to.

For converting estimates to invoices after a revision, the estimate vs invoice best practices guide covers the document trail (original estimate -> deposit invoice -> change orders -> final invoice with all referenced).

Communicating Material Price Changes

For construction and trade work, material prices move. An estimate dated three months ago may no longer match supplier prices. Two approaches:

Approach 1: Estimate Validity Period

State on the estimate: "Valid for 14 days from issue. Material prices subject to verification at contract signing."

After 14 days, you have the right to re-quote. Most clients understand this for trade work.

Approach 2: Price Escalation Clause

For larger projects with longer sales cycles: "If steel prices change by more than 5 percent between estimate date and order date, the steel line item will be adjusted to reflect supplier pricing at order date."

This is more common on commercial work. The clause has to be in the original estimate to be enforceable.

For 2026 context, building material prices were up 3.5 percent year over year in late 2025, per the NAHB analysis of BLS data. For trade businesses, two months of price drift can eat your margin. Validity periods matter.

Common Pitfalls in Revision Handling

The patterns we see most often:

  • Verbal change orders. "Yeah, I can add that, no problem" said on a phone call. With no written record, the client remembers it as a free add and you remember it as a $1,500 line item.
  • Bundling multiple changes into one change order weeks later. The client sees a $12,000 change order at the end of the project and disputes the whole thing. Issue change orders as changes happen.
  • Editing the original estimate. Once signed, the original estimate is part of the agreement. Editing it weakens the audit trail. Use change orders.
  • No clear approval mechanism. A change order signed by the project manager but not the budget owner is not enforceable in many corporate contexts.
  • Absorbing too many small changes. A 30-minute favor here, a $100 fix there. After 20 projects, you have given away two weeks of work. Track everything, even what you absorb.

What Triggers a Full Renegotiation

Sometimes the project has changed enough that neither the change order nor the new estimate is the right move. Renegotiation is appropriate when:

  • The original scope is no longer the goal (the client pivoted)
  • Key stakeholders changed and the new ones want a different approach
  • External events (regulation, supplier failure, key team departure) made the original plan infeasible
  • The relationship has deteriorated enough that the change order conversation is unproductive

In a renegotiation, both sides are free to walk away. Sometimes that is the right outcome. For the legal mechanics of ending a signed agreement cleanly, see our guide on how to cancel a signed quote.

How to Recover from a Rejected Revision

A client may reject your change order. The most common reasons and what to do:

Stated reason Real reason What to do
"I thought this was included" Original scope was unclear Walk through original estimate's exclusions, calmly. Offer to reduce scope to fit budget.
"That's too expensive for the change" Sticker shock Break down the cost into materials, labor, OH. Reduces the feeling of arbitrariness.
"I'll have my internal team do it" They want to avoid paying you Confirm in writing that the work is out of scope. Document that the change was offered and declined.
"Can we just skip the change?" Budget is real Offer two paths: skip the change (no cost, no benefit) or descope something else to fit the change.

Document the rejection. If the client later complains that the deliverable does not include the rejected scope, the written record settles the argument.

FAQ

What are estimate revisions? In project work, an estimate revision is any change to the original estimate's scope, price, or timeline. Pre-acceptance revisions edit the estimate directly. Post-acceptance revisions either replace the original estimate or get handled as separate change orders.

(Note: in stock market analysis, "estimate revisions" refers to analyst changes to earnings forecasts. That is a different topic. This guide covers project estimate revisions for service and contractor businesses.)

When should I issue a new estimate vs a change order? Change orders for changes under 10 to 15 percent of original price. New estimates for changes above 25 percent, or any structural change to the project. The 10 to 25 percent range is judgment-based; a phone call before the change order goes out usually clarifies the right path.

How do I improve estimates so revisions are less frequent? Three changes that have the biggest effect: list exclusions as carefully as inclusions, name the change order process in the original estimate, and track actuals against estimates after every project. See our guide to estimating project hours accurately for the longer playbook.

Do I need the client's signature on a change order? Yes. A change order without the budget owner's signature is not enforceable in most disputes. For small projects, an email approval with clear language ("approved to proceed with change order CO-009 at $850") is usually enough. For larger projects, a signed PDF is worth the extra minute.

What if the client refuses to sign a change order but wants the work? Do not do the work. State in writing that the change is out of scope, requires a signed change order, and you cannot proceed without it. If they push for the work anyway, the lack of signature is your defense if the bill is later disputed.

Should the change order include a deposit? For change orders that materially increase the project (above 20 percent of the original total), yes. Match the deposit terms of the original. For smaller change orders, fold the additional cost into the next milestone invoice. See our guide to deposit invoicing.

What about scope creep that nobody formally requests? Track it. Many scope changes enter as informal asks ("can you also..." in a meeting). When you spot one, send a one-line email: "Adding this to the change order tracker. I'll send the change order shortly." That email starts the paper trail.

Can a change order reduce the price? Yes. Change orders can credit the contract for removed scope. The math works the same way, with the cost as a negative number. This is common on construction projects when the owner cuts scope to fit budget.

When This Guide Isn't for You

  • Pure agile contracts with continuous billing. If you bill by sprint regardless of scope, revisions are handled in sprint planning, not change orders. The principles transfer (decision tree, communication script) but the mechanism is different.
  • Government contracts. Federal and state contract modifications follow specific FAR rules. Change orders on government work require formal modifications, not the simplified protocol in this guide.
  • AIA-contract construction. For construction projects on AIA contracts, use AIA Document G701 rather than a custom change order form. The protocol is the same; the document is standardized.
  • Pure product sales. Subscription changes are handled by the order form, not a change order. SaaS contracts have their own modification process.
  • Hourly retainers. Open-ended hourly work does not need revisions or change orders in the project sense. Scope is set per period. See our retainer invoicing guide.

How We Verified This

Where sources disagreed (most commonly on the typical size of change orders by industry), we used the most current figures and noted the range.

Related Articles

Quick checklist

0 of 16 completed0%
Share

Was this article helpful?