A pre-bid drawing review assumes something design-bid-build always gives you: one complete, issued-for-bid set, checked once, before every bidder prices off the same paper. Design-build — especially progressive design-build — doesn't work that way. There's no single moment where the whole building is drawn and nobody's broken ground yet. Instead there's a design-builder selected on qualifications, a rolling design process, and a guaranteed maximum price (GMP) that gets set in pieces as packages of drawings reach enough detail to price. By the time anyone would traditionally call a set "issued for bid," parts of it may already be under construction.
That doesn't mean document-level review becomes unnecessary on a design-build job. It means the review has to move to match the delivery method, because the packages are the new bid sets — smaller, more frequent, and each one still capable of hiding a cross-discipline conflict that a GMP gets priced against.
Why design-build doesn't have a bid set to review
In progressive design-build, the owner typically selects the design-build entity on qualifications before a baseline design exists, then works with that team through a preliminary design phase toward a GMP. Rather than one complete design handed off for competitive pricing, the design-builder develops a preliminary GMP at early milestones and refines it as design detail increases — commonly once a package reaches somewhere around 60% design development — at which point a formal GMP proposal gets submitted for that scope. Some delivery structures go further and authorize multiple GMPs on a rolling basis, so earlier packages (sitework, foundations, structural steel) can be priced and released to construction while later packages (interiors, low-voltage, finishes) are still being designed.
That structure is the entire point of design-build for an owner chasing schedule — construction starts on the packages that are ready while design keeps moving on the rest. But it also means the traditional trigger for a pre-bid review (a complete set, issued, with a bid date on the calendar) never actually happens. There's no single date where "the drawings" exist in finished form, because they don't; they exist in a sequence of packages, each maturing on its own timeline toward its own GMP.
The absence of a bid set isn't the absence of a pricing moment — it's a lot more of them. Every package that gets priced into a GMP is functionally a mini bid set: a document snapshot that a dollar figure gets attached to, at a specific point in time, before construction starts on that scope.
Where the review moment actually lands
If there's no single bid date, the review has to attach to something else: the point just before each package's GMP gets finalized. That's the design-build equivalent of "pre-bid" — the last window where a conflict is still a design change instead of a change order, because the price for that package hasn't been locked yet and the work hasn't started.
Concretely, that means:
Review each package as it approaches its GMP milestone, not the project once at the end. A structural and foundations package reaching 60% design development gets checked against the mechanical and electrical packages that touch the same footprint, even if those later packages are still in schematic design. The review can't wait for a complete set that will never exist as one document at one moment.
Weight the review toward interfaces between packages, not just within one. The conflicts that matter most on a phased release aren't errors inside a single package — they're places where an early, already-priced package makes an assumption that a later, still-developing package quietly contradicts. A structural package locked at 60% DD that assumes a mechanical penetration pattern the MEP team hasn't actually finalized yet is the design-build version of the classic cross-discipline clash, just spread across two different design timelines instead of two sheets in the same set.
Re-check a package against later ones as they mature. Because earlier packages get priced and built before later ones are finished, a conflict can be introduced after the fact — a later package's design decision contradicts an earlier package that's already under construction. On a traditional bid set, that kind of change gets caught by re-checking the full set against a bulletin or addendum before it's issued. On a design-build job, the same discipline applies per package, on the design-build team's own schedule rather than a formal addendum process.
Why this is harder to catch without a review, not easier
It's tempting to assume design-build needs less outside document review, since the design-builder is a single entity holding both the design and construction risk, with an obvious incentive to coordinate its own drawings before pricing them. That incentive is real, and it's a genuine advantage of the delivery method — collaborative input from the construction side earlier in design does limit some categories of constructability problems that show up on design-bid-build jobs, where the designer of record never had a contractor at the table during design.
But that same structure raises a different risk: an owner reviewing a rolling sequence of packages, each priced by the same team that's asking to be paid for it, has less independent visibility into cross-discipline conflicts than an owner reviewing one complete bid set from an architect of record with no stake in the construction price. The fast-tracked and design-build math on where change orders concentrate doesn't disappear just because the delivery method is different — it shows up in different places, spread across packages instead of concentrated in a single set, which makes it easier to miss rather than harder.
The timing argument for pre-bid review holds just as well here, just relocated. The core logic — that a conflict is far cheaper to fix before a price is attached to it than after — doesn't change because the price gets attached in installments instead of all at once. A structural-versus-mechanical conflict caught before a package's GMP is a design revision. The same conflict caught after that package is under construction is a change order against an already-signed price, exactly like it would be on a traditional set — the only difference is which package it's attached to and how many other packages have already been locked around it.
Key takeaways
- Progressive design-build replaces one issued-for-bid set with a sequence of packages, each priced into a GMP as it reaches enough design detail — commonly around 60% design development.
- Because there's no single bid date, the pre-bid review moment has to attach to each package's GMP milestone instead of one project-wide date.
- The highest-value review target on a phased release is the interface between an already-priced package and a still-developing one, not just conflicts inside a single package.
- A single design-build entity holding both design and construction risk reduces some constructability problems, but it also reduces independent visibility into cross-discipline conflicts compared to a bid set from an unaffiliated architect of record.
- The core timing argument for review doesn't change: a conflict caught before a package's GMP is a design revision, the same conflict caught after is a change order.
Frequently Asked Questions
Does a design-build project need a pre-bid drawing review if there's no bid set?
It needs the same kind of review, timed differently. Instead of one review before a single bid date, each package gets reviewed as it approaches its own GMP milestone — the point where a price is about to get attached to that scope and construction is about to start on it.
Isn't the design-builder already coordinating the drawings since one team owns both design and construction?
The design-builder has a strong incentive to coordinate its own packages, and that's a real advantage of the delivery method. But that same team is also the one proposing the GMP, which means an owner has less independent visibility into cross-discipline conflicts than they would from a bid set produced by an architect of record with no stake in the construction price.
What's the highest-risk conflict type on a phased, package-based release?
Conflicts at the interface between packages on different timelines — an early package that's already priced and under construction making an assumption that a later, still-developing package quietly contradicts. Those are harder to catch than conflicts inside a single package, because no one document shows both sides of the disagreement at once.
How is reviewing a design-build package different from reviewing a full bid set?
The mechanics are the same — checking one discipline's sheets against every other discipline's, and specs against drawings, for contradictions. What changes is the target: instead of one complete set checked once, it's a rolling series of narrower packages, each checked against both the packages already priced and the packages still in progress.
Does catching a conflict before a GMP milestone actually save money compared to catching it later?
Yes, for the same reason it does on a traditional bid set. A conflict caught before a package's GMP is finalized is a design revision with no signed price attached yet. The identical conflict caught after that package is under construction is a change order against a price the design-builder has already committed to, plus the cost of undoing whatever's already been built around it.