Concrete dispatch is the discipline that decides whether a bid becomes a profitable pour or a callback. The quote book can be perfect and the mix design can be right, but if the wrong two-person crew is on the slab at the wrong hour the job still loses money. This walkthrough covers the four levers a concrete dispatcher actually uses in production — weather-aware scheduling, crew assignment by skill, on-site pour sequencing, and the dispatch board that ties it all together on the day of the pour — with the field logic and small habits that turn a group-text chaotic morning into a run-the-board dispatch.
1. Weather-aware scheduling — the rain delay and the slump window
Every concrete pour starts with a weather read. Rain inside the cure window is the most expensive forecast miss a dispatcher can make: water on the slab during the first four hours after the pour scours the surface, ruins the finish, and forces a tear-out the homeowner will not pay for. A forecast that turns wet inside that cure window is a pushout, not a gamble — the pour moves a day, the crew rolls to the next ticket, and the homeowner gets a call before the truck is loaded. Scheduling concrete pours against a live radar, not a five-day outlook, is the difference between a clean pour day and a callback.
The other half of the weather check is temperature. A 90°F+ day shortens the slump window — the working time between the truck arriving and the slab going off — from ninety minutes to forty-five. Hot-weather pours need either a retarder admixture, a chilled mix, or a re-temper on the truck, and a finisher who knows the difference. Cold mornings do the inverse: set time stretches, blankets go on the slab overnight, and the cure-window checklist grows. A dispatcher who logs the weather window that drove the push-out keeps the original quote’s line items intact on the reschedule — no re-measuring, no re-quoting. That is exactly what the field-tested reschedule workflow in the quoting guide walks through, and it is why the dispatch board on the morning of the pour shows the weather call next to the line items, not buried in a back-channel text thread.
2. Crew assignment by skill and availability
Not every finisher can run every pour. A slab crew needs a lead who can read a screed and a fresher who can place; a footing crew needs a lead who can drive a pump-truck chute and a hand on the vibrate; a stamped crew needs certification and a heat-day pour needs the last finisher left on the roster, not the first available body in the dispatch queue. The wrong two-person crew on a stamped patio is not a learning experience — it is a tear-out. Crew assignment in concrete is skill-mapped, not alphabetically assigned, and the dispatch board that ignores that turns a profitable day into a punchlist.
Availability is the other half of the split. A heat-day pour at ninety-five degrees eats a finisher faster than a sixty-degree morning — the last finisher standing turns into the only asset the dispatcher actually has at two in the afternoon. Crews that are split across two concurrent pours need a hard handoff time, not a soft estimate, or the second pour starts an hour late and the truck bill grows. The live crews board in the dashboard surfaces those splits — who is certified where, who is on a hot pour, who is off at noon — so the answer that gets dispatched is the one that finishes the pour, not the one that looked right at 7 a.m.
3. On-site sequencing for multi-pour days
Two pours on the same day is a logistics problem, not a calendar problem. The foundation pour and the slab pour on the same site have to sequence against the cure-window gap — foundation first, slab after the foundation has taken initial set, usually a four-to-six-hour window between trucks. The pump-truck scheduling on top of that turns a two-pour day into a single dispatch ticket rather than two competing ones: one pump on site, one crew rotation, one truck lane, and a hard time-on-site target that keeps the second pour from bleeding into overtime. Concrete dispatch is where time-on-site math earns its keep.
A generic field-service tool treats multi-pour days as two unrelated work orders, which is why the truck bill grows and the second pour starts an hour late. Foundation-software pricebooks handle a flat bid cleanly but miss the crew-split side of the equation — the same pricebook line for “foundation” and “slab” cannot model that the second pour needs a different crew on a heat day. PourSmart vs foundation pricing software walks through where that flat pricebook breaks down on a real two-pour day, and where the time-on-site math has to take over.
4. The dispatch board workflow
The PourSmart dispatch board is the surface the dispatcher actually lives in on the morning of the pour. The board shows the day’s pours in time-on-site order — truck arrival, crew assignment, weather call, and the line items carried over from the original quote. The dispatcher reads the board top to bottom: rain-delay pushes first, then the multi-pour day, then the standalone slab. Each row carries the crew split that drives the assignment, the weather window that drove the date, and the contact for the reschedule call if the forecast moves. This is where the dispatch logic in sections one through three turns into a runnable morning.
House-call routing tools understand a flat route but not the certification layer that concrete crews need. A dispatcher running the morning on a house-call routing app ends up re-doing the crew split in a text thread while the first truck is loading. PourSmart vs House Call Pro walks through why a routing list does not translate to a finisher-certified crew, and how the dispatch board in the dashboard keeps the certification, the weather call, and the pour-day contacts on the same screen so the dispatcher stops at one surface, not five.
Bring a real pour into PourSmart.
Pick a pour you have bid recently and run it through the calculator — see the breakdown PourSmart produces in seconds, before you commit.