Over 25 years of delivering Civic & Justice projects across the country, I’ve watched Design-Build transition from an alternative delivery model into the industry standard. The benefits that drove this adoption are well-documented: faster delivery, improved schedule certainty, single-point accountability, and reduced owner risk.

Yet, after working alongside hundreds of public owners, architects, operators, and trade partners, I’ve realized we are missing the larger point.

The contract isn’t what makes Design-Build successful. The collaboration is.

The contract merely creates the opportunity. Success is determined by how effectively the Owner, Architect, and Contractor use that structure to solve complex problems together.

Too often, Design-Build conversations remain trapped in legal provisions, procurement strategies, and risk allocation. Owners understandably want to know who is responsible if something goes wrong. But when Design-Build is treated strictly as a contracting mechanism, teams miss its greatest value: creating an environment where better early information produces far better long-term decisions.

 

The Gap Between “Contractual” and “True” Collaboration

There are two distinct ways teams execute Design-Build:

  1. Transactional Design-Build: The contractor’s involvement is limited to periodic milestone cost checks and listening quietly in design meetings. The architect designs; the builder prices. It meets the legal definition of the delivery method, but it functions like traditional Design-Bid-Build.
  2. Collaborative Design-Build: The builder and key trade partners sit alongside the owner and architect from day one—evaluating real-time material volatility, discussing operational impacts, and pressure-testing decisions while options are still open.

The difference isn’t the contract; it’s the outcome.

In today’s market, material pricing, labor availability, and lead times shift rapidly. Specialty contractors live in that market every day. When brought in early, their insight transforms cost discussions from a narrow look at line items to a true evaluation of total value, long-term operations, and risk mitigation.

 

What True Early Involvement Looks Like in Practice

When you expand the conversation to include trade partners, operators, and end-users early, you unlock solutions no single discipline could design in isolation.

  • Rethinking Systems Delivery: On a recent detention project, early collaboration with a security electronics trade partner led to a pre-assembly strategy. Equipment was coordinated, integrated, and tested in a controlled shop environment before hitting the job site—improving quality control, speeding up installation, and lowering labor risk. That solution would never have surfaced under a standard bid process.
  • Rethinking Facility Configuration: On another facility, an early operational review focused on staffing efficiency evolved into a complete redesign of the housing layout. By bringing the owner, architect, and contractor together to evaluate operational flows, the team eliminated an entire floor tier. The result was reduced square footage, lower overall construction cost, and a safer, more efficient operational model for facility staff.

Customization Is the New Complexity

Public architecture is undergoing a seismic shift. Communities are no longer just replacing aging courthouses, detention centers, or behavioral health facilities—they are fundamentally rethinking them.

Facilities built 30 years ago prioritized capacity and containment. Today’s civic leaders face a much more complex mandate: balancing security with treatment, accountability with rehabilitation, staff wellness with operational efficiency, and fiscal responsibility with community expectations.

There is no off-the-shelf prototype for these challenges. What industry professionals label as “complexity” in civic projects is actually customization. Every county, city, and judicial district operates under distinct political realities, staffing constraints, and community priorities.

You cannot solve those challenges with a contract clause. You solve them with people.

 

Moving Beyond the Contract

Design-Build was built to break down silos, yet too many teams still operate inside them.

As public infrastructure demands become more nuanced, our industry needs to spend less time talking about how the contract manages risk and more time leveraging the framework to solve problems.

The contract is what made Design-Build popular. Collaboration is what makes it work.