In addition to the technical requirements specification document, the content plan document is used to support the intranet implementation project. The plan can be also called content concept plan or content structure plan.

In my previous post, I discussed the Three functions of an intranet framework which provides a helpful tool for intranet content planning.

Today, the intranets are no longer just “internal websites” with static content in hierarchical content structures. They are digital workplaces with several applications. The framework helps to set roles to the applications.

The intranet or digital workplace content concept should outline both the roles of the applications and the logic of the content sets.

The content plan is created in collaboration with the content creators’ network and used to guide the content creation work. The technical implementation partner is involved in planning the page templates for different content types.

To communicate the planned content, the plan may contain e.g. the following:

1. Service description

  • Goals and targets
  • Users
  • Basic concept
  • Style policies

2. Content concept/structure

  • Support for distribution of official information, common culture and employeeship, support for job tasks and processes, and coordination of work, creation of new information.
  • Targets, role, purpose of use, content, style
  • Page and content types for each content section

3. Publishing and editing policies

Guidelines, allowed publishers, approval processes, and objectives for publishing different content types. This includes e.g. instructions updates, publishing news, event announcements…

4. Page and content types

For each page template: purpose of use, page template elements, possible wireframe images for each page and content type.

5. Content creator checklist

Short checklists for the most common situations.