Change Orders 101: How to Estimate and Price Scope Changes Fairly

Change orders are where a lot of contractor-client relationships either stay healthy or start to sour, and the difference usually comes down to how the pricing is handled, not whether a change was needed in the first place. Priced fairly and documented clearly, a change order is a routine part of construction. Priced inconsistently or explained poorly, it becomes the thing clients remember most about the project.

What Actually Counts as a Change Order

A change order is a formal, documented modification to the original scope of work, cost, or schedule, agreed to by both parties after the contract was signed. It's distinct from normal project execution decisions that fall within the original scope, and distinct from a contractor simply doing extra work informally without documentation, a practice that creates real risk for both parties if a dispute arises later.

Change orders generally originate from one of a few sources: an owner-requested change (a new finish selection, an added feature), a design or drawing error discovered during construction, an unforeseen site condition (common in renovation work, where existing conditions aren't fully knowable until walls or floors are opened), or a code-required change identified during inspection.

Why Change Order Pricing Should Differ From Base Bid Pricing

A common mistake is pricing change order work at the exact same markup applied to the original competitively bid work. That approach undervalues real differences between the two:

There's no competitive pressure on a change order. The client has already selected you for the project; you're not competing against other bidders for this specific piece of additional work, which changes the pricing dynamic entirely.

Change orders disrupt planned sequencing. Work that wasn't part of the original schedule interrupts planned crew movement and material staging, a real cost that a straightforward base-bid markup doesn't capture.

Smaller change orders carry disproportionate administrative overhead. Processing, documenting, and pricing a $2,000 change order requires nearly as much administrative time as a $20,000 one, meaning the overhead recovery per dollar needs to be higher on smaller change orders to actually cover that fixed cost.

Given these factors, change order markup commonly runs 15 to 25 percentage points higher than base bid markup. If your standard project markup is 25%, a change order markup in the 40% to 50% range is a defensible, commonly used approach, provided it's disclosed and understood by the client upfront rather than sprung on them at change order time.

Building a Fair, Defensible Change Order Estimate

Document the trigger clearly. State specifically what caused the change: an owner request, a discovered condition, a design revision, referencing the specific drawing, spec section, or field condition involved. This documentation matters enormously if a dispute arises later over whether a cost was genuinely outside the original scope.

Price it with the same rigor as the original estimate. A change order deserves an actual takeoff and current pricing, not a rough verbal estimate. Rushed, imprecise change order pricing is a common source of disputes, since an inaccurate number discovered later damages trust in a way that a clearly justified, well-documented number doesn't.

Include both direct and indirect costs. Direct costs (materials, labor for the specific added work) are usually straightforward to capture. Indirect costs, schedule impact, disruption to other trades, additional supervision time, are easy to underprice or forget entirely, and they're often the larger cost driver on a change order that seems small on paper.

Quote schedule impact explicitly, not just cost. A change order that adds work without extending the schedule implicitly assumes the added work fits into existing float, which isn't always true. State clearly whether the change affects the completion date, and by how much, rather than leaving that connection unaddressed until it becomes a dispute later.

Get written approval before proceeding, not after. Performing change order work before receiving signed approval creates exactly the ambiguity that leads to payment disputes, regardless of how reasonable the pricing ultimately turns out to be.

Handling Owner-Requested vs. Discovered-Condition Change Orders Differently

Owner-requested changes (a new fixture, an added feature) are generally the most straightforward to price and the easiest for clients to accept, since the change is visibly something they asked for. Clear, prompt pricing and a fast approval turnaround keeps these from becoming friction points.

Discovered-condition change orders (water damage found during demolition, outdated wiring that doesn't meet code, soil conditions different than assumed) are more likely to generate pushback, since the client didn't choose the added cost and may feel blindsided by it. These require more careful documentation, photographs of the discovered condition, clear explanation of why it wasn't identifiable before demolition or excavation began, and a transparent walkthrough of the pricing, to maintain trust through what's often a frustrating moment for the client.

A Detail Worth Knowing: Set Expectations Before They're Needed

The single most effective way to keep change orders from damaging a client relationship is addressing the topic before the project even starts, not after the first change order arrives. A brief, plain-language explanation in the original contract or proposal, how change orders will be priced, what markup applies, how quickly they'll be documented and presented, sets an expectation the client can refer back to later, rather than encountering the policy for the first time in the middle of a disagreement over an unexpected cost.

Common Change Order Mistakes

• Performing the work before getting written approval, creating ambiguity over what was actually authorized
• Pricing inconsistently across different change orders on the same project, without a clear, repeatable methodology
• Failing to document the specific trigger, leaving the change order's justification vague if questioned later
• Ignoring schedule impact, then facing pushback when the completion date shifts without prior explanation
• Underpricing indirect costs, disruption, supervision, sequencing impact, that are real but less visible than direct material and labor costs

The Bottom Line

Change orders aren't a sign something went wrong with the original estimate; they're a normal part of how construction projects evolve as real conditions and real decisions unfold. What separates a change order process that protects a client relationship from one that damages it is consistency, documentation, and transparency: a clear trigger, a rigorously priced estimate, appropriately higher markup that's disclosed upfront, and written approval before work proceeds.

Change order disputes almost always trace back to unclear scope or inconsistent pricing. A documented process, set before the first change order ever comes up, protects both the relationship and the margin.