Concrete is the least forgiving trade on the job. Frame a wall an inch off and you shim it. Set rebar wrong and you re-tie it. But once the truck starts turning and mud hits the forms, you are committed. There is no undo button on a pour. That single fact — that concrete is irreversible the moment it lands — is why scheduling concrete work is a different animal than scheduling almost anything else on site, and why a sloppy plan costs you a demo hammer and a very bad week.
I have spent enough mornings standing in a form at 5 a.m. watching the sky, phone in hand, deciding whether to send the trucks or eat the cancellation fee, to have strong opinions about how this work should be planned. What follows is how I think about sequencing concrete, where crews get burned, and how a proper look-ahead keeps a pour from turning into a fire drill.
Why concrete lives and dies on the look-ahead
A pour is not one activity. It is the visible tip of a chain of predecessors that all have to land in the right order, and every one of them is a place the whole thing can stall. Forms, rebar, embeds, sleeves, waterstop, inspection, and the ready-mix order itself — miss any single link and you are either standing around with idle finishers or you are pouring over incomplete work and living with the consequences.
This is exactly the problem short-interval scheduling was built for. A three- or four-week look-ahead pulls the pour date back into view early enough that you can see whether the electrician's underslab conduit, the plumber's stub-ups, and the rebar delivery are all actually going to converge on the same day. The value is not the calendar — it is the constraint hunting. Two weeks out, you want to be asking "what could stop this pour?" while you still have time to fix it, not discovering the answer at 6 a.m. with a batch plant on the line.
Build the sequence backward from the pour
The mistake I see young supers make is scheduling forward from where the crew is today. Concrete rewards the opposite. Fix the pour date, then walk it backward and hang every predecessor off it with honest durations.
A slab-on-grade sequence, roughly, reads like this:
- Fine grade and compaction — proof-roll it, get the density test back before you build on top of it.
- Underslab MEP — plumbing, electrical conduit, sometimes low-voltage. This is where you lose days, because it is three different subs whose work has to interleave.
- Vapor barrier and any underslab insulation — patched and taped, penetrations sealed.
- Form the perimeter and any pour strips / construction joints.
- Set rebar or mesh, chairs, and dowels — tied, not just laid.
- Set embeds, anchor bolts, sleeves, blockouts, and waterstop.
- Pre-pour inspection — usually rebar/deck inspection by the jurisdiction plus a special-inspector sign-off.
- Pour, screed, finish, cure.
Every one of those is a row on your weekly work plan, with the trade that owns it named. When you can see the whole ladder in one view — and see where two trades are stacked on the same location on the same day — you catch the collisions before they happen. That is the entire point of laying trade flows out visually: the conflict jumps off the screen in a way it never does buried in a bar-chart CPM printout nobody on the crew reads.
The predecessors that quietly kill pours
Embeds and blockouts. This is the classic. The pour goes off clean, everyone goes home happy, and three weeks later a sub shows up looking for the sleeve that was never set, or the equipment pad anchor bolts that are now buried in six inches of finished slab. Embeds are somebody else's scope dropping into your pour, which means they get forgotten. Put embed installation on the schedule as its own line with the responsible trade, and make "embeds verified" a hard checkpoint on the pre-pour walk. A five-minute walk with the embed drawings beats a core-drill-and-epoxy repair every time.
Underslab MEP interleave. Plumbing rough usually wants to go first because their lines are bigger and deeper; conduit weaves around it. If you schedule them as one blob called "underslab MEP," you will find both crews in the same trench fighting over the same square footage. Break them into separate activities with a day or two of sequence between them, and give the earlier trade enough finish time that the later one isn't stepping on wet work.
Inspection timing. Never schedule the pour for the morning after the rebar inspection. Give yourself a buffer day. Inspectors write corrections — missing dowels, wrong bar spacing, insufficient cover, a hook that doesn't develop — and you need a day in hand to tie the fixes and get the re-check without blowing the truck schedule. On a Friday pour that buffer is oxygen; a Thursday correction with no slack means a Monday pour and a weekend of the slab sitting open.
Weather is a predecessor, treat it like one
Concrete cares about temperature more than any other trade you run. Hot-weather placing — roughly above 90°F, and honestly earlier if there's wind and low humidity — accelerates set, steals your finishing window, and invites plastic shrinkage cracking. Cold-weather work below 40°F slows strength gain to a crawl and, if it drops below freezing before the concrete reaches about 500 psi, can wreck it outright.
So weather is not a "monitor and hope" item. It is a scheduling input. In hot weather you move the pour earlier — trucks rolling at first light, finishers staged before you order the first load. You spec a retarder, plan for evaporation retardant, and have water or fogging ready. In cold weather you schedule blankets, plan the accelerator, and build in the extra days before you can strip forms or load the slab, because that concrete simply is not getting to strength on the summer timeline. A rolling look-ahead earns its keep here: when the ten-day forecast turns, you slide the pour and re-sequence the trades around it in one pass instead of a dozen phone calls.
Curing is a real activity, not dead air
The single most abused number in concrete scheduling is cure time, because people treat it as a gap on the calendar instead of a gate on the work that follows. It is a gate. You cannot strip forms, load the deck with material, saw control joints, or run traffic over the slab until it has the strength for that specific action — and those are different thresholds.
Rules of thumb worth internalizing:
- Control-joint sawing wants to happen in a narrow window — early enough to beat the shrinkage cracks, late enough that you don't ravel the edge. Often the same day or the next morning. Miss it and the slab cracks where it wants to, not where you cut.
- Form stripping on verticals is frequently the next day; on suspended and shored slabs it can be days to weeks and is governed by the engineer, not by feel.
- Loading a slab — staging pallets of block or drywall — before it's ready will crack it. Wait for the strength, not the calendar guess.
- Seven days is a common minimum before heavy follow-on, but let the break results drive it, not habit.
Put curing on the schedule as its own bar with a duration, and hang the follow-on trades off the end of it. When the whole crew can see that the slab is curing until Thursday, nobody schedules the framers onto it Wednesday and nobody stages steel on it Tuesday.
Post-tensioning adds two gates, not one
PT slabs bring their own choreography and they are unforgiving of a bad plan. The tendon layout has to be set and inspected before the pour, which is a real coordination job in itself. Then, after the pour, you get a second gate: you cannot stress the tendons until the cylinders hit the specified strength — commonly around 3,000 psi, but read the engineer's spec — and you generally cannot strip supporting forms until stressing is done. Schedule the break tests, the stressing operation, and the grouting/patching as distinct activities with the strength milestone as their trigger. Guess on PT strength and you either stress too early and damage the slab, or you sit around a day longer than you needed to with a crew waiting.
Ordering mud: the plan meets the batch plant
The ready-mix order is where your paper schedule collides with the real world. A few habits that save pours:
- Confirm quantity off the actual measured forms, plus waste — a few percent for slab-on-grade over compacted base, more over rough subgrade. Running short mid-pour and waiting on a "hot load" gives you a cold joint you didn't design.
- Match truck spacing to your placing rate. Order too tight and trucks stack up and start to set in the drum; too loose and you're waiting between loads, risking cold joints. Tell the dispatcher your real pour rate, not a wish.
- Lock the mix design and any admixtures the day before, not the morning of. Retarder in hot weather, accelerator in cold, the right slump for the pump — these are decisions made off the forecast, not off the truck.
- Have your pre-pour checkpoint clear the pour before the trucks roll. The dispatcher moving trucks toward your gate should mean forms, steel, embeds, and inspection are all signed off. That readiness confirmation living in one shared plan, rather than in your head, is what keeps a green super from ordering mud onto work that isn't actually done.
Where a look-ahead tool actually helps
None of this requires software to be true — good supers ran concrete off yellow pads for decades. What a location-based look-ahead like LookAheadWall changes is the coordination overhead. When forming, rebar, embeds, inspection, pour, and cure are all rows tied to a location and a week, the whole crew and every sub are reading the same plan. The finish crew knows which pour is theirs and when. The plumber sees that his stub-ups gate a Thursday slab. The super sees, two weeks out, that inspection and the pour are stacked on the same day and slides one before it becomes a 6 a.m. problem. Crew leaders carry that same plan in their pocket on the mobile app instead of relaying it over the radio.
The tool doesn't pour the concrete or make the calls. It just makes the sequence visible early, keeps everyone honest about predecessors, and turns "I thought someone set that embed" into a checkbox somebody actually owns. On work you can't take back, seeing the collision a week early is the whole game.