Committee Process

Technical documents that form the basis of the Scoping Decision Document are developed by project staff then reviewed by committee before review by the broader public.
General deliverables process graphicView full-size image


  1. Share existing, background and reference information: MnDOT staff and consultant project team members review background and reference information collected during Phase 1 or provided by city and county project partners.
  2. Data collection and analysis:
    Project team members identify what new data is needed. For example, new traffic data can be collected on the interstate, entrance or exits ramps, or adjacent street network. The team collects and analyzes the data.
  3. Discuss assumptions and rough framework: The project team discusses any assumptions made in the analysis and starts to develop a rough framework of the technical document.
  4. Draft for Technical Advisory Committee: A draft is shared with the Technical Advisory Committee for review and comment. Engineering and planning staff from MnDOT, Federal Highway Administration, Ramsey County, Hennepin County, City of Minneapolis, City of St. Paul, and other government entities serve on the Technical Advisory Committee. The committee provides technical advice to the project team.
  5. Coordination with Policy and Planning Committee Working Group: Coordination of technical information with the Livability Framework occurs at the Policy and Planning Committee (PPC). The PPC focuses on potential strategies for implementing the Livability Framework developed during Phase 1 (sense of place, community connections, economic opportunities, equity, safety, and a healthy environment for the communities that live, work, and play there). Professional planning staff from MnDOT, Federal Highway Administration, Ramsey County, Hennepin County, City of Minneapolis, City of St. Paul, and other government entities serve on the PPC.
  6. Revisions: At each step in the process the project team is taking in feedback and revising the draft.
  7. Engagement with Cooperating and Participating Agencies: The draft is shared with the Cooperating and Participating Agencies. This is a process requirement under the National Environmental Policy Act. Cooperating agencies are Federal agencies, other than the lead agency, with jurisdiction. Participating agencies are those with an interest in the project. There roles are defined by the Council on Environmental Quality which oversees the NEPA implementation.
  8. Revisions: The project team presents information, receives feedback, and revises the draft.
  9. Engagement with Community Leaders: The draft and/or staff developed education materials and questions are shared with community leaders to gather initial feedback on the information, the presentation of the information, and the plan for gathering broader public feedback. The Community Leaders, formerly Community Advisors, includes leaders from community organizations representing neighborhoods, business interests, and cultural associations.
  10. Revisions: The project team presents information, receives feedback, and revises the draft.
  11. Recommendations to Policy Advisory Committee: The project team presents the draft to the Policy Advisory Committee (PAC). The PAC consists of elected and appointed officials who provide decision direction. Current PAC members include; MnDOT Commissioner, Federal Highway Administration Minnesota Division, Metropolitan Council (Committee Co-Chair), County Commissioners, Mayor and City Council Members, and State Senators and Representatives.
  12. Revisions: The project team presents information, receives feedback, and revises the draft.
  13. Engagement with Broader Public: The project team presents the technical information to the public in both it’s technical document form and in plain language format. Technical information and format is available on request. Engagement opportunities will be online and in-person using various tools. These will be opportunities for the project team to learn from the community’s lived experiences.
  14. Revisions: The project team presents information, receives feedback, and revises the draft.
  15. Report back to PAC; Continuing analysis and engagement as needed: The project team reports back to the PAC following the broader public engagement. Analysis, revision, and further engagement continue. The technical information becomes a base for the Scoping Decision Document that also flows through the committee and public review cycles.


Share on Facebook Share on Twitter Share on Linkedin Email this link