Next, what are the different types of risk? I divide them into two main categories: construction and contractual. Construction risks relate to the project's site and execution, while contractual risks are those allocated (or sometimes unfairly imposed) by contracts.
In my view, these traditional assumptions are neither complete nor accurate (nor for that matter very helpful). For example, I've seen (and prepared) conventional design-bid-build contracts that assigned an enormous amount of construction and contractual risk to the contractor. I've also seen contracts where the owner, in the interest of more competitive bids and a more constructive relationship, rationally assigned risks and in many instances retained them.
Similarly, the so-called "CM at risk" contract doesn't necessarily place the CM at much financial risk if the target numbers were fat from the outset. Finally, some owners plunge headlong into the use of design/build because it's the sexy delivery system of the 1990s. In doing so, they often blindly or naively assume enormous risk by not recognizing that they need to provide or obtain appropriate design and performance criteria. Thus, the traditional paradigms don't really hold up because the analyses are superficial and based on generalizations and assumptions.
Unfortunately, there is no software program into which an owner can enter priorities and parameters and receive as output arecommendation for an ideal delivery system. Among the prerequisites that the owner--the ultimate beneficiary of the project--should consider are:
Is the owner experienced, or will it require a good bit of outside
advice?
Multi-prime, design/build, and turnkey projects actually require the
greatest
experience/ sophistication/advice, while BOOT is at the other end of
the scale.
Internal staff capabilities
What are the owner's staff capabilities? Multi-prime and traditional
require a
great deal of staff effort from the owner, while CM and BOOT require
much less.
The project delivery system should be selected based on a careful evaluation of the process and its consistency with the owner's needs, priorities, and capabilities. Just as a hospital owner wouldnt select a sports facilities architect for an ambulatory care addition, an owner shouldn't select a delivery method without an objective analysis to identify a system that best matches its needs.
In the life cycle of the project, the delivery system should be selected before other project activities ensue. It will determine the scope of work for the A/E, e.g., performance specs and design criteria in the case of design/build, final plans and specs in the case of traditional design-bid-build, and multiple coordinated bid packages for fast-track delivery.
For example, acts of God or force majeure events are always best shared, with the contractor and owner both absorbing their respective dollar consequences of the delay, and transferring property damage risk to insurers for a fixed premium. In managing such a risk in the contract documents, the most important thing is to include a clear and complete listing of force majeure events.
The assignment of risk for design adequacy, on the other hand, varies depending on the type of delivery system. In traditional design-bid-build, the owner warrants the adequacy of the design and can manage that risk through retaining a highly qualified design professional and providing adequate scoping information and fair compensation.
In design/build, while the ultimate design is prepared by the design/builder, the owner also has some design risk. If its performance specifications or design criteria are inadequate or incomplete, its expectations probably won't be fulfilled. Thus, the owner needs to recognize the need to invest in this effort up front.
The basic rule is that risk should be allocated to the contracting party that is in the best position to assume, manage, or bear the risk. It is also well recognized that every risk has an associated cost that must be borne by one party to the process or another. The clearer and fairer the risk allocation, the more effective the project delivery system. I use a simple computer checklist of about 200 risks for analyzing projects. After becoming familiar with the project and identifying risks that should be analyzed, I determine which party should be assigned the risk and then draft appropriate language.