DBIA Liberty Region Conference 2026: check the teaming assumptions before pricing a pursuit
Prepare a design-build teaming review from the DBIA Liberty conference context, recording design scope, pursuit costs, estimate basis and decision owners.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 2 min
- Published
On this page
A conference contact is not a teaming agreement. Before a design-builder prices a pursuit with a designer, document the assumed design scope, maturity, decision authority and pursuit cost responsibility. If those boundaries remain open, present the estimate as conditional and send the commercial issues to the people authorized to resolve them.
The DBIA Liberty event listing places its past September 15–16, 2026 conference in Breinigsville, Pennsylvania. Its regional audience includes Upstate New York. Separately, DBIA's May 2026 teaming guidance announcement emphasizes early alignment and team responsibilities. The announcement does not establish that the conference covered that guidance. DBIA's best-practices overview organizes general guidance around procurement, contracting and execution; applicability depends on the project. This is independent analysis, not a conference recap.
Create an alignment record before pricing
| Decision | Evidence to capture | Escalation |
|---|---|---|
| Design scope | Disciplines, deliverables, interfaces and exclusions | Design lead confirms who does what |
| Estimate basis | Issued documents, allowances, pricing assumptions and revision | Chief estimator approves basis |
| Pursuit cost | Who authorizes work and tracks proposal expense? | Commercial lead resolves authority |
| Design maturity | What is drawn, implied or still owner-selected? | Designer and owner decision lead identify gaps |
| Communications | Who sends questions and approves commitments? | Name a single decision owner and backup |
| Changes and exclusions | Which boundary or later change remains unresolved? | Counsel and authorized commercial leads review allocation |
Use the matrix to expose commercial questions, not to write contract clauses. Preserve each party's assumptions and the unresolved decisions alongside the estimate. The team's counsel and design lead should review risk allocation and the actual agreement. A contact's willingness to discuss a pursuit is not authority to commit either firm.
Worked boundary: design-build building services
For a fictional design-build renovation, the design-builder expects the designer's fee to include coordination of existing services. The designer's initial scope covers new systems but does not describe investigation of concealed services. The estimator must not assume both descriptions mean the same work. Record the existing-services investigation as open, ask the designer for a defined deliverable and fee assumption, and ask operations how access limitations affect investigation. The commercial lead determines who can authorize additional pursuit work.
If the owner has not decided the extent of renovation, identify the decision and its effect on scope and schedule. Carry a documented assumption or alternative for internal approval; do not present unresolved investigation as a committed price. Record who approves any change to the basis after the team's agreement is signed.
Connect the agreement to the estimate
The delivery-method comparison shows why design-build changes estimating interfaces. The incomplete-drawings guide helps distinguish documented design from assumed intent. If a GMP is contemplated, the GMP basis review connects outstanding owner decisions to the proposed ceiling. None of those resources substitutes for project-specific legal or design review. The conference selection guide notes the event's out-of-state location.
Related reading
Hard-bid vs CMAR vs design-build: estimating workflows for GC estimators
Compare how estimating unfolds under hard-bid (DBB), CMAR/GMP, and design-build (solicitation, scope, leveling, carry, and closeout) with checkpoints and checklists for each method.

Design intent is what estimators price when the drawings stop talking
Review implied assemblies and ambiguous interfaces, document the source and decision owner, and keep assumptions visible even when the drawing set appears complete.

Guaranteed maximum price: review the estimate basis before agreeing to the ceiling
A guaranteed maximum price needs a reviewable scope and cost basis. A GC checklist for reconciling documents, trade coverage, allowances and unresolved design.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.