Progressive Design Build: 7 Decisions for Two-Phase Construction Delivery
Progressive design build is a project delivery approach that brings a design-builder into a project before the final design and construction price are established. The owner and design-builder collaborate during an early development phase, then negotiate the terms for construction. This approach can suit projects with uncertain site conditions or complex systems, but it requires clear commercial rules, open cost discussions, and a credible alternative if the parties cannot agree.
This guide explains seven decisions that make progressive design build easier to manage, including procurement, scope development, commercial controls, communication, and closeout. The examples are illustrative, not claims about a specific client’s project.
Agree on responsibilities, decision rights, price assumptions, and evidence at every handoff. A good delivery method cannot compensate for unclear scope or missing approvals.
When does progressive design build make sense?
Owners should begin by asking how certain they are about scope and design, how soon construction expertise is needed, and which risks they can manage. The best route may differ between a repeatable office fit-out and a treatment facility with difficult operating constraints.
Moreover, the contract structure matters just as much as the project label. The agreement should make the parties’ responsibilities, review stages, and payment rules understandable to the people who will administer them.
1. Choose the team for capability, not only early price
Evaluate the design-builder’s experience, key people, construction knowledge, collaborative practices, and capacity. Early selection should create a team capable of shaping the solution with the owner.
Example: A water utility selecting a team for treatment plant upgrades needs process design and live-facility experience, not simply the lowest preliminary design fee.
Documents and decisions to retain
Keep the relevant drawings, contract clauses, correspondence, estimates, and meeting decisions tied to a unique project reference. Also record who approved the decision and when it took effect. If a choice affects cost or schedule, identify the previous approved baseline so staff can explain the difference.
How to test the project workflow
Ask a project manager to locate the latest version without searching multiple private inboxes. Next, have a second reviewer trace the decision from its initial request through approval and any change in cost. The process should make it clear which action comes next and who owns it. Otherwise, even an accurate document may fail to reach the person who needs it.
In addition, discuss the consequences of a late change at this stage. The team should distinguish ordinary coordination from an instruction that changes the contract. A written exception path helps prevent disputes while keeping work moving.
2. Define phase-one services and deliverables
Set out the required investigations, design progress, estimating, scheduling, procurement planning, and decision points. Agree how the team will be paid for this development work.
Example: A site survey and utility conflict review might be essential before anyone can responsibly price the final construction scope.
Documents and decisions to retain
Keep the relevant drawings, contract clauses, correspondence, estimates, and meeting decisions tied to a unique project reference. Also record who approved the decision and when it took effect. If a choice affects cost or schedule, identify the previous approved baseline so staff can explain the difference.
How to test the project workflow
Ask a project manager to locate the latest version without searching multiple private inboxes. Next, have a second reviewer trace the decision from its initial request through approval and any change in cost. The process should make it clear which action comes next and who owns it. Otherwise, even an accurate document may fail to reach the person who needs it.
In addition, discuss the consequences of a late change at this stage. The team should distinguish ordinary coordination from an instruction that changes the contract. A written exception path helps prevent disputes while keeping work moving.
3. Use an auditable open-book estimate
Agree what the owner can inspect, including subcontractor quotes, cost assumptions, labor estimates, contingencies, and allowances. Also define how the team will update costs as design decisions change.
Example: If a proposed pump specification raises cost, the owner should see the new quote and understand whether other elements can offset it.
Documents and decisions to retain
Keep the relevant drawings, contract clauses, correspondence, estimates, and meeting decisions tied to a unique project reference. Also record who approved the decision and when it took effect. If a choice affects cost or schedule, identify the previous approved baseline so staff can explain the difference.
How to test the project workflow
Ask a project manager to locate the latest version without searching multiple private inboxes. Next, have a second reviewer trace the decision from its initial request through approval and any change in cost. The process should make it clear which action comes next and who owns it. Otherwise, even an accurate document may fail to reach the person who needs it.
In addition, discuss the consequences of a late change at this stage. The team should distinguish ordinary coordination from an instruction that changes the contract. A written exception path helps prevent disputes while keeping work moving.
4. Advance design and constructability together
Bring operators, designers, contractors, and key specialty trades into decisions while they can still influence the solution. Document options with lifecycle cost, maintainability, and schedule effects.
Example: A utility may choose a slightly more expensive pipe arrangement that reduces shutdown time and improves future maintenance access.
Documents and decisions to retain
Keep the relevant drawings, contract clauses, correspondence, estimates, and meeting decisions tied to a unique project reference. Also record who approved the decision and when it took effect. If a choice affects cost or schedule, identify the previous approved baseline so staff can explain the difference.
How to test the project workflow
Ask a project manager to locate the latest version without searching multiple private inboxes. Next, have a second reviewer trace the decision from its initial request through approval and any change in cost. The process should make it clear which action comes next and who owns it. Otherwise, even an accurate document may fail to reach the person who needs it.
In addition, discuss the consequences of a late change at this stage. The team should distinguish ordinary coordination from an instruction that changes the contract. A written exception path helps prevent disputes while keeping work moving.
5. Agree on the off-ramp before negotiating construction
The contract should explain what happens if scope, risk allocation, or phase-two price cannot be agreed. Clarify rights to use phase-one design documents and the payment consequences.
Example: If the open-book estimate exceeds the approved budget, the owner should know whether it can seek a different construction route and what deliverables it can retain.
Documents and decisions to retain
Keep the relevant drawings, contract clauses, correspondence, estimates, and meeting decisions tied to a unique project reference. Also record who approved the decision and when it took effect. If a choice affects cost or schedule, identify the previous approved baseline so staff can explain the difference.
How to test the project workflow
Ask a project manager to locate the latest version without searching multiple private inboxes. Next, have a second reviewer trace the decision from its initial request through approval and any change in cost. The process should make it clear which action comes next and who owns it. Otherwise, even an accurate document may fail to reach the person who needs it.
In addition, discuss the consequences of a late change at this stage. The team should distinguish ordinary coordination from an instruction that changes the contract. A written exception path helps prevent disputes while keeping work moving.
6. Negotiate phase-two price, risk, and schedule
Only after sufficient definition should the parties agree on a guaranteed maximum price or other commercial arrangement, the contingency rules, procurement commitments, and the construction schedule.
Example: A contractor may propose a contingency for ground conditions. The owner needs to know what risks it covers, who controls its use, and how unused funds are handled.
Documents and decisions to retain
Keep the relevant drawings, contract clauses, correspondence, estimates, and meeting decisions tied to a unique project reference. Also record who approved the decision and when it took effect. If a choice affects cost or schedule, identify the previous approved baseline so staff can explain the difference.
How to test the project workflow
Ask a project manager to locate the latest version without searching multiple private inboxes. Next, have a second reviewer trace the decision from its initial request through approval and any change in cost. The process should make it clear which action comes next and who owns it. Otherwise, even an accurate document may fail to reach the person who needs it.
In addition, discuss the consequences of a late change at this stage. The team should distinguish ordinary coordination from an instruction that changes the contract. A written exception path helps prevent disputes while keeping work moving.
7. Control changes while design continues
Track owner decisions, design evolution, subcontractor commitments, schedule implications, and approved changes against the agreed baseline. Do not treat every design refinement as a cost-free clarification.
Example: If treatment capacity increases during detailed design, the team should assess equipment, structural, electrical, and commissioning impacts together.
Documents and decisions to retain
Keep the relevant drawings, contract clauses, correspondence, estimates, and meeting decisions tied to a unique project reference. Also record who approved the decision and when it took effect. If a choice affects cost or schedule, identify the previous approved baseline so staff can explain the difference.
How to test the project workflow
Ask a project manager to locate the latest version without searching multiple private inboxes. Next, have a second reviewer trace the decision from its initial request through approval and any change in cost. The process should make it clear which action comes next and who owns it. Otherwise, even an accurate document may fail to reach the person who needs it.
In addition, discuss the consequences of a late change at this stage. The team should distinguish ordinary coordination from an instruction that changes the contract. A written exception path helps prevent disputes while keeping work moving.
Choosing the delivery approach
In practice, the owner’s experience, the market’s capacity, the complexity of the site, and the available design information will influence the choice. Design bid build normally places a completed design before construction bidding. By contrast, progressive design build brings construction expertise into development earlier and generally includes a later commercial agreement for construction. Neither method guarantees a lower price or faster delivery.
The relevant professional institute offers background on contract and delivery practice. The second construction industry reference provides another perspective on project delivery choices. Owners should confirm local procurement law, public-sector obligations, insurance, and contract terms with the appropriate professionals.
Teams can also benefit from a shared software register for scope, approvals, schedule revisions, risks, and cost changes. Anomoz’s article about related construction project controls explains why consistent records matter.
Practical implementation checklist
- Define project purpose, operating constraints, budget, and target dates.
- Choose decision-makers and document their authority.
- Agree on design reviews, cost information, and revision control.
- Set rules for requests, clarifications, changes, and approvals.
- Track schedule assumptions and important dependencies.
- Review risks before contract commitments.
- Keep a single register of issues, decisions, and current documents.
- Verify closeout evidence and operational handover.
Common mistakes to avoid
One common mistake is treating a tentative estimate as a firm commitment without documenting its assumptions. Another is relying on verbal approvals when a change affects several disciplines. Also, teams can misread a status report when it reflects an outdated drawing or contract version.
Instead, give each decision a named owner and a documented date. Keep financial values linked to their source and include the effect on schedule and operations where appropriate. Regular reviews should focus on unresolved decisions, not only the amount of work completed.
Frequently Asked Questions
Does progressive design build guarantee lower costs?
No. Cost outcomes depend on scope, market conditions, risk allocation, contract management, and the quality of information available.
What records should project software retain?
Keep current contract documents, revision history, approvals, requests for information, decisions, schedule updates, and supporting cost evidence.
Who should approve project changes?
The contract should identify authorized roles and any monetary or schedule limits. Staff should not assume a verbal request is formal approval.
How can teams reduce handoff disputes?
Use consistent records, defined response times, a named decision owner, and a clear process for escalating unresolved questions.
Conclusion
Progressive design build works best when owners, designers, contractors, and project managers understand who decides what and when. Use these seven decisions to review procurement, contract controls, execution, and handover before problems become expensive.
