# Project Communication Plan Template

**Project:** [Project name]
**Project manager:** [Name]
**Sponsor:** [Name]
**Plan version:** [1.0]
**Last reviewed:** [Date]

## 1. Purpose and objectives

- **What this plan covers:** [Scope, phase, or workstream]
- **Communication objective 1:** [Example: Every stakeholder hears about a schedule change from the project team first]
- **Communication objective 2:** [Example: Decisions are recorded within one business day]

## 2. Stakeholders

| Stakeholder or group | Role in the project | Influence and interest | What they need to know | Preferred channel |
|---|---|---|---|---|
| [Sponsor] | [Approves scope and budget] | [High / High] | [Milestones, risks, decisions needed] | [Weekly email, monthly meeting] |
| [Core team] | [Delivers the work] | [Medium / High] | [Tasks, blockers, deadlines] | [Chat thread, standup] |
| [Department heads] | [Provide people or sign-off] | [High / Medium] | [Impact on their team, dates] | [Status page, email] |
| [End users or customers] | [Use the result] | [Low / High] | [What changes and when] | [Announcement, help docs] |

## 3. Communication plan

| Communication | Audience | Purpose | Channel | Frequency | Owner | Artifact | Feedback and response time |
|---|---|---|---|---|---|---|---|
| Kickoff meeting | [Sponsor, core team, key stakeholders] | Align on scope, roles, and timeline | [Video call and shared doc] | Once, at the start | [Project manager] | Kickoff agenda, project charter | [Questions answered before the next meeting] |
| Team standup | [Core team] | Surface blockers early | [Chat thread or 15-minute call] | [Daily] | [Team lead] | Three-line update | [Blockers picked up the same day] |
| Status update | [Sponsor, department heads] | Report progress, health, and decisions needed | [Email with a link to the status page] | [Weekly] | [Project manager] | Progress report with RAG status | [Replies by the next business day] |
| Steering meeting | [Sponsor and decision makers] | Approve scope, budget, or timeline changes | [Meeting] | [Monthly or at milestones] | [Sponsor] | Decision memo, risk register | [Decisions logged within one business day] |
| Change notice | [Teams affected by a change] | Explain what changes and why | [Email or memo] | As needed | [Project manager] | Change memo | [Acknowledged within two business days] |
| Launch announcement | [All users or customers] | Announce go-live and where to get help | [Email, intranet, in-app message] | Once, at launch | [Marketing or comms lead] | Announcement memo | [Questions routed to the support channel] |
| Lessons learned | [Core team and sponsor] | Capture what to repeat and what to change | [Retrospective meeting] | Once, at close | [Project manager] | Lessons learned log | [Each action has an owner] |
| [Add a row] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

## 4. Escalation path

| Level | When to escalate | Who | Response time |
|---|---|---|---|
| 1 | A blocker the team cannot clear itself | [Team lead] | [Same business day] |
| 2 | A risk to a milestone, budget, or quality target | [Project manager] | [One business day] |
| 3 | A change to scope, budget, or the launch date | [Sponsor] | [Two business days] |

## 5. Where information lives

- **Project hub or status page:** [Link]
- **Team chat channel:** [Channel name]
- **Decision log:** [Link]
- **Risk register:** [Link]
- **Meeting notes:** [Link]

## 6. Review schedule

- Review this plan at kickoff, at each milestone, and whenever a stakeholder joins or leaves.
- Ask stakeholders one question at each review: "Are you getting the information you need, at the right time, in the right place?"
- Record changes to this plan here: [Date, what changed, who approved]
