Project Name
Document Version 1.0
Prepared by Jane Doe, ITS
Last Edited July 23, 2016
PLAN
REQUIREMENTS
SOLUTION
ANALYSIS
DESIGN
BUILD
TEST
TRAIN/DEPLOY MAINTENANCE
TO THE DOCUMENT OWNER: This template is provided as a guideline and resource. The structure and instructions
give detail about what might go into a completed document. Only you and your team, however, know what will
best fit the needs of your specific effort, and you are encouraged to adapt the template as appropriate to meet
those needs.
Communication Plan
The Communication Plan identifies the types of communication and documentation that will be delivered
to specified audiences for the project, including customers and other stakeholders. The Communication
Plan specifies the way in which information will be shared and sets the schedule for communications
throughout the project. The plan will be reviewed by key project stakeholders to ensure that all
interested groups and all types of project information are covered, as well as to confirm the plans for
timely delivery of that information.
Executive Summary
Provide a short summary of the project and the communications strategy.
Key Audiences
Give a brief overview of the key audiences for the expected communications. If there are key messages
to be communicated to a specific audience, please note that in the “Key Messages” section.
Key Messages
Provide the key messages that will be communicated to the intended audiences. Provide a description for
each message and the corresponding audience(s). Please consider the following message topics:







Schedule
Progress
Issues and risks
Decisions
Technical instructions
Functional directions
Project documentation
An example would be: Project Schedule – The Project Schedule will provide the key milestone dates for
the project. It will be provided to the Project Team, the Director, and the Steering Committee.
Communication Plan
Page 1 of 2
Project Name
Document Version 1.0
Communication List and Timeline
Provide a list of communication deliverables expected to be developed based on the audiences and key
messages. Examples are provided in the table below. Consider a full range of communication tools,
including targeted and general emails, website announcements, presentations, inclusion on governance
and other group meeting agendas, and sharing of project documentation.
Initial
Schedule
Deliverable/Mode of Communication
Update
Frequency
Audience
Q1 2013
Project status report
Bi-weekly
CSC, Executive
Sponsors
Q1 2013
Project wiki
Weekly
Developers
Q1 2013
ITS project web site
As needed
General public
Q1 2013
Project change requests
Periodically
CSC
Q1 2013
Schedule & budget change requests
Periodically
Executive Sponsors
Q1 2013
Frequently asked questions (FAQs)
As needed
Public
Q3 2013
Installation instructions
As needed
Developers
Q1 2014
Test results
Once
Steering Committee
Q1 2014
Help Desk instructions
As needed
User Services
Q2 2014
Release of product (deployment
announcement)
Once
University
community
Issues/Concerns
List any concerns or issues facing the project that might affect communications.
Notes
List any notes that might affect communications or the timeline.
Revision History
Version
Date
Updater Name
V1
Description
Initial draft completed
Signatures
Formal written signoff is preferred for larger, more complex projects.
Name
Role
Communication Plan
Signature
Date
Page 2 of 2