Progressive Design-Build (PDB) is no longer a fringe delivery method. Per DBIA and FMI's market outlook, design-build is on track to represent close to half of U.S. construction spending by 2028, and PDB now accounts for roughly a third of design-build procurements - especially on projects with technical complexity, scope uncertainty, or volatile pricing. Owners like it because it brings the design-build team in early, shifts design risk, and lets them "progress" toward scope, schedule, and price together rather than locking in a lump sum on the front end.
But the schedule behind a PDB project is not just a traditional CPM schedule with the word "progressive" stapled to the front. The two-phase structure, the progressive pricing, and the collaborative design development create a specific set of milestones that have to be modeled - and a specific set of risks that, if ignored, quietly eat the float before anyone notices.
What Makes a PDB Schedule Different
In a traditional Design-Bid-Build, design finishes before construction starts, and the schedule is essentially linear. In a lump-sum or Best-Value Design-Build, the design-builder commits to a price at award against a defined owner scope. In PDB, neither of those things is true at the starting gun.
Under DBIA Document 544 (Progressive Design-Build Agreement, 2nd Edition, 2022), the project is contractually split into Phase 1 Services (preconstruction, design development, pricing) and Phase 2 Services (construction under a GMP or Lump Sum established partway through the job). That structural split has three big schedule implications:
- Design progression belongs on the schedule. In PDB, design is not a separate track managed by the architect on a spreadsheet - it's on the critical path of the overall project and needs to be logic-tied to procurement, permitting, and construction.
- There is an "off-ramp" built in. If the owner and design-builder can't agree on the GMP, the owner can terminate and take the design elsewhere. That possibility - however unlikely the parties think it is at kickoff - is a real schedule contingency.
- Phases overlap. Early work packages (long-lead procurement, site prep, enabling works) typically start before full design is complete. Overlap is the source of PDB's speed advantage and its biggest schedule risk.
The Milestones Your PDB Schedule Should Actually Show
A defensible PDB master schedule spans both phases and calls out, at minimum, the following:
Phase 1 - Preconstruction and Design
- Notice to Proceed, Phase 1 - contract execution and kickoff.
- Validation Phase Complete. DBIA emphasizes validation as the foundation of everything downstream: a realistic budget tied to a reasonable scope and an achievable schedule. Skipping or shortchanging validation is the single most common way PDB projects get into trouble.
- Preliminary Design / Schematic Design milestone (often ~30%).
- Design Development milestone (often ~60%, where the first serious GMP indication lands).
- Basis of Design documents finalized - this is the exhibit that gets attached to the Contract Price Amendment and defines what the GMP actually covers.
- Contract Price Amendment / GMP established. This is the pivot point. Until this milestone, there's no committed price; after it, the project behaves much more like a conventional GMP build.
- Off-Ramp decision window - explicitly show the period during which the owner could exercise termination rights if GMP negotiations fail.
- Early Work Package milestones - long-lead equipment procurement, enabling works, utility relocations, demolition. Each should have its own NTP, design-release, procurement, and delivery logic.
- Permit submittals and approvals - often multiple packages (site, foundation, shell, MEP, final). Realistic agency review durations, not aspirational ones.
Phase 2 - Construction
- Notice to Proceed, Phase 2 - post-GMP.
- 100% Construction Documents issued (may occur after Phase 2 NTP given overlap).
- Major procurement milestones - subcontract buyout, fabrication, delivery for structural, MEP, and long-lead packages.
- Mobilization.
- Interim Substantial Completion milestones - DBIA 544 explicitly contemplates different Substantial Completion dates for portions of the work (e.g., phased building turnovers, early operational areas). These need to be distinct activities with their own liquidated damages exposure if applicable.
- Overall Substantial Completion - with the grace period DBIA 544 builds in before liquidated damages kick in.
- Final Completion.
A scheduler who omits the design progression, the validation milestone, the GMP pivot, or the off-ramp window has built a schedule that looks like a conventional GMP job and will not hold up under forensic review if something goes sideways.
The Risks Worth Flagging on Every PDB Schedule
PDB's collaborative structure doesn't eliminate schedule risk - it relocates it. Here are the risks that most deserve a line in the risk register and, ideally, a modeled reflection in the schedule itself.
1. A Weak Validation Phase
Validation sets the scope, budget, and schedule assumptions the rest of the project rides on. If validation is rushed or if owner stakeholders aren't aligned (procurement, technical, legal, end users), every subsequent milestone is built on sand. DBIA calls out internal owner alignment as a make-or-break factor, and it's worth treating validation as a gate - not a checkbox.
2. Owner Decision Latency
In PDB, the owner is an active participant in design decisions, not a passive reviewer. When decisions are slow, the design can't progress, and when design can't progress, GMP can't be established. Schedule owner-review and decision durations explicitly; don't assume zero-day turnarounds.
3. GMP Negotiation Stall
The transition from Phase 1 to Phase 2 is where many PDB projects lose time. If the GMP comes in over budget, the parties renegotiate scope, and the schedule slips by weeks or months. Build a realistic GMP negotiation window into the schedule - and model a contingency scenario where it extends.
4. Off-Ramp Exposure
Everyone signs the contract intending to complete the project together. Off-ramps still get exercised. If it happens, the owner needs a plan for taking the design to bid, and the design-builder needs to understand what survives and what doesn't. The schedule should at least acknowledge the decision point exists.
5. Incomplete Design at Construction Start
This is the core tension of PDB. Overlap is the speed advantage, but starting construction against a 60–70% design means that change management has to be exceptional. Every design change after Phase 2 NTP has cost and schedule consequences that are harder to price than in a fully-designed-then-built model.
6. Long-Lead Procurement Against Maturing Design
Releasing a procurement package for a major piece of equipment at 50% design saves months - unless the design changes after the order is placed. Schedule the design-freeze date for each long-lead package explicitly, and treat it as a hard milestone.
7. Permit Path Assumptions
Progressive design means progressive permitting. Agencies may not be set up to review a design that evolves after submittal, and resubmittal cycles can compound. Don't collapse permitting into a single activity - break it down by package and by reviewing agency, with realistic durations.
8. Progressive Subcontractor Buyout
Traditional buyout assumes complete documents. PDB often requires progressive buyout - locking in trades before their scopes are fully defined. This is manageable with the right pricing structures (allowances, unit prices, open-book accounting), but the buyout sequence belongs in the schedule, not just the procurement log.
9. Float Ownership in a Two-Phase Schedule
Who owns float during Phase 1? Who owns it during Phase 2? Float erosion during design development is easy to ignore because there's no physical work visibly slipping, but it's real and it absolutely affects the Phase 2 completion date. Contract language on float ownership (a standard issue in any CPM-driven delivery) needs to be clear, and the schedule needs to report it consistently.
10. Stakeholder Churn
PDB projects often run long enough that owner personnel change mid-project. New stakeholders reopen closed decisions, which cascades into design rework, which cascades into schedule. This is a soft risk but a frequent one; a disciplined decision log and change-management protocol tied to the schedule helps.
Practical Habits That Make PDB Schedules Hold Up
A few things separate a PDB schedule that survives the first EAC update from one that doesn't:
- Build the integrated master schedule once, across both phases. Don't manage Phase 1 as a separate design schedule and Phase 2 as a construction schedule. The handoffs are where time gets lost.
- Tie the risk register to the schedule. Review both at each major milestone - validation complete, 30%, 60%, GMP establishment - and adjust. PDB risk registers are living documents.
- Document pricing milestones explicitly. Owners commonly expect pricing updates at 30/50/70/90% design. Each of those is a schedule milestone, not just a cost event.
- Use an Independent Cost Estimator (ICE) checkpoint. ICE reconciliations at each pricing milestone keep the design-builder's numbers honest and give the owner confidence to keep progressing - preventing the late-stage GMP surprise that stalls projects.
- Schedule the off-ramp. Even if nobody plans to use it, showing the decision window in the schedule forces clarity about what would need to be true for the project to continue.
The Bottom Line
PDB earns its speed and flexibility advantages honestly - but only when the schedule actually reflects how PDB works. A schedule that ignores validation, compresses design review durations, hides the GMP pivot, and treats overlap as free is a schedule that will underdeliver and invite disputes. One that models design progression, permit cycles, progressive buyout, the off-ramp window, and interim completion milestones is a schedule that can actually be managed - and defended if someone later asks what happened and why.
References
- DBIA, Design-Build Done Right® Universally Applicable Best Practices (2023 edition), with specific guidance on Progressive Design-Build.
- DBIA, Progressive Design-Build Done Right® Best Practices (2026 release).
- DBIA Document No. 544, Progressive Design-Build Agreement (2nd Edition, 2022), including the Instruction Sheet.
- DBIA, Progressive Design-Build: A Design-Build Done Right® Deeper Dive (Primer).
- FMI / DBIA industry outlook on design-build market share through 2028.
- Thaxton, R., and DBIA National Progressive Design-Build Committee materials on PDB procurement and contracting.