On a hard-bid, design-bid-build job, you get a complete set of drawings before you ever pull a permit. You know what you're building. On design-build, you're building the plane while it's still on the drafting table. Design and construction run at the same time, and the schedule has to hold both of them together without one running the other over. That's a different animal, and if you try to schedule it like a plan-and-spec job, you'll spend the whole project chasing a design that keeps moving under your feet.
I've run enough of these to know where they go sideways. The short version: on design-build, your schedule's job isn't just to sequence trades. It's to keep the design ahead of the construction by exactly the right margin — enough that the field never waits on a drawing, not so much that you're building off details that haven't been coordinated yet. Here's how to actually do that, and where a look-ahead scheduling tool earns its keep.
Treat Design As a Trade on Your Schedule
The single biggest mistake I see is running the design schedule and the construction schedule as two separate documents owned by two separate people. The architect keeps a design milestone list, the super keeps a construction look-ahead, and the two only meet in a coordination meeting where everyone discovers the design release everyone assumed was done is actually two weeks out.
Put design deliverables on the same wall as the field work. A design package release — foundations, structural steel, exterior envelope, MEP rough-in — is an activity with a duration, a responsible party, and successors, exactly like a concrete pour. Once you see "Level 3 slab-edge details — Issued for Construction" sitting three rows above "L3 deck pour" on the same weekly plan, the dependency stops being abstract. You can see the gap. And when the design date slips, you can see, that same afternoon, which pour it just pushed.
Set the Design-to-Field Buffer Deliberately
Every activity that depends on a drawing needs lead time between "design issued" and "we build it." Too tight and a one-day design slip stops the crew. Too loose and you're pouring footings off a foundation plan that the structural engineer is still revising because the geotech came back different.
Rules of thumb I hold to on design-build:
- Anything with long-lead procurement — structural steel, switchgear, elevators, custom glazing, air handlers — the design that fixes those dimensions and specs needs to be locked well before the field cares, because the buy drives the delivery, and delivery drives the sequence. Get the steel design and connections resolved early even if erection is months out. A late design release on a long-lead item doesn't cost you days, it costs you the lead time of the item.
- Field-critical details (embed layouts, sleeve and penetration locations, slab depressions, blockouts) want the design 1 to 2 weeks ahead of the pour, minimum. Miss an embed and you're either chipping concrete or field-welding a fix — both are worse than waiting.
- Finish-level design — where the design can float latest — still needs to beat the trade to the wall. Tile layout, casework, specialty lighting: get it resolved before the substrate goes up, not after.
The point of a rolling look-ahead here is that you're constantly checking the design front against the construction front. In your three-week window, every construction activity should trace back to a design package that's already issued. Anything in weeks four through six that's still waiting on a drawing is a constraint you flag now, while there's still time to expedite the design instead of stopping the crew.
Make Design a Constraint You Track, Not an Excuse You Discover
If you run any flavor of the Last Planner System — and design-build is exactly where it pays off — treat design availability as a formal constraint on made-ready work. An activity isn't ready to be committed to a weekly work plan until its design is released, its submittals are approved, and its material is on site or scheduled. Design is usually the constraint that gets waved through with "it'll be done by then," and it's usually the one that isn't.
Run your constraint log honestly. For each activity entering the look-ahead, ask: is the governing drawing Issued for Construction, or is it still a progress set? A CD-level or "for coordination" drawing is not something you build off of, and treating it like one is how rework starts. Screen it out of the weekly plan until the design is genuinely locked, and put the design release date in the constraint log with an owner and a needed-by date. That's the difference between a delay you saw coming three weeks out and one that hit you Monday morning.
Submittals and Procurement Move Earlier Than You Expect
On design-build, the submittal doesn't wait for a complete design — it often is part of the design. A steel fabricator's connection design, a curtain wall shop drawing, a fire-sprinkler layout: those come back from the sub and feed decisions the design team is still making. That's good — it's concurrent engineering working the way it's supposed to — but it means your submittal register and your design schedule are the same conversation.
Map it backward from the field. If steel erection starts in week 20, you need approved shop drawings by roughly week 10 to 12, which means fabricator design started around week 6, which means the design-assist package and structural criteria had to be firm by week 4. Miss the front of that chain and every downstream date is fiction. Put submittal review durations on the schedule as real activities — a two-week review that everyone treats as instantaneous is a favorite way to lose a month across a dozen packages.
Fast-Track Means Overlap, Not Just Speed
Most design-build jobs are also fast-track: you're mobilizing sitework and foundations while the interiors are still being designed. Fast-track isn't about working faster, it's about deliberately overlapping phases that a traditional job would run in series. The risk is obvious — you commit concrete to the ground before the design above it is fully settled, and a change up top ripples down to what you already built.
Manage the overlap by phasing your design releases to match your construction sequence, bottom-up and outside-in: foundations and structure locked first, envelope next, then interiors and finishes. Your look-ahead should show design staying exactly one phase ahead of the field. When you see the interiors design falling behind and the structure topping out, that's your early warning that the overlap is collapsing and you're about to run out of released work — time to either accelerate the design or find make-ready work to keep crews productive without building off unsettled details.
Design Changes Will Happen — Have a Path for Them
On plan-and-spec, a design change is a change order and an argument. On design-build, it's Tuesday. The team is genuinely refining the design as construction reveals real conditions, so changes aren't failures — but each one has a schedule impact, and undocumented changes are how a design-build job quietly loses six weeks nobody can account for.
When a design decision changes, run it through the look-ahead immediately: which released activities does it touch, what's already built that's now affected, and does it move a downstream date? Keep the change history where the whole team can see it — the design lead who made the call needs to see that it just pushed the MEP rough-in a week, and the owner needs to understand that "small" design tweaks have a cost even when there's no separate contractor to bill. Visibility is the whole game. A schedule that quietly absorbs changes until the float is gone is lying to everybody.
Keep the Owner in the Loop — Because There's No One Else to Blame
Design-build puts design and construction under one roof, which is the selling point and also the trap: when a design decision slows construction, there's no other party to point at. That makes owner communication more important, not less. The owner made a design-build choice partly for speed and single-point accountability; they need to see both disciplines moving and understand when their own decisions are on the critical path.
Give the owner a view they can actually read — not the full working look-ahead with every constraint, but a clean picture of design progress next to construction progress and the decisions you need from them and by when. Half the design slips on these jobs trace back to an owner selection that sat on someone's desk. A schedule that shows "finish selections due — needed by [date] to hold flooring start" turns a vague nag into a specific, dated ask, and owners respond to that.
What the Right Tool Actually Has to Do
All of this comes back to one requirement: design and construction have to live on the same schedule, updated by the same rhythm, visible to everyone who can move a date. A tool built for weekly look-ahead and short-interval planning — like LookAheadWall — fits this because it's location-based and trade-flow driven: you sequence work by area and connect the hand-offs, so a slipped design release visibly breaks the flow into the space it feeds instead of hiding in a bar somewhere on a Gantt chart. Crew leaders see the current week on their phones; the design and construction leads work the three-to-six-week window together.
Whatever you use, hold it to this bar: it has to show design deliverables and field work side by side, let you flag design as a constraint before work is committed, make change impacts visible the day they happen, and give the owner a view they'll actually open. Get those four things and you're scheduling design-build the way it needs to be scheduled — with the design always a deliberate step ahead of the crew, and everyone looking at the same wall.