WeVote

Bill

Bill

HF 4531

Department of Transportation required to modify evaluation and planning process for certain transportation projects.

2025-2026 Regular Session Introduced by Katie Jones

MnDOT must adopt context-specific, multidisciplinary planning and stronger stakeholder engagement for trunk highway projects, with comprehensive documentation and accountability.

Introduction and first reading, referred to Transportation Finance and Policy
0
WeVote Research Nonpartisan
Bill Summary · HF 4531

Summary of HF 4531 (2025-2026) — Department of Transportation required to modify evaluation and planning process for certain transportation projects

This bill proposes substantial changes to how the Minnesota Department of Transportation (MnDOT) develops, evaluates, and documents transportation projects, with a strong emphasis on context-specific planning, multidisciplinary review, and enhanced coordination with stakeholders. Key elements include new requirements for purpose-and-need development, scoping, multidisciplinary project development, internal audits, and a revised complete streets framework. Some provisions take effect in 2027, with broader implementation by 2028 for many sections.

1) Primary purpose and intent

  • To modify MnDOT’s evaluation, planning, and decision-making processes for trunk highway projects that require environmental review and/or investments in the State Highway Investment Program.
  • To ensure context-specific planning, earlier stakeholder engagement, multidisciplinary review, and accountability through enhanced documentation and audits.
  • To align project development with statewide multimodal plan priorities and reduce reliance on tiered level-of-service metrics alone.

2) Key provisions and changes

A. New purpose, need, and scoping framework (Section 1)

  • Introduces new concepts and definitions for context-driven planning.
  • Establishes a Planning Worksheet Scoping Guide to be developed by MnDOT for stakeholder engagement and determining project scope.
  • Defines “purpose and need” to explain the problem, desired transportation outcomes, and how multiple approaches will be considered (not prematurely identifying a single improvement).

B. Context-specific scoping and coordination requirements (Section 1)

  • Applies to projects that involve construction, bridge work, capacity changes, access alterations, or permanent right-of-way acquisitions and require an environmental impact statement (EIS).
  • Requires a context-specific scoping document before inclusion in the state highway investment program.
  • Mandates a coordination field visit and walking audit of the project corridor prior to finalizing scoping documents.
  • Requires a stakeholder checklist, recognition of variability across project types, and a context-and-modal accommodation analysis (which modes are appropriate, tradeoffs, baseline mode prioritization, and mode-priority influences).

C. Purpose and need adjustments and multidisciplinary review (Section 1)

  • prohibits locking in a specific improvement as the sole need.
  • allows broader consideration of needs, including cost, safety, community input, and alignment with statutes and program goals.
  • requires multidisciplinary review processes to be integrated into the purpose-and-need development.

D. Documentation and non-duplication (Section 1)

  • All alternative options studied must remain part of the permanent project record and be carried into later environmental reviews, investment scoring, and reporting.

E. Implementation safeguards (Section 1)

  • Implemented in a manner consistent with federal NEPA and state environmental law.

F. Internal compliance, ombudsperson, and audits (Sections 2–3)

  • Creates an internal MnDOT ombudsperson (effective March 1, 2028) with duties to resolve disputes, inform the public, facilitate discussions, and monitor performance. The ombudsperson must report certain findings to the internal auditor if statutory requirements are not met.
  • Requires an internal compliance audit by MnDOT’s internal auditor (effective March 1, 2028) when there are repeated noncompliance reports to identify and address gaps.

G. Departmental organization and affirmative action (Section 4)

  • Revisions to organizational requirements; introduces a chief financial officer with authority over financial controls and budgeting across districts and divisions.
  • Removes some older language related to affirmative action plans, replacing it with an updated framework (specifics indicate ongoing emphasis on diverse staffing).

H. Standards-based performance reviews (Section 5)

  • Requires performance reviews for supervisors and lead project managers to assess implementation of the new planning requirements and multidisciplinary obligations (effective March 1, 2028).

I. Outcome analysis and reporting for statewide plan (Section 6)

  • Requires outcome analysis of projects included in the statewide multimodal transportation plan during revisions of the 20-year highway investment plan, focusing on:
    • When projects were added and their purpose-and-need basis.
    • Milestones and alignment with statewide plan priorities.
    • The scoping process and decision-making criteria.
    • How multidisciplinary development efforts were applied.
  • Requires post-completion reporting on whether projects met projected safety, emissions, access, and cost outcomes, with findings of deviations reported to the internal auditor (effective March 1, 2028).

J. Multidisciplinary project development (Section 7)

  • Establishes a formal multidisciplinary core project team for eligible projects (capacity expansion).
  • Core team duties include: integrated field visits/walking audits, including a local planner; serving as co-reviewers on purpose-and-need and budgeting; assessing decisions against statewide plan priorities; and evaluating outcomes using a broad set of metrics (economic development, equity, transportation insecurity, access to services/jobs, affordability, environmental justice, and public health).

K. Complete streets and implementation guidance (Sections 8–9)

  • Requires a revised complete streets policy, developed with stakeholder input, integrating context-sensitive solutions and multidisciplinary resources (including 174.742 elements and 161.1611 planning context).
  • Guidance to accompany the complete streets policy, detailing:
    • An analysis framework for project characteristics and purpose-and-need context.
    • Highway system categorization by context and emphasis on vulnerable road users and transit.
    • Consideration of speed-limit reductions where appropriate.

3) Who/what would be affected

  • MnDOT and its districts/divisions: must implement the new context-driven planning, scoping, and multidisciplinary processes.
  • Statewide multimodal transportation planning: alignment with new purpose-and-need and scoping requirements.
  • Transportation ombudsperson: new statutory role with oversight and reporting duties (effective March 1, 2028).
  • MnDOT staff in leadership, project management, and auditing: new accountability and evaluation requirements; performance reviews reflecting compliance.
  • Stakeholders and the public: enhanced early engagement through planning worksheets, field visits, and walking audits; ongoing transparency via documentation of alternatives and outcomes.

4) Procedural and timeline aspects

  • Effective dates for core changes:
    • March 1, 2028: Sections covering ombudsperson, internal audits, performance reviews, multidisciplinary development, outcome analysis reporting, and most implementation provisions become effective.
    • July 1, 2027: Subsection 4 (scope-related scoping document and field visits) takes effect for projects scoped on or after that date.
  • Ongoing requirements:
    • All alternative studies must be retained in the project record and carried into future environmental reviews and reporting.
    • Multidisciplinary project development (174.742) applies to eligible projects starting March 1, 2028.
    • Complete streets policy and accompanying guidance are implemented with coordinated stakeholder input and training.

Overall, HF 4531 would push MnDOT toward more transparent, context-specific, and multidisciplinary project planning, with stronger stakeholder engagement, enhanced accountability, and deliberate consideration of diverse outcomes beyond traditional level-of-service metrics.

Compiled from official sources — confirm details with the bill’s official record.

Sign in to ask a question.