Separate age from validity.
An old document is not necessarily wrong, and a recent one is not necessarily reliable. A review date records an activity; it does not explain the result of that review. A reference collection needs a visible way to express whether an item remains approved for its intended use.
Define a few states that people can act on. A draft is not ready for routine use. An approved reference has a responsible owner. An item under review may need a warning. A retired reference should explain where the reader should go next, when there is a replacement.
Keep the state names plain. If readers cannot distinguish “validated” from “verified,” the distinction probably belongs in a simpler set of rules.
Assign responsibility at the right level.
A collection administrator can maintain the platform without being able to judge every document. Subject ownership and platform administration are different responsibilities. Record the role or team that can confirm the content, and define who receives a correction request.
Where possible, use responsibilities that survive staff changes. An operational role may be more durable than an individual’s name, provided someone actually monitors the associated channel.
A useful owner record also explains what happens when responsibility is unclear. Otherwise, unowned references tend to remain in circulation because nobody feels able to remove them.
Make review proportional to change.
Not all resources need the same interval. A stable technical explanation and a frequently changing operational instruction have different maintenance needs. Review timing should consider how quickly the underlying subject changes and the consequences of relying on an outdated version.
Give the reviewer a short checklist: does the information still apply, do the links work, is the responsible role correct, and has a newer resource replaced it? A review should result in confirmation, correction, escalation, or retirement.
Start with an achievable schedule. A complicated review policy that no one can carry out is less useful than a modest routine that produces clear decisions.
Retire without creating a dead end.
Removing an item from normal discovery may be appropriate while retaining a limited historical record. The right treatment depends on the organization’s obligations and the purpose of the collection. Do not silently delete information that another process still references.
When a replacement exists, provide a visible link and a concise explanation. When no replacement exists, explain that the original should no longer guide current work. Search and navigation should distinguish retired material from active guidance.
Check incoming links and dependent records before removal. Retirement is a change to a small network of information, not only a status field on one document.
Watch for signs of maintenance friction.
Repeated correction requests, missing owners, and long review queues can reveal where the operating model is too demanding. These observations can guide simplification: fewer states, clearer responsibilities, or a smaller collection.
The aim is a reference space that readers can interpret and maintainers can sustain. Keeping everything forever is not the same as preserving useful knowledge.