Biological Resources Sections Dissected!
Friday, May 19, 2017
1:45 p.m. - 3:15 p.m. CDT
San Francisco, CA, United States
CM | 1.50Add to My Log
Biological resources analysis for CEQA documents should be based in solid factual information from site-specific analysis. Often times not all information can be gathered and presumptions are made leading to potential holes in the analysis subject to challenge, and what may amount to deferred mitigation. Additionally, CEQA documents are often based on a huge overburden of somewhat related, but irrelevant information that can divert the reader's attention from the real issues affecting biological resources. Why not provide clear and succinct project site baseline information based on answering the key questions? Are there special-status species present or absent based on protocol or industry accepted survey methods? Are there jurisdictional wetlands present and mapped based on accepted methodology? Are there other issues that need to be established based on the CEQA Appendix G Guidelines? Based on real factual information, the biologist can then make appropriate determinations of significance of project impacts on biological resources. This session will provide a brief overview of the baseline information requirements for CEQA documents and then delve into examples of the good, the bad, and the ugly of CEQA biological resources analysis and mitigation measure development. The panel of two well-seasoned biologists and one attorney will provide their experience on crafting readable CEQA biology sections that answer the question accurately, succinctly, and in a way that will address agency concerns as well as that of the public. Well-crafted mitigation measures covering the key biological resources issues will be offered. We will also review CEQA case law related to biological resources to further inform our audience of how to develop iron clad and bullet proof CEQA biology sections, how to avoid the deferred mitigation trap, and to make responses to comments a breeze.
Lynne Bynder, firstname.lastname@example.org