| What is communicated | How communicated | Who to | When |
| Project awareness/purpose/benefits | Email by Sponsor | SMT | Once at project start up |
| Project awareness/purpose/ benefits | Email by SMT cascaded | Departments / sub departments | Once at project start up |
| Project status | Monthly status report by PM | Project Board, Programme Office | Monthly |
| Project status | Verbally, scheduled meets and ad-hoc drop ins by PM | Project Board | Weekly / ad hoc |
| Project purpose, status | Intranet by PM | Anyone who visits | Dynamically |
| Project purpose, status | Presentations by PM | Key stakeholders | At first daily, later less frequently |
| Project purpose, status | One to one meets / interviews by PM | Key stakeholders | Project start up |
| Project plans | One to one meets | Other PMs | During the course of the project |
| Project awareness | Standing agenda item on team meets | Management teams | When management team meets occur |
| Project awareness/benefits | General evangelising by Project Board members | Peers, colleagues | Where appropriate |
| Project awareness/benefits | Posters on department notice boards by PM | Everyone | Weekly / Monthly |
| Project awareness/benefits | Lunch and learn type drop in sessions by PM | Anyone interested | Weekly / Monthly |
| Project awareness/benefits | Intranet | All visitors to site | Dynamically |
| Project awareness/benefits | Team brief | All readers | Monthly |
| Business process changes | Via workshops | Nominated department representatives | According to plan |
| Project risks/issues | Depending on urgency/significance via email. Urgent risks/issues face to face or via phone. Risks and issues reviewed monthly at PB | Sponsor or suitable owner | As they occur |
| Scope change | Project change control process | Project Board | Project Board meets |