A building job is a stack. You work floors, you work zones, and the schedule lives inside a footprint you can walk in ten minutes. Infrastructure is the opposite. Your job is a line — a corridor of road, a run of pipe, a bridge across a gap — and the work marches along that line by the station, not by the floor. If you try to run a highway widening or a two-mile utility replacement with a schedule and a set of field tools built for vertical construction, you'll feel the friction on day one. The math is different, the constraints are different, and the way work fails is different.
Field management software earns its keep on infrastructure only when it thinks in the same terms the job does: linear, exposed to weather, tangled up with traffic and existing utilities, and answerable to a public owner who documents everything. Here's what actually matters when you're planning and running that kind of work in the field.
Work moves along a line, so the schedule has to speak in stations
The single biggest shift from buildings to infrastructure is that location is a distance, not a room. You're not framing unit 304; you're grading from station 112+00 to 128+00. Your crews, your inspections, your material deliveries, and your quality tests all attach to a stretch of the alignment. If your planning tool can't express "where along the corridor," it's fighting you.
This is where linear scheduling — sometimes called line-of-balance or a time-location chart — beats a plain bar chart for corridor work. A bar chart tells you an activity runs three weeks. It doesn't tell you the paver and the pipe crew are both going to want station 90+00 on Thursday. A time-location view puts distance on one axis and time on the other, so every crew shows up as a sloped line, and the moment two lines cross you can see the collision before it happens on the ground. That's the whole game on linear work: keeping crews from stacking up on the same station and keeping the fast trades from running up on the slow ones.
You don't need to abandon the tools your crews already use. A weekly work plan and a rolling look-ahead still drive the field. But on infrastructure, every activity on that plan should carry a from-station and a to-station, not just a duration. When a location-based scheduling tool like LookAheadWall lets you tag work to a stretch of the alignment, your three-week look-ahead stops being a to-do list and starts being a map of who's working where and when the handoffs land.
Plan by production rate, not by "days"
On a building, durations are mostly experience and gut. On linear work, you have something better: a production rate. Your grading crew moves so many linear feet a day. Your pipe crew sets so many feet of main. Your paver lays so many tons or so much lane-mileage per shift under good conditions. Once you know the rate, the schedule falls out of arithmetic.
Say your storm crew installs roughly 200 linear feet of RCP a day in this soil. A 4,000-foot run is about 20 working days of trenching and pipe — before you add rain days, before utility conflicts, before the days you spend dewatering a trench that won't stay dry. Plan the raw production first, then apply your buffers honestly:
- A weather factor. Outdoor earthwork and paving lose real days. Depending on your region and season, penciling in a 15–25% loss on weather-sensitive operations is closer to reality than assuming clear skies.
- A learning curve. The first few stations of any repetitive operation run slow while the crew finds its rhythm and the logistics shake out. Don't schedule day one at day-thirty production.
- A congestion factor. Rates published in a vacuum assume open access. Traffic control, utility conflicts, and a tight work zone all drag the number down.
When you track actual feet-per-day against your planned rate week over week, you get an early-warning system a bar chart never gives you. If the crew planned for 200 feet is doing 140, you don't wait for the milestone to slip — you already know the finish date moved, and you know it three weeks early while you can still do something about it.
Utilities: locate, pothole, and don't guess
Nothing stops a linear job faster than an unmarked utility. The one-call ticket is the floor, not the ceiling. Locates expire, marks get paved over or washed away, and as-builts on old utilities are optimistic fiction. The crews that don't hit lines are the ones that treat every crossing as suspect until proven otherwise.
Build the utility work into the look-ahead as its own sequence, ahead of the pipe or the excavation that depends on it:
- Get the locate ticket, then verify it. On anything critical — a gas main, a fiber trunk, a transmission water line — pothole and expose it by hand or with a vac truck before the machine ever swings.
- Track locate ticket expiration dates the way you track submittal dates. A ticket that lapses mid-excavation is a lost day and a real hazard.
- Sequence utility relocations as predecessors. If the power company has to move a pole before you can widen the shoulder, that relocation is on your critical path whether it's your scope or not, and it moves on the utility's schedule, which is slower than yours. Get it on the look-ahead early and chase it hard.
The point of documenting all this in the field isn't paperwork for its own sake. When you hit something that wasn't marked, the photo of the clean pothole and the dated locate ticket are what turn a fight into a change order.
Traffic control is a work zone that has to be planned like one
On public work, the traffic control setup is part of the schedule. A lane closure often needs advance notice to the DOT, sometimes days, and many agencies restrict when you can close lanes at all — no closures during rush hour, no closures on game day, night work only on the arterial. Your crews can be ready to pour at 7 a.m. and still sit idle because the closure permit says you can't take the lane until 9.
Two things go wrong here constantly. First, teams schedule the production work and forget that the setup and teardown of traffic control eats a real chunk of every shift — sometimes an hour or more on each end. Second, they don't align the allowed closure windows with the crew's plan, so a night-only restriction quietly turns a day operation into a night operation with all the productivity loss that comes with it. Put the closure window and the setup/teardown time on the weekly work plan explicitly, and the crew stops discovering the constraint at the tailgate meeting.
Earthwork lives or dies on the mass haul
Earthwork isn't just "dig here." It's a balance problem: cut from one station has to go somewhere, and ideally it becomes fill at another station instead of getting hauled to a spoil site and replaced with imported borrow. The mass haul diagram tells you which direction dirt should move and how far, and the schedule has to respect it.
Coordinate cut and fill as linked operations, not independent ones. If your fill placement out-runs your cut, you're buying borrow you didn't need to. If cut out-runs fill, you're stockpiling and double-handling. Track daily quantities against the earthwork model — cubic yards moved, not just "worked on grading" — because volume is the real unit of progress here, and a grading operation that looks busy can be badly behind on yardage. Moisture matters too: fill placed and compacted wet, or dry of optimum, comes back as a failed density test and a re-work day, so keep the water truck and the compaction testing inside the same daily plan as the placement.
Paving runs on a thermometer
Asphalt is unforgiving about temperature. There's a window — mat temperature at breakdown rolling, ambient and base temperature at placement — and once the mat drops below the point where the rollers can get density, you're done for the day whether you finished the pull or not. That makes paving a coordination puzzle with almost no slack: the plant has to be producing, the trucks have to be cycling without gaps, the mill (if you're milling) has to stay ahead, the rollers have to be right behind the paver, and the whole train has to move at a pace that keeps the mat hot.
Plan paving as one linked operation, not a stack of separate line items. If any element of the train breaks — the plant goes down, trucks bunch up, a roller falls behind — the mat cools and the day is compromised. Sequence base, binder, and surface courses with the joint locations and cure/tack requirements in mind, and get the plant, trucks, and crew committed for the same window well ahead. A paving day lost to a truck shortage is one of the most expensive no-progress days on the whole job.
Bridges and structures often set the real finish date
On a corridor job, the roadway can feel like the main event, but the structures usually drive the critical path. A bridge has long-lead items — steel, girders, bearings — and a sequence you can't compress: foundations, then substructure, then set the beams, then deck, then cure, then approach work. Miss the girder delivery and no amount of hustle on the paving recovers it. Track structure milestones separately and watch them harder than the linear work, because that's where the schedule tends to actually slip while everyone's attention is on the visible dirt moving.
You're building a claim file whether you like it or not
Public infrastructure comes with an owner who documents relentlessly and a contract with real teeth — liquidated damages, defined milestones, certified payroll, environmental permit conditions. Two habits keep you out of trouble:
- Daily reports that are actually contemporaneous. Weather, crews and headcounts, quantities placed, equipment on site, delays and their causes, tests taken. Written the day it happened, not reconstructed from memory three weeks later when the dispute starts. A field tool that captures this from the crew's daily plan — with photos and location — turns your daily record into the backbone of any delay claim or change order.
- Quality holds treated as schedule constraints. Density tests, concrete breaks, proof rolls — work often can't proceed until the test passes, and the test takes time to run. If you don't schedule the inspection and the result into the sequence, you'll have a crew standing on a section they can't build on top of yet.
Environmental conditions belong on the plan too. Waterway work windows, in-stream restrictions, stormwater and erosion-control requirements, seasonal limits for wildlife — these aren't nice-to-haves, they're hard dates and daily obligations that a violation can shut the job down over.
When there's more than one prime, the handoffs are the risk
Big infrastructure jobs often run multiple prime contractors under one owner, which means nobody's subcontract binds the other primes to your schedule. The interfaces — where your grading has to be done before the other prime's paving, where you share a work zone or a haul road — are exactly where things fall apart, because each prime is optimizing its own plan. The fix is unglamorous: make the interface points explicit, agree on the handoff dates in writing, and keep them visible on a look-ahead everyone can see. Sharing the weekly plan with the other primes and the subs, so they see the same who's-working-where-and-when picture, is worth more than any amount of after-the-fact coordination meetings.
The through-line
Everything above comes back to one idea: infrastructure work is defined by location along a line and exposure to the outside world — weather, traffic, existing utilities, public owners. Plan by station and by production rate. Verify what's underground before you dig it. Treat traffic windows, quality holds, and environmental limits as real constraints on the daily plan, not afterthoughts. Document as you go. Do those things and the tooling almost picks itself — you want field management and short-interval scheduling that lets you tag work to the alignment, track feet-per-day against plan, and share the picture with everyone who touches the corridor. Get that right, and even a long, messy, exposed linear job stays on top of you instead of the other way around.