Every contractor has a story about the change order that got away. The owner asks for "just a small tweak" on-site. You accommodate it because the relationship matters. Three months later, you realize that tweak cost you $4,200 in labor and materials you never billed. Multiply that across a dozen projects a year, and you're looking at $30,000 to $50,000 in lost revenue — not because you didn't do the work, but because you didn't document it.

Change orders aren't just paperwork. They're the mechanism that keeps your project profitable when reality diverges from the original plan — and reality always diverges. According to industry data, the average commercial construction project experiences a scope change rate between 10% and 15% of original contract value. On a $500,000 project, that's $50,000 to $75,000 in work that either gets properly billed or quietly absorbed into your overhead.

Why Change Orders Go Wrong

The root problem isn't that contractors don't know what a change order is. It's that the process breaks down in predictable ways on real job sites. Understanding these failure points is the first step toward fixing them.

  • Verbal agreements without documentation — The superintendent says "go ahead and do it" on a Friday afternoon. By Monday, nobody remembers the exact scope or who authorized what. Without a written record created at the time of the conversation, you have no leverage when the invoice is disputed.
  • Delayed pricing — You start the extra work immediately but don't price it until weeks later. By then, you've forgotten half the materials you used, your crew's hours weren't tracked separately, and your estimate is a guess. Guesses almost always undercount.
  • Fear of the conversation — Many contractors, especially those building long-term relationships with general contractors or owners, avoid raising change orders because they don't want to seem difficult. This is a business decision disguised as a personality trait, and it's an expensive one.
  • Unclear contract language — If your contract doesn't define what constitutes a change, how changes are authorized, and what markup is allowed, every change order becomes a negotiation from scratch. That's exhausting and inefficient for everyone involved.
If you wouldn't do $5,000 worth of work for a new client on a handshake, don't do it for an existing client on a hallway conversation. The standard should be higher for larger relationships, not lower.

Building a Change Order Process That Actually Works

A workable change order process doesn't need to be complicated. It needs to be consistent. The contractors who capture the most revenue from changed work aren't the most aggressive negotiators — they're the most disciplined documenters. Here's a framework that works whether you're a $2 million subcontractor or a $20 million GC.

Start with identification. Every person on your team who interacts with the owner, architect, or GC needs to recognize when a request falls outside the original scope. This sounds obvious, but it's the most common failure point. Train your foremen and project managers to ask one question when they receive a directive: "Is this in our contract scope?" If the answer is no — or even maybe — it triggers the process.

Next comes documentation. Within 24 hours of identifying a potential change, create a written notice. This doesn't have to be a polished proposal. It can be an email that says: "Per our conversation today, you've requested [specific description]. We consider this outside our original scope per [contract section]. We will provide pricing within [timeframe]." That email alone is worth thousands of dollars in disputed situations.

Then comes pricing, which we'll cover in detail below. And finally, authorization — getting a signature or written approval before the work begins, or at minimum before you invoice for it.

How to Price Change Orders Without Losing the Client

Pricing is where the tension lives. Price too high and the owner pushes back or finds someone else. Price too low and you're subsidizing their scope changes with your profit margin. The key is transparency and consistency.

Build your change order pricing from three components: direct costs, indirect costs, and markup. Direct costs include the labor hours at burdened rates (base wage plus benefits, taxes, and insurance — typically 30% to 45% above the base hourly rate), materials at actual cost with receipts, equipment rental or usage, and any subcontractor costs. Indirect costs cover the project management time to coordinate the change, potential schedule impact, and any disruption to sequenced work.

Your markup should be established in the original contract. Standard change order markups in commercial construction run 10% to 15% for overhead and 5% to 10% for profit on self-performed work, with 5% to 10% on subcontractor pass-throughs. If your contract is silent on markup, you'll fight this battle on every single change order.

The best time to negotiate your change order markup is before the contract is signed. The worst time is after you've already done the work. Put your markup percentages in writing during contract negotiation, and you'll eliminate 80% of change order disputes.

Present your pricing as a clear breakdown, not a lump sum. When an owner sees "$6,400 for the electrical revision," their instinct is to push back. When they see 32 labor hours at $85/hour burdened, $1,120 in materials with supplier quotes attached, and a 15% markup that matches the contract terms, there's very little to argue with. Transparency builds trust and speeds approval.

The 48-Hour Rule and Why Timing Matters

Speed is a competitive advantage in change order management. The longer you wait to document and price a change, the worse your outcome will be — financially and relationally. Adopt what experienced project managers call the 48-hour rule: from the moment a scope change is identified, you have 48 hours to issue written notice and no more than five business days to deliver a complete priced proposal.

This matters for three reasons. First, memories are fresh. Your foreman can tell you exactly what happened and what it will take to do the work. Wait two weeks and those details evaporate. Second, the owner or GC is still mentally connected to the request. They remember asking for it, they understand why it's extra, and they're primed to approve it. Third, it demonstrates professionalism. Contractors who respond quickly to changes get their change orders approved faster and with less friction than those who submit a stack of change orders at the end of the month.

