Professional Technical Consultant Services

Scope Template Library

See Something | Say Something

Project Manager's play an important role in ensuring the Scope Template Library is up to date. As you compile your scope documents, if you notice something is out of date, reach out to the lead project manager in your district [Project Management Leadership Group (PMLG) Membership]. The PMLG maintains the scopes that reside in the Scope Template Library.

Missing Table of Contents

Occasionally, there may be a misconfiguration with Microsoft Word which would not prompt you to update automatic links to generate the table of contents. As a temporary work around, use the following steps.

1. Close all open Microsoft Word documents.
2. Open a new, empty Microsoft Word document.
3. Select File > Options to open the setting window.
4. Select the Advanced tab and scroll to the General section.
5. Select to enable the update automatic links checkbox.
6. With the empty file still open, open the scope of work document and you should be prompted to update fields to generate the table of contents.

Introduction

This template database is set up as an a la carte system with a library of existing standard scopes for use by project managers. There are many work package topics included in the database, and additional work package templates may be added in the future. A list of work package topics can be found in the User Guide and Administrative Manual link to the right (page 7).

MnDOT has built this scope of work template database to be easy to use and allow flexibility while setting a baseline standard for consistency and readability for scopes of work among all Districts and project managers. The goal of this scope of work database is to create efficiencies in preparing consistent scopes of work and removing incomplete or unclear scope language that is open for interpretation.

To get started, you will need:

1. Description of the project to be covered by the scope of work
2. List of P6 work packages required to complete the project
3. Draft P6 schedule for project

Document Requirements

Plain Language

All deliverables must be provided in “Plain Language,” as defined in Governor Mark Dayton’s Executive Order 14-07 which requires the Office of the Governor and all Executive Branch agencies to communicate with Minnesotans using Plain Language. As defined, Plain Language is a communication which an audience can understand the first time they read or hear it, providing Minnesotans better state services by reducing confusion, saving time, and improving customer satisfaction. To achieve that, the following steps must be taken:

• Use language commonly understood by the public;
• Write in short and complete sentences;
• Present information in a format that is easy-to-find and easy-to-understand; and
• Clearly state directions and deadlines to the audience.

For guidance read the Federal Plain Language Guidelines.

ADA

Consultants must ensure that all documents and content provided to MnDOT, for posting on MnDOT’s public website, or shared electronically, meet the provisions of the State of Minnesota’s Accessibility Standards: including Minnesota’s accessibility standard for electronic documents.

Both state and federal ADA law requires that all documents posted online must be ADA compliant, which ultimately helps improve understanding among all audiences. MnDOT will provide consultants with access to resources for accessible documents, emails and webpages.