Building construction goes up. Infrastructure goes out. That one difference changes almost everything about how you plan the work. On a vertical job you can stand in the lobby and, floor by floor, watch the trades stack behind each other. On a roadway, a pipeline, a runway, or a transmission line, your crews are strung out over miles, working in a moving parade, and half your schedule is dictated by things you don't control: a utility company's relocation crew, an environmental window, a lane-closure permit, a batch plant an hour away. A schedule that works fine for a five-story apartment building falls apart the first time you try to bend it around a linear job. Below is how heavy-civil superintendents actually plan this work, where it goes wrong, and what to look for in the tools you use to run it.
Think in stations, not floors
The first mental shift is location. On a building you schedule by area and level. On a linear job you schedule by station or mile marker, and your crews chase each other down the alignment like cars on a highway. Clear-and-grub is out ahead. Behind it, earthwork. Behind that, subgrade prep, then base, then paving. Each operation moves at its own rate, and the whole thing only flows if the crew in front stays far enough ahead of the crew behind.
This is why line-of-balance thinking beats a wall of bar-chart activities for this kind of work. Instead of asking "is activity 4230 done?" you ask "where is the paving crew relative to the grading crew, and is that gap growing or shrinking?" If your grader is producing 1,500 feet a day and your base crew eats 1,800 feet a day, the base crew catches the grader in a week and then stands around. You want to see that collision coming on a location-based view before it happens, not discover it when a foreman calls you at 7 a.m. asking what he's supposed to do. Good look-ahead scheduling software that lets you lay work out by location instead of just by date is doing real work for you here, because the geographic picture is the picture that matters.
Build the three-to-six week window around constraints, not activities
The heart of running a linear job is the rolling look-ahead — the two-to-six week window you rebuild every week and walk the field team through. On infrastructure the trap is populating it with activities when the real content is constraints. An activity says "install 48-inch RCP, Sta 112+00 to 118+00." The constraint is the reason that activity can't start: the gas line crossing it hasn't been relocated, the SWPPP inspection isn't signed off, or the pipe hasn't shipped. A weekly work plan that lists the activity but ignores the constraint is a wish, not a plan.
So run every activity entering your look-ahead through a screen before you commit to it. A workable version of the checklist:
- Design — is the plan sheet current, and has the last RFI on this reach been answered?
- Utilities — are conflicting utilities relocated or verified clear? Have you potholed the crossings?
- Permits and environmental — is the work inside an allowable window (in-water, nesting, noise), and are the permit conditions met?
- Material — is it on site or firmly scheduled, with lead time that clears the start date?
- Right-of-way and access — do you have the easement, and can equipment physically get to the station?
- Layout — has survey set line and grade ahead of the crew?
Anything that fails the screen stays out of the committed week. That's the whole discipline of short-interval scheduling: only promise the work that's genuinely ready, and spend the week clearing constraints on the work that isn't. Teams that measure their percent-plan-complete — the share of the week's promises actually kept — almost always find the misses trace back to a constraint nobody cleared, not to a lazy crew.
Utilities will set your pace whether you plan for them or not
If there's one thing that eats linear schedules alive, it's utility coordination. The utilities you find in the field never quite match the ones on the plans, the relocation crews answer to their own company's priorities and not yours, and a single unmarked duct bank can shut down a whole reach.
Protect yourself with sequence. Pothole ahead of the excavation — a week or two out, not the morning of. Treat every relocation by others as a hard predecessor with a real, named contact and a committed date, and follow it like you'd follow a critical submittal. Build the crossings into the look-ahead as their own line items so a delayed gas relocation shows up as a red flag three weeks early instead of as a surprised crew standing in an open trench. And keep a documented trail of every "clear to dig" you get, because on utility conflicts the disputes are expensive and the memory of who said what gets short.
Windows, not just durations
Vertical work mostly cares about how long an activity takes. Linear work also cares about when it's allowed to happen at all. Environmental windows are the obvious ones — in-water work restricted to a few summer months, bird-nesting seasons that lock down clearing, dust and noise limits that shrink your workday. Miss a window and the penalty isn't a day; it's a season, plus a violation.
Weather compounds it. You can't pave asphalt below a minimum surface temperature, you can't place concrete into a hard freeze without protection, and freeze-thaw turns a graded subgrade into soup. Compaction on wet fill is a fool's errand. So your longer look-ahead — the four-to-six week horizon — should be reading the calendar and the season, not just the sequence. When you know a hard environmental window is closing, you sequence the constrained work first and let the flexible work fill in behind it. The crews that get burned are the ones who treated a fixed window like a soft target and left it for "when we get to it."
Traffic control is a trade, and it has lead time
On any job in live traffic, the lane closure is a predecessor to the actual construction. You can't set up the work zone until the closure is permitted and the traffic control plan is approved, and many agencies restrict closures to nights, weekends, or off-peak windows — which quietly caps how many productive hours you actually get. Flaggers and the setup/teardown of the taper burn real time on both ends of the shift.
Plan traffic control as its own line in the weekly plan, coordinated with whoever owns flagging, and size the productive window honestly. A "10-hour night shift" with a 90-minute setup and a 90-minute teardown is a seven-hour dig. Schedule it as ten and you'll blow the plan every night and never understand why.
Feed the equipment and the batch plant
Heavy civil is equipment-intensive and material-hungry in a way building work rarely is, and both of those want to sit at the center of your plan. Equipment moves between spreads cost you — a lowboy day to shift the excavator from one crossing to another is a day the machine isn't producing, so sequence work to minimize the moves and stage the machines ahead of the crews.
Material is often the true governor of pace. A grading operation is limited by how fast trucks can haul, a paving day by how much mix the plant can deliver before it goes cold, a concrete pour by batch truck cycle time. Tie the material-heavy activities in your look-ahead to the supply that actually feeds them — plant capacity, haul distance, truck count — because a paving crew with no mix and a pour crew waiting on trucks are both just expensive standing armies. When your weekly plan is built around what the plant can produce and what the trucks can move, the crews stop outrunning their supply.
Phase completions, agencies, and the paper trail
Infrastructure rarely opens all at once. You turn over an interchange, cut a detour over to newly built lanes, energize one segment of line — each a hard milestone with its own punch list and, usually, its own agency sign-off. Work the look-ahead backward from each phase turnover, and let the near-term weekly plan prioritize whatever is genuinely blocking the next opening rather than whatever happens to be convenient that week.
Two things ride alongside all of it. Agency inspections are constraints like any other — a hold point you can't pour or backfill past until it's signed — so build the inspector's availability into the plan instead of assuming someone shows up when you're ready. And as-built documentation isn't a closeout afterthought; on buried infrastructure, the record of what actually went in the ground is half the deliverable. Capture line, grade, and field changes as the work closes, day by day, while a crew can still tell you what they hit. Chasing as-builts six months later, after the trench is backfilled and the crew is on another job, is how good contractors lose money at the very end of a good project.
What to ask of the tool
None of this requires software to be true — superintendents ran linear jobs off butcher paper and line-of-balance charts for decades. But a schedule that lives in one person's head or in a plan-and-schedule binder in the trailer doesn't survive a moving job with a dozen constraints per reach. What actually helps is a tool that lets you lay work out by location, build the look-ahead around constraints so nothing enters the committed week until it's ready, and push the current weekly plan to the crew leaders in the field on their phones so the parade stays in sequence. That last part matters more on linear work than anywhere else, because your foremen are literally miles apart — the whole point of a mobile-friendly look-ahead like LookAheadWall is that the grader operator and the pipe foreman are looking at the same picture without driving back to the trailer to find out.
Pick the tool that fits how linear work actually behaves — stations, windows, utilities, supply, phases — and it earns its keep. Force a vertical-building tool onto a heavy-civil job and you'll spend more time fighting the schedule than running the work. The job is hard enough without that.