Building construction rewards planning by area: pour a deck, frame it, rough it in, close it up, move to the next floor. Infrastructure doesn't work that way. On a highway widening, a bridge replacement, or a mile of new sewer trunk line, the work marches down a corridor. Crews chase each other along stations, not floors. Weather can shut you down for a week. A single utility that didn't get relocated on time can strand three trades and idle a paving train that costs you thousands a day just to have on the property. The Last Planner System was built to make commitments reliable in exactly this kind of environment, but you have to adapt it to how linear, weather-driven, permit-heavy work actually behaves.
This is a field-level look at how to run look-ahead and weekly work planning on infrastructure jobs, what breaks, and how to keep your production commitments honest when the ground, the weather, and a dozen outside agencies all have a vote.
Why Infrastructure Punishes Sloppy Planning
The thing that trips up superintendents coming off building work is that infrastructure has fewer places to hide. On a vertical job, if the drywall crew can't get into unit 304, they slide over to 306 and you barely feel it. On a corridor job, if you can't work station 42+00 because the gas main is still live, you often can't jump ahead either, because your access, your traffic control, and your material staging are all sequenced to move in one direction. A single stuck location can cascade into a stalled work front.
Add the money problem. Infrastructure runs on big, expensive, rate-driven equipment: paving trains, excavators with GPS grade control, drill rigs, crane picks scheduled with the DOT. Those assets bleed money whether they're producing or parked. That's why the planning discipline matters more here than almost anywhere else. Every hour of idle production time is a number you can put a dollar sign on.
Plan by Station, Not by Floor
The first adaptation is organizing your plan geographically. Instead of "Level 3 rough-in," your activities read "storm drain, STA 30+00 to 38+00." Linear work is best planned on a location basis, and the most useful view you can build is a time-distance (or time-chainage) picture: stations across one axis, dates down the other, each crew drawn as a sloping line moving down the corridor. When two lines are about to cross, two crews are about to be in the same place at the same time. That's your conflict, visible weeks out, before anyone shows up to fight over the same 200 feet of grade.
Once you're thinking in stations, three habits follow:
- Commit to production rates, not just tasks. A crew doesn't finish "the paving." It lays 1,800 tons a day, or grades 400 linear feet a shift. Your look-ahead should carry those rates so you can see whether the excavation crew is outrunning the pipe crew and about to run out of open trench to hand off.
- Manage the gap between work fronts. On linear jobs the follow-on trade needs a buffer of completed, accepted work ahead of it. If your pipe crew is only two days ahead of backfill and compaction, one bad-weather day collapses the gap and stalls both. Build and protect that cushion deliberately.
- Sequence access and staging with the work. Material delivery, equipment moves, and haul routes all move down the corridor too. Plan them into the look-ahead, or you'll have a crew ready and no way to get aggregate to them.
Constraints Are the Whole Game
The heart of Last Planner is screening future work for constraints and clearing them before the work is scheduled to start. The difference on infrastructure is that the constraints are bigger, slower, and controlled by people who don't report to you. These are the ones that reliably wreck schedules:
- Utility relocations. The single most common cause of a stalled work front on corridor jobs. The gas, electric, or telecom relocation must finish before you can excavate through that station, and the utility owner works on their own calendar. Track these by station with a hard "need-by" date, and start leaning on them weeks before your crew arrives, not the day they get blocked.
- Environmental permits and windows. In-water work windows, migratory bird restrictions, endangered species timing, dewatering and turbidity limits during rain. Miss a window and you don't reschedule by days — you wait for next season.
- Right-of-way and access agreements. You can't work ground you don't legally have yet. A single unacquired parcel can put a gap in the middle of an otherwise clean work front.
- Traffic control and lane closures. Many DOTs only allow closures in specific night or off-peak windows. Your available work hours are dictated by a permit, not the sun.
- Bulk material supply. Asphalt plant availability, a concrete supplier's daily truck limit, aggregate on allocation. On a big pour or a paving day, the plant's schedule is your schedule.
Because so many of these clear on the order of weeks or months, a two-week look-ahead is not deep enough to protect you. Run a longer horizon — six weeks is a reasonable working depth, and permits and utility relocations often need to be visible several months out on a separate long-lead log. The rule of thumb: your look-ahead needs to reach at least as far as the lead time of your slowest constraint. If a relocation takes eight weeks and you're only looking two weeks ahead, you are already late and don't know it.
Treat Weather as a Planned Input, Not an Excuse
Everybody says weather hurt them. The good superintendents plan around it instead of writing it up after the fact. Infrastructure is far more exposed than enclosed building work, and each operation has real thresholds worth knowing cold:
- Earthwork lives and dies on moisture. You can't hit compaction if the subgrade is too wet, and you can't get density in dust either. A rain day isn't just the rain day — it's the day or two after while the grade dries back to optimum moisture.
- Paving has temperature floors. Hot-mix asphalt has minimum ambient and surface temperatures, and it cools fast on cold, windy days, which shortens your compaction window behind the screed. Cold weather doesn't just slow paving, it can put the mat out of spec.
- Concrete has both ends. Hot-weather placement risks flash set and plastic cracking; cold-weather placement needs protection and can't freeze before it gains strength. Both change your crew size, your admixtures, and your cure plan.
Practically, that means every weekly work plan on an exposed job should carry a weather contingency: if we can't grade Monday, the crew shifts to the box culvert, or pulls forms, or runs pipe under the bridge where it's dry. A rained-out crew with no backup plan is a rained-out crew that goes home. Build the backup work into the plan before the week starts, not at 6 a.m. when the radar's already red.
Weekly Work Planning That Holds Up
The weekly work plan is where look-ahead planning turns into commitments people actually make to each other. On infrastructure, a good weekly plan is explicit about four things: where each crew works (by station), what production they're committing to, what has to be true for that to happen (traffic control set, materials on site, the location released from the trade ahead), and what the backup is if weather or access falls through.
The point of only committing to work whose constraints are actually cleared is simple: a plan full of hopeful tasks trains everyone to ignore the plan. When a foreman commits to 300 feet of pipe at STA 40+00 on Thursday, that commitment should only be on the board because the trench is shored-ready, the bedding stone is stockpiled, the relocation is done, and the lane closure permit covers that window. This is exactly the kind of coordination a visual, location-based look-ahead tool like LookAheadWall is built to make legible — you can see the trade-flow handoffs down the corridor and the crew leaders can pull the current week on their phones in the field instead of working off a PDF that went stale on Tuesday. The tool matters far less than the habit, but the right tool makes the habit stick.
Measuring PPC When Work Is Continuous
Percent Plan Complete — the share of your weekly commitments you actually hit — is the metric that tells you whether your planning is getting more reliable or you're just guessing louder. On infrastructure it needs a small adaptation. A binary "done / not done" doesn't fit continuous production. If you committed to 400 feet of grade and got 340, that's not a zero. Score against the production commitment and track the shortfall, because the shortfall is where the learning is.
And be honest about "complete." Work only counts when it meets spec and passes the inspection or density test. A trench you backfilled that fails compaction isn't done; it's rework you haven't discovered yet. Tying completion to acceptance keeps your PPC from lying to you.
The real value isn't the percentage — it's the reasons for the misses. Log why each commitment failed: weather, utility not clear, material short, inspection failed, equipment down, crew short. After a few weeks the pattern is undeniable. If half your variances trace to utility relocations, you don't need a motivational speech about hitting the plan — you need to get in front of the utility coordinator earlier and stop scheduling into ground that isn't clear.
Playing the Long Game on Multi-Year Jobs
Big infrastructure spans seasons and years, and the planning has to nest. Pull planning sets the major phases and the season-boundary milestones — get the bridge deck poured before the in-water window closes, get the base course down before winter shuts down paving. Inside each season, the six-week look-ahead screens constraints. Inside that, the weekly plan makes the commitments. Each layer feeds the one below it. Lose the top layer and you'll make beautiful weekly plans that quietly march you into a missed seasonal window you can't recover for months.
The Habit, Not the Software
None of this is exotic. Screen the work far enough ahead to clear the constraints that actually control your job. Plan by station and commit to production rates. Protect the buffer between work fronts. Give weather a backup plan before the week starts. Only put commitments on the board that are truly ready, then measure whether you hit them and study why you didn't. Good look-ahead scheduling software makes all of that visible and shareable across a corridor full of crews and subs, and that visibility is worth a lot when your work front is a mile long. But the discipline is what delivers the job. The software just keeps everyone looking at the same honest picture.