Contracts used on DB projects should be which of the following?

Contracts used on DB projects should be which of the following?

• A. Rigid and Punitive
• B. Lengthy and Opaque
• C. Fair and Collaborative
• D. Inconsistent and Negotiable

Answer: (C)

DB projects work best when contracts are fair and collaborative. This approach sets the tone for teamwork across the design and construction teams, aligns incentives, and enables open, timely decision-making. With a fair, collaborative contract, parties are more willing to share information, engage in value engineering, and solve problems together rather than blaming each other. That environment reduces disputes and change orders, distributes risk through shared responsibility, and keeps the project aligned with client goals, cost, and schedule. In contrast, rigid and punitive, or lengthy and opaque, or inconsistent and negotiable contracts tend to erode trust, slow decisions, and create confusion. So, fair and collaborative is the best fit for design-build, supporting better integration and project outcomes.

DB projects work best when contracts are fair and collaborative. This approach sets the tone for teamwork across the design and construction teams, aligns incentives, and enables open, timely decision-making. With a fair, collaborative contract, parties are more willing to share information, engage in value engineering, and solve problems together rather than blaming each other. That environment reduces disputes and change orders, distributes risk through shared responsibility, and keeps the project aligned with client goals, cost, and schedule. In contrast, rigid and punitive, or lengthy and opaque, or inconsistent and negotiable contracts tend to erode trust, slow decisions, and create confusion. So, fair and collaborative is the best fit for design-build, supporting better integration and project outcomes.