Every superintendent knows the feeling. You walk the job at 6:45 with your coffee, and before you've made it to the second floor, three things have already gone sideways. The drywall crew is standing around because the electrician never got a green sticker on the second-floor rough-in. The concrete pour scheduled for tomorrow is now questionable because the rebar inspector can't come until Thursday. And a sub you've been chasing for two weeks just told you his crew got pulled to another job. None of these are on paper yet. They're just problems, and by the end of the day, one of them is going to cost you a week if you don't get in front of it.
The job isn't avoiding problems. Problems are the job. What separates the superintendents who deliver from the ones who are always behind is how fast and how systematically they see a problem, size it up, and kill it before it spreads. Good tools help, but only if you use them to think, not to generate reports nobody reads. Here's how experienced supers actually work a problem from the moment it shows up.
See it before it's a problem
The cheapest problem to solve is the one you catch while it's still a constraint. A constraint is anything a crew needs before they can work that they don't have yet: material not on site, the deck not stripped, the inspection not signed off, the shop drawing not approved, the wall not framed. On a look-ahead board, constraints are exactly what a proper weekly work plan is supposed to surface. You're not just listing what you hope happens next week. You're asking, for every activity you're about to commit to, "what has to be true before this crew can start, and is it true yet?"
The discipline that makes this work is running a real constraint log during your look-ahead planning, three to six weeks out. Walk the schedule with your foremen and, for each upcoming task, name the constraint and the person who owns clearing it, with a date. If a constraint can't be cleared in time, that activity doesn't go on the committed weekly plan. It stays in the backlog until it's clean. This is the heart of short-interval scheduling, and it's where a tool like LookAheadWall earns its keep, because you can see the whole trade-flow sequence at a glance and spot where a link is about to break before the crew shows up to a task they can't do.
The habit to build: treat "we'll figure it out when we get there" as a red flag, not a plan. Anything you can't confirm is ready three weeks out is a problem waiting to happen. Log it now.
Get to the actual cause, not the symptom
When a task doesn't finish on time, the temptation is to write down "drywall behind" and move on. That's a symptom, not a cause, and if you don't chase it down you'll be writing the same note next month. The Last Planner practice of tracking Percent Plan Complete and, more importantly, the reasons for variance is worth stealing here. Every time a committed task doesn't complete, you record why in plain language: prerequisite work not done, materials late, inspection failed, crew undermanned, design change, weather, rework.
After a few weeks a pattern shows up, and it's almost never what you'd guess. Nine times out of ten the drywall isn't slow because the drywall crew is slow. It's slow because rough-in inspections keep slipping two days, which means insulation slips, which means the wall can't close. The real problem is your inspection lead time, and no amount of yelling at the drywall foreman fixes it. A short-interval scheduling record that carries the variance reasons forward is what lets you find that. The five-whys drill works on a jobsite exactly like it works anywhere else: ask why until the answer is something you can actually change.
Size the damage before you react
Not every problem is worth a fire drill, and treating a two-hour hiccup like a catastrophe burns credibility you'll want later. Before you reshuffle the whole job, figure out what actually depends on the thing that broke. This is where seeing the downstream chain matters. A one-day slip on a task with three days of float behind it is a note in the log. A one-day slip on a task that's feeding a concrete pour, a crane pick, or an inspection window with no slack is a problem you drop everything for.
Two questions size almost any problem fast. First: what's the float on the affected activity? If there's real slack downstream, you have room to solve it quietly. Second: does this touch a hard constraint, a pour, a crane day, an inspection you waited three weeks for, a milestone with liquidated damages attached? Anything feeding a task that can't move without dragging ten others is where your attention goes. A look-ahead view that shows the trade-flow connections lets you trace that chain in a minute instead of holding it all in your head at 6 a.m.
Generate more than one option
The trap under pressure is grabbing the first fix that comes to mind. The supers who recover jobs instead of just documenting the slide force themselves to put two or three real options on the table before choosing. On a schedule problem the usual moves are:
- Re-sequence. Can another trade take that area first while you clear the constraint? If the electrician's held up on the second floor, can the crew flip to the third floor where rough-in is done, and come back? Location-based sequencing is your best friend here, because the work follows areas that are actually ready instead of stalling on one that isn't.
- Add resources. More bodies or a second shift on the critical task. This costs money, so save it for problems that genuinely feed a hard date. Throwing crew at a task with float is just burning margin.
- Overlap. Start the following task before the current one is fully done, accepting some risk of rework. Sometimes worth it, sometimes a disaster, so know which trades tolerate it. Paint chasing right behind trim is usually fine. Insulation chasing an inspection you're not sure will pass is asking to open the wall back up.
- Absorb it. Sometimes the honest answer is the milestone moves, and the right thing is to say so early, cleanly, with a recovery plan attached, rather than pretending you'll make it up and looking like you lied a month later.
Being able to try a re-sequence on the board and see whether it actually clears the jam, before you commit crews to it, is the difference between a plan and a hope. A rolling look-ahead you can rework quickly lets you test the move on screen instead of in the field where mistakes cost real days.
Move resources without creating the next problem
Reallocating crew is the most common recovery move and the one most likely to backfire. Pull a crew from an area with float to hit a hot spot, and you've solved today's problem, but you've quietly created next week's if that borrowed-from area is feeding something down the line. The rule of thumb: only rob activities with real float, and check what that activity feeds before you touch it.
The coordination piece is the hard part, because most of the crews aren't yours. When you re-sequence, every affected sub needs to know their new start, and they need to know it today, not the morning they show up. This is where a shared, current schedule pays for itself. If your subs and foremen are all looking at the same live weekly plan on their phones, a re-sequence propagates in minutes. If your schedule lives in a spreadsheet you email out on Fridays, half of them are working off last week's plan and you'll spend Monday untangling it. A companion app that puts the current plan in a crew leader's pocket is worth more on a chaotic week than any Gantt chart ever printed.
Build a recovery plan you'd actually bet on
A recovery plan that just says "make up time" isn't a plan. A real one names the specific activities that will be compressed or resequenced, the resources it takes, and the new dates, and it's honest about what it costs. If recovery needs a Saturday, say so and price it. If it needs the mechanical sub to double up, confirm he can before you write it down. The fastest way to lose your team's trust is to publish a recovery plan built on crews and hours nobody agreed to.
Give frame-to-rough-in transitions and similar handoffs a small buffer when you rebuild, usually a day or two, for cleanup, punch, and inspection. A recovery schedule with zero slack between trades looks great on paper and collapses the first time an inspector runs late. Building in a realistic buffer isn't padding, it's the difference between a plan that survives contact with the jobsite and one that doesn't.
Tell the right people, the right amount, early
Different audiences need different messages. The owner and PM need impact and the plan, not a play-by-play of whose fault it was. Your subs need their new dates and what you need from them. Your own crew needs the priority for the day. The mistake is either hiding a problem until it's too big to fix quietly, or blasting everyone with alarm over something you had handled. Pull your data from the schedule so the story is consistent, and lead with the plan, not the panic. A PM who hears "here's the slip, here's why, here's how we get it back" trusts you a lot more than one who hears nothing until the milestone's already blown.
Track it to closed, and steal the lesson
A problem isn't solved because you have a plan. It's solved when the work is done and verified. Keep an issue open until someone confirms in the field, and don't let your look-ahead show a task complete on a foreman's word when the inspection sticker isn't on the wall. On the electrical side that means megger the runs and confirm the green tag before insulation goes near it, not after, because reopening a closed wall is exactly the kind of self-inflicted rework that turns a small problem into a two-week one.
Then capture the lesson while it still stings. If inspection lead time burned you this month, the fix isn't a memo, it's a standing rule in your planning: rough-in inspections get requested two days earlier, and that constraint goes on the log every time now. The best supers don't just recover, they quietly rebuild their planning so the same problem can't come back the same way. That's what turns twenty years on jobsites into judgment instead of just twenty years of the same fires. The tools help you see and share and remember, but the thinking is still yours, and that's the part that gets better every job.