Track your change order cycle time — the number of days from identification to signed approval. If your average is over 14 days, you're leaving money on the table. Top-performing contractors keep this under 7 days for straightforward changes.

What Your Contract Needs to Say About Changes

Your contract is either your best friend or your worst enemy when a change order is disputed. Most standard contract forms (AIA A201, ConsensusDocs 200) include change order provisions, but they're general by design. You need to make sure your specific contract addresses these elements clearly:

  • Definition of a change — What constitutes work outside the original scope? Reference the specific drawings, specifications, and scope narrative that define the baseline.
  • Authorization requirements — Who has the authority to direct changes? A field superintendent? The project manager? Only the owner? Get this in writing so you know whose signature you need.
  • Markup rates — Specify your overhead and profit percentages for self-performed work, subcontractor work, and materials. Nail this down before the job starts.
  • Time for pricing — How many days do you have to submit a change order proposal after receiving a request? How many days does the owner have to respond?
  • Disputed changes — What happens when you believe something is a change but the owner disagrees? The best contracts include a "proceed under protest" clause that lets the work continue while the dispute is resolved, protecting both the schedule and your right to payment.
  • Documentation requirements — What level of backup is required? Daily time sheets? Material receipts? Photos? Define this upfront so there are no surprises during billing.

If you're working under a contract that's silent on most of these points, send a letter before work begins proposing your change order procedures. Even if the other party doesn't formally agree, you've established a documented baseline for how you intend to handle changes.

Tracking Change Orders Across Multiple Projects

Managing change orders on a single project is a process problem. Managing them across your entire portfolio is a systems problem. And it's the systems problem that separates contractors who capture 90% of their entitled change order revenue from those who capture 60%.

At minimum, you need visibility into four things across all active projects: pending change orders (identified but not yet priced), submitted change orders (priced and awaiting approval), approved change orders (signed but not yet billed), and disputed change orders (where scope or pricing is contested). If you can't pull up these four numbers for every project in under five minutes, your tracking system isn't working.

Many contractors still manage change orders in spreadsheets, which works until it doesn't. The typical failure mode is a change that gets approved in the field but never makes it into the billing cycle. The project manager knows about it, the foreman knows about it, but the person preparing the pay application doesn't — so it never appears on an invoice. Over the course of a year, these gaps add up to real money.

The change order you forget to bill costs you just as much as the one that gets rejected. Your tracking system should make it impossible to approve a change without it flowing into your next billing cycle.

Whether you use dedicated construction management software or a disciplined spreadsheet process, the key requirement is a single source of truth that connects field identification to pricing to approval to billing. Break any link in that chain and revenue leaks out.

Handling Disputed Change Orders Without Burning Bridges

Not every change order gets approved smoothly. Sometimes the owner genuinely believes the work is within your original scope. Sometimes they agree it's extra but dispute the price. How you handle these moments defines both your profitability and your reputation.

For scope disputes, go back to the contract documents. Pull up the specific drawing sheet, specification section, or scope narrative that defines your work. Show, don't argue. If the contract is ambiguous — and sometimes it genuinely is — acknowledge the ambiguity and propose a reasonable split. "We can see how this could be read either way. We'd propose splitting the cost 50/50 rather than letting this slow down the project." That kind of pragmatism builds long-term relationships.

For pricing disputes, offer to open your books. Share your labor tracking, material receipts, and rate calculations. If the owner's estimator comes back with a lower number, understand their assumptions before pushing back. Often the gap comes down to different burdened labor rates or a disagreement about how many hours the work actually took. Daily time sheets with foreman signatures close these gaps quickly.

For chronic disputes — where every change order becomes a battle — the problem is usually upstream. Either the contract language is inadequate, the original scope was poorly defined, or there's a trust deficit between the parties. Address the root cause rather than fighting each change order individually. A 30-minute meeting to align on the change order process can save dozens of hours of dispute over the life of a project.

Measuring Your Change Order Performance

What gets measured gets managed. Track these metrics quarterly and you'll have a clear picture of how well your change order process is working:

  1. Capture rate — Of all identified changes, what percentage made it to a submitted proposal? If this is below 85%, work is falling through the cracks between identification and pricing.
  2. Approval rate — Of submitted proposals, what percentage were approved? A rate below 70% suggests pricing or documentation issues. Above 90% might mean you're underpricing.
  3. Cycle time — Average days from identification to signed approval. Benchmark against your 7-day target for simple changes, 14 days for complex ones.
  4. Collection rate — Of approved change orders, what percentage were billed and collected? This should be 100%. Anything less means your billing process has a gap.
  5. Change order revenue as percentage of contract value — Compare this against industry averages for your project type. If your projects consistently show 2% change order revenue on project types that typically run 10% to 15%, you're probably under-identifying changes.

Review these numbers with your project managers monthly. The conversation shifts from "did you submit that change order?" to "our capture rate dropped 8 points this quarter — what's breaking down?" That's a much more productive discussion.

Change order management isn't glamorous work. It doesn't show up in project photos or award submissions. But it's one of the highest-leverage activities in construction project management — a disciplined process can add 3% to 5% to your net margins without winning a single additional project. Build the process, train your team, track the numbers, and stop giving away work you've already earned.