Every job has that moment. You're three weeks into drywall on the third floor, the crew has a rhythm going, and the owner walks the space with the architect and decides the conference rooms need to be bigger. A new door here, move that wall four feet, add a data closet nobody drew. It comes back to you as a two-line email that says "please price and schedule." The pricing part everybody understands. The scheduling part is where jobs quietly bleed time and money, because the impact of a change order almost never shows up on the change order itself.
A change order is a scope change with a schedule shadow attached, and that shadow is usually longer than the scope. This article is about the discipline of catching that shadow early, tracing it through your near-term work, and documenting it well enough that six months from now, when everyone's memory has gone soft, you can still prove what the change actually cost you in time. A good scheduling tool doesn't do this thinking for you, but it makes the thinking visible and keeps the record honest.
The impact is never just the new work
The first mistake crews make is pricing the change in isolation. Someone estimates the framing, the drywall, the paint for the reworked conference room, adds a markup, and calls it done. What's missing is everything that new work touches. That data closet needs power and low-voltage rough-in, which pulls the electrician back to a floor he'd already demobilized. It needs a fire-rated wall, which changes the inspection sequence. It moves a sprinkler head, so now the fire protection sub is back too, and their return isn't free — they've got other jobs and you're waiting on their availability, not your own crew's.
Before you touch a date, walk the change through your predecessor logic. Ask a simple question about every affected activity: what has to happen before this, and what can't happen until this is done? On a look-ahead schedule that shows your trade sequences visually, this is a five-minute exercise instead of a guessing game. You're looking for the ripple — the activities downstream of the change that inherit its delay whether or not their own scope changed at all. That's the difference between a two-day change and a two-week change, and it's the number people miss.
Snapshot the schedule before you touch it
This is the single most valuable habit in change order work, and almost nobody does it consistently. The moment a change lands — before you've moved a single activity — capture the current state of your schedule. What were you planning to do this week and next? What was the sequence? When were you going to finish?
That frozen snapshot is your baseline for the impact. When you later argue for a time extension, the question you'll be asked is "compared to what?" If you can produce the schedule as it stood the day before the change, with your near-term work plan intact, you have an answer. If you're reconstructing it from memory three months later, you have a story, and stories lose to documents in every claim negotiation you'll ever be in. Software that lets you version or snapshot the schedule turns this from a chore into a click, and that record is worth more than any report it generates.
Time impact analysis, without the theater
Time impact analysis has a reputation for being a specialist's tool, something you hire a scheduling consultant to produce for a big claim. The formal version is. But the everyday version is just discipline: take the change, insert the added or modified activities into your logic at the point they actually occur, keep the relationships honest, and see where your finish date lands. The difference between the new finish and the snapshot finish is your impact.
A few things that trip people up:
- Not every change extends the job. If the change hits work that has float — work that isn't on the critical path — it may consume that float without moving your finish date at all. That's fine, but note it, because a later change to the same chain now has no float to absorb it. Float is a shared resource and change orders spend it.
- The critical path can move. A change big enough to delay a non-critical chain can make that chain the new critical path. If you only look at your old critical path, you'll miss it. Recalculate the whole thing.
- Sub availability is a real duration, not a formality. "The electrician needs half a day" is true for the labor. But if he's off your job and can't be back for a week, your impact includes that week. Field reality beats the estimate sheet.
Adding and modifying activities cleanly
When you bring change work into the schedule, tag it. Every activity that exists because of a change order should carry that change order's number. Do this from the start, not as cleanup later. Six weeks on, when you're looking at a wall of activities, you want to be able to filter to "everything CO-14 touched" and see it instantly. That tag is what turns your schedule into evidence.
Distinguish added work from modified work. Adding a new activity is clean — it's a new bar with its own logic. Modifying an existing activity is where errors hide, because you're changing a duration or scope that other work already depends on. If you stretch an activity's duration to absorb changed scope, check what that does to everything tied behind it. The relationship is still there; you've just made the predecessor longer, and the schedule should push the successors accordingly. When it doesn't, you've usually got a broken link or a hard-coded date someone forced in, and it'll bite you at the worst time.
Pending changes: the work you're not sure you're doing
Real jobs run on a backlog of changes that are priced but not approved. The owner is "thinking about it." Meanwhile your crew needs a plan, and you can't just stop. This is one of the trickier parts of change management and it's worth handling explicitly rather than by gut feel.
The honest approach is to plan the base scope as committed work and treat pending-change work as conditional. In your weekly work plan, be clear about what's firm and what's contingent on an approval you don't have yet. The danger is drift: a crew starts doing pending-change work on the assumption it'll be approved, the approval stalls, and now you've spent labor on scope you may never be paid for, and you've disrupted the committed sequence to do it. If you do proceed at risk — sometimes you have to, to hold the job — document the direction to proceed and the date. A verbal "yeah, go ahead" from a busy owner's rep is worth exactly nothing when the invoice shows up.
Concurrent delays and why you separate causes
Here's where documentation earns its keep. Suppose the change order that pushed your closeout also happened to overlap with a two-week weather delay and a late material delivery. When the finish date slips, everyone points at each other. The owner says your material was late. You say the change disrupted the sequence. The subs say the weather stopped them.
The only way through concurrent delay is to have tracked each cause separately as it happened — not reconstructed afterward. Keep the change impact documented against its change order, the weather documented in the daily logs, the material delay documented against its purchase order. When you can lay three clean, separately-sourced records side by side, the conversation about who owns what delay becomes a fact-based negotiation instead of a shouting match. When you can't, you tend to eat all of it, because you can't prove which part wasn't yours.
When the change comes with "and hold the date"
The nastiest change orders add scope and expect the original completion date anyway. That's an acceleration, whether or not anyone uses the word, and it costs money — overtime, added crews, shift work, trade stacking that kills productivity. Before you agree, model it. Show what holding the date actually requires: which activities would have to run in parallel that were sequential, how many more bodies, how much overtime. Often the exercise itself changes the conversation, because the owner sees that "just keep the date" has a price tag they didn't expect.
If you do accelerate, watch trade stacking. Two crews in the same room aren't twice as fast — they're often less than 1.5x and generate rework and safety exposure. A realistic acceleration plan spreads the intensification across space, not just time: more floors going at once rather than more people crammed into one. A location-based look-ahead makes that easy to see, because you're planning by area, not just by activity list.
Make the impact visible, then report it
The last piece is communication, and it's mostly about showing rather than telling. A before-and-after of the schedule — here's where we were, here's where the change puts us — lands with an owner far harder than a paragraph of narrative. Highlight the change-affected activities so anyone can see, at a glance, what moved and why. When you can point at a screen and say "these seven activities all shifted because CO-14 pulled the electrician back," you're not asking anyone to trust you. You're showing them.
This is where a purpose-built look-ahead tool like LookAheadWall pulls its weight — not because it calculates your entitlement for you, but because it keeps the trade-flow sequence, the change tags, and the schedule snapshots in one place where the story is self-evident. The software's job is to make the truth easy to see and hard to lose.
The bottom line
Contractors have gotten disciplined about the cost side of change orders. Everybody prices the labor and material, everybody argues the markup. Far fewer treat the time side with the same rigor, and time is where the real money hides — in the overhead you carry for the extra weeks, the liquidated damages you eat because you couldn't prove the delay wasn't yours, the crews you kept mobilized waiting on a decision.
Handle the schedule impact of a change the way you handle the cost impact. Snapshot before you touch anything. Trace the ripple through your sequence, not just the new scope. Tag the change work so it's findable. Keep concurrent causes separate. Model acceleration before you promise it. Do that consistently and change orders stop being the thing that quietly sinks your schedule and become just another part of the job you're on top of. The change is coming either way — the only question is whether you can see what it costs you in time before it's too late to do anything about it.