2007 ORS 184.664¹
Status report for projects in Highway Construction Plan

(1) The Department of Transportation shall create a concise status report for the Legislative Assembly of projects listed in the Highway Construction Plan and in the previous status report. The department shall include all of the following in the status report:

(a) An identification of each project, with enough specificity to enable readers of the report to know where the project is located and what the project will accomplish.

(b) An indication of the total amount of moneys the department anticipates will be spent to complete the project and the amount spent on the project as of the date of the status report.

(c) An indication that the project is on schedule, or an explanation if it is not on schedule.

(d) The expected year of completion for the project.

(e) An explanation of any change in priority of a project within the plan or the STIP since the previous status report was issued.

(f) An explanation of any amendments to the STIP that have been made since the Highway Construction Plan was issued.

(g) An explanation of any changes to the adopted budget made by the Emergency Board since the Highway Construction Plan was issued.

(2) When a project has been completed or abandoned, that fact shall be shown in the first status report presented after the completion or abandonment, but need not appear in status reports thereafter.

(3) The status report shall be submitted quarterly to the Legislative Assembly in the manner prescribed by ORS 192.245 (Form of report to legislature). [1999 c.939 §8; 2005 c.612 §5]

1 Legislative Counsel Committee, CHAPTER 184—Administrative Services and Transportation Departments, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­184.­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.