2015 ORS 419C.623¹
Frequency and content of report

(1) The Oregon Youth Authority or private agency shall file the reports required by ORS 419C.620 (Circumstances requiring report) at times required by the court, required by the youth offender’s reformation plan or case plan and as determined necessary by the youth authority or agency. The youth authority or agency shall file reports more frequently if the court so orders. The reports shall include, but need not be limited to:

(a) A description of the offenses that necessitated the placement of the youth offender with the youth authority or agency;

(b) A description of the youth offender’s risk to reoffend and an analysis of the need for services and assistance; and

(c) A proposed reformation plan or case plan, or proposed continuation or modification of an existing reformation plan or case plan, including, where applicable, a description of services to be provided in furtherance of the youth offender’s reformation and safe return to the community.

(2) Notwithstanding the requirements of subsection (1) of this section, reports following the first report that is required by subsection (1) of this section need not contain information contained in prior reports.

(3) Notwithstanding the requirements under ORS 419C.620 (Circumstances requiring report) that reports be filed with the court, any report after the first report that is required by subsection (1) of this section on a youth offender whose case is being regularly reviewed by a local citizen review board shall be filed with that local citizen review board rather than with the court. [1993 c.33 §264; 1999 c.92 §3; 2005 c.159 §6]


1 Legislative Counsel Committee, CHAPTER 419C—Juvenile Code: Delinquency, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors419C.­html (2015) (last ac­cessed Jul. 16, 2016).
 
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.