Content Lifecycle: Creation, Review, Deprecation, Archival

Knowledge has a lifecycle. It is created, it is used, it becomes outdated, it is updated or deprecated, and eventually it is archived or deleted. A knowledge system without lifecycle management is a system that never removes anything — which means that three years after launch, a user searching for the onboarding process finds seventeen documents ranging from the current one to versions from 2021 that describe a process that no longer exists. The inability to distinguish current knowledge from deprecated knowledge is one of the primary reasons users stop trusting knowledge systems.

Lifecycle management requires four defined stages and a governance process for moving content between them.

1. Stage 1: Creation A new knowledge artifact is created, passes the schema validation (required fields completed, naming convention followed), is reviewed by the domain owner or a designated peer reviewer, and is published. The publication process assigns an owner, sets a review date, and makes the artifact discoverable. No document is published without an assigned owner and a review date.
2. Stage 2: Active Use The document is current, in use, and maintained. The governance system monitors for the review date. When the review date approaches, the owner receives an automated notification to confirm the document is still accurate. Confirmation is a five-second action: 'still current, extending review date by 12 months.' Failure to confirm within 30 days triggers an escalation — first to the domain lead, then to the central KM function.
3. Stage 3: Deprecation When a document is superseded by a new version, a changed process, or an organizational change, it is moved to deprecated status rather than deleted. Deprecated documents are not surfaced in default search results but remain accessible via direct link or filter. Every deprecated document should include a 'superseded by' pointer to the current document. Deprecation without a replacement pointer is the governance failure that creates dead ends.
4. Stage 4: Archival Documents deprecated for more than 12 months, or documents related to completed projects or retired products, are archived. Archived documents are removed from the active knowledge base and stored in a read-only archive. They are not indexed for standard search but can be retrieved by administrators or for historical reference. The archive is not a trash folder — it is a historical record with deliberate access controls.

Review cadence should be calibrated to the volatility of the content. A policy document governing employment terms changes rarely and might have a 24-month review cycle. A sales process runbook in a company that is rapidly evolving its GTM motion might need a 90-day cycle. An AI integration configuration guide might need a 60-day cycle because the tools change that fast. One-size review cycles are a governance simplification that works against the goal — the content with the fastest decay rate needs the shortest review cycle.