The design-build project delivery method is when the design-builder (typically the contractor) is responsible for both the design and construction of the project. Thus, the responsibility for both the design and construction falls under the same umbrella and, naturally, carries more risk. The discussion below demonstrates risk involved in the design-build project delivery method, particularly in the government contracting arena:
Design-build contracts are common for construction, renovations, and repair projects, where the government provides the contractor with its requirements, but the contractor is free to exercise its ingenuity in achieving that objective or standard of performance and selecting the means to do so. It is not uncommon for issues to arise in design-build contracts. One of the more common issues is when the contract describes a certain requirement, but later during the design process, the contractor will submit in the 35% or 100% design submittal with a lower requirement. The government will unknowingly approve that design, not realizing the contractor may have “slipped in” or made an error on one of the requirements; thus, the approved 100% design has a lower requirement as compared to the contract. In these situations, we have found that the government is justified in demanding the contractor provide the requirements specified in the RFP and resulting contract.
Thus, our long-held rule has been that the government cannot properly be blamed for approving the design when the contractor failed to inform the government that its design deviated from Task Order minimum requirements.
Appeals of – Meltech Corporation, Inc., ASBCA No. 61766, 2025 WL 2166133 (ASBCA 2025) (internal citations omitted).
What about the opposite? If the government approves a design that contains components of a HIGHER, not lower, quality?
In a recent appeal with the Armed Services Board of Contracts Appeal, the design-build contractor made a mistake during the design process where it was giving the government a higher quality than required of it in the RFP with the design criteria for the project. (It is typically the opposite where the design-builder gives the government a lower quality than required of it in the RFP.) The design-build contractor sought to substitute the higher quality material for the material required by the RFP. Through the substitution, the government wanted a credit claiming the design-builder should be bound by the 100% design that the government approved with the higher quality material. The Board, however, did not see it the unfair way the government saw it:
As we have held that the government does not waive RFP requirements when it unwittingly approves a lesser quality design, a contractor’s reasonable mistake should not require it to provide materials above and beyond the contracts requirements. This is an example of a contractor’s mistake during the design-build phase, in which the contractor ultimately provided a finished material at the quality specified in the RFP/Design Criteria. There was no savings by [the design-builder] nor a loss to the government. The equitable adjustment should not increase or decrease the contractors’ loss at the government’s expense. Moreover, the government presented no evidence to the Board that it incurred any costs of significance associated with its review of [the design-builder’s] submittals on these issues. Accordingly, the government has failed to carry its burden of establishing that it is due a deductive credit….
Appeals of – Meltech Corporation, Inc., ASBCA No. 61766, 2025 WL 2166133 (ASBCA 2025) (internal citations omitted).
Thus, while the design-builder cannot skirt its responsibilities by providing a lesser quality than required of it. The government can’t take advantage of the design-builder’s mistake with a higher quality when the higher quality exceeds the benefit of the bargain.
Please contact David Adelstein at dadelstein@gmail.com or (954) 361-4720 if you have questions or would like more information regarding this article. You can follow David Adelstein on Twitter @DavidAdelstein1.