Paving is one of the least forgiving trades on a jobsite. Most of the work happens outdoors, on the critical path, in a narrow window where temperature, moisture, and the readiness of the base all have to line up on the same day. Get the sequence right and a crew can lay thousands of tons in a shift. Get it wrong and you're either chasing a rained-out subgrade or watching a loaded belly-dump idle at $200 an hour while somebody figures out why the roller can't get on the mat. This is exactly the kind of work a disciplined weekly work plan is built to protect.
I've run enough parking lots, access roads, and heavy-highway sections to know that paving problems are almost never paving problems. They're upstream problems that nobody caught until the paver was already on site. What follows is how to build a short-interval schedule that actually catches them.
Start With the Base, Not the Paving
The single most common way a paving day goes sideways is that the base wasn't truly ready. "Grade's done" from a text message and "grade's done" verified with a stringline and a proof-roll are two very different things. Before you commit trucks and a crew, the subgrade or aggregate base needs to be at line and grade, compacted to spec, and proof-rolled with no pumping or soft spots. If the geotech or inspector hasn't signed off, you don't have a paving day — you have a hope.
Build the dependency into your look-ahead explicitly. In a good weekly work plan you don't just show "paving Thursday." You show the base completion, the proof-roll, and the inspection as their own predecessor activities, each with an owner and a date. When you connect those as a trade-flow sequence in scheduling software like LookAheadWall, the whole crew can see that Thursday's mat depends on Tuesday's proof-roll passing — and that if the proof-roll slips, everything downstream slides with it. That visibility is worth more than any status meeting.
A practical rule of thumb: give yourself a one-day buffer between base acceptance and first lift. That day absorbs the punch-list fixes that always surface at proof-roll — a soft corner, a utility trench that settled, a grade that's a tenth low near the catch basin. Crews that pave the same day the base "passes" are the ones who end up milling out low spots later.
Weather Is a Constraint, Not a Surprise
Asphalt and concrete both live and die by conditions, but they fail in different ways, and your schedule has to respect both.
For hot-mix asphalt, the enemy is a cold mat that you can't compact before it stiffens. Rolling has to happen inside the compaction window, and that window shrinks fast on a windy 45-degree morning with a thin lift. As a general guide, most agencies want ambient and surface temperatures at or above 50°F and rising for surface courses, with tighter limits on thin lifts. When the calendar pushes you into late fall, thicken the lift or move the pour — a 1.5-inch surface course laid on a cold base in a stiff wind is a callback waiting to happen.
For concrete paving, the risks flip: too hot and you get plastic shrinkage cracking and flash set; too cold and you're fighting to reach strength before a freeze. Above roughly 90°F you're on hot-weather protocols — evaporative retarders, wind breaks, maybe a night pour. Below 40°F and dropping, you're into blankets and cold-weather curing.
The scheduling discipline is the same for both: look at the forecast when you build the weekly plan, not the morning you're supposed to pour. Weather forecasts are usable at 5-7 days out, which is exactly the horizon a weekly work plan or a rolling three-week look-ahead covers. If Thursday shows an 80% chance of rain, you make the call Monday — reshuffle to pull interior or site-utility work forward and slide paving to the dry window — instead of standing in the mud Thursday morning making a panic decision with a crew already on the clock. Note the reason for the move in the plan, too. When the owner asks in three weeks why paving is behind, "here are the four days it rained" is a much better answer than a shrug.
Sequence Material and Equipment Around Production, Not the Other Way Around
Paving is a supply-chain problem disguised as a construction task. Your production rate is set by whatever link is weakest — the plant's output, your truck rotation, or your crew — and the whole thing only works if it's balanced.
Two failure modes to design against in the plan:
- Trucks waiting on the plant. If the asphalt plant can load faster than your paver consumes, fine. If it can't, your paver starves and stops, and every stop is a cold joint and a bump. Confirm plant capacity and your ticket sequence before you set the day's tonnage target.
- The paver waiting on trucks. Under-trucking is the classic mistake. Figure your haul cycle honestly — load time, travel each way (in real traffic, not at 2 a.m.), dump, and return — and put enough trucks in rotation that the paver never stops moving. A paver that stops and starts leaves a mark you can see and feel forever.
Same logic for equipment moves between phases. A milling machine, a distributor truck, a paver, and a breakdown/finish/pneumatic roller train don't teleport. If you're paving Lot A Thursday and Lot B Friday, the lowboy move, the fuel-up, and any maintenance need to be their own line items. I've watched a crew lose a full morning because nobody scheduled the transport and the roller was still on last week's job an hour away. In the weekly plan, equipment moves get the same respect as labor — an owner, a time, and a predecessor.
The Site-Coordination Gotchas That Actually Bite
Paving touches almost everything else on a horizontal job, and the conflicts are predictable enough that you can plan them out.
Utilities and Structures First — All of Them
Never pave over work that isn't finished underneath. Every manhole, valve box, catch basin, and monument needs to be set to final grade before the surface course, or you're coring and patching later — and a patched utility casting is an obvious, permanent scar on a fresh lot. Walk the area and physically confirm castings before you accept the base. Put "adjust structures to grade" in the look-ahead as a hard predecessor to the surface lift, not an afterthought.
Curbs, Then Base Paving, Then the Interaction
On most site work the curb and gutter goes in before you pave up to it, which means the concrete crew and the paving crew are sequenced, not simultaneous. Give the curb enough cure time to take truck traffic before you run loaded haul trucks along it. Crushing a two-day-old curb with a belly dump is an expensive way to learn about cure schedules.
Traffic Control and Cure Windows on Active Sites
If you're paving a road or a lot that has to stay partly open — a phased mill-and-fill, an occupied retail center — traffic control is a schedule constraint in its own right. It needs a plan, sometimes a permit, and lead time to arrange flaggers or lane closures. And you have to hold traffic off fresh work through the cure/cool-down window: hot asphalt generally wants to cool to roughly ambient before it takes traffic (a few hours, longer for thick or shaded mats), and concrete paving needs real cure time — often 7 days before full loading, sometimes opened earlier to light traffic under a high-early mix. Bake those restrictions into the plan so nobody promises the client a lot that's still off-limits.
Striping and Final Grading Come Last, and Have Their Own Lead Times
Layout striping can't go down until the surface has cured enough to hold paint and the traffic-control and cure windows have cleared. Booking the striping sub is a lead-time item — call them when paving hits the three-week look-ahead, not the day the mat cools. Same with final landscaping and cleanup crews who want to close out edges after paving. Sequence them so they're not standing on a lot that's still off-limits, and so you're not re-mobilizing anyone.
Build Quality Checks Into the Schedule, Not After It
Testing is not paperwork you catch up on Friday. Nuclear density gauge readings, core samples, thickness checks, and smoothness testing all have to happen while the work is fresh — and some of them gate whether you can keep going. If the density on the first lift doesn't pass, you need to know before you bury it under the surface course.
Put testing activities on the plan as their own line items with the testing agency named as the owner. Coordinate the lab so a tech is on site the day you pour — a load of concrete with no one there to pull cylinders is a load you may have to defend or remove. Tracking test results and their pass/fail status in your field management tool, alongside the schedule, means a failed density reading triggers a rework activity immediately instead of surfacing at final acceptance when it's ten times more expensive to fix.
Run the Week Like a Paving Superintendent, Not a Spectator
Pull all of this together and the pattern is clear: paving success is set upstream, days before the paver shows up. The weekly work plan is where you force those upstream items into the open — base acceptance, structure adjustments, weather calls, plant and truck capacity, testing, traffic control, and the trades that come before and after you.
A few habits that separate crews who hit their numbers from crews who chase them:
- Commit to the week, then protect it. Decide Monday what's realistic given the forecast and the base status, and treat those commitments as promises to the trades downstream. A plan that changes every morning isn't a plan.
- Make every dependency visible. If Thursday's mat depends on Tuesday's proof-roll, the whole crew should be able to see that connection. Trade-flow sequencing in a look-ahead tool makes the ripple effect obvious the moment something slips, so you reschedule with a day's notice instead of a morning's panic.
- Measure percent-plan-complete honestly. At week's end, count how many of your planned activities actually finished. When paving keeps missing, the reason column — rain, base not ready, trucks short, testing failed — tells you exactly which upstream link to fix. That feedback loop is the whole point of short-interval scheduling.
None of this requires software to understand. But once you're juggling multiple phases, a dozen structures to adjust, three trades sequenced around your window, and a forecast that changes daily, a visual weekly work plan earns its keep fast — it keeps the base, the plant, the crew, and the trades before and after you all reading from the same page. The paving is the easy part. The week that leads up to it is where the job is really won or lost.