(a)

1. (1) The project scope should be developed using existing work products and/or products from data gathered during the programming process.
2. (2) These products and data should provide the basis to describe the existing conditions, the proposed project form and limitations, as well as the expected impacts and outcome.

3. (3) Work product examples to be reviewed include, but are not limited to:

   1. (A) Preliminary reviews;
   2. (B) Environmental surveys;
   3. (C) Photogrammetric surveys;
   4. (D) Topographic maps;
   5. (E) Existing soil borings;
   6. (F) Previous construction plans; and
   7. (G) Right-of-way maps.
4. (4) The background information should be sufficient to facilitate the development of the project scope and to guide the initial preliminary engineering and environmental work efforts.

(b)

1. (1) As preliminary engineering and other project development work continues, the project scope should be updated regularly to ensure that key assumptions regarding scope, schedule, and funding are appropriately modified.
2. (2) The project scope should accurately describe the work presented in the procurement documents, in particular, the RFQ and the RFP.
3. (3) In a manner consistent with the DB-B process, the D-B process requires early determination of the project expectations including the project description, project limits, typical section or sections, project schedule, and the budget to be presented to the proposer during the procurement phase.
4. (4) If the design-build to a budget method is selected for the project, the documents would be presented as the baseline project documents during the procurement phase as the baseline or minimum standard acceptable for the project with the expectation that the short-list proposers will improve on the standard presented within their respective proposals.