A distribution center looks simple on paper. Big box, flat slab, dock doors, done. Anyone who has actually built one knows better. The building shell is the easy part. What kills the schedule is the handoff between the general contractor and the material handling integrator — the moment your tilt-up box becomes somebody else's assembly line. Two separate schedules, two separate cultures, and a slab that has to be flatter than anything you have ever poured. Get the choreography wrong and you eat weeks of float you didn't have.
This is the job where short-interval scheduling earns its keep. A three-month bar chart tells you the conveyor install starts in April. It does not tell you that the integrator needs the northeast quadrant power-washed, laid out, and released four working days before their crew flies in, or that your slab moisture numbers won't clear the epoxy floor coating in that same zone. Those are weekly-work-plan problems, and that is where the schedule actually lives or dies.
The Two Schedules Problem
On most DC jobs you are running two projects at once. There is the base building — foundations, tilt panels or structural steel, roof, dock equipment, MEP rough-in — and there is the material handling system, which is usually a separate contract, often direct to the owner. Conveyors, sortation, print-and-apply, robotics, the whole automated guts of the building. The integrator has their own project manager, their own schedule, and frequently their own idea of when your building will be ready.
The failure mode is predictable. The base building schedule shows substantial completion on a date, the integrator's schedule shows equipment install starting on that same date, and nobody has reconciled the make-ready work that connects them. Then the integrator's crews land, find the slab isn't coated, the fire main isn't charged, or the roof still leaks over grid line C, and everybody stands around at $200 an hour while the two PMs argue about whose float it was.
Pull both schedules into one look-ahead window and the collisions surface early. A four to six week look-ahead is the right horizon here — long enough to catch equipment deliveries and long-lead switchgear, short enough that the commitments are real. The base building trades and the integrator's install crews need to be on the same weekly work plan, staring at the same wall, or the handoff will be a fight every single time.
The Slab Is the Whole Ballgame
Nothing on a distribution center will humble you faster than the floor. Automated guided vehicles, high-bay very-narrow-aisle racking, and robotic pickers don't tolerate a slab that heaves and dips. You are no longer pouring to a "broom finish, drain to the door" spec. You are pouring to a defined-traffic or random-traffic floor flatness number — FF and FL values, or in the VNA aisles, a straightedge and elevation-differential tolerance that makes finishers sweat.
A few hard-won rules on DC slabs:
- Test flatness within hours, not days. FF/FL numbers have to be measured within 72 hours of finishing per the standard, and practically you want the dipstick or profileograph on the slab the next morning. Wait a week and you have lost the ability to grind or re-finish while it's still cheap, and you have lost the argument about who's responsible.
- Grinding is not a plan, it's a rescue. Budget the pour to hit the number wet. If your look-ahead shows grinding remediation as a standing line item, your finishing crew or your mix is the problem, and grinding an entire quadrant will blow a week you didn't schedule.
- Moisture will ambush the floor coating. If there's an epoxy or urethane topcoat — and in the pick modules there usually is — the slab has to hit a moisture vapor emission or relative-humidity threshold before the coating goes down. On a slab-on-grade poured in winter, that clock can run 30, 60, even 90 days. Put the moisture testing milestones in the look-ahead the day you pour, not the week the coating crew shows up.
- Protect the finish you paid for. The flattest slab in the county is worthless if a scissor lift chews a rut into it during steel erection. Sequence the high-tolerance pours late, or ram-board and plate anything with wheels.
The slab connects to almost every downstream activity, which is exactly why it belongs in a constraint-based, make-ready plan rather than a static bar. Before you release a zone to the integrator, somebody has to physically confirm: flatness signed off, coating cured, embeds and anchor points laid out, and the area clean. That's a make-ready checklist, and if it isn't tracked at the weekly level it becomes a surprise at the worst possible moment.
Make-Ready: Removing Constraints Before You Commit
The single most useful idea from Last Planner-style planning on a DC is simple: don't schedule work you can't actually do. Before a task earns a slot in the weekly work plan, walk its constraints and knock them down. For distribution centers the recurring constraints are almost always the same short list:
- Slab flatness verified and coating cured in the work zone
- Overhead clear — roof watertight, and the deck above not still hosting sprinkler drops or duct mains that the equipment crew will collide with
- Temporary power adequate for the tools and the equipment commissioning that follows
- Layout and control lines shot, anchor points located, embeds confirmed against the equipment shop drawings
- Equipment physically on site, or a delivery date you actually trust, staged where the install crew wants it
- Preceding trade genuinely complete, not "90 percent" — that last 10 percent is where the punch-list wars start
Run that checklist in a planning conversation, not in your head. When the base building super and the integrator's install lead sit at the same look-ahead each week and one of them says "I can't commit to the east conveyor run because the fire main isn't charged and my anchors land in a zone you haven't coated," you just saved yourself a delay. That constraint-conversation is the entire point of a weekly work plan, and it's where scheduling software that lets both parties see the same location-based plan — LookAheadWall exists precisely for this kind of multi-party, location-driven coordination — beats a spreadsheet that only one person maintains.
Sequencing the Handoff and the Overhead
The nastiest coordination gotcha on a DC is the ceiling. Fire suppression, conveyor structure, catwalks, mezzanine steel, lighting, and equipment power all fight for the same air. And in a high-piled-storage building, the fire suppression design is driven by the rack layout — in-rack sprinklers, ESFR head placement, and clearances all depend on where the racking actually lands. If the racking layout shifts even a little after the sprinkler is roughed in, you're moving heads, and the fire marshal doesn't grade on a curve.
So the sequence discipline is: lock the equipment and rack layout, then let fire suppression, then let the equipment install, then trim out lighting and power to the exact head and drop locations. When those run out of order — sprinkler first on an assumed layout, then the real racking comes in eight inches off — you're paying to relocate heads and you're chasing a re-inspection. A rolling look-ahead that keeps the fire suppression milestones tied to the equipment layout release is how you keep that from sneaking up.
Mezzanines add another layer. The steel erection has to slot in before the equipment that sits under and on top of it, which means it has to be planned against both the slab below (loading and shoring) and the overhead trades above. Erect it too early and it's in everybody's way; too late and the conveyor crew is standing around waiting for a deck to work off of. A day or two of buffer between mezzanine steel completion and the first equipment set on it is cheap insurance — it gives you room for decking, handrail, and the inevitable "we found a conflict" fix.
Commissioning and Phased Turnover
Here's the part owners forget and schedulers underestimate: on a DC, mechanical completion is not the finish line. Once the conveyors and sortation are installed, the integrator commissions the system — powers it up zone by zone, runs test totes, tunes the scanners and diverts, and integrates the controls with the warehouse management software. That commissioning can run for weeks, and it needs the building genuinely done: permanent power energized, HVAC balanced enough to keep the electronics happy, and the floor coating cured so test loads aren't tracking dust into the scanners.
Two things wreck commissioning schedules. First, punch-list work still crawling around the building — you cannot commission a live conveyor while a painter is on a lift over it. Second, permanent power slipping. Utility coordination and switchgear are long-lead items; if energization drifts, commissioning drifts with it, and commissioning is usually on the critical path to the owner's operational start date. Put the utility milestone in the look-ahead early and treat any slip as a red-flag event, because everything downstream of it moves in lockstep.
Most big distribution centers also turn over in phases. The owner wants to start receiving product in the finished half while you're still commissioning the automation in the other half. That's a gift and a trap. It's a gift because it takes schedule pressure off. It's a trap because now you've got live operations — forklifts, associates, inbound trucks — sharing a building with active construction, and the wall between "occupied" and "under construction" has to be real: fire separation, egress, dust control, and a hard site-logistics plan for keeping the two populations apart. Phased occupancy has to be planned as its own set of milestones with the fire marshal and the owner at the table, not bolted on at the end.
What Actually Keeps These Jobs on Track
Distribution centers reward planning discipline more than raw manpower. The building is big but not complicated; the coordination between the base building and the automation is complicated, and that coordination happens at the weekly and daily level, not on the master schedule. The teams that deliver these on time are the ones who reconcile the two schedules into one look-ahead, run every equipment-install zone through a real make-ready checklist, and treat the slab and permanent power as the two constraints that quietly govern everything else.
None of that requires fancy tools. It requires the base building superintendent and the material handling integrator looking at the same location-based weekly plan, having the honest constraint conversation, and committing only to work they can actually complete. Whether you run that on a whiteboard or in look-ahead scheduling software, the practice is the same — plan short, plan by location, remove constraints before you commit, and never let the handoff between your building and their machine be a surprise to either side.