<PROJECT NAME>

IMPLEMENTATION PLANNING
Version <1.0>
<mm/dd/yyyy>

[Insert appropriate Disclaimer(s)]

 <Project Name>

VERSION HISTORY
[Provide information on how the development and distribution of the Implementation
Planning Template up to the final point of approval was controlled and tracked. Use the
table below to provide the version number, the author implementing the version, the
date of the version, the name of the person approving the version, the date that
particular version was approved, and a brief description of the reason for creating the
revised version.]
Version Implemented Revision Approved Approval Reason
# By Date By Date

1.0 <Author name> <mm/dd/yyyy <name> <mm/dd/yyyy> <reason>

>

Implementation Planning Template (v1.0) Page 2 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

Note to the Author

[This document is a template of an Implementation Planning document for a project. The template
includes instructions to the author, boilerplate text, and fields that should be replaced with the values
specific to the project.

 Blue italicized text enclosed in square brackets ([text]) provides instructions to the document
author, or describes the intent, assumptions and context for content included in this document.

 Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced
with information specific to a particular project.

 Text and tables in black are provided as boilerplate examples of wording and formats that may be
used or modified as appropriate to a specific project. These are offered only as suggestions to
assist in developing project documents; they are not mandatory formats.

When using this template for your project document, it is recommended that you follow these steps:
1. Replace all text enclosed in angle brackets (i.e., <Project Name>) with the correct field values.
These angle brackets appear in both the body of the document and in headers and footers. To
customize fields in Microsoft Word (which display a gray background when selected):
a. Select File>Properties>Summary and fill in the Title field with the Document Name and
the Subject field with the Project Name.
b. Select File>Properties>Custom and fill in the Last Modified, Status, and Version fields
with the appropriate information for this document.
c. After you click OK to close the dialog box, update the fields throughout the document with
these values by selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update
an individual field by clicking on it and pressing F9. This must be done separately for
Headers and Footers.
2. Modify boilerplate text as appropriate to the specific project.
3. To add any new sections to the document, ensure that the appropriate header and body text
styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and
Heading 3. Style used for boilerplate text is Body Text.
4. To update the Table of Contents, right-click and select “Update field” and choose the option-
“Update entire table”
5. Before submission of the first draft of this document, delete this “Notes to the Author” page and
all instructions to the author, which appear throughout the document as blue italicized text
enclosed in square brackets.]

Implementation Planning Template (v1.0) Page 3 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

TABLE OF CONTENTS
1 INTRODUCTION...........................................................................................................5
1.1 Purpose of Implementation Planning.............................................................5
1.2 Implementation Objectives.............................................................................5
1.3 Assumptions...................................................................................................5
1.4 Constraints.....................................................................................................5
2 PLANNING....................................................................................................................5
2.1 Roles and Responsibilities.............................................................................5
2.2 Workforce Changes.......................................................................................5
2.3 Employee Transition......................................................................................6
2.4 Business Process...........................................................................................6
2.5 Technology Requirements.............................................................................6
2.6 Communication Approach..............................................................................6
2.7 Data Conversion Approach............................................................................6
2.8 Verification and Validation.............................................................................6
3 IMPLEMENTING...........................................................................................................6
3.1 Roles and Responsibilities.............................................................................6
3.2 Workforce Changes.......................................................................................6
3.3 Employee Transition......................................................................................6
3.4 Business Process...........................................................................................6
3.5 Technology Requirements.............................................................................7
3.6 Data Conversion............................................................................................7
3.7 Verification and Validation.............................................................................7
4 TRANSITIONING..........................................................................................................7
4.1 Training..........................................................................................................7
4.2 Technical Document......................................................................................7
APPENDIX A: IMPLEMENTATION PLANNING APPROVAL........................................8
APPENDIX B: REFERENCES..........................................................................................9
APPENDIX C: KEY TERMS............................................................................................10

Implementation Planning Template (v1.0) Page 4 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

1 INTRODUCTION
1.1 PURPOSE OF IMPLEMENTATION PLANNING
[Describe the purpose of the Implementation Planning.]
The intended audience of the <Project Name> Implementation Planning is the
Business Sponsor and the Integrated Project Team.
1.2 IMPLEMENTATION OBJECTIVES
[Describe objectives of the Implementation Planning.]
 [Insert description of the first objective.]
 [Insert description of the second objective.]
 [Add additional bullets as necessary]
