Www.transportation.ohio.gov



Path 3 Project Public Involvement Path 3 projects usually involve moderate roadway and/or structure work and may include capacity additions, minor realignments or reconstruction, intersection or interchange upgrades, and/or median widenings. These projects typically include right-of-way acquisition or minor utility impacts and generally require a higher-level environmental document which requires NEPA studies and approval. Public Involvement activities for Path 3 projects can vary greatly depending upon technical issues and impacts. There will likely be more contact with property owners, public notifications will be more frequent and diverse, and the District Public Information Officer (PIO) may be involved in PI activities. All Path 3 projects require a Public Engagement Plan and some Path 3 projects will require a Public Involvement Meeting. For some Path 3 projects, ODOT completes a Feasibility Study and may also complete an Alternative Evaluation Report. Both documents are developed in conjunction with stakeholder and Public Involvement. Many times, ODOT meets with stakeholders and coordinates with agencies, prior to presenting Feasible Alternatives to the Public. Comments on alternatives are addressed as the project continues through the PDP.Please consult with District Environmental staff during project initiation for assistance with determining the appropriate project path and for developing a scope and budget for public involvement activities. Templates and examples for the below requirements and considerations can be found in the Public Involvement Toolbox.REQUIREMENTSEnsure project is listed on STIP and that any PI performed during the STIP process is incorporated into the NEPA decisionProjects must be listed on the STIP/TIP and the next phase of development must be fully funded and included in the STIP/TIP to meet fiscal constraint requirements.? For projects with no STIP ID and that the next phase/authorization (PE Detail Design, RW phase, or CO phase) is using 100% state and/or local funds, please insert a comment on the STIP reference line for environmental clearance indicating that the next phase is “non-federal 100% [Insert state or local, as applicable] funded and is fiscally constrained.”? The District may then proceed with environmental document approval.The use of Statewide Line Items (SLI) is excellent as it greatly speeds up the process, however, we must have the reference ID number to meet the requirements. It’s not acceptable to just say a project meets the SLI criteria. It must be proven it meets the SLI criteria by being approved and included in the STIP and applicable TIPs. If the project is SLI eligible, it must receive a STIP SLI Group Reference ID, which is found on the View Phase tab in Ellis, before NEPA is approved.? NEPA may not be approved until this happens. Please refer to the STIP process document for the specific process to be followed.To document this requirement has been met:The STIP Reference ID number, Statewide Line Item number, or Damage Survey Report number must be added to Item 4 – STIP Reference # on the C2/General tab in EnviroNet. (Please refer to the STIP process document for the specific process to be followed.) It is not necessary to upload documentation to the project file in EnviroNet.Ensure Project Information is published on ODOT Website (Construction Plan, Work Plan, etc.)Ensure project information and one point of contact is listed on the ODOT website in a location that is easy for the public to find. This can be achieved by posting the district annual work plan, the annual construction plan, a list of upcoming projects, a dedicated project website, etc. When project data is entered into Ellis it is also automatically populated into ODOT’s Transportation Information Mapping System (TIMS), ODOT’s web-based project management system. To document this requirement has been met:It is not necessary to upload documentation to EnviroNet for this requirement.Develop Public Engagement Plan (Submit to OES for review and approval if D2 or higher)A Public Engagement Plan is required for all Path 3 or higher-level projects with a D1 or higher level environmental document. Exempt from this requirement are:Disposal of Excess Right-of-Way projectsC2 level environmental document projects that were elevated to a D1 due to requiring an individual waterway permitLimited case-by-case instances with approval from OESFor projects with a D2, D3, EA, or EIS level environmental document, the Public Engagement Plan must be submitted to OES for review and approval. Please refer to the Public Involvement Manual and the Public Engagement folder in the PI Toolbox for additional details and guidance regarding requirements for formatting and information to be included in the Public Engagement Plan. It is strongly recommended the district Public Information Officer (PIO) be involved in the planning and development of PI activities for complex or controversial projects.To document this requirement has been met:The Public Engagement Plan must be uploaded to the project file in EnviroNet.For projects with a D2, D3, EA, or EIS level environmental document, the Public Engagement Plan Approval IOC issued by OES must be uploaded to the project file in EnviroNet.Issue Public Notification LettersPublic notification letters must be sent to those impacted by the project (due to access restrictions, right-of-way takes, etc.). A public notification letter may be combined with the legal notification for right-of-entry, which allows the project team to gain access to property not owned by ODOT but must include specific language required for each purpose. To document this requirement has been met:Public notification(s) must be uploaded to the project file in EnviroNetInclude details regarding where the information was distributed, such as a mailing list, location of where fliers were posted/distributed, etc.Consult with StakeholdersStakeholder consultation will be needed if there are property owners who are impacted by the project, if there are maintenance of traffic concerns, or if some minor local controversy exists. Typical stakeholders might include County Engineer, Service Director, Mayor, City Council, Township Trustees, fire, police, schools, businesses, historical society, transit providers, large employers in or adjacent to the project area, etc. To document stakeholder consultation, if it occurs:Supporting documentation must be uploaded to the project file in EnviroNet. Include details regarding who was contacted and how they were communicated withMay include copies of correspondence, mailing list, phone log, etc.Initiate Contact with Emergency and Public Services (EMS, Police, Fire, Schools, Etc.) during Planning or PE Phases of PDP (during NEPA) if detours and/or roadway restrictions are anticipated that may cause substantial traffic disruptionsContact with emergency and public services must be initiated during Planning or Preliminary Engineering if detours or roadway restrictions are anticipated that may result in substantial impacts to these resources (Such as emergency response times or bus route schedules, etc.). Contact to provide updates must be maintained throughout project development and construction. It is up to each ODOT district to develop a contact list and reach out to these entities to determine their preferred method of contact and/or dissemination of information. It may also be necessary to notify adjacent counties, especially if closures or detours have the potential to impact their roads. Examples of projects where coordination is not required may include rural two-lane maintenance/resurfacing projects, traffic signal maintenance projects, ditch maintenance, berm repairs, pothole patching, etc. that only require daily lane restrictions and will maintain two-way traffic utilizing a flagger. Backups for these types of projects are minimal and emergency services vehicles always take priority and are waved through the construction zone as quickly as possible. To document this requirement has been met:Box 1 on the Public Involvement Tab must include a statement that PI activities during NEPA included initiation of MOT discussions with public and emergency services. Include details regarding this contact, including MOT details, etc.State whether traffic will be maintained/detoured, etc.Include detour information, if applicable/known, or indicate that MOT is not known at this timeUpload supporting documentation to the project file in EnviroNet including details regarding who was contacted and how they were communicated withMay include copies of correspondence, mailing list, phone log, etc.Floodplain findings must be posted to the ODOT websiteIssue Public NotificationsPublic notifications for Path 3 projects may be used to provide essential information to the traveling public, such as notices and updates on the project and travel advisories related to roadway closures and detours. These public notifications may be in the form of a press release, website posting, social media posting, flier, or public notification letter to those impacted by the project (such as access restrictions, right-of-way takes, etc.), etc. To document this requirement has been met:For projects with a C2 level environmental document:The project description must include information about what was done, including MOT details – whether traffic will be maintained/detoured, etc.Include detour information, if known, or indicate that MOT is not known at this timePublic notification(s) uploaded to project file in EnviroNetInclude details regarding where the information was distributed, such as a mailing list, location of where fliers were posted/distributed, etc.For projects with a D1, D2, D3, EA, or EIS level environmental document:The questions under the “Maintenance of Traffic During Construction” section on the General tab must be answered.The Remarks Box under the “Maintenance of Traffic During Construction” section on the General tab must include information about what was done, including MOT details – whether traffic will be maintained/detoured, etc.Include detour information, if known, or indicate that MOT is not known at this timePublic notification(s) uploaded to project file in EnviroNetInclude details regarding where the information was distributed, such as a mailing list, location of where fliers were posted/distributed, etc.Conduct an Open House, Formal, or Combination Formal & Open House Public Meeting, as appropriatePublic meetings are not required for Path 3 projects with no property owner impacts; however, certain circumstances may warrant a meeting, which could include impacts to upon a business or historic district, minor controversy related to environmental concerns, or overall dissent toward the project. For projects of this type, District Environmental Staff and the Project Manager (PM) are responsible for considering and assessing the complexity of issues and determining the need for a meeting.Projects with property owner impacts have a greater potential to impact, alter, or disrupt day-to-day activities and community cohesion. Therefore, these projects require a public meeting during the planning phases of the PDP to provide detailed information to the public about the project and get feedback. Projects with a high level of complexity and impacts may require one or two open house public meetings early in the process, prior to holding a formal public meeting to inform stakeholders and the public early and often and afford opportunities to provide input as the project is being developed.Depending on the context and need, public meetings can either be formal or informal. Typically, most public meetings are structured as open house meetings with a formal presentation (Combination Formal & Open House Public Meeting).For all Open House, Formal, or Combination Formal & Open House Public Meetings:Direct Invitations are requiredTo residents, businesses, and organizations within or adjacent to the project area and potentially impacted by the projectPrefer 30-day notice (requires 15-day notice – should be the exception, not the rule)Published press release/article or paid advertisement (not in legal section) requiredMeeting date, time, and location; project description; project area map; purpose of meeting; comment due date; and contact information for only one point of contact must be includedPrefer 30-day notice (requires 15-day notice – should be the exception, not the rule)Post on social media and ODOT website requiredPrefer 30-day notice (requires 15-day notice – should be the exception, not the rule)Additional tailored outreach, as needed (especially for UPs)To document this requirement has been met:For projects with a C2 level environmental document:The Project Description must include a summary of all PI activitiesUpload supporting documentation to the project file in EnviroNet including details regarding who was invited, what the purpose of the meeting was, when and where the meeting was held, etc.May include copies of correspondence, mailing list, sign-in sheet, handouts, exhibits, presentation, comment forms, etc.For projects with a D1, D2, D3, EA, or EIS level environmental document:The Public Involvement Tab must be completed and include a summary of all PI activitiesUpload supporting documentation to the project file in EnviroNet including details regarding who was invited, what the purpose of the meeting was, when and where the meeting was held, etc.May include copies of correspondence, mailing list, sign-in sheet, handouts, exhibits, presentation, comment forms, etc.Provide Public Review and Comment Period (Includes Consideration of and Response to Comments in Accordance with ODOT’s Public Involvement Manual)The public must be provided ample opportunity to review project information and submit comments. A 30-day comment period is preferred (15-day minimum comment period required, which should be the exception, not the rule). All comments must be considered and responded to during the project decision-making process. Response to questions or comments from the public should be provided within 30 calendar days of receiving the comment, if possible. Please refer to the PI Manual and the Public Meetings and Public Hearings folder in the PI Toolbox for additional details and guidance.To document this requirement has been met:For projects with a C2 level environmental document:The Project Description must include a summary of the number of and nature of comments receivedUpload supporting documentation to the project file in EnviroNet including details regarding who submitted comments, as well as ODOT’s responseMay include copies of comment forms, response to comments, a comment summary table, etc.For projects with a D1, D2, D3, EA, or EIS level environmental document:The Public Involvement Tab must include a summary of the number of and nature of comments receivedUpload supporting documentation to the project file in EnviroNet including details regarding who submitted comments, as well as ODOT’s responseMay include copies of comment forms, response to comments, a comment summary table, etc.Ensure NEPA Assignment Disclosure Statement on Posters or Brochures Available at Public MeetingsIn accordance with the Memorandum of Understand (MOU) pursuant to 23 U.S.C. 327 between the Federal Highway Administration (FHWA) and the Ohio Department of Transportation (ODOT) executed June 6, 2018, Districts or the project sponsor are required to distribute information explaining NEPA Assignment to the public on projects assigned under the MOU. OES has developed brochures and poster boards to be used for this purpose. The brochures or poster boards shall be made available for public meetings related to NEPA Public Involvement.To document this requirement has been met:For projects with a C2 level environmental document:The Project Description must include a statement about having the poster and/or brochures available at the public meeting in the summary of all PI activitiesIt is not necessary to upload documentation to EnviroNet for this requirement.For projects with a D1, D2, D3, EA, or EIS level environmental document:The Public Involvement Tab must include a statement about having the poster and/or brochures available at the public meeting in the summary of all PI activitiesIt is not necessary to upload documentation to EnviroNet for this requirement.Submit all PI Materials to OES for review and approval if D3 or higherFor projects with a D3, EA, or EIS level environmental document, all PI materials must be submitted to the following OES staff for review and approval:OES NEPA Document CoordinatorOES Major Project CoordinatorOES Public Involvement CoordinatorTo document this requirement has been met:An approval IOC from the Office of Environmental Services must be uploaded to the project file in EnviroNet.Conduct Tailored Outreach to Underserved Populations, if applicableFollow ODOT’s Underserved Populations Guidance to properly identify Underserved Populations. If Underserved Populations will be impacted by the project, tailored outreach must be conducted to ensure these populations are appropriately engaged in the project decision-making process. Please refer to the Underserved Populations folder in the Public Involvement Toolbox for additional details and guidance regarding conducting outreach for Underserved Populations.To document tailored outreach to Underserved Populations, if applicable:The outreach must be summarized in the C2/General tab and supporting documentation must be uploaded to the project file in EnviroNet.To document and confirm all Public Involvement Requirements have been met:For projects with a C2 level environmental document, select the appropriate dropdown for “Box 59. Public Involvement” on the C2 tab which states, “Minimum PI Requirements Met; No Minor Public or Agency Controversy on Environmental Grounds.”For projects with a D1, D2, D3, EA, or EIS level environmental document, ensure the Public Involvement Tab in EnviroNet has been completed and all supporting documentation has been uploaded to the project file.ADDITIONAL CONSIDERATIONSFeasibility Study & Alternatives Evaluation ReportComplex Path 3 projects generally require a Feasibility Study (FS) be completed. If a FS is required, stakeholder consultation occurs at completion of Feasibility Study. Additionally, an Alternatives Evaluation Report (AER) may be needed based on the findings of the Feasibility Study. If an AER is needed, stakeholder consultation occurs again upon completion of the AER. Stakeholder meetings are typically held prior to presenting the FS and/or AER to the public.To document the Feasibility Study/Alternatives Evaluation Report has been completed, if needed:The Feasibility Study/Alternatives Evaluation Report must be uploaded to the project file in EnviroNetSupporting documentation of stakeholder consultation must be uploaded to the project file in EnviroNet.Include details regarding who was contacted and how they were communicated withMay include copies of correspondence, mailing list, phone log, handouts, presentations, etc.Conduct Resource Specific PI, if applicableDepending on the context and intensity of anticipated project impacts to the human and natural environment based on the results of technical and environmental studies, it may become necessary to incorporate resource specific PI activities during any phase of the Ohio Department of Transportation’s (ODOT) Project Development Process (PDP). Several regulations require ODOT to investigate impacts to certain types of resources and conduct appropriate Public Involvement before affecting these resources. Section 106Section 106 of the National Historic Preservation Act (NHPA) of 1966 requires Federal agencies to consider the effects of their actions on historic properties. The Section 106 process seeks to incorporate historic preservation principles into project planning through consultation between ODOT, the State Historic Preservation Office, and other parties with an interest in the effect a project may have upon historic properties. Existing regulations require that Section 106 consultation be “appropriate to the scale of the undertaking and the scope of Federal involvement in the undertaking”. This is a requirement for all federally-funded projects that may affect properties included in or eligible for inclusion in the National Register of Historic Places (NRHP). As public involvement (PI) is ongoing through the Section 106 process, it is essential that District Environmental Staff, the Project Manager (PM), or the Project Management Team incorporate the intent of Section 106 into the PI process.Public outreach conducted for purposes of NEPA can be used to satisfy Section 106 PI requirements. For ODOT to use NEPA PI procedures in lieu of having a separate Section 106 PI process, the requirement for Section 106 consultation is integrated (regardless of its PDP path) to identify consulting parties that may have an interest in impacts upon cultural resources within a proposed project’s Area of Potential Effect (APE).Depending on a project’s type and complexity, and the potential impact a project may have on known or potential historic properties, it may become necessary to reach out to potential consulting parties and conduct PI specific to Section 106. This process can begin at any time, especially if it becomes known early in the Planning Phase of the PDP that impacts to an historic property or properties are anticipated. Consulting PartiesIndividuals and groups or organizations are entitled to be consulting parties and will come forward on their own accord when presented the opportunity. On occasion, ODOT, on behalf of FHWA, can identify and invite parties to participate. Pursuant to 36 CFR 800.2(c), individuals and organizations that “demonstrate an interest in the undertaking” will be identified and invited to participate as consulting parties in the Section 106 process.Furthermore, 36 CFR 800.2(d) states “The views of the public are essential to informed…decision-making... The agency official shall seek and consider the views of the public in a manner that reflects the nature and complexity of the undertaking and its effects on historic properties…”Most projects will not require participation of consulting parties. For those projects that require Section 106 PI, consulting parties are documented or identified in a PI Plan (if one is required). A reasonable and good faith effort to identify consulting parties is conducted by District Environmental Staff, the PM or the Project Management Team, with assistance from ODOT-OES Cultural Resources Staff. Consulting parties may include, but are not limited to: State Historic Preservation OfficerFederally recognized Native American Tribes Representatives of local governments Applicants for federal assistanceIndividuals and organizations with a demonstrated interest on a project’s effect upon historic propertiesProperty owners, local historical groups or museums, neighborhood organizations, historic bridge organizations, or other partiesThe publicInformation on the Section 106 process and applications to become Section 106 consulting parties should be made available at public meetings or through other means if a public meeting is not required. The project sponsor forwards all requests to be consulting parties for processing by ODOT’s Office of Environmental Services (OES) on behalf of FHWA. On-going communication with consulting parties may be conducted via email, one-on-one meetings, or through Section 106 consultation meetings. District Environmental Staff, the PM, or the Project Management Team and the Cultural Resources Section of ODOT-OES facilitate this process. Controversy related to a project’s potential effects on historic properties is identified early in the process. If you anticipate controversy related to Section 106 impacts, contact OES Cultural Resources Staff. For more information on how to involve the public in the Section 106 process, refer to ODOT’s Office of Environmental Services (OES) Cultural Resources Manual. Additional information and examples can be found on the ODOT Office of Environmental Services Cultural Resources Manual web page.Section 4(f)Section 4(f) of the Department of Transportation Act of 1966 (codified at Title 49, United States Code, Section 303(c)) applies only to the agencies of the U.S. Department of Transportation (USDOT). Section 4(f) protects publicly-owned parks and recreation areas, wildlife and waterfowl refuges, and private or publicly-owned historic sites listed on or eligible for listing on the National Register of Historic Places (NRHP).As discussed in the ODOT Section 4(f) Manual, and in compliance with Section 4(f) regulations at 23 CFR 774, the majority of Section 4(f) determinations do not have specific PI requirements. However, when Section 4(f) specific PI is required, those actions can be combined with other National Environmental Policy Act (NEPA) PI activities. If no specific PI requirements are required, the normal project development and NEPA PI requirements are followed in accordance with 23 CFR 771.111. Section 4(f) determinations that require specific PI is designed to make the public aware of impacts to a protected Section 4(f) property. Doing so gives the public an opportunity to review and comment on impacts to a property’s protected recreational activities, features or attributes. The list below clarifies when and what type of Section 4(f) PI may be required.No specific Section 4(f) PI requirements are needed for the following determinations:No 4(f)No UseExceptions (23 CFR 774.13) De minimisFor this level of determination, public notice and opportunity for public comment is required. This can be combined with similar PI activities undertaken as part of the NEPA process as long as the proposed impacts to the Section 4(f) property have been adequately disclosed. "The public involvement requirements associated with specific NEPA document and process will, in most cases, be sufficient to satisfy the public notice and comment requirements for the de minimis impact finding (23 CFR 774.5(b)(2))” (FHWA Policy Paper Q&A #11C). If a de minimis impact determination was not known until later in the PDP process and project related PI activities have been conducted, public notice must still be provided. For parks, recreation areas, or wildlife and waterfowl refuges, examples of public notifications include, but are not limited to, press releases, fliers, direct mailings, park kiosk postings, and website postings. The public notice must disclose location of project impacts within the boundaries of the property and associated effects upon the protected recreational activities, features, or attributes (23 CFR 774.5 [b][2][i]). For historic sites, compliance with 36 CFR Part 800 satisfies the public involvement and agency coordination requirement for de minimis impact determinations for historic properties (23 CFR 774.5 (b)(1)(iii)). Members of the public who expressed an interest in the project’s effect on historic properties via the NEPA public involvement process, and all identified Section 106 consulting parties, must be provided an opportunity to review and comment on the Section 106 effect finding.This is, of course, dependent upon clear documentation that the NEPA public involvement clearly discloses and solicits input on the Section 4(f) use as well.NoiseNoise PI is typically conducted after the Noise Analysis is prepared and approved and after the environmental document has been approved. Results of preliminary studies conducted may be shared, if available, during PI conducted in the early stages of the PDP. Once final studies are complete, specific PI meeting(s) are typically held for each proposed noise barrier project per ORC 5517.05. Outreach with property owners and residents of the benefited receptors are conducted by ODOT when noise barriers are offered as noise abatement. As other forms of Noise PI are available, technical assistance is provided by OES.The overall project, as well as noise barrier material type, textures and colors are discussed, and preferences documented (this is one of the only forums in which the public can vote on items related to a project). Coordination with the local political authorities may be done at a separate meeting or concurrently during the PI meeting. Concerns of local officials will be considered in the noise abatement design but will not be a determining factor regarding noise barrier construction. This provides the opportunity to obtain input to indicate whether they want noise abatement or not. If noise abatement is feasible and reasonable, the affected receptors may choose the aesthetic appearance of the receptor side of the noise barrier. For more information on PI specific to noise, refer to the ODOT Highway Traffic Noise Analysis Manual. Aesthetic DesignThe objective of Aesthetic Design is to incorporate principles of project planning and development into a collaborative and interdisciplinary approach (that includes identified stakeholders and the public) to develop a transportation facility that compliments its surrounding natural and human environment. Incorporating Aesthetic Design into the PI process may occur when concerns arise regarding how a project will complement the surrounding community or local stakeholders and officials see an opportunity to incorporate a design that identifies or represents their community. Aesthetic Design considers the total context within which a project will exist, and includes early, continuous and meaningful PI throughout the PDP. Typically, PI specific to Aesthetic Design will occur on Path 4 and Path 5 projects. These higher-level projects involve greater visual impacts and involve major changes to transportation functions, in which a high level of public involvement will take place. Depending on a project’s type and complexity, design workshops may be conducted, where the goal is to offer an opportunity for stakeholders and the public to share ideas and explore viable aesthetic options to incorporate. This open discussion will provide opportunities to reach consensus. The agenda should be designed to encourage everyone to freely share ideas and opinions, as well as listen to others. A professional facilitator is required for such a meeting. ODOT has several facilitators on staff with experience in this type of meeting or a consultant may be selected to serve in this capacity. The design workshop plan will clearly describe a structured decision-making process, and may include the following:Identify the team member or consultant who will serve as the principal liaison with the community. This team member may be someone added to the team specifically because of their knowledge and experience in PI.Identify stakeholders.Identify community concerns to increase awareness of them.If a design workshop is right for this project, ask some of the stakeholders for suggestions regarding time and location for the meeting.Develop a detailed agenda for the workshop.See sample Aesthetic Design Workshop Agenda in Public Involvement Toolbox.Develop and communicate a plan to follow up on workshop outcomes.Follow up by asking participants and other stakeholders to evaluate designs created in response to the design workshop. This step may already be part of an established Public Engagement Plan.The design workshop process has successfully been used by ODOT prior to the initiation of a design and when the public has reacted strongly to a proposed design. For additional information refer to the Community Participation section of the ODOT Aesthetic Design Guidelines.To document Resource Specific Public Involvement, if applicable:The outreach must be summarized in the C2/General tab and supporting documentation must be uploaded to the project file in EnviroNet under the appropriate discipline.DOCUMENTATIONODOT is required to retain project files and general administrative files related to NEPA responsibilities and provide evidence that all minimum PI requirements have been met. Every related decision-making document must be included in ODOT’s online environmental project file system, EnviroNet. To insure PI documentation requirements are being met, all PI activities must be documented and the materials must be uploaded to the project file in EnviroNet as they are developed, per the ODOT NEPA File Management and Documentation Guidance and ODOT’s Categorical Exclusion Guidance, which includes an appendix outlining the minimum documentation required for each level of environmental document.POST-NEPAIssue Public Notifications – Ensure standard plan notes are executed to publicly disclose:Construction schedule/updatesRoad closures and detoursPost-NEPA public notifications must adhere to the requirements in the ODOT Construction and Materials Specifications Manual (614 – Maintaining Traffic) and in the ODOT Traffic Engineering Manual (642-8 – Item 614, Maintaining Traffic (Notice of Closure Sign)). These notifications are usually requested by the contractor through the ODOT Project Manager and disseminated by the District Public Information Officer. These notifications may be in the form of a press release, public notification letter to those impacted by the project (such as access restrictions, right-of-way takes, etc.), social media posting or website posting, etc.To document post-NEPA notifications:It is not necessary to upload documentation to EnviroNet for Post-NEPA public notifications unless the notification is the result of and/or related to a specific Environmental Commitment. If the post-NEPA notification is the result of and/or related to a specific Environmental Commitment, documentation that proves the Environmental Commitment was met must be uploaded to the project file in EnviroNet. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download