*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
-
Created by
user-7ed06, last updated by user-32c34 on Jul 19, 2010
1 minute read
Item |
How often? |
Responsible party |
|---|---|---|
CPMM Communication Guide |
Annual |
|
CIT Audience and Channels Checklist |
Annual |
|
Telecommuting Guide |
|
|
Tier 0 - Service Communication Plans |
Annual |
Service owners |
Style Guide |
|
|
Usability Practices |
|
|
Browser Compatibility Guide for Administrative Services |
|
|
News Moderator Best Practices |
|
|
Cost Saving Tips |
6 months |
|
FOR CIT |
Weekly |
|
|
|
|
|
|
|
|
|
|
|
|
|
1 Comment
user-2ae9f
Jul 12, 2010On the CPMM, I'd recommend an update happen at least twice yearly, or even quarterly. Ideally, C&O people who discover changes to lists or contacts would make them as discovered. In lieu of that, can we make a repository of known changes in one place, like a Confluence space? Kind of a dumping ground until update time?