2007 ORS 279C.355¹
Evaluation of public improvement projects not contracted by competitive bidding

(1) Upon completion of and final payment for any public improvement contract, or class of public improvement contracts, in excess of $100,000 for which the contracting agency did not use the competitive bidding process, the contracting agency shall prepare and deliver to the Director of the Oregon Department of Administrative Services, the local contract review board or, for public improvement contracts described in ORS 279A.050 (Procurement authority) (3)(b), the Director of Transportation an evaluation of the public improvement contract or the class of public improvement contracts.

(2) The evaluation must include but is not limited to the following matters:

(a) The actual project cost as compared with original project estimates;

(b) The amount of any guaranteed maximum price;

(c) The number of project change orders issued by the contracting agency;

(d) A narrative description of successes and failures during the design, engineering and construction of the project; and

(e) An objective assessment of the use of the alternative contracting process as compared to the findings required by ORS 279C.335 (Competitive bidding).

(3) The evaluations required by this section:

(a) Must be made available for public inspection; and

(b) Must be completed within 30 days of the date the contracting agency accepts:

(A) The public improvement project; or

(B) The last public improvement project if the project falls within a class of public improvement contracts. [2003 c.794 §111; 2003 c.794 §112; 2007 c.764 §§22,23]

1 Legislative Counsel Committee, CHAPTER 279C—Public Contracting - Public Improvements and Related Contracts, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­279c.­html (2007) (last ac­cessed Feb. 12, 2009).
 
2 OregonLaws.org contains the con­tents of Volume 21 of the ORS, inserted along­side the per­tin­ent statutes. See the preface to the ORS An­no­ta­tions for more information.
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.