Minnesota Department of Transportation

511 Travel Info

MnDOT Policies

Agency Policy Manual

Effective Date: July 29, 2021

Print Manual (pdf)

Contacts

Policy Coordinator

Andrea Barker
651-366-3018
andrea.barker@state.mn.us

Technical Memo Coordinator

Nancy Yoo
651-366-4703
nancy.yoo@state.mn.us

Administrative Rule Coordinator

Beth Scheffer
651-366-4792
elizabeth.scheffer@state.mn.us

Introduction

MnDOT is committed to excellence in policy administration by:

  • maintaining the timeliness and accuracy of policies;
  • ensuring stakeholder input in policy development and review;
  • ensuring accessibility and usability;
  • using a standardized template and process to ensure consistency and transparency; and
  • using plain language.

As part of the agency’s internal control system, policy helps minimize risk by defining standards, roles and responsibilities, and providing clear department leadership expectations. MnDOT’s policy development and management program considers input from a broad range of stakeholders in order to develop, implement, and manage policies that support operational excellence.

Employees must notify and work with the Policy Coordinator when the need for a new policy, a revision, or retirement of an existing policy is identified.

Reason for Manual

This manual provides a clear, transparent, and standardized process for developing and managing agency policies. It describes internal duties and responsibilities related to the lifecycle of policy governance from intake to development, review, approval, publication, maintenance, and finally, retirement.

About Policies

What is a policy?

A formal declaration of an organization’s principles and expectations. Policies are mandatory, broad and comprehensive, and backed by laws, regulations, statutes, Executive Branch agency policies, or other governing authority.

When is a policy developed?

Policies are developed:

  1. when required by law or another Executive Branch agency policy; or
  2. to set expectations, establish internal controls, and/or to mitigate risk. Policy directives must be long-term and department-wide or across several divisions.

Note: Policies are developed for MnDOT’s internal management. Regulation that directly affects the rights of or procedures available to the public is addressed through the administrative rulemaking process.

Policy Categories and Numbering

There are five policy categories:

  • Administrative (AD) policies – establish the framework for policy development and management and describe MnDOT’s position on overarching business issues
  • Data Management (DM) policies – the business function of planning for, controlling, and delivering data management and information needs
  • Financial Management (FM) policies – ensure the management and safeguarding of MnDOT’s financial assets and resources
  • Workforce (WF) policies – set expectations for the workforce to safeguard MnDOT’s workplace and to protect employees and others
  • Operations and Engineering (OE) policies – broad, long-term, and describe MnDOT’s position on technical matters not otherwise covered by a Technical Memo or other guidance

Policy Template

Policies are standardized and contain the following content:

Policy Category

Policies are categorized as Administration, Data Management, Financial Management, Workforce, or Operations and Engineering.

Policy Title

Identifies the purpose of the policy. Must be concise and “searchable” for all users and the name must succinctly identify the topic.

Policy Number

Policies are numbered by category and in the order they are created, for example, AD001, AD002, AD003, FM001, FM002.

Effective Date or Revised Date (in header)

The date the policy is signed by the Responsible Senior Officer (Deputy Commissioner). This is the last signature on the document.

Policy Owner

The Office Director most closely related to the subject matter of the policy, such as Director of Communications, Director of Land Management, but can be another person. There may be more than one Policy Owner.

Policy Contact

The subject matter expert for the policy. There may be more than one policy contact.

Policy Statement

Identifies what the policy requires and who must comply with it. Sets the scope, agency commitment, and expectation.

Reason for Policy

The legal, regulatory, or business rationale for the policy. Ensures compliance with law and regulations.

Applicability

All MnDOT employees must comply with MnDOT policies. Some contractors, consultants, suppliers, and other third parties who are engaging in MnDOT business may be required by contract to comply with MnDOT policies. This section also includes a list of the key stakeholders responsible for successful development, implementation, operation, compliance, and maintenance of the policy.

Definitions

Formal statements of the meaning or significance of a word or phrase contained elsewhere in the policy. Definitions enhance clarity of meaning and accurate interpretation. May also include a note or comment following the definition giving additional context related to the policy. All new definitions must be added to the Business Data Catalog (BDC) before adoption. Contact the BDC Coordinator to add new definitions or update old ones.

Responsibilities

Lists the roles and responsibilities of the key stakeholders for the successful development, implementation, and required review of the policy. Describes the "what" but not the "how" of the responsibility. Includes the standard responsibilities of the Policy Owner.

Resources and Related Information

Links to forms, procedures, manuals, statutes, rules, etc. Always includes a link to the Business Data Catalog (BDC) and the MnDOT Policy website.

History and Updates

Identifies the date of initial adoption and captures dates of and reasons for substantive revisions.

Authorization

Required signatures for policy implementation or revision.

  • Policy Owner(s)
  • Governance Committee Chairperson
  • Responsible Senior Officer(s) (Deputy Commissioner(s))
Policy Review

Documentation of review cycle. Policy Owner signs to indicate that the policy was reviewed, the policy content is current, and no significant modifications are needed. Minor edits may be made to the policy during review and noted in this section.

Document Header

Contains the MnDOT logo, policy title, policy number, and effective date.

Document Footer

Contains the unique document number assigned in the eDOCs document repository, followed by the page number (x of x), and the policy title and number.

Retention

All policies (whether new, revised, or retired) must be archived permanently in eDOCs in accordance with the Records Retention Schedule.

Definitions

Communications Plan

A plan to communicate the new policy or policy revisions to affected parties. Plans may include: Newsline article, iHUB updates, presentations, trainings, targeted emails, etc. Consult with Office of Communications and Public Engagement to develop a communications strategy prior to presenting the policy to Governance Committee for approval.

Education and Training Plan

A plan addressing the knowledge or skill gaps resulting from the policy. The plan should, at a minimum, address needs analysis, learning objectives, delivery methods, and tools that may be used to educate or train MnDOT employees. Tools may include live training/presentations, lunch and learns, e-learning, iHUB, email communications, etc.

Equity Lens

One of MnDOT’s core values is diversity and inclusion. MnDOT has adopted an Equity Lens Framework which requires an understanding that decisions within the agency can affect all groups of people differently. The ultimate goal is to produce the most equitable outcome possible in a given scenario. Each policy development team must demonstrate how it applied the equity lens in developing the policy by providing answers to the questions to the Governance Committee.

Governance

The way in which an agency is managed at the highest level and the system of rules, practices, and processes for doing this.

Types of governance at MnDOT include:

  • Best Practices

    Procedures that have been shown by research and experience to achieve effective results. They are established or proposed as a method suitable for widespread implementation.

  • Charter

    A founding document that defines the authority, roles and responsibilities, mission, composition, and standard protocols of an organization or ad hoc group.

  • Commissioner's Order

    An official act or determination of the Transportation Commissioner, Deputy Transportation Commissioner or other official under delegated authority.

  • Directive (Commissioner or Deputy Commissioner's Memo)

    An official mandate from MnDOT senior leadership that provides specific instructions to managers, employees, or another broad group.

  • Executive Order (Gubernatorial)

    A written statement executed by the governor pursuant to constitutional or statutory authority and denominated as an executive order. Executive orders have the force of law and agency leadership and staff must implement and remain in compliance with the executive order’s requirements. Agency policies inform the implementation of such requirements within a State agency.

  • Guidance

    A statement of recommended, but not mandatory, practice in typical situations. Guidance is issued to provide a preferred method of accomplishing a task or solving a problem.

  • Guidelines

    Recommended or suggested practices to promote consistent practice and decision-making. Guidelines may include “best practices” which offer criteria for consideration in decision-making but allow for exceptions.

  • Plan (Strategic Operating Plan, Statewide Multimodal Transportation Plan, etc., not Construction Plans)

    A detailed proposal for doing something or achieving a desired outcome. MnDOT plans may include operational goals, processes, or investment and resource priorities. 
    Note: Planning is an active way of discussing the goals, objectives, strategies, and tasks that we need to accomplish. Plans are the documentation of planning. Plans may be developed in alignment with or in consultation with other agencies and partners. Plans may require a formal public comment opportunity and formal approval or adoption. 

  • Policy

    A formal declaration of an organization’s principles and expectations. Policies are mandatory, broad and comprehensive, and backed by laws, regulations, statutes, Executive Branch agency policies, or other governing authority.

  • Procedure

    A step-by-step sequence of activities or course of action that leads to a result or expected outcome. Procedures often describe “who,” “what,” “when,” “where,” “why,” and “how” and serve as a consistent internal control mechanism required to mitigate risk.

    Note: Procedures, or steps in procedures, that are mandatory are identified as such or contain the word “shall” or “must.” Procedures, or steps in procedures, that are discretionary contain the word “may.”

  • Standard

    A statement of required, mandatory, or specifically prohibitive practice.

  • Technical Memorandum

    A document intended to expedite official changes in technical standards and procedures, to provide technical guidance, or to provide essential information until a technical manual, standard drawing (plates/plans),  or specification is officially issued or updated, or when the change is temporary.

    Tech memos are mandatory, very specific or narrow in focus, technical in nature, define standards, procedures, and guidance, and are created for a limited timeframe with an expiration date (see Tech Memo iHUB page for additional information).

Governance may be published on agency websites or in a:

  • Guidebook/Handbook

    A concise reference book covering a particular subject.

  • Manual

    A comprehensive reference document of instructions and supporting information that is updated on a regular basis.  Manuals communicate expectations, are established for both technical and non-technical areas, and are considered a repository for standards, guidelines, and procedures.
    Note: Some MnDOT manuals are required by FHWA.

Governance Committee

A MnDOT Committee responsible for a broad range of governance matters including but not limited to administrative policy, data governance, data practices, internal controls, mission and vision, risk management, records management, and technology priorities.

Internal Controls

Activities, plans, attitudes, policies, and efforts of MnDOT staff working together to provide reasonable assurance that the agency's strategic priorities are being met. Good internal controls encourage efficiency, comply with laws, regulations, and policies, and seek to eliminate fraud, waste, and abuse.

Minor (Policy) Edit

A non-substantive change or correction of error in a MnDOT policy.

Plain Language

All policies are written in plain language. Plain language is communication your audience can understand the first time they read it or hear it.

It:

  1. Reduces confusion
  2. Saves time and resources
  3. Improves customer satisfaction
  4. Enhances the value of services provided

Plain language techniques include understanding who the reader is, planning and organizing content and writing concisely and simply, which improves overall accessibility for all audiences.

Policy

A formal declaration of an organization’s guiding principles and expectations of employees.  Policies are mandatory, broad and encompassing, and backed by laws, regulations, statutes, or governing authority.

Policy Development Team

Work group responsible for collaboratively drafting policy content. Usually comprised of the Policy Contact and 2-8 additional stakeholders.

Roles and Responsibilities

Decision-making and signature roles and responsibilities

Executive Leadership Team (ELT)
  • Set strategic direction for the agency, evaluate significant high-level agency risk, and make other decisions of importance to the commissioner.
Senior Leadership Team (SLT)
  • Review and approve all new policies.
  • Review and approve policies which substantially change current policy or business practices or pose significant risk to the agency.
Responsible Senior Officer (Deputy Commissioner)
  • Approve and sign all policies.
  • Subject matter of the policy determines which Deputy Commissioner signs the policy
    • Chief Administrative Officer – Administrative, Data Management, Financial, Workforce categories.
    • Chief Engineer - Operations and Engineering category and policies that are technical in nature.
    • If either Deputy is unavailable, the other may sign.
    • Only one deputy signature is required on most policies. Depending on the subject matter, some policies may require the signature of both Deputy Commissioners.
Governance Committee
  • Review and approve new policies and updates to or retirements of existing policies.
  • Chairperson informs SLT of all policy decisions.
  • Refer policies to SLT for approval when any action substantially changes current policy or business practices, poses significant risk to the agency, or introduces new policy or business practices.
  • Chairperson signs all policy documents on behalf of the Committee.
Policy Owner
  • Provide executive leadership on policy development, implementation, related processes/procedures, and compliance.
  • Appoint a Policy Contact for the policy.
  • Consult with Assistant Commissioner and/or Assistant Division Director within the chain of command for subject when a policy action is initiated.
  • Review policies every two years, or sooner as needed, to ensure policy remains up-to-date.
  • Ensure any procedures, processes, education, training, and other resources associated with policy remain current.
  • Communicate to agency employees and other stakeholders when newly adopted, revised, or retired policies are published.
  • Sign the policy document.

Policy development, review process, and production roles

Assistant Commissioner, Chief Financial Officer, Chief Counsel, or Chief of Staff (Policy Sponsor)
  • Initiate or sponsor new policies to address risk, establish direction, or set expectations.
  • Policy Sponsor is required for all new policies.
Office of Chief Counsel
  • Provide legal review and interpretation of policies.
  • Act as legal advisor to Governance Committee; review and advise Committee on policies.
Policy Coordinator (Office of Chief Counsel)
  • Oversee and manage the Agency Policy Program by providing leadership, analysis, design, and development of Agency Policy Program.
  • Receive and review requests for new policies, updates to existing policies, or policy retirements.
  • Work with Policy Owners to ensure accountability for the quality, accuracy, and timeliness of policy updates.
  • Coordinate flow of policy from inception to implementation.
  • Edit and publish policies, ensuring consistency of policies agency-wide.
  • Maintain a standardized format and consistent classification of policies.
  • Confirm Assistant Commissioner/Chief sponsorship of new or revised policies.
  • Research laws, rules, and regulations related to existing policies for currency and accuracy.
  • Serve as a partner to the policy development team to move policy drafts through the approval process.
  • Make and track minor edits to policies and inform Governance Committee of changes.
  • Manage and maintain policies and policy resources by establishing and upholding a policy review cycle and by updating templates, procedures and web pages.
  • Communicate additions or updates to policy definitions to the Business Data Catalog Coordinator.
  • Maintain policies in accordance with the MnDOT Records Retention Schedule.
Policy Sponsor
  • Sponsor new policies, initiate revisions to existing policies, and recommend retirement of policies.
Policy Contact
  • Serve as subject matter expert and first point of contact to answer questions about policy.
  • Provide business-related expertise in drafting and review of policies.
Policy Development Team

The team is convened and led by the Policy Owner or designee and consists of stakeholder representatives and business or technical experts. One or more members of the team – or the Policy Owner – presents the draft policy to Governance Committee for approval.

  • Conduct an equity analysis for each new or updated policy. Comment on draft policy and share expertise.
  • Seek stakeholder feedback on policy drafts, including legal review from the Office of Chief Counsel.
  • Submit completed drafts to Policy Coordinator.
  • Research laws, rules, and regulations related to existing policies for currency and accuracy.
Division Business Manager
  • Review policy drafts from an agency perspective and help identify potential budget and administrative impacts.
  • Advise Policy Owners and help prepare policy presentations for Governance Committee.
Employees
  • Read, understand, and follow MnDOT policies.

Policy Development

Questions to Consider when Determining the Appropriate Type of Governance

  • Is there a federal or state law or another Executive Branch agency policy that requires MnDOT to adopt a policy?
  • Who needs to know about the proposed governance (Employees only? The public? Contractors/consultants)? How will affected parties know it exists? Where would they logically go to find the information?
  • Is there existing governance on the subject matter, such as Statewide Policy, other MnDOT policy, MnDOT Technical Memo, manual, guideline, law, regulation, or rule?
  • Does the subject matter rise to the level of policy or is another form of governance sufficient?
  • Will the governance be used to set expectations, establish internal controls, and/or mitigate risk? Is a policy required to accomplish these objectives?
  • What risk are we trying to mitigate? Consider impact on discretionary immunity (at what level does the governance decision need to be made to ensure discretionary immunity?).
  • Is the governance intended to be long-term or temporary? (Note: policies must be long-term.)
  • Is the governance addressing a department-wide issue or is it limited to a specific office, district or program area? (Note: policies must be department-wide or affect several divisions.)
  • Is there opportunity to consolidate various forms of governance?

Questions to Consider when Adopting a New Policy

  • What procedures, training, resources, and other internal controls are needed to accompany the policy?
  • Should the policy review cycle be one year rather than two? All policies must have a review cycle identified under the Policy Owner responsibilities in the “Responsibilities” section. The default review cycle is every two years. Consider whether the policy needs to be reviewed annually.

Questions to Consider when Revising Current Policies

  • Is the current policy in step with business practices, best practices, customer needs, or emerging trends?
  • Is the policy still needed? Should the policy be retired?
  • Is the existing form of governance appropriate? Consider whether another form a governance could accomplish the same objectives.

Statewide Policies

All agencies are subject to Statewide Policies and MnDOT follows those policies unless otherwise stated. MnDOT may adopt an agency-specific policy with additional restrictions to a Statewide Policy but cannot make a policy that is less restrictive. When presenting a MnDOT-specific policy to the Governance Committee for approval, include the Statewide Policy for reference and the rationale for adopting a MnDOT-specific policy. Rationale for adopting an agency-specific policy may include:

  • addition of restrictions;
  • assignment of responsibilities;
  • clarifications; or
  • the Statewide Policy requires each agency to specifically adopt the policy.

MnDOT-specific policies must be updated when corresponding Statewide Policies are updated.

Collective Bargaining Agreements and Compensation Plans

Always consult the Office of Human Resources – Labor Relations when drafting policies that relate to matters that are covered by a collective bargaining agreement or compensation plan for review of potential interactions. When presenting these policies to the Governance Committee for approval, provide the language from the collective bargaining agreement(s) or compensation plan(s).

Definitions and Approval Requirements

  • New means the policy subject matter is not addressed in current policy and meets the criteria for creation of a policy. New policies require approval by the Governance Committee and the Senior Leadership Team (SLT) and are signed by the Policy Owner, Governance Committee Chairperson, and the Responsible Senior Officer(s).
  • Review means the Policy Owner verifies that the policy content, training, and resources related to the policy are current and do not require significant modifications. Minor edits to the policy may be made following review with Policy Owner approval. Review occurs according to the cycle identified in the policy.
  • Minor edit means non-substantive changes or correction of error. Minor edits are coordinated by the Policy Coordinator and Policy Owner. Corrections of hyperlinks or contact information are not an edit. All edited policies must retain a document history for reference consistent with the Records Retention Schedule. The Policy Owner approves minor edits and the Policy Coordinator informs the Governance Committee.
  • Revise means the policy requires substantive content changes. Revisions require the approval and signature of the Policy Owner, the Governance Committee Chairperson, and the Responsible Senior Officer(s).
  • Retire means the policy is no longer needed. Retirement requires the approval and signature of the Governance Committee Chairperson, and the Responsible Senior Officer(s).

All policies and revision history must be archived pursuant to the Records Retention Schedule.

Phase I – Initiate

To request a change to a policy or to propose a new policy, complete the online form on the MnDOT Governance webpage.

Depending on the request, follow the process to create a new policy or to revise or retire a current policy.

Create New Policy
  1. Policy Coordinator confers with the requester and potential Policy Owner to determine:
    1. business need for the policy;
    2. who will be affected by the policy;
    3. opponents to the policy and possible controversies; and
    4. consequences to adopting or not creating a policy.
  2. When necessary, Policy Coordinator consults with the Tech Memo Coordinator and/or the Administrative Rule Coordinator to determine whether the correct form of governance is a policy, Tech Memo, administrative rule, or something else (see "Determining the Appropriate Type of Governance" section above)..
  3. If determined that a policy is the correct path, Policy Coordinator notifies the Governance Chair of policy development and adds to work plan.
Revise Policy
  1. Policy Coordinator collaborates with the current Policy Owner to determine:
    1. business needs for revision;
    2. who will be affected by the change;
    3. possible opponents or controversies; and
    4. consequences of change.
  2. If determined that there is a need for change, the Policy Coordinator adds to work plan.
Retire Policy
  1. Policy Coordinator collaborates with the current Policy Owner to determine business need (or lack thereof) for the policy.
  2. Policy Coordinator consults with Office of Chief Counsel and subject-matter experts about potential policy retirement.
  3. Policy Coordinator and/or Policy Owner consults with SLT Sponsor about potential policy retirement.
  4. Policy Coordinator consults with Division Business Manager about potential policy retirement.
  5. If Policy Owner, Office of Chief Counsel, SLT Sponsor, DBM, and subject-matter experts concur that the policy should be retired, Policy Coordinator completes the Executive Briefing Tool and requests addition of the policy and any supporting documents to the Governance Committee agenda.
  6. If retirement is approved by the Governance Committee, the Policy Coordinator obtains signature approval by the Governance Committee Chairperson and the Responsible Senior Officer(s).
  7. Policy Owner reviews all published documentation to ensure information is retracted and disposed and/or retired to support the retirement of the policy.
  8. Policy Owner updates any training or other materials that reference the policy.
  9. Policy Coordinator archives retired policies consistent with the Records Retention Schedule.
  10. Policy Coordinator updates the MnDOT policy website and Policy Owner communicates retirement of policy.

Phase II – Pre-development

This phase applies to policy revision and new policy development. Policy Coordinator and Policy Owner (or designee) complete the tasks listed below.

Identify the policy scope

The policy scope must be clear and concise. Properly scoping a policy helps identify key risk elements, compliance requirements, expectations, procedures, and the audience for the policy.

Identify legal or regulatory matters

Consult with the Office of Chief Counsel and business/technical subject matter experts regarding legal or regulatory matters.

Identify related information, such as other forms of business governance

Identify other statewide policies, MnDOT policies, Technical Memos and/or other types of governance related to the policy. Policy Coordinator may collaborate with owners of related MnDOT policies and/or Tech Memos. Research other resources that may be useful to the policy development team, such as Transportation Research Board documents, similar policies at other Minnesota state agencies or other state departments of transportation. Policy Coordinator synthesizes information for policy development work team.

Consult with Assistant Division Director (if applicable), SLT Sponsor for the policy (Assistant Commissioner/Chief), and Governance Committee Chair to confirm support for policy action

The Policy Owner is responsible for the content and accuracy of the policy and accountable for the operation of and compliance with the policy. The SLT Sponsor sets the tone for expectations for employees regarding the policy.

Assemble a policy development work team
  1. Policy Owner recommends a policy contact, who is an agency subject matter expert that will provide expertise during policy development and will serve as the point of contact after policy approval.
  2. Identify team members with legal and technical content and process expertise at MnDOT. Do not only include immediate chain-of-command (think broadly). Limit team to approximately six to ten members.
  3. Invite team members, confirm participation, and prepare the work plan for policy development.
  4. Prepare for the kick-off team meeting with materials such as:
    1. Existing policies, Tech Memos, references to state/federal law, and external guidance (MMB/Admin/MNIT Statewide policies)
    2. Roles and responsibilities
    3. Explanation of the policy development and review process (policy phases)
    4. Review of policy template and use of plain language
    5. Reference materials or related information
  5. Establish an approximate timeline for policy development and Governance Committee presentation. The pace or meeting frequency depends on the subject matter, availability of team members, and the urgency for policy completion, for example, legislative requirement.

Phase III - Development

  1. Policy Work Team Identifies and engages key stakeholders. The policy program depends on:
    1. the professional expertise of its employees;
    2. inclusivity and multiple points of view; and
    3. transparency.
  2. Policy Coordinator facilitates meetings and tracks comments and changes to add content to the policy template. Members of the work team draft content and send the document to the Policy Coordinator.
    1. Policy Coordinator assembles draft content, edits, and recirculates the document to the team for the next team meeting. The Policy Coordinator evaluates and edits drafts to ensure:
      1. consistent style and voice in approved policy template;
      2. alignment with Business Data Catalog (BDC) definitions; and
      3. proper categorization, numbering, tracking, and archiving of MnDOT policies.
    2. Policy Coordinator ensures policies are drafted using plain language. Words and phrases to avoid include:
      1. Us, them, you, your, our, we
      2. Can, could, should, will, would, shall
      3. Since (use “because” instead)
      4. Help, better (i.e. “To help…” or “To better…”)
      5. “But not limited to”
      6. “In order to” (use “to” instead)
    3. Policy Coordinator contacts BDC Coordinator to add new definitions to the BDC and to coordinate existing definitions.
    4. Policy Coordinator ensures Equity Lens Framework is completed.
  3. Policy Owner provides feedback on the draft and revises the document as requested by the Policy Owner and the work team. The drafting process continues until there is a draft ready for stakeholder review that addresses the business matter, using plain language.

Phase IV – Legal, Stakeholder, and Leadership Review

Policy Coordinator facilitates completion of the Policy Approval Checklist. Set the review period for two weeks (extend to accommodate holidays and seasonal vacation schedules). Legal, stakeholder, and leadership review may be conducted separately or in tandem.

Policy Coordinator distributes draft policy for review and feedback to:

  • Stakeholders identified by the work team;
  • Office of Chief Counsel
  • Office of Tribal Affairs; and
  • Agency leadership
    • Policy Owner (typically the Office Director)
    • Division Business Manager (DBM)
    • SLT Sponsor (if needed)
    • Governance Committee Chairperson
Policy Work Team Reviews Feedback
  1. Policy Coordinator assembles comments received and schedules a meeting with the policy work team to review feedback.
  2. Work team evaluates feedback and modifies the draft, as needed.
  3. Policy Coordinator prepares the final policy draft.
Final Review and Submittal
  1. Policy Coordinator reviews final draft with Deputy Chief Counsel or designee.
  2. Policy Coordinator prepares the policy request packet, which includes the Executive Briefing Tool, Approval Checklist, final policy draft, and other supporting documentation.
  3. Policy Coordinator informs the Governance Chairperson that the policy is ready for the Governance Committee agenda.

Phase V – Policy Review by the Governance Committee

Preparation for Governance Committee
  1. Presentation materials must be submitted by the agenda deadline for the scheduled Governance Committee meeting. Required materials include:
    1. Copy of the new or updated policy draft and tracked changes version, if applicable;
    2. Completed Executive Briefing Tool (EBT) summarizing the need for the policy or policy update and feedback received;
    3. Approval checklist including dates of review by legal, SLT Sponsor and DBM, a summary of the communications plans, and analysis showing application of the equity lens; and
    4. Supplementary documents, if applicable:
      1. Guidance/manual/procedures (Note: These documents must be completed before the policy is reviewed by Governance Committee to ensure that individuals are able to abide by the policy as soon as it is approved.)
      2. Risk assessment
      3. Other documents
  2. Policy Coordinator assists Policy Owner in preparing presentation for Governance Committee.
Governance Committee Protocol

The Governance Committee Charter is the guide for determining whether a policy requires SLT approval.

  1. Policy Owner and/or Policy Contact present the policy at the Committee meeting and respond to questions.
  2. The Committee chair entertains a brief discussion on the policy.
  3. The Committee chair calls for a vote on the policy. Policy approval requires a majority vote (see Governance Committee Charter for details).
  4. If policy is not approved, Governance Committee provides feedback and direction for next steps.

Phase VI – Policy Review by the Senior Leadership Team (if needed)

  1. Governance Chairperson adds policy to the SLT agenda and distributes materials prior to meeting.
  2. Governance Chairperson and/or Policy Owner presents to SLT.
  3. SLT considers request and determines whether to approve the policy.
  4. If the policy is not approved, SLT provides feedback and direction for next steps.

Phase VII - Signatures

The Policy Coordinator routes policy for signatures by the Policy Owner(s), Governance Committee Chairperson, and Deputy Commissioner(s). The policy is effective when all signatures are obtained.

Note: In some cases, an effective date may be decided by the Governance Committee or SLT before the policy is routed for signature. In these situations, the effective date is added to the top of the policy document before it is routed rather than after the last signature is obtained. All signatures must be obtained before the agreed upon effective date.

Phase VIII – Policy Publication, Communication, and Implementation

Document publication
  • Policy Coordinator prepares the document for the MnDOT Policy Website. The website serves as the trusted source for policies and information about the Policy Program. All content must be accessible and meet requirements set forth by the Minnesota State Accessibility Standard.
  • Policy Coordinator contacts the Office of Communications and Public Engagement to update the front page of MnDOT’s iHUB intranet site to inform employees about policy activities.
Implementation
  • Policy Owner executes the communications strategy to stakeholders regarding approved policies.
  • Policy Owner works with the Office of Human Resource’s Workforce Development Unit to update or develop and implement employee education and training.
Document preparation for storage
  • Policy Coordinator saves the signed policy in eDOCS, the official repository for policy records.

Phase IX – Maintain Policy for Quality Assurance and Continuous Improvement

Annual or Biennial Review (Dependent on policy)
  • Policy Coordinator manages the policy review cycle and works with the Policy Owner to ensure that timely review of existing policies is completed according to established timelines.
  • Policy Owner verifies the policy content is current and works with Policy Coordinator to make minor edits. If substantive edits are needed, the policy revision is added to the policy work list.
  • Policy Owner verifies that source information such as laws, rules, or other regulations are current.
  • Policy Owner signs the policy review section on the Authorization page. New signatures are not required from the Governance Chair or Responsible Senior Officer.
  • Policy Coordinator reports that review was completed at next Governance Committee meeting (informational – no vote needed).
  • Policy Coordinator saves updated policy document in eDOCS.
Records Retention

Policy management must align with the Records Retention Schedule. The MnDOT Records Retention Schedule sets rules for how long to retain records and the proper disposal of the records at the end of their lifecycle. The MnDOT Records Policy identifies legal obligations and the responsibilities for MnDOT records retention and disposal.

Forms

Related Information

Policy Map

Overview

Visual representation of the policy process overview as outlined below

  1. Policy Coordinator receives policy request (new, revised, retire)
  2. Policy Coordinator determines whether a policy is appropriate (consults with Tech Memo Coordinator, Rule Coordinator, and/or Governance Chair)
    1. If no, Policy Coordinator refers requester to Tech Memo coordinator, Rule Coordinator, or other
    2. If yes, proceed to Policy Development Process
  3. Complete Policy Development Process
  4. Complete Governance Committee Review Process
  5. Governance Committee determines if policy requires SLT approval
    1. If no, Governance Committee determines whether to approve policy
      1. If yes, proceed to Policy Execution Process and publish policy
      2. If no, policy is rejected or Policy Owner/Development Team develop other document
      3. If contingent approval, return to Policy Development Process
    2. If yes, complete SLT Review Process
  6. SLT determines whether to approve policy
    1. If yes, proceed to Policy Execution Process and publish policy
    2. If no, policy is rejected or Policy Owner/Development Team develop other document
    3. If contingent approval, SLT determines whether policy needs to return to Governance Committee or SLT after changes
      1. If Governance, return to Governance Committee Review Process
      2. If SLT, return to SLT Review Process
      3. If neither, proceed to Policy Execution Process and publish policy
  7. Complete Policy Execution Process

Initiate Policy Process (Phase I)

Visual representation of the policy process - phase 1 as outlined below

  1. Requester submits a policy request to the Policy Coordinator.
  2. Policy Coordinator receives request and consults with Tech Memo Coordinator and/or Rule Coordinator.
  3. Policy Coordinator determines whether the require is a policy, tech memo, or rule. (See "Determining the Appropriate Type of Governance" section above.)
    1. If Tech Memo or Rule, Policy Coordinator informs Requester to develop other governance.
    2. If Policy, Policy Coordinator begins Policy Development Process 

Policy Development Process - Pre-development (Phase II)

Visual representation of the policy development process - pre-development - phase 2 as outlined below

  1. Policy Coordinator informs the Governance Chair of the need for a new policy or revision (awareness)
  2. Policy Coordinator notifies the Policy Owner, if the Policy Owner was not the one making the initial request, and completes the policy intake checklist.
  3. Policy Owner consults with Asst. Division Director and SLT Sponsor (AC or Chief) and gains feedback and support for policy.
  4. Policy Owner develops preliminary proposal
  5. Governance Chair reviews proposal, determines whether it’s ok to proceed with policy development, and informs Policy Coordinator of decision.
    1. If no, Policy Coordinator informs Requester and Policy Owner who may appeal to Governance Chair.
    2. If yes, Policy Owner identifies a Development Team (Subject Matter Experts)

Policy Development Process - Development (Phase III)

Visual representation of the policy development process - development - phase 3 as outlined below

  1. Policy Coordinator facilitates policy development meetings and tracks changes and comments; Development Team identifies stakeholders (i.e. people interested in the policy)
  2. Development Team engages critical stakeholders and legal, as needed
  3. Development Team drafts policy
  4. Policy Coordinator reviews and edits draft policy to ensure it complies with policy manual, policy template, and plain language and provides feedback to Development Team; Policy Coordinator works with Business Data Catalog Coordinator to add new definitions to BDC
  5. Development team receives feedback, revises draft policy, and provides to Policy Coordinator until draft is ready for stakeholder review
  6. Policy Coordinator prepares final draft for review

Policy Development Process - Legal, Stakeholder, and Leadership Review (Phase IV)

Visual representation of the policy development process - legal, stakeholder, and leadership review - phase 4 as outlined below

  1. Policy Coordinator submits draft policy for review and feedback to legal, Subject Matter Experts/stakeholders, and agency leadership
  2. Policy Coordinator gathers feedback
  3. Policy Coordinator provides feedback to Policy Development Team
  4. Development Team receives feedback and revises policy draft
  5. Policy Coordinator prepares final draft
  6. Policy Coordinator reviews final draft with Deputy Chief Counsel
  7. Policy Coordinator and Development Team prepare Policy Request Package
  8. Policy Coordinator informs Governance Chairperson that policy is ready for Governance Committee

Governance Review and Approval Process (Phase V)

Visual representation of the governance review and approval process - phase 5 as outlined below

  1. Policy Owner, or designee, works with Division Business Manager to prepare presentation for Governance Committee
  2. Policy Coordinator provides Policy Packet to Governance Chair by agenda deadline
  3. Governance Chair, or designee, distributes Policy Packet to Committee members prior to meeting
  4. Governance Committee members review Policy Packet prior to meeting
  5. Policy Owner, or designee, presents policy to Governance Committee
  6. Governance Committee considers policy request and determines whether to approve policy
    1. If no, Policy Coordinator informs Development Team of rejection and need to develop other form of governance (tech memo, guidance, etc.), if appropriate
    2. If contingent, Governance Committee determines whether policy needs to return to Governance Committee
      1. If yes:
        1. Development Team implements directive(s) and revises policy draft as appropriate
        2. Policy Coordinator provides Policy Packet to Governance Chair by agenda deadline
      2. If no:
        1. Development Team implements directive(s) and revises policy draft as appropriate
        2. Policy Coordinator submits policy to Governance Chair for email vote of approval
        3. Governance Chair distributes to Governance Committee members for email vote
          1. If approved, Governance Committee determines whether SLT approval is required
            1. If no, begin Policy Execution Process
            2. If yes, begin SLT Review Process
          2. If not approved, return to “a.”
    3. If yes, Governance Committee determines whether SLT approval is required
      1. If no, begin Policy Execution Process
      2. If yes, begin SLT Review Process

SLT Review and Approval Process (Phase VI)

Visual representation of the SLT review and approval process - phase 6 as outlined below

  1. Governance Chairperson requests adding policy to SLT meeting agenda and distributes Policy Packet to SLT members for review prior to meeting
  2. SLT adds policy approval item to agenda
  3. Governance Chairperson works with Policy Owner to decide who will present to SLT
  4. Governance Chairperson and/or Policy Owner presents to SLT
  5. SLT considers the policy request and determines whether to approve policy
    1. If no, SLT provides feedback and Policy Coordinator informs Development Team of rejection and need to develop other form of governance (tech memo, guidance, etc.), if appropriate
    2. If yes, SLT informs Policy Coordinator to begin Policy Execution Process
    3. If contingent, SLT provides feedback and determines whether policy needs to return to SLT or Governance
      1. If SLT:
        1. Development Team makes needed revisions
        2. Governance Chairperson requests adding policy to SLT meeting agenda
      2. If Governance, return to Governance Review Process
      3. If neither:
        1. Development Team implements directives and revises policy draft as appropriate
        2. Begin Policy Execution Process

Policy Execution Process (Phases VII and VIII)

Visual representation of the policy execution process - phases 7 and 8 as outlined below

  1. Policy Coordinator obtains signatures from the Policy Owner, Governance Chair, and Responsible Senior Officer
  2. Policy Coordinator requests policy to be published
  3. Communications publishes policy
    1. Policy Owner communicates to audience and educates; and
    2. Governance Chair communicates to SLT that policy is published
  4. Policy Coordinator ensures periodic review of policy