Getta Byte Software
Instructions
| COMMUNICATIONS MATRIX | |
| Column | Instructions For Completing This Document |
| Complete the Project Name, NC, Project Manager Name, and Project Description fields | |
| For each identified communication, complete the following. | |
| A | ID: A unique ID number is used to identify the communication within the communication matrix. |
| B | Communication Vehicle: This column should be populated with a description of the type of communication that will be conducted. |
| C | Target Audience: This field should be populated with a description of the target audience for this communication vehicle. |
| D | Description/Purpose: This field should be populated with a description of the purpose of the communication. |
| E | Frequency: This field should be populated with the frequency of which the communication will be distributed. |
| F | Owner: This field should be populated with the name of the owner of the communication. |
| G | Distribution Vehicle: This field should be populated with the type of distribution vehicle that will be used to disseminate the communication. |
| H | Internal/External: This field should indicate if the communication is for internal, external, or both internal and external distribution. |
| I | Comments: This column should be populated with any additional comments. |
Communication_Plan
| COMMUNICATIONS MATRIX | ||||||||
| Project Name: | <optional> | |||||||
| Project Manager Name: | <required> | |||||||
| Project Description: | <required> | |||||||
| ID eze3: • ID: A unique ID number used to identify the communication within the communication matrix. | Communicaton
Vehicle eze3: • Communication Vehicle: This column should be populated with a description of the type of communication that will be conducted | Target
Audience eze3: • Target Audience: This field should be populated with a description of the target audience for this communication vehicle. | Description/Purpose eze3: • Description/Purpose: This field should be populated with a description of the purpose of the communication. | Frequency eze3: • Frequency: This field should be populated with the frequency of which the communication will be distributed. | Sender eze3: • Owner: This field should be populated with the name of the owner of the communication. | Distribution
Vehicle e: Distribution Vehicle: This filed should be populated with the type of distribution vehicle that will be used to disseminate the communication. | Internal /
External? e: Internal/External: This field should indicate if the communication is for internal, external, or both internal and external distribution. | Comments eze3: • Comments: This column should be populated with any additional comments. |
| 0 | Weekly status report | Project Team | Communicate updated project status | Weekly | John Doe | Internal and External | Full team meeting. We will invite stakeholders when necessary | |
| 1 | Steering Committee review | CEO, CFO, Finance Director, Accounting Director, Sales Director, Project Manager, Data Architect | Upodate current status of the project | Monthly | Project Manager | Meeting | Internal | Sterring Committee |
| 2 | Weekly status report | CEO, CFO, Finance Director, Accounting Director, Project Team | Status update, Key accomplishment, planned work, current timeline | Weekly | Project Manager | Internal | ||
&"Arial,Bold"&8UP Template Version:&"Arial,Regular" 11/30/06 &8Page &P of &N
DropDown_Elements
| Frequency | Internal_External |
| Daily | Internal Only |
| Weekly | External |
| Bi-Weekly | Internal & External |
| Monthly | |
| Bi-Monthly | |
| Quarterly | |
| Semi-Annually | |
| Annually | |