Change Orders: The Basics

Say you're the project manager on a mid-size office renovation. Six weeks in, the owner walks the site and decides they don't like the lobby tile they picked back at the start of the project; they want a different, more expensive tile instead. Nobody flagged this as a possibility in the contract. Nobody built it into the schedule. And the tile crew is supposed to start in four days. This is exactly the situation a change order exists for. Owners changing their minds isn't rare; it happens on almost every project of any size. The problem is that a construction contract only covers what's actually written into it: a specific scope, at a specific price, on a specific schedule. The moment any of those three things changes, the contract itself is technically wrong, and technically-wrong contracts are where disputes come from. A change order is the fix: a short written document, signed by both the owner and the contractor, that says exactly what's different and what that difference costs, in money, in time, or both. Here's what one actually contains. Not much, by design: a description of the changed work in plain language ("replace specified lobby tile (Product A) with upgraded tile (Product B), 800 square feet"), the price difference, any schedule impact, and two signatures. That's it. The whole point is that it's simple enough to turn around fast, because the crew that was supposed to start in four days is still waiting on an answer. Now play out what happens if the project manager skips this step, which happens constantly, usually with good intentions. The owner says "yes, let's do the upgraded tile, just go ahead," the PM tells the tile subcontractor to proceed, and everyone moves on without paperwork. Two things go wrong from here, and neither shows up immediately. First, the price was never actually agreed to in writing. Say the upgraded tile costs $4,200 more in material alone, plus two extra days of labor. If the owner later disputes that number (maybe they remember a different verbal figure, maybe they just decide $4,200 feels high once the invoice arrives), there's no signed document settling it. Second, the schedule impact never got acknowledged anywhere. If the tile delay pushes the painters back, and the painters push the final inspection back, the contractor now owns a two-week schedule slip with no paper trail showing the owner caused it. Change orders aren't bureaucracy for their own sake; they're what keeps "the owner asked for this" provable months later, when nobody remembers the conversation the same way.

There's also a timing lesson buried in here that experienced people learn the hard way: get it signed before the work starts, not after. Once the tile crew has already ripped out the old floor and started setting the new one, the owner knows the job is happening either way, and that changes the negotiation completely. Contractors who chase change order signatures after the fact routinely end up settling for less than the change actually cost them, simply because they gave up their only real leverage: the ability to say "we won't start until this is signed." A good project manager treats "get the signature first" as close to a hard rule, even when a client is pushing for speed. The paperwork feels slow in the moment; being unable to prove what you're owed feels much slower six months later. Picture the same tile example again: if the crew finishes installing the upgraded floor before anyone signs anything, the owner has little reason to agree to the full $4,200 difference: the floor exists either way, and every extra day spent negotiating just delays the next trade, which is now the contractor's problem, not the owner's. Whatever number the owner offers to close it out quickly, the contractor is negotiating from behind, not from "we won't move forward until this is signed." Multiply that pattern across a project with fifty or sixty change orders over its life, which is completely normal on a project of any real size, and it's the difference between a contractor who protects their margin all year and one who quietly gives small pieces of it away, order by order, without ever seeing one dramatic loss to point to.

There's more than one way to actually price the changed work, and which one gets used matters. The simplest is lump sum: the contractor quotes one total number for the change, the owner accepts or negotiates it, and that's the price, fast, but it puts the estimating risk on the contractor if they under-price it. Unit pricing works well for anything measured in a quantity that might shift, like square footage of tile or cubic yards of concrete: the original contract already has an agreed price per unit, so the change order just multiplies that rate by the new quantity. Time and materials, usually shortened to T&M, is the fallback for anything genuinely hard to estimate in advance: the contractor tracks actual labor hours and material costs as the work happens, with an agreed markup on top. T&M is common for anything that turns out to be a bigger mess than expected once a wall gets opened up, but it's also the pricing method most likely to make an owner nervous, since the final number isn't locked in ahead of time. It's also worth being precise about what does and doesn't need a change order at all. A request for information, an RFI, that gets answered with no cost or schedule impact doesn't need one; nothing about the contract changed, only a detail got clarified. A minor schedule shuffle within the contractor's own control, like moving a subcontractor's start date by a couple of days to work around weather, usually doesn't either, as long as it doesn't affect the overall completion date or the price. What triggers a change order is specifically a change to scope, price, or the contracted schedule, something the owner is agreeing to that's different from what they originally signed up for. Confusing these categories is one of the most common mistakes new project engineers make: treating every field decision as either "nothing" or "change order," when a lot of real jobsite decisions fall in a middle zone that just needs to be documented as a clarification, without reopening the contract.

Sometimes a disagreement over a change doesn't get resolved informally: the two sides genuinely can't agree on what was promised, or one side believes a change order should have been issued and never was. That's when it escalates from a conversation into a formal claim, often reconstructed from every RFI, email, and daily report on the project to establish what actually happened and when. This is a large part of why construction disputes can drag on for months: piecing together intent after the fact from scattered records is slow and expensive, compared to having had a signed change order in the first place. It's also exactly the kind of problem construction claims consultants get brought in to untangle on larger or more contentious projects; an entire career path exists around exactly this gap. If you're the one filling one out, a few habits separate a change order that gets signed same-day from one that sits on someone's desk for two weeks. Be specific about scope: "upgraded lobby tile" invites a dispute about what counts as upgraded; "Product B, 800 square feet, per attached spec sheet" doesn't. Price it the way the original contract was priced, using the same markup and labor rates already agreed to, rather than negotiating a fresh number from scratch. And say plainly whether the schedule moves, even by a day, even if it feels like something everyone will just understand informally.

If you're new to the industry, change orders are usually one of the first real responsibilities handed to a Project Engineer, precisely because they're contained enough to learn on and consequential enough to matter. Getting comfortable with the mechanics here is a fast way to look competent in your first few months on a job, well before anyone expects you to run a whole project on your own. The pattern to actually remember, more than any of the specific mechanics: a signed change order is the only thing standing between "we agreed to this" and "we're now arguing about what we agreed to." Everything else about the process exists to make that one sentence hold up under pressure, months after everyone's memory of the conversation has started to drift. If any part of this sounded like something you'd want to do for a living, the Project & Operations interview guide covers what interviewers actually ask about change-order judgment calls, among other day-to-day project management questions.