Nobody hands you a schedule that survives contact with the jobsite. The plumber shows up a day early and there's no wall to rough into. The architect kills the mechanical chase you framed last week. The concrete pour slips because the pump truck broke down in Fresno. By the time you've had your second cup of coffee, half of what you planned for Thursday is already wrong. The difference between a foreman who thrives and one who burns out isn't whether changes hit — it's how fast and how cleanly they absorb them.
This is really the whole job. Anybody can run a crew when the plan holds. The craft is in re-planning on your feet, keeping your people productive through the churn, and doing it without turning every change into a fire drill. Here's how the good ones do it.
Know Where Changes Actually Come From
Changes aren't random noise. They come from a handful of recurring sources, and once you can name the source, you can predict the ripple. In rough order of how often they'll bite you:
- Design changes and RFI responses. An architect's answer to your RFI, an ASI, a bulletin — these change scope, and they almost always arrive after you've already planned the work the old way.
- Unforeseen conditions. You open a wall and find a beam that isn't on the drawings. You dig and hit rock, or a utility nobody located. Existing-conditions surprises are the ones that blow up a whole week.
- Trade sequencing and predecessor slips. The most common change of all, and the most preventable. Somebody upstream of you didn't finish, so your work can't start. Framing isn't topped out, so drywall waits. The slab isn't poured, so underground can't be inspected and backfilled.
- Inspection and approval delays. A failed rough-in inspection, a permit that's still "in review," a fire marshal who wants one more thing before he'll sign the ceiling. These stop you cold and you can't muscle through them.
- Weather and material. The pour that can't happen at 34 degrees, the long-lead switchgear that's now eight weeks out instead of four.
When a change lands, your first question shouldn't be "what do I do?" It should be "what caused this, and what else does that cause touch?" A design change to the mechanical room doesn't just move the mechanical work — it moves your framing, your inspection, and the electrician who was going to follow you. Trace the chain before you react.
The First 30 Minutes Decide How Bad It Gets
The instinct when a change hits is to grab your crew and start swinging. Resist it. The most expensive mistakes I've seen came from foremen who reacted before they understood the impact. You pull the crew onto the next area, then find out the next area got changed too, and now you've got demo to do on work you just built.
Slow down for half an hour and do this instead:
- Confirm the change is real and approved. A verbal from a nervous PM is not a change. A signed directive, an approved RFI, or a documented instruction from your super is. Don't rebuild the world on a rumor — but don't ignore a hazard while you wait for paperwork either.
- Map what it touches over the next two to three weeks. This is exactly what a look-ahead schedule is for. Pull up your window and physically walk the affected activities: what's now blocked, what freed up, what moved.
- Find the productive pivot. If the change stops your planned work, what can the crew do instead that's real, needed, and won't get changed again? Never let a change turn into standing around. The pivot is where a good foreman earns his keep.
- Re-sequence, then communicate. Only after you know the new plan do you tell people. Communicating a half-baked reaction just creates a second round of confusion when you correct it an hour later.
Use Your Look-Ahead as a Change Simulator, Not Just a Calendar
A three-week look-ahead earns its keep the moment a change hits, because it lets you see the ripple before you feel it. If you're still running your two-week plan on a printout taped to the gang box, you're finding out about downstream impacts one blown day at a time.
The power of a location-based, trade-flow view — the kind of short-interval scheduling LookAheadWall is built around — is that the connections between activities are already drawn. When you move framing on the third floor east wing, you can immediately see the drywall, the MEP rough, and the inspection that were tied to it slide too. You're not guessing at the impact; you're reading it. That turns "the change broke everything" into "the change moved these six activities, and here's the new sequence."
A few habits that make this work in the field:
- Keep the look-ahead current, not perfect. Update it at least at the weekly work plan and again mid-week after the big changes. A schedule that's three days stale during a change storm is worse than useless — it tells you confident lies.
- Plan by location and constraint, not just by trade. "Drywall, 4th floor" means nothing if the 4th floor isn't dried in and inspected. Tie your activities to their real predecessors so a change to one automatically flags the other.
- Carry buffer where you know it bites. Frame-to-rough-in usually wants a one-to-two-day buffer for cleanup, layout, and inspection. Rough-in to cover wants a hard inspection hold — never close a wall on a promise. Concrete wants cure time you can't compress no matter who yells. Bake those buffers in and a slip eats the float instead of your finish date.
Communicate the Change Once, Clearly, to the Right People
A change nobody hears about is a change that hits twice — once when it happens and again when your crew builds the old thing. But over-communication is its own problem: blast every trade about every wiggle and they start ignoring you, and they'll ignore the one that actually matters.
Sort your communication by who's actually affected:
- Your crew needs the new plan for today and tomorrow, in plain terms: where to go, what to build, what changed about it. Do it at stretch-and-flex or in a two-minute huddle, not in a group text they'll scroll past.
- The trades ahead of and behind you need to know only if the change moves the handoff. If drywall slips a day, the painter following you needs a heads-up; the guy pouring sidewalks out back does not.
- Your superintendent needs the impact and your recommendation, not just the problem. "The RFI answer moves the chase; I'm re-sequencing 4-east to 4-west and we hold one day, no schedule hit" is a report a super loves. "Hey, the drawing changed, what do you want me to do?" makes you the problem instead of the solution.
This is where a shared digital schedule beats a paper one every time. When you re-sequence in the app, the trades looking at the same plan — and the crew leaders checking the mobile view before they drive in — see the update without you making ten phone calls. The plan becomes the message. But don't hide behind the app: the change that matters still gets a look in the eye and a "here's what moved and why."
Don't Forget the Second-Order Effects
Rookies fix the schedule and think they're done. Veterans know a change ripples into everything the work depends on:
- Material. If the sequence moved, does your just-in-time delivery still land on the right day? Nothing's dumber than material showing up for work that's now two weeks out, clogging your laydown and getting damaged. Call the supplier the same day you re-plan.
- Equipment. The lift you reserved, the pump, the crane pick — if the work moved, the equipment window moved with it. Release it or reschedule it before you eat a standby charge.
- Inspections. Reschedule the inspector as soon as you know, not the morning of. Inspectors book out, and a missed inspection window can cost you more days than the original change did.
- The trade behind you. Give the following trade the same courtesy you'd want. A day's warning lets them redeploy their crew; no warning means they show up, find no work, and remember it next time you need a favor.
Document It — Not for Fun, for Your Own Protection
Every real change needs a paper trail, and the foreman is usually the last person to think about it until it's too late. When a change hits, note it: what changed, who directed it, when, and what it cost you in time and labor. You don't need a novel — a photo, a daily-report line, and a timestamp will do.
Two reasons this matters. First, changes that eat your time are frequently changes somebody owes you a change order for, and "I remember it took about a day" loses to a documented record every time. Second, patterns only show up if you write them down. Log your reasons a job can't start as planned for a few weeks and you'll see the truth: it's the same three predecessors slipping, or the same trade over-promising, or your own material always landing a day late. That's the Last Planner idea — track why the plan failed, and the data tells you where to fix your planning. A change well documented today is an argument you win next month.
Adaptability Is a Skill, Not a Personality Trait
The best change managers I've worked with weren't calmer people by nature — they'd just built a system so that a change was a known drill instead of a crisis. They kept a current look-ahead, they knew their real predecessors and buffers cold, they had a productive pivot in their back pocket, and they communicated the new plan once and cleanly. When the change came, they'd already thought about it.
That's the whole thing. You can't stop the schedule from changing — twenty years in, I've never seen a job where it didn't. What you can control is how fast you see the impact, how cleanly you re-sequence, and how little of the disruption reaches your crew's productivity. Get that right and the changes stop feeling like they're happening to you. They start feeling like just another part of the work — because they are.