Corridor Planning Guidebook

Step 5. Implementation Plan

This chapter describes action steps and commitments following the refinement and evaluation of potential solutions in Step 4. The implementation plan (Step 5) helps pair the evaluation findings with funding practicalities and jurisdictional responsibilities. Note that the implementation plan does not identify a preferred solution, which is conducted as part of the environmental review process.  

The implementation plan should be developed with the direct involvement of the affected or owning agency and partner staff. Commitments documented in the plan should be based on specific discussions with staff, such that they can become part of the formal implementation process. 

Actions and Commitments 

The implementation plan should describe in concrete detail how a given solution will be advanced and how, including specific commitments by MnDOT and agency partners. If the project team is not able to provide all the requested details for a given solution, that information also should be documented. 

For each solution, discuss and document the following: 

• Solution and Estimated Cost: Describe the solution and its estimated cost, if known. For larger solutions, especially infrastructure projects, it may be appropriate to consider dividing into phases based on likelihood of funding or other constraints.  
• Champion and Partners: Which agency and department is the leader or champion for this action. Also identify agency partners. 
• Commitments: What action or actions are the lead and partner agencies committing to in order to advance the identified solution. 
• Funding Status and Source: Is this solution funded and what is the source; if not funded, what is the intended source and timing? Indicate whether solution may require cost participation from local agencies per Cost Participation Policy. 
• Timing, Triggers, and Constraints: Includes considerations such as desired timing for implementation, triggers or constraints, including any coordinated actions or projects. Indicate whether area outside of MnDOT right-of-way is anticipated to be needed, and if so, whether partners are engaged in official mapping activities.  
• Outstanding Questions: Document uncertainties, areas or issues that require further understanding or exploration prior to, or as part of, implementation.  
• Priority: For each solution, identify its relative priority and reasoning. Priorities could be reported as a numerical ranking or a high/medium/low rating.  

Table 16. Implementation Plan Summary Table Examples 

Policy Solutions 

Management and Operations Solutions 

Infrastructure Solutions 

Transition to MnDOT Project Development Process 

As relevant, each project or action identified in the implementation plan should include reference to potential next steps in the MnDOT Project Development Process. For example, a CHIP project will typically proceed to scoping and environmental review.  

Project Development Tools  

MnDOT’s districts have adopted several tools to support early project development. Plan outcomes can inform project charters and planning risk registers to aid in transitioning plan outcomes to the project development process. 

• Project Charters. Project charters document project context and discovery elements before project scoping begins. Completed corridor plans can be used as a source for this context. Project charters also define the proposed project scope that MnDOT staff will develop, which is signed off on by MnDOT leadership. Corridor plan alternatives form the basis for the project that will move forward into scoping. 
• Planning Risk Registers. Planning Risk Registers document known risks to a project’s schedule and budget as early as the planning phase. This helps MnDOT staff work proactively to address risks as early as possible and work systematically to reduce known risks as project development continues. MnDOT planners can use findings during corridor plans to inform risks documented in Planning Risk Registers.