Information Management

Information management makes sure everyone on the programme can find the current, approved version of what they need, that sensitive information is protected, and that records are kept for as long as they must be and no longer. It is the plumbing that Knowledge Management and Knowledge Transfer depend on.


What is Information Management?

Definition: Information management is the set of standards, processes and tools a programme uses to create, store, control, share, protect, retain and dispose of its documents, records and data.

Programmes produce far more information than single projects: board papers, plans, designs, contracts, benefits data, supplier reports and the records of every decision. Several projects and suppliers create and change that information at once, so without shared rules it fragments quickly.

Without information management With information management
Several “final” versions of the same document One controlled version, with history
Decisions that cannot be traced back to evidence An audit trail from decision to supporting records
Personal data stored wherever it was convenient Sensitive data classified, access-controlled and retained correctly
Handover to business as usual is a file dump Records transferred in a known structure with owners

The Information Lifecycle

flowchart LR A[Create or
receive] --> B[Classify
and store] B --> C[Review and
approve] C --> D[Share and
use] D --> E[Retain] E --> F[Archive or
dispose] D -->|Change| C classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D,E,F blue
Stage What happens Programme control
Create or receive Documents drafted, data collected, supplier deliverables received Templates, naming convention
Classify and store Information placed in the agreed location with metadata File plan, security classification
Review and approve Content checked and signed off Approval workflow, version management
Share and use Information made available to those who need it Access rights, distribution lists
Retain Records kept for the required period Retention schedule
Archive or dispose Records archived for business as usual or securely destroyed Handover plan, disposal log

The Information Management Strategy

Agree an information management strategy during programme definition. It sets the rules that every project in the programme follows. Keep it short and practical; a few pages is enough for most programmes.

Section What to include
Scope Which information the strategy covers: documents, records, data, email, collaboration spaces
Repository and file plan Where information lives and the folder or library structure
Naming and versioning File naming convention and version numbering rules
Classification Security levels (for example Public, Internal, Confidential) and how to apply them
Access control Who can see and change what, and how access is granted and removed
Personal data How data protection law applies, data processing records and privacy impact assessments
Retention and disposal How long each record type is kept and who authorises disposal
Supplier information How suppliers submit, store and return information, as written into contracts
Roles Who owns, manages and audits information
Handover How records move to business as usual when the programme closes

Roles and Responsibilities

Role Responsibility
Senior Responsible Owner Accountable for information risk on the programme
Programme manager Makes sure the strategy is followed across projects
Programme office Runs the repository, file plan, document control and audits
Information asset owners Own specific record sets, such as the benefits register or contracts
Project managers Apply the strategy within their projects
Data protection officer Advises on personal data and privacy impact assessments

Key Records to Control

These records need formal control on almost every programme:

  • Programme mandate, brief and business case
  • Blueprint and benefits map, with benefit profiles
  • Programme and tranche plans
  • Board papers, minutes and the decision log
  • Risk, issue and dependency registers
  • Contracts, supplier deliverables and acceptance records
  • Assurance and review reports
  • Handover and acceptance records for each transition

Common Pitfalls

Pitfall Fix
Each project or supplier sets up its own repository Set up one programme repository before projects start, and require it in contracts
Naming convention exists but nobody follows it Keep it simple, use templates with names built in, and audit monthly
Access is granted but never removed Review access at each tranche end and when people leave
Retention is ignored until closure Agree the retention schedule in definition and apply it as records are created
Handover to business as usual is left to the last week Plan records handover as part of transition

Information Management Checklist

Programme definition

  • Information management strategy agreed?
  • Repository and file plan set up?
  • Naming, versioning and classification rules published?
  • Retention schedule agreed?
  • Information requirements written into supplier contracts?

During delivery

  • Access reviewed at each tranche end?
  • Monthly spot-check of naming and version control?
  • Privacy impact assessments in place where personal data is used?

At closure

  • Records handed over to business as usual owners?
  • Records past retention securely disposed of, with a disposal log?
  • Repository archived and access removed?

Last updated: 17 November 2026