129.2 The Public Involvement Plan (PIP)/Communication Plan

Early in the project scoping process a Public Involvement Plan (PIP) should be developed that is appropriate for each project. A PIP is a strategy document which guides outreach activities for a project. It helps to establish the schedule, methods, and locations for public outreach and assists with determining project stakeholders. For Programmatic Categorical Exclusion (PCE)(rare) and CE2 classifications (required), the PIP is often developed by the Project Manager (PM), district staff including Communications staff (CR Division), and/or project consultant, if applicable, and approved by MoDOT staff (PM, CR, etc.). The project core team (EPG 104.1) typically develops the PIP for larger, more complex projects, especially those requiring an EA or EIS, which are approved by FHWA. The nature and complexity of the project along with the core team’s specialized knowledge of any sensitive issues within the project area will determine the best course of action to gain public input into the development of the project’s scope (EPG 104.8). After identifying potentially affected populations and the issues they may have with the proposed project, this information can be compiled in the PIP (see sample above). It may become necessary to revise the PIP as a project evolves, conditions change, oppositional groups emerge, public controversy develops, or new issues arise. The size, scope and complexity of a project will help determine the extent of outreach and engagement for a project and whether a project requires a more formalized and comprehensive PIP. The PIP becomes part of the official project record and should be uploaded to the RES or to MoProjects as evidence of planned public involvement.

Early use of demographic data can help identify members of the public that should be involved. After determining who to involve, a variety of outreach methods can be selected to encourage the most effective public involvement. During public outreach the following could be involved:

• adjacent property owners and tenants
• low-income populations
• minority populations
• cooperating and participating agencies (NEPA Glossary)
• local, state, and federal government staff and elected officials
• community groups such as clubs, civic groups, business groups, environmental groups, labor unions, disability advocacy groups, and churches
• schools/school districts
• MPOs/RPCs
• commuters and the traveling public
• law enforcement and emergency/first responders
• utility service providers
• adjacent billboard owners and clients
• general public and others known to be affected
• others expressing interest.

The following are examples of common outreach methods that can be identified in the PIP:

• Virtual Public Involvement (VPI) meetings
• public and open house meetings
• MoDOT project e-mail alert lists
• drop-in information centers or booths
• surveys or questionnaires
• advisory committee and group meetings
• public hearings
• design workshops/charettes
• direct mail/email
• meetings with public officials
• individual (one-on-one) meetings
• meetings with community groups
• internet blogs
• project Internet pages/news releases
• established media relations and contacts
• telephone hot lines.

In addition, MoDOT provides information to the public about traffic impacts as part of its Transportation Management Plan (TMP) for projects (EPG 616.13.6.6). MoDOT also provides general work zone information to the public through various outlets. These include, among other things, publication of a statewide work zone map and work zone driving safety tips, posting of current work zone locations and conditions to the internet, promotion of Work Zone Safety Awareness Week, and advertisement of work zone safety-related messages via radio, television, electronic message boards along the roadway and, billboards. These details can also be incorporated in the PIP.

The example PIP or a more detailed plan shall be utilized on all CE2, EA, and EIS classified projects. Use of a PIP on all other projects should be evaluated by the core team members of that project individually depending on the needs of that project.