1.3 ASSUMPTIONS
This section identifies the statements believed to be true for the implementation of
the product or IT system.
 [Insert description of the first assumption.]
 [Insert description of the second assumption.
 [Add additional bullets as necessary]
1.4 CONSTRAINTS
This section identifies any limitation that must be taken into consideration prior to
the implementation of the product or IT system.
 [Insert description of the first constraint.]
 [Insert description of the second constraint.]
 [Add additional bullets as necessary]

2 PLANNING
[Describe the strategy, potential impacts, and activities that will be addressed in
planning for the implementation. ]

The <Project Name> Implementation Planning provides an outline of activities

necessary to ensure that the project’s product is available for use by its end-users
as originally planned.
2.1 ROLES AND RESPONSIBILITIES
[Describe the plans for implementing changes to current roles and job
responsibilities/functions. Roles include the project sponsor, project and customer
stakeholders, end users of the project’s product, integrated project team, etc]
2.2 WORKFORCE CHANGES
[Describe the plans for implementing changes to workforce relocations, increases,
reductions, etc]

Implementation Planning Template (v1.0) Page 5 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

2.3 EMPLOYEE TRANSITION

[Describe the plans for implementing changes to employee morale, training,
retention, etc]
2.4 BUSINESS PROCESS
[Describe the plans for implementing changes to business processes, workflows,
reporting, etc. This may also include policy and procedure changes.]
2.5 TECHNOLOGY REQUIREMENTS
[Describe the plans for implementing changes to current technology requirements.
This could include selection of hardware and software, testing requirements,
installing and testing the actual system, etc]
2.6 COMMUNICATION APPROACH
[Describe the strategy and processes for communicating the changes that are being
implemented. This strategy may have been included in the Communications Plan.]
2.7 DATA CONVERSION APPROACH
[Describe the data conversion strategy. Be sure to consider any dependencies
between activities]
2.8 VERIFICATION AND VALIDATION
[Describe the approach to ensure that the new system is completely operational and
available to the end users]

3 IMPLEMENTING
[Implementing the project’s product is the act of actually making the project’s
product available for use by the customer and its user community]

The <Project Name> Implementation Planning provides an outline of activities and

steps that are necessary to ensure that the project’s product is available for use by
its end-users as originally planned.
3.1 ROLES AND RESPONSIBILITIES
[Describe the steps that need to be executed to implement changes to roles and
responsibilities]
3.2 WORKFORCE CHANGES
[Describe the steps that need to be executed to implement changes to workforce
relocations, increases, reductions, etc]
3.3 EMPLOYEE TRANSITION
[Describe the steps that need to be executed to implement changes for employee
transition activities]
3.4 BUSINESS PROCESS
[Describe the steps that need to be executed to implement the changes to the
business processes]

Implementation Planning Template (v1.0) Page 6 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

3.5 TECHNOLOGY REQUIREMENTS

[Describe the steps that need to be executed to implement the changes to current
technology requirements. Be sure to consider any dependencies between the
activities and system installation, configuration and testing]
3.6 DATA CONVERSION
[Describe the steps that need to be executed to convert the data from the old
system to the new system. Be sure to consider any dependencies between
activities]
3.7 VERIFICATION AND VALIDATION
[Describe the steps that need to be executed ensure that the new system is
completely operational and available to the end users]

4 TRANSITIONING
[Describe the strategy and activities that will be addressed once the
implementation has taken place]
The <Project Name> transitioning activities will ensure an orderly migration of
existing data and users from the old system to the new system.
4.1 TRAINING
[Describe the training activities that need to take place to complete the transition to
the new system]
4.2 TECHNICAL DOCUMENT
[Describe the activities that need to take place to complete the creation and
transition of the technical document to those who will support the new system]

Implementation Planning Template (v1.0) Page 7 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

APPENDIX A: IMPLEMENTATION PLANNING APPROVAL

The undersigned acknowledge they have reviewed the Implementation Planning
and authorize and fund the <Project Name> project. The undersigned herby give
the project manager the authority to apply the approved level of organizational
resources to project activities. Changes to this Implementation Planning will be
coordinated with and approved by the undersigned or their designated
representatives.
[List the individuals whose signatures are desired. Examples of such individuals
are Business Sponsor and Project Manager. Add additional lines for signature as
necessary. Although signatures are desired, they are not always required to move
forward with the practices outlined within this document.]

Signature: Date:
Print Name:
Title:
Role:

Signature: Date:
Print Name:
Title:
Role:

Signature: Date:
Print Name:
Title:
Role:

Implementation Planning Template (v1.0) Page 8 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

APPENDIX B: REFERENCES
[Insert the name, version number, description, and physical location of any
documents referenced in this document. Add rows to the table as necessary.]
The following table summarizes the documents referenced in this document.
Document Description Location
Name and
Version
<Document [Provide description of the <URL or Network path where
Name and document] document is located>
Version
Number>

Implementation Planning Template (v1.0) Page 9 of 10

[Insert appropriate disclaimer(s)]
 <Project Name>

APPENDIX C: KEY TERMS

[Insert terms and definitions used in this document. Add rows to the table as
necessary. Follow the link below to for definitions of project management terms
and acronyms used in this and other documents.]

The following table provides definitions for terms relevant to this document.
Term Definition
[Insert Term] [Provide definition of the term used in this document.]

[Insert Term] [Provide definition of the term used in this document.]

[Insert Term] [Provide definition of the term used in this document.]

Implementation Planning Template (v1.0) Page 10 of 10

[Insert appropriate disclaimer(s)]