Develop a Records Management Plan


Documents are tangible artifacts containing data; used to organize data, preserve records, and communicate information.

  • need to create a historical record of some documents
  • contains data
  • some documents are also records

Data is raw information, facts, and figures available within systems and artifacts.

Record is an artifact that preserves historical information needed to operate the business later, such as financial records, business decisions, and operating licenses.

  • are compliance driven

Records management is the process of controlling data throughout its lifecycle.

  • many project decisions are made via team discussions
    • records management involves capturing these decisions within appropriate documents
  • cover which records to keep and how to classify and protect the data

Types of Records

  • Project Management Artifacts
    • artifacts used to manage the project
    • e.g., project budget, stakeholder engagement plan
  • Project Artifacts
    • documents created to move the project along
    • e.g., requirements documentation, blueprints
  • Legal Documents
    • project will generate project contracts and other legally binding agreements
  • Communications
    • meeting notes, status reports, and written communications generate communications records.

Types of Data

  • Public data
    • has no restrictions
    • Anybody can access public data
    • e.g., company website and public records
  • Internal data
    • available to anybody within the company
    • exposing this data wouldn’t violate laws or trust
    • e.g., work procedures and project plans
  • Confidential data
    • limited access
    • only available to authorized users either on a role or case-by-case basis
    • e.g., Personnel records are confidential data
  • Restricted data
    • top secret
    • access is severely restricted
    • highest-security information
    • company is likely to
      • bring criminal charges against unauthorized users
      • face charges if it inadvertently leaks the information
    • e.g., research, top-secret projects, user’s passwords

Requirements of a Records Management Plan

  • The plan needs to comply with organizational policy
  • Records need to be organized and easy to find
  • The plan needs to make information accessible
  • Information needs to be inaccessible to unauthorized users
  • The plan needs to establish accepted communication channels

Elements of a Records Management Plan

  • Every record flows through a three-stage life cycle
  • records management plan should include standards for each stage
  1. Creation
    • define naming conventions, file owners, and who can create files
    • Include data classification standards and confidentiality expectations in this
  2. Storage and Retrieval
    • identify where the team will store files and the file organizational structure
    • Address the process for adding new versions and managing old versions
    • Establish standards for retrieving and sharing the records
    • Set restrictions on downloading or sharing files outside the project team
  3. Archival and Disposition
    • define how to handle duplicate files and outdated files
    • Decide how long records will be archived after the project closes

Example

CreationStorage and RetrievalArchival and Disposition
Naming Convention: Start with “P475”Storage location for project backlog: Portfolio Tool X, Project 475Previous file versions, including emails, downloads, and markups, can be deleted immediately.
Each artifact is in a separate fileStorage location for procedures: Knowledge Base ZUpon closure, project files are retained for seven years per corporate policy.
Use Tool X to apply a classification to all filesStorage location for all other project files: File Share A
Only authorized users may access project files.