Policy Experts / The library

Retiring documents is the neglected half

Nothing in the process prompts anybody to remove one.

Policy libraries only grow. Every trigger produces a new document and no routine event produces a removal, so after a decade an organisation holds documents governing systems it no longer runs, roles that no longer exist, and obligations that have been superseded.

This is not merely untidy. Obsolete documents are still the organisation's stated position, they are still findable by anybody looking, and they can still be cited against it. A superseded procedure that contradicts the current one is a genuine liability rather than dead weight.

Retirement needs to be an explicit action with the same formality as approval: a decision, a date, a reason, and the document moved somewhere clearly marked as no longer in force rather than deleted, since the historical version may still be needed for a past period.

The practical prompt is to require, whenever a new document is approved, an answer to what it replaces. Frequently the answer is nothing, and occasionally it identifies two documents that have been quietly contradicting each other for years.

The one document category that should never be retired quietly is anything a third party relied on. A policy published to customers, students or the public, or referenced in a contract, has an existence outside the organisation, and withdrawing it internally does not withdraw the expectation it created. Those need an explicit communication rather than a version change.