Nobody builds a job the way it was drawn. On a good project you might see a couple dozen change orders; on a rough one, a few hundred. The paperwork side gets plenty of attention — pricing, markups, who signed what. The part that quietly wrecks jobs is the schedule side. A change hits, everybody argues about the number, the PM buries it in a log, and three weeks later the framers are standing around because a wall they were about to close got a revised opening that nobody pushed into the field plan.
Your look-ahead is where that failure shows up first, and it's also where you catch it. The weekly work plan is the closest thing you have to the truth of what's actually going to happen in the next few weeks. If changes don't flow into it fast and honestly, your schedule quietly turns into fiction while everyone's still treating it as gospel. Here's how to handle change orders inside a rolling look-ahead so they don't blindside you.
Not all changes hit the schedule the same way
Before you can plan a change, sort out what kind it is, because they behave differently in the field.
- Added scope is the obvious one — new work, new activities, new make-ready. It needs its own line, its own crew, its own materials, and its own lead time. The trap is treating "small" adds as free. A dozen added receptacles is a half-day of rough-in you didn't have, plus an inspection you didn't schedule.
- Modified scope is more dangerous because it hides. The activity already exists on your board, so it looks handled. But the duration changed, or the detail changed, and if you don't touch the activity the schedule lies to you. Upgrading a slab from 4" to 6" doesn't add an activity — it adds cure time, more concrete, maybe a pump you didn't book.
- Deleted scope feels like a gift and sometimes bites. Pulling work out frees up float, but it can also strand a crew you'd sequenced to follow that work, or leave a mobilization you're now paying for with nothing to do.
- Resequencing — same scope, different order — is the sneakiest of all. No line items change, so nothing looks different, but your trade flow just got rewired. This is the one that produces the "wait, drywall's here and the in-wall blocking isn't done" phone call.
Name the type first. It tells you which part of the plan to go touch.
Run the impact assessment before you argue about the money
The schedule impact of a change is usually worth more than the direct cost, and it's almost always assessed too late. The day a potential change lands, walk it through three questions:
What activities does this touch? Not just the obvious one — the predecessors and successors too. A revised door opening touches framing, but also the electrician who was going to pull a home run through that stud bay and the drywall crew queued behind them.
Does it change any durations? Added quantity, tougher access, a stricter detail — all of it stretches the activity. Be honest here. The classic mistake is pricing the labor for extra work but keeping the original duration on the board, so the calendar says you're fine right up until you're not.
What does it do to the sequence? This is where a look-ahead earns its keep. Trace the tie-ins. If the change pushes an activity that another trade is waiting on, you don't have one delayed activity — you have a ripple, and the guy at the end of the chain has no idea it's coming yet.
Do this on a whiteboard if you have to. The point is to catch the ripple while it's still a pencil mark, not after three subs have mobilized around the old plan.
Get added work into the make-ready pipeline immediately
New scope is still work, which means it has constraints, and constraints are the whole reason short-interval scheduling exists. The moment added scope looks likely — not approved, likely — start the make-ready clock on it. Does it need a submittal? A long-lead material? An engineered detail? A permit revision? An inspection?
Change order work is where lead times go to die, because everyone treats it as an afterthought. The base-contract material was ordered months ago; the change-order material gets ordered the week you need it and shows up two weeks late. If a change adds a piece of equipment with an eight-week lead and you're four weeks from that wall, the change just moved your finish date no matter how fast the crew works. Flag it the day it appears, not the day the CO gets signed.
Treat added activities exactly like base-scope activities: identify the constraints, get them on the make-ready list, and don't let the work into a committed weekly plan until it's genuinely ready. A change order doesn't earn a pass on the constraint check.
Tell the subs before the schedule does it for you
The trade most affected by a change is usually the last to hear about it. Somewhere between the owner, the architect, the PM, and the super, the message that "the layout in the northeast corner moved" doesn't make it to the foreman until his crew is already there.
When a change hits a sub's work, three things need to travel to them fast: the scope change itself (what's different), the schedule effect (are you still on for Tuesday, or is it now next Monday), and the pricing path (are we proceeding on a T&M ticket, a signed CO, or are you at risk). Keep those separate in your head — plenty of subs will happily do the work but need the money conversation closed, and plenty of jobs stall because the schedule was ready but the paperwork wasn't.
This is exactly the kind of thing a shared, visual look-ahead is built for. When the sub is looking at the same weekly work plan you are — and the changed activity is sitting right there on the board with its new date — you skip the game of telephone. In LookAheadWall, a resequenced activity just moves on the wall everyone's looking at, and the foreman sees his week the way it actually is now, not the way it was drawn in the base contract.
Where changes meet the Last Planner side of things
If you're running any flavor of the Last Planner System, changes collide directly with your commitments. An activity you already committed to this week may no longer be buildable because a change made it not-ready. That's not a broken promise by the crew — but if you don't attribute it correctly, it looks like one.
Two disciplines matter here. First, when a change knocks out a commitment, log the reason honestly. Your Percent Plan Complete number is only useful if the misses are attributed to real causes, and "change order made it not-ready" is a real cause you want visible — it's ammunition for a time-extension request later. Second, a change creates new constraints, and those constraints belong in your tracking the same day. The whole point of the make-ready process is that no constraint gets to hide; change-order constraints hide better than any others because they arrive off-cycle.
Document the impact while it's fresh, not at claim time
Here's the hard-won lesson: the schedule impact of a change is nearly impossible to reconstruct six months later, and that's usually exactly when you need it — during a delay claim or a fight over a time extension.
Keep a schedule baseline you can compare against. When a change lands, capture three things in plain language: what changed, why, and the schedule effect. "CO-14 relocated the electrical room; framing in Area B pushed 3 days; MEP rough-in in Area B pushed 3 days; net project impact 2 days after resequencing." That sentence, written the week it happened, is worth more than a lawyer's afternoon a year from now.
The other thing baselines give you is the ability to show cumulative impact. Any single change might be "just two days." Twenty of them is six weeks, and the owner who approved each one individually will swear the schedule should be fine. A running comparison of current plan against baseline is how you make that conversation factual instead of emotional. Death by a thousand cuts is real, and it's only provable if you were tracking the cuts.
Handle pending changes without pretending they're free
Most of the pain lives in the gray zone — the change everyone knows is coming but nobody has signed. You can't fully build to it, and you can't ignore it. So model it.
Carry the likely impact as a visible "what if" rather than a hidden assumption. If a pending change would push a milestone, you want that showing as a risk now, so decisions get made on time. Half the schedule damage from changes isn't the work itself — it's the decision latency. The change sat in someone's inbox for three weeks while the crew that could've built around it demobilized. Track the date by which a decision has to land to protect the schedule, and put that date in front of the people who owe you the decision. "We need direction on the canopy detail by the 14th or it moves the roof" is a sentence that gets changes signed.
Plan the recovery, don't just absorb the hit
When a change costs you time, resequencing is almost always your cheapest recovery lever — cheaper than overtime, cheaper than adding crews. Before you throw bodies or hours at it, look at whether the work can flow differently. Can a downstream trade start in an area the change didn't touch while you sort out the area it did? Can you break a big activity into locations and run them in parallel?
This is where a location-based look-ahead beats a bar chart. When you can see the work by area and by week, the resequence that saves you three days is often sitting right there — you just couldn't see it in a Gantt chart that treats "framing" as one 40-day bar. Only after you've exhausted the free moves should you price acceleration, and when you do, model it honestly so the owner is choosing to spend money to recover time they cost you, with the tradeoff in plain view.
The mistakes that turn manageable changes into disasters
- Processing the CO but never touching the schedule. The number gets negotiated, the paperwork gets filed, and the field plan still reflects the old scope. This is the number-one killer. A change that isn't in the look-ahead isn't managed — it's just documented.
- Waiting for signatures to update the plan. Approval can take weeks; the crew shows up Monday regardless. Update the plan when the change is known and directed, flag the pricing status separately, and don't let a slow signature strand your sequence.
- Pricing the labor but keeping the old duration. If it's more work, it takes more time. Put the time on the board, not just the dollars on the ticket.
- Letting the foreman find out from the crew. If the person swinging the hammer learns about a change by hitting it, you've already lost the coordination.
Make it a process, not a scramble
The firms that ride out heavy-change jobs aren't the ones with fewer changes — it's the same drawings for everybody. They're the ones where a change has a defined path into the plan: someone owns pushing it into the look-ahead, the impact assessment happens in days not weeks, the affected subs hear it directly, and the cumulative picture is always current.
Get that process running, keep your weekly work plan honest, and changes stop being the thing that ambushes the job. They become just another input you plan around — which, on a real jobsite, is about the best you can ask for.