1. Channels
1.1. CABlink
1.1.1. CABlink page
1.1.2. ICT Newsletter
1.1.3. Non-ICT pages
1.1.3.1. Training
1.1.3.2. Membership services
1.1.3.3. Development
1.1.3.4. CABLegal
1.1.4. Key messages in monthly update
1.1.5. Grapevine
1.2. Face to face
1.2.1. 1-1
1.2.1.1. ITMCs
1.2.1.2. ICTAs
1.2.1.3. BST
1.2.1.4. Bx reps on design groups
1.2.1.5. BMCs
1.2.1.6. Public Direct
1.2.2. 1-x
1.2.2.1. ICT Tech Meetings
1.2.2.2. ICT Management Meetings
1.2.2.3. Membership services events
1.2.2.4. Dev services events
1.2.2.5. Conference
1.2.2.6. Roadshows
1.2.3. Formal/informal
1.2.3.1. Personal contacts/networking
1.3. Paper
1.3.1. Midmonth Pack?
1.3.2. Distributed at events - leaflets etc
1.3.3. Non-ICT Newsletters
1.3.3.1. Arian
1.4. Other online
1.4.1. Blog?
1.4.1.1. Could act as content source for other channels?
1.4.1.2. Integrate into CABlink?
1.4.2. Assume ruling out consumer s media
1.5. email
1.5.1. subscription list?
2. stakeholders
2.1. As for project
2.2. Senior stakeholders out of scope for comms? (direct contact with proj team)
3. messages
3.1. Awareness (early stages)
3.2. Action (towards launch)
3.3. Support and value (internal esp)
3.4. News & updates - is this wanted? For which audience(s)?
4. Key Audiences
4.1. Bureau Managers
4.2. Bureau IT Coordinators
4.3. Training coordinators
4.4. Users
4.4.1. Specialists
4.4.2. Gateway Advisers
4.4.3. Reporting Users
4.4.4. Supervisors
4.4.5. Generalist Advisers
4.5. CItA Internal
4.6. Bureau Partners?
4.7. Logica Internal
5. Timeline
5.1. Work back from launch?
5.2. Announcement of pilot
5.3. Development info
5.4. Business process change Planning
5.5. Technical Planning
5.6. Training
6. 1-way/2-way
6.1. Links with other stakeholders (e.g. PD, MSD)
6.2. Links with support
7. Scope
8. Objectives
8.1. Why are we communicating?
8.2. What do we want people to do as a result of our comms?
8.3. How will we know if it's working?
9. Evaluation
10. Name/Brand???
10.1. Name
10.2. Logo?
10.3. Strapline?
10.4. "The promise you make to your customers"
10.5. Identity as a product and as a project
10.5.1. CASE Replacement or ???
10.5.2. Assume limited scope
10.6. Assume corporate colours etc
10.7. Needs to take a longer view on branding
11. Questions/Issues
11.1. Consultation on implementation? (as per dev process?)
11.2. Roles
11.3. Resources
12. Principles
12.1. honest
12.2. succinct
12.2.1. plain english
12.3. cost effective
12.4. avoid overload - minimum to be effective
13. Resources
13.1. Budget
13.1.1. Assume very limited
13.1.2. Decent branding will need to be commisioned