2015 ORS 291.200¹
Budget policy

This section is amended
Effective April 4, 2016
Relating to state financial administration; creating new provisions; amending ORS 171.130, 171.557, 173.025, 173.029, 173.035, 173.420, 176.110, 181A.265, 181A.270, 181A.410, 184.345, 184.656, 276.429, 276.625, 283.091, 286A.035, 286A.720, 286A.772, 286A.792, 286A.826, 291.002, 291.060, 291.100, 291.110, 291.200, 291.202, 291.203, 291.204, 291.206, 291.208, 291.210, 291.214, 291.216, 291.217, 291.218, 291.220, 291.222, 291.223, 291.224, 291.258, 291.260, 291.272, 291.276, 291.328, 291.332, 291.334, 291.348, 291.371, 291.373, 291.405, 293.462, 297.110, 341.937, 350.075, 350.090, 350.160, 352.089, 353.140, 403.455, 409.160, 409.161, 410.072, 410.555, 410.625, 423.525, 461.140, 462.265, 463.195, 469.421, 477.777 and 496.138 and section 23, chapter 121, Oregon Laws 2014; repealing ORS 171.559, 184.354, 291.212, 291.226, 291.228, 291.305 and 291.336; and declaring an emergency.

(1) It is the intent of the Legislative Assembly to require the Governor, in the preparation of the biennial budget, to state as precisely as possible what programs the Governor recommends be approved for funding under estimated revenues under ORS 291.342 (Annual estimation of state revenues). If estimated revenues are inadequate, the Legislative Assembly intends that it be advised by the Governor as precisely as possible how the Legislative Assembly might proceed to raise the additional funds. It is also the intent of the Legislative Assembly, in the event that the additional funding is not possible, to be informed by the Governor precisely what programs or portions thereof the Governor recommends be reduced accordingly. Finally, if the Governor chooses to recommend additional new programs or program enhancements, the Legislative Assembly intends that the Governor specify how the additional funding might be achieved. The Legislative Assembly believes that the state government must allocate its resources for effective and efficient delivery of public services by:

(a) Clearly identifying desired results;

(b) Setting priorities;

(c) Assigning accountability; and

(d) Measuring, reporting and evaluating outcomes to determine future allocation.

(2) In addition to the intentions of subsection (1) of this section, in preparing the biennial budget, the Governor and the Legislative Assembly shall use an outcomes-based budgeting process described in ORS 291.217 (Outcomes-based budget) (2) and (3).

(3) To achieve the intentions of subsections (1) and (2) of this section, it is the budget policy of this state to create and administer programs and services designed to attain societal outcomes such as the Oregon benchmarks and to promote the efficient and measured use of resources.

(4) To effect the policy stated in subsection (3) of this section, state government shall:

(a) Allocate resources to achieve desired outcomes;

(b) Express program outcomes in measurable terms;

(c) Measure progress toward desired outcomes;

(d) Encourage savings;

(e) Promote investments that reduce or avoid future costs;

(f) Plan for the short term and long term using consistent assumptions for major demographic and other trends; and

(g) Require accountability at all levels for meeting program outcomes. [1985 c.270 §1; 1993 c.724 §8; 2011 c.563 §6]

Note: 291.200 (Budget policy) was enacted into law by the Legislative Assembly but was not added to or made a part of ORS chapter 291 or any series therein by legislative action. See Preface to Oregon Revised Statutes for further explanation.

1 Legislative Counsel Committee, CHAPTER 291—State Financial Administration, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors291.­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.