Design Assist, Delegated Design, and Design-Build: Are We All Talking About the Same Thing?
What happens when project teams use the same terminology but have different expectations about responsibilities, processes, and outcomes?
In this episode of What a Week, Dave Stutzman, Steve Gantner, and Elias Saltz explore the distinctions between design assist, delegated design, and component-level design-build, following a CSI panel discussion focused on ornamental stair construction. The conversation examines how different interpretations of these approaches can affect competitive bidding, subcontractor involvement, design responsibility, and the potential for costly redesign.
Through real-world examples involving ornamental stairs, curtain walls, and structural glass, the discussion highlights the importance of defining expectations early, particularly when balancing aesthetics, performance requirements, fabrication expertise, and procurement strategies.
The central takeaway: These terms alone don't establish a shared understanding. Project teams must clearly define the intended process, responsibilities, and deliverables to protect design intent and avoid unnecessary risk, confusion, and rework.
Design assist, delegated design, and component-level design-build are often interpreted differently across the construction industry. Without a shared understanding, project teams risk misaligned expectations regarding design responsibility, procurement, and deliverables.
Design assist does not necessarily guarantee that the participating subcontractor will be awarded the work. Competitive bidding can introduce complications when the selected contractor uses different fabrication methods or cannot execute the original design approach.
Design assist should be clearly defined as a collaborative process, with established expectations for participation, compensation, design reviews, and deliverables. Early clarity can help prevent redesign and lost efficiencies.
Architects, contractors, and specialty fabricators must coordinate both technical performance and aesthetic intent. Their involvement and responsibilities should be established before design development progresses.
When subcontractors contribute proprietary expertise without assurance of future work, questions arise about compensation, information sharing, and the potential for additional design costs. Thoughtful procurement strategies can help protect the value of collaboration.
The terminology doesn't define the process. Successful collaboration depends on establishing a common understanding of responsibilities, expectations, and outcomes before work begins.
Make certain that we understand what is the process, what is the end result, how is this actually going to be used, whether it's design assist, delegated design, or design build.