Laserfiche WebLink
• <br /> MEMORANDUM <br /> TO: Colorado Water Conservation Board Members <br /> FROM: Peter Evans <br /> Acting Director <br /> DATE: November 20, 1998 <br /> RE: Agenda Item 12a, November 23-34, 1998 Board Meeting-- <br /> Construction Fund Loan Program—Statutory Purposes of the CWCB <br /> Construction Fund <br /> One of the major items in our strategy for responding to the September 1998 <br /> • performance audit of the Construction Fund Loan Program is a review of the statutory <br /> purposes. This element of this strategy is responsive to at least two of the <br /> recommendations: Recommendation 2 indicates, in part,that the Board should work with <br /> the General Assembly to make a statutory change as needed to put more of the cash <br /> balance to work out in the community; recommendation 4 suggests that the Board should <br /> consider expanding the statutory funding priorities to more clearly provide authorization <br /> for any future projects the Board anticipates (e.g.,the purchase of water rights,the <br /> purchase of federal reservoirs)that may not fall as obviously into the existing statutory <br /> priorities (see attached copy of C.R.S. Sections 119 and 121). <br /> Based upon a discussion with our Sr. Staff, I have identified the following <br /> potential categories of a activity that seem to provide comprehensive inclusion of all the <br /> sorts of projects we have funded or undertaken in recent years. <br /> • Increase beneficial consumptive use of waters in Colorado (including storage <br /> and delivery facilities, well field development, etc.); <br /> • Rehabilitation of existing water supply infrastructure in Colorado (including <br /> facilities under restriction by the State Engineer for safety purposes); <br /> • Acquisition of existing infrastructure or water rights; <br /> • Flood protection projects (limit to 5% of income? 10%? 5% unless there are <br /> more funds than water supply projects can use and worthy flood protection <br /> • projects would be unnecessarily delayed?); <br />