Every job has that moment. You're three weeks into rough-in, the owner walks the space with the architect, and somebody decides the electrical room needs to move eight feet to the left. Now you've got a change order coming, and the real question isn't whether it gets priced fairly — your PM will fight that battle. The question is what it does to next week's work plan, and whether your framers and your electrician are about to run headlong into each other because the schedule still shows the old layout.
Change orders don't just cost money. They cost sequence. And sequence is the thing that quietly kills a schedule long before the budget ever raises a flag. This is where the connection between your change management process and your look-ahead scheduling actually matters — not in the ledger, but in the field, in the next 10 working days, where a missed hand-off turns into a crew standing around.
Separate the paper trail from the field decision
The first mistake I see supers make is treating a change order as a single event: it gets approved, then it gets built. In reality there are two clocks running, and they almost never line up.
There's the contractual clock — the request, the pricing, the owner's signature, the executed CO. That can take two weeks or two months depending on the owner and the design team. Then there's the field clock — the moment the work actually has to happen so it doesn't hold up everything downstream of it. If you wait for the paper to catch up to the field, you'll blow the schedule. If you build ahead of the paper with no documentation, you'll eat the cost when the negotiation goes sideways.
The discipline that separates good jobs from bad ones is this: decide early, in writing, whether a change proceeds on a T&M basis, on a not-to-exceed, or waits. Track that decision as its own thing, distinct from the executed change order. Your weekly work plan lives on the field clock. Your cost report lives on the contract clock. Keep them straight or they'll both lie to you.
Do the schedule impact assessment before you price the work
Most change order impact assessments are all dollars and no days. Somebody counts up the added material and labor, tacks on markup, and calls it done. Then three weeks later the owner is furious because the "small" $12,000 change pushed substantial completion by nine days and nobody warned them.
When a change lands, walk it through your look-ahead the same way you'd walk a new activity:
- What does it add? New activities, new inspections, new material with a lead time you don't have.
- What does it delete or rework? Demo of work already in place is the silent killer here — you're paying to build it, then paying to tear it out, and both eat calendar.
- What does it re-sequence? This is the one everyone misses. Moving that electrical room doesn't just add conduit; it changes the order the framers, the sheet-metal crew, and the drywallers hit that corner of the building.
- What's the lead-time exposure? If the change needs a switchgear that's 14 weeks out, the labor is trivial and the procurement is the whole story.
A change that's schedule-neutral and a change that costs you two weeks can carry the same dollar figure. The owner needs to hear the days at the same time they hear the money, and you need a look-ahead you can actually run the "what if" against before you commit to a number. Pricing a time extension after the fact, once you're already behind, is a losing argument every time.
Keep pending changes visible in the weekly work plan
Here's a habit that pays for itself. When a change is pending — priced but not signed, or directed but not yet papered — it should show up in your short-interval schedule flagged as pending, not hidden until it's official.
Why? Because your foreman is planning next week around what he can see. If the pending duct rerouting isn't on the board, he'll load the ceiling grid crew into that area on schedule, and now you've either got them working over top of a change that's about to happen or, worse, you close a ceiling you're about to reopen. A pending change that's visible lets the field plan around it. A pending change that's invisible becomes rework.
The way I run it: pending change activities go on the look-ahead in a distinct state — everyone can see them, nobody commits crews to the affected area until the direction is firm, and the moment it converts to an approved change it drops cleanly into the plan without anybody having to remember it existed. Good look-ahead scheduling software handles this natively, letting you park a tentative activity in the plan and promote it when it's real. If you're running the whole thing on a spreadsheet, this is exactly the kind of thing that falls through the cracks at 4:45 on a Friday.
Watch the trade-flow hand-offs, not just the added scope
The added work in a change order is usually the easy part. The damage is at the seams — where the change touches a hand-off between two trades that were already sequenced.
Say a change adds blocking in a wall that's already framed. On paper it's a half day of carpentry. In practice: the electrician was scheduled to pull wire in that wall Tuesday, the insulator Thursday, drywall Friday. Your half-day of blocking has to slot in before the electrician, which means either you pull the electrician off for a day or you push the whole chain right. If you don't map that hand-off, you find out about it when the electrician shows up Tuesday to a wall that's now open again.
This is the case for building your look-ahead around location-based trade flows rather than a flat activity list. When you can see the sequence of crews moving through a space — frame, rough-in, inspect, insulate, close — a change that inserts a step lights up the collision immediately. You see the pinch point before the crews do. That's the whole point of short-interval planning: catch the constraint two weeks out, when moving a crew costs a phone call, instead of two days out, when it costs a no-show and a day of standby.
Document the field conditions in real time — future-you will need it
Half of change order disputes come down to one question the owner asks six months later: "Why did this cost what it cost?" And the honest answer is usually buried in a field condition nobody wrote down at the time.
When a change is driven by a differing site condition — the slab's not where the drawings said, there's abandoned conduit in the demo area, the existing steel isn't plumb — photograph it and date it that day. Not when the CO gets negotiated. That day. Same with directed work: if the owner's rep tells your super to proceed verbally, get it in an email before the crew swings a hammer. "Per your direction this morning, we're proceeding with X on a T&M basis pending a formal change order" takes ninety seconds and has saved more money than any other sentence in construction.
Your field team is where this documentation is either captured or lost, and it's almost always lost when capturing it means "remember to do it back at the trailer." Anything that lets a foreman attach a photo and a note to the actual activity, from the actual location, while he's standing there, is worth its weight. A change order log full of scope and dollars but empty of field conditions is a log that wins you nothing in a dispute.
Run the subcontractor change in step, not after
When a change hits a sub's scope, you've got a nested problem: your CO to the owner and their CO to you have to agree, and the field work can't wait for either. The trap is directing the sub to proceed, letting them run the work, and then discovering their number is double what you carried in your price to the owner. Now you're upside down on a change you thought was a wash.
Get the sub's pricing — even a rough not-to-exceed — before you commit your own number upward. And make sure their change work shows up on the same look-ahead your other crews are reading, so the sub's added activities coordinate with everyone else's instead of appearing as a surprise the week they show up. A sub's change that lands in the schedule as an afterthought is a sub's change that collides with somebody.
Mine the change log for the pattern
One change order is an event. Twenty change orders are a story, and the story usually points at a root cause you can do something about.
At the end of a project — better yet, at each monthly owner meeting — sort your changes by cause. If half of them trace to drawing conflicts, you've got a design coordination problem and the next job needs a harder clash-detection push up front. If they cluster around one area or one system, that's where the design was thin. If they cluster around one sub, that's a scope-gap in how you bought the work. The log isn't just a billing record; it's the cheapest lessons-learned document you'll ever produce, and it's already written itself if you've been categorizing as you go.
Tie it off at closeout while it's still fresh
Nobody wants to reconstruct change order history at closeout, six months after the fact, chasing down which verbal direction became which CO and where the backup went. The teams that close out clean are the ones that treated each change as a small, self-contained package the day it happened — scope, pricing, approval, field photos, affected drawings, sub backup, all in one place.
Do it in real time and closeout is assembly. Do it at the end and it's archaeology. The difference is a few minutes of discipline per change, spread across the whole job instead of dumped on your last miserable month.
The bottom line
Change orders are not the enemy. They're a normal, permanent feature of building things for people who are still figuring out what they want. What separates a super who rides them out from one who gets buried is treating every change as a scheduling event first and a billing event second — assessing the days alongside the dollars, keeping pending work visible in the weekly plan, mapping the trade-flow hand-offs the change disturbs, and documenting field conditions the day they exist.
The tooling should serve that discipline, not replace it. A look-ahead you can run "what if" scenarios against, that shows pending changes without committing crews, and that ties a foreman's field notes to the actual location and activity — that's the difference between a change order that costs you a number and one that costs you a schedule. Get the process right, and the software just makes it faster. Get the process wrong, and no software will save you.