My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD00349
CWCB
>
Board Meetings
>
Backfile
>
1-1000
>
BOARD00349
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 2:49:14 PM
Creation date
10/4/2006 6:36:32 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
9/9/1980
Description
CWCB Meeting
Board Meetings - Doc Type
Meeting
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
66
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />Needless to say, this procedure has led to misunderstandings <br />by those unfamiliar with the process. Since the Board's approval <br />of the Preliminary Recommendations was only intended as a proce- <br />dural step in the review process, it is recommended that: (1) the <br />title of the Preliminary Recommendation list be changed to Pre- <br />liminary Notice and (2) no formal motion be made "accepting" or <br />"approving" of the Preliminary Notice. Rather, this Preliminary <br />Notice would simply be mailed to an established notification list <br />(see discussion below) 30 days prior to the Board meeting at which <br />the Preliminary Notice would be presented to the Board for its <br />information. The streams and/or lakes on the Preliminary Notice <br />would then automatically advance, subject to staff consideration <br />of any comments which may have been received, to the Pinal Re- <br />commendation list, which would be renamed the pinal Notice list. <br />The pinal Notice would be mailed 30 days prior to the Board meet- <br />ing at which it was to be considered. <br /> <br />Notification List/Notification Schedule <br /> <br />The question as to whether the public has received adequate <br />notification of pending Board action on minimum streamflow matters <br />has often been the focus of discussion at past Board meetings. <br />The question is two-fold: first, has adequate distribution been <br />made of the notice to all interested parties, and secondly, has <br />adequate time been given for review and comment by those interes- <br />ted parties? <br /> <br />To alleviate the first half of this question, an expanded <br />notification list has been developed in an attempt to reach all <br />interested parties. Part I of the list includes those (e.g., <br />Board members; various state, federal, and municipal agencies; <br />certain conservancy districts; etc.) who will receive notice of <br />all minimum streamflow recommendations (preliminary and final). <br />Part II of the list is broken down into the seven Water Divisions <br />of the State and includes such parties as the Division Engineer, <br />conservancy districts, county commissioners, councils of govern- <br />ment, regional planning commissions, etc. Those in Part II of <br />the list will only receive the notices for streams within their <br />area of interest. <br /> <br />These lists are attached for your information. If you have <br />any additions or deletions, please bring them to the attention of <br />the staff. While we are trying to make the distribution as com- <br />plete as possible, additions and deletions can be made at any time. <br /> <br />The second problem, that of adequate time for review and com- <br />ment, can be addressed through a standardization of existing pro- <br />cedures within a more specific timeframe. The Preliminary Notice <br />will be mailed 30 days prior to the Board meeting. If no comments <br />are received by the staff at that Board meeting or otherwise, <br />those streams will appear on the pinal Notice for the following <br />Board meeting. This pinal Notice will also be mailed 30 days prior <br />to the Board meeting at which it will be considered. Thus, this <br />procedure will provide two separate notifications and at least <br /> <br />2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.