On a traditional bid-build job, you get a full set of construction documents before you ever break ground. You know what the building is. Your job as a superintendent is to sequence and execute a design somebody else finished months ago. Design-build tears that comfort away. Now design and construction run at the same time, you're pouring footings while the third floor is still a set of loose sketches, and the thing that can wreck your week isn't a late trade. It's a late drawing.
That's the whole reason a six-week look-ahead earns its keep on design-build work in a way it never quite does on a fully-designed job. The extra horizon isn't about seeing more construction. It's about seeing the design decisions and information releases you need before the crew shows up expecting to build something nobody has drawn yet.
Why three weeks isn't enough here
On a conventional job I'll happily run a three-week look-ahead. The design is done, procurement is mostly buttoned up, and three weeks is plenty of runway to clear constraints and confirm crew loading. Design-build breaks that math for one simple reason: the lead time on a decision is longer than the lead time on a task.
Say the framing crew hits an exterior wall in five weeks. In bid-build, you already have the wall section, the window type, the header schedule. In design-build, that same wall might be waiting on a curtainwall system selection the owner hasn't approved, which the architect can't finalize until they get a shop drawing back, which the fabricator won't produce until they have a signed contract. That chain is easily four to six weeks long. If your planning window is three weeks, you find out about the missing decision the week the crew is standing at the wall. Now it's a change, a delay, and a crew you're paying to sweep floors.
Six weeks lets you catch the decision while there's still time to make it. Anything shorter and design-build will eat you alive on the information side.
Put design work on the schedule, not next to it
The single most common mistake I see on design-build look-aheads is treating them as a construction-only tool and keeping design status in someone's head or a separate spreadsheet. Design deliverables are activities. Give them a row.
"Issue Level 2 structural for construction," "Owner selects storefront system," "Return approved MEP coordination drawings" — these belong right in the look-ahead alongside "form and pour SOG pour 3." When a design task and a construction task sit on the same wall, the gap between them becomes obvious to everyone in the room. A drawing due Friday that feeds framing that starts Monday has zero float, and you want the designer staring at that the same way you'd stare at a crane pick with a tight window.
A practical rule of thumb: for any construction activity in weeks one through three, walk the chain backward and confirm the design that enables it is either done or has a hard release date inside the window. If you can't name the drawing and the date, that activity isn't ready to plan — it's a hope.
Track information as a constraint, because it's the one that gets you
Every look-ahead worth running does a make-ready pass: for each upcoming activity, what has to be true before it can start? Material on site, crew available, prior trade complete, area accessible, inspection passed. On design-build you add a category most jobs underweight — information.
Get specific about the types, because they behave differently:
- Drawing releases. Not "drawings coming soon" — a package name and an issued-for-construction date. Track the date it's promised and the date you actually need it, and watch the gap.
- Owner and design decisions. Finishes, fixtures, systems, elevations. These stall more work than any late sub. A selection that seems small — say, a change from a 2-hour to a 3-hour rated assembly — can ripple into framing, MEP, and door hardware.
- Shop drawing and submittal turnaround. In design-build the loop is faster but it's still a loop. Track review as an activity with a real duration; "architect reviewing" for two weeks with no end date is how you lose a month.
- RFI responses. Field questions need design answers, and unanswered they become constraints. Put a response-needed-by date on every open RFI that gates work inside the six weeks and review that list every single planning meeting.
Here's the discipline that matters: an information constraint you've written down but never chased is worse than useless, because it makes you feel covered. Assign an owner and a due date to each one, and clear them the same way you'd chase a late delivery.
Procure before the design is finished — deliberately
Design-build almost always means committing to long-lead items before the drawings that describe them are complete. Structural steel, switchgear, elevators, curtainwall, generators, chillers — the lead times run twelve to thirty weeks or more, and you cannot wait for a finished design to order them.
The move is to identify the minimum design needed to release procurement, not the complete design. Steel doesn't need the interior partition layout finalized; it needs the frame, connections, and loads. That's a much smaller design deliverable, and it should be a flagged, high-priority item on your six-week look-ahead: "structural design freeze sufficient for mill order."
Walk the long-lead list backward from need-on-site date, through fabrication and submittal review, to the design freeze that unlocks the order. That backward date is often inside your six-week window even when the material won't arrive for months — which is exactly why the six-week horizon fits design-build. It catches the procurement trigger, not the delivery.
Get the designer in the room
A construction look-ahead meeting with no design presence is a design-build meeting missing half the team. On a bid-build job you're coordinating trades against each other. Here you're also coordinating the designer's output against the crew's input, and that only works if the person producing drawings hears, in plain terms, what's about to be missing.
Run the meeting so design commits the way a trade commits. A framer says "wall 4 is closed by Thursday." A designer should be able to say "Level 3 mechanical is issued Wednesday." Those are the same kind of promise, and you should track both the same way — including whether they landed. When you start measuring how often design commitments come in on time, you learn very quickly where the real bottleneck lives, and it's often upstream of anything the trades control.
One caution from experience: design-build's "we're all one team" spirit tempts everyone to resolve things by hallway conversation and never write it down. Fast decisions are the whole point — but document the ones that change scope or sequence. Six months later when there's a dispute about who decided what, the look-ahead history and a short written confirmation are worth more than anyone's memory.
Fast-track raises the stakes on all of it
Most design-build jobs are also fast-tracked — foundations released while the superstructure is still being designed, the shell out for permit before interiors are done. That compresses everything and it means different building systems live at different design maturity at the same moment. Steel might be 90% done while interiors are 30%. Your look-ahead has to hold those parallel streams without pretending they're synchronized.
Two habits keep fast-track from becoming chaos. First, protect a real buffer at every design-to-construction handoff — a day or two minimum between "drawing issued" and "crew builds from it," so someone can actually read the thing, coordinate it against the field, and catch the conflict before it's built. Skip that buffer and you'll be demoing new work. Second, look for the design conflicts early: when two systems are being designed in parallel, they will clash somewhere — a duct through a beam, a fixture in a shear wall — and the six-week window is where you want that fight to happen, on paper, not in the field.
A quick weekly checklist
Before you call a design-build look-ahead complete, run down this list:
- Does every construction activity in the next three weeks have its enabling design confirmed — drawing named, release date inside the window?
- Is every open RFI and pending decision that gates near-term work on the board with an owner and a needed-by date?
- Did design make specific, dated commitments this week, and did we check last week's against what actually landed?
- For every long-lead item, is the procurement trigger — the design freeze that lets us order — visible and on track?
- Is there a real buffer between each drawing release and the crew that builds from it?
- Are the parallel design streams reconciled where they physically intersect in the next six weeks?
Miss any of those and you've found this week's most likely delay before it costs you.
Where the tools fit
None of this depends on software — plenty of good superintendents have run design-build off a whiteboard and a sharp memory. But the coordination gets heavy fast when design and construction share a plan, and a visual, location-based look-ahead tool earns its place by making the design-to-construction dependencies impossible to ignore. When a tool like LookAheadWall lets you put a drawing release on the same wall as the framing it feeds, link them, and give the designer a live view of what the field is waiting on, the gaps stop hiding in someone's inbox. The value isn't the feature list — it's that everyone, designer and crew alike, is reading the same six weeks.
The bottom line
Design-build doesn't fail because crews are slow. It fails at the seam between design and construction — a decision made too late, a drawing that arrived a week after the crew, a long-lead item nobody ordered because the design "wasn't ready." The six-week look-ahead exists to work that seam: long enough to catch the decisions, structured enough to treat design as real work with real deadlines, and honest enough to show you the information you're missing while there's still time to go get it. Run it that way and the seam holds. Ignore it and it's the first thing that tears.