On a hard-bid job, the drawings are done before you break ground. You get a full set, you take off the work, you schedule the trades, and if the design is wrong that's the owner's problem and the architect's headache. Design-build throws that comfort out the window. Now you're pouring footings while the interior partitions are still being drawn, procuring switchgear off a one-line that hasn't been stamped, and holding the whole thing together with a schedule that has to track two clocks at once: how fast the design can mature, and how fast the field can build it.
That's exactly the seam where design-build jobs get hurt. And it's exactly the seam a six-week look-ahead is built to watch. The long-form CPM baseline tells you the design-build story at 30,000 feet. The six-week window is where you catch the design package that's running three days late before it strands a framing crew.
Why design-build breaks a construction-only look-ahead
The mistake I see most often is treating the look-ahead like it's still a hard-bid job — populating it only with construction activities and assuming the drawings will be there when the crew shows up. On design-build that assumption is a trap. Half your real constraints in the next six weeks aren't field work at all. They're design deliverables, owner decisions, and long-lead procurement that hasn't been released because the design isn't frozen yet.
So the first rule is simple: design activities belong on the look-ahead alongside the construction activities. Not in a separate spreadsheet the design lead keeps to himself. In the same weekly work plan the field is looking at, with the same start and finish dates, tied to the construction activities that depend on them. If your framing pull date is Monday and the interior layout package isn't sealed until the Friday before, that's a one-business-day cushion on a deliverable that historically slips — and you want to be staring at that gap two weeks out, not the morning the crew is standing in the parking lot.
Why six weeks is the right window
People ask why six weeks and not three, or eight. On design-build, six is the sweet spot because it's about the length of one full design-to-construction cycle for a mid-size package. A typical design package — call it a floor's worth of interior partitions, or a mechanical room layout — takes roughly four to six weeks to develop, coordinate, review, and release. If your look-ahead window is shorter than that cycle, you're seeing the construction activity land before you ever saw the design activity that feeds it. Six weeks lets you watch a package be born, reviewed, and handed off, and still have runway to react when a step slips.
It also matches the rhythm of procurement release. In design-build, design completion is the trigger that frees procurement, and procurement lead time is what actually governs when a crew can mobilize. Six weeks of forward visibility is usually enough to see "design freezes here → PO releases here → submittal here → fab here" for anything that isn't a genuine long-lead item. The long-lead stuff — switchgear, air handlers, custom glazing, elevators — you handle separately as early-release packages, because those clocks start months out and no six-week window will save you if you miss them.
Map the design-to-construction handoffs first
Before you worry about durations, get the handoffs right. Every construction activity in your window has a design predecessor, and the interface between them is where design-build jobs live or die. For each construction activity coming up, ask three questions:
- What design information does this need, and is it released or preliminary? "Preliminary" drawings in the field are how you end up demoing your own work. Mark clearly whether the crew is building off issued-for-construction documents or something softer.
- What's the last responsible moment for that information? Work backward from the crew's start date through submittal review, fabrication, and delivery to find the date the design actually has to be done. That date is a constraint, and it goes on the look-ahead as one.
- Who owns the decision that unlocks it? Sometimes it's the design team. Often it's the owner — a finish selection, a layout sign-off, a value-engineering call. Owner decisions are real schedule constraints and they take real time, so put owner review durations in the plan instead of assuming a decision arrives the day you ask for it.
When you make those handoffs explicit, the look-ahead stops being a to-do list and becomes a constraint log. And a constraint you can see three weeks out is a constraint you can clear. A constraint you discover the morning of is a stand-down.
Procurement is where optimism kills you
Here's the failure mode that costs design-build jobs the most money. The design isn't fully frozen, but the team convinces itself it's "basically done," so procurement gets held waiting for the final version. Then the drawings release, the PO goes out, and now you're eating full fabrication lead time with zero float because you burned the runway waiting for perfect. Meanwhile a crew that could've been productive is idle.
The discipline that fixes this is separating what has to be final from what's stable enough to act on. A lot of procurement can be released on design that's specification-complete even if a few dimensions are still moving — you're ordering a pump based on its performance spec, not the exact routing of the pipe to it. Your look-ahead should show two distinct milestones: "specification finalized" (which usually frees procurement) and "design fully coordinated" (which frees the field). Confusing the two is what strands crews. Track long-lead procurement as its own early-release stream that starts before design completes, and be honest that fabrication and submittal review durations are what really set your mobilization dates — not the field activity itself.
Make design commitments in the weekly plan
The single highest-leverage move on a design-build job is to bring the design lead into the weekly work plan meeting and hold them to commitments the same way you hold a subcontractor foreman. Short-interval scheduling — the Last Planner discipline of making and tracking weekly commitments — works just as well on design deliverables as it does on drywall. Design work has constraints too: it needs input from other disciplines, it needs review capacity, it needs owner decisions. Treat "issue the interior package" like any other promised activity, track whether it hit, and when it misses, ask why and count it.
The payoff is that your percent-plan-complete number starts telling the truth about the whole job, not just the field. If your field crews are running at 90% PPC but your design commitments come in at 55%, you don't have a labor problem — you have a design-flow problem starving the field, and the number makes that impossible to hide. That single metric, tracked honestly across both teams, is worth more than any Gantt chart.
The trade-flow angle
Design-build lets you do something hard-bid jobs can't: you can sequence design to follow the same trade flow your crews will follow through the building. If your construction pull plan runs a location-based sequence — say framing, rough-in, and finishes chasing each other floor by floor or area by area — the design releases should march in that same order. Design the first area to construction-ready detail, get crews moving, and let the design team stay a controlled distance ahead of the field rather than trying to complete every drawing before anyone lifts a hammer.
This is where a visual, location-based look-ahead earns its keep. When you can see design releases and construction activities flowing through the same locations on one board, the gaps jump out — the area where the crew is about to catch up to the drawings, the floor where two trades and a design package all want the same week. Tools built for this kind of planning, LookAheadWall included, let you lay design deliverables and field work on the same timeline and connect the sequences, so the design-to-construction handoff is something you can actually see instead of something you reconstruct after it's already blown up.
A practical routine that works
None of this requires heroics. It requires a repeatable weekly rhythm:
- Roll the window forward every week. A look-ahead that's a month stale is just a wall decoration. Re-baseline the six weeks, drop completed work, pull in the new far edge.
- Walk every design-to-construction interface in the window. For each one, confirm the design will be released in time, the constraint is being worked, and the crew knows whether it's building off final or preliminary documents.
- Get design commitments in writing in the weekly meeting. Same room, same table, same accountability as the trades.
- Flag the interfaces where design and field are within a day or two of each other. Those are your fire hazards. Give them attention before they're on fire.
- Track PPC for both teams and talk about the misses. The reasons behind missed commitments are the most valuable data on the job. Late owner decisions, thin review capacity, upstream discipline holding up coordination — that's where next month's delays are hiding.
The bottom line
Design-build's whole promise is overlap — building while you design, compressing the schedule by running the two in parallel. But overlap only pays off if the interface between design and construction is managed tightly, and that interface moves week to week, faster than any master schedule tracks. That's the job the six-week look-ahead does. It's the place where a slipping design package, a stalled owner decision, or a procurement release that never went out becomes visible while there's still time to do something about it.
Keep the design activities on the same board as the field work. Make the handoffs explicit. Hold the design team to weekly commitments the same way you hold your subs. Do that consistently, and the look-ahead stops being paperwork and becomes the thing that actually lets design-build deliver on its speed — instead of quietly bleeding the schedule one stranded crew at a time.