Knowledge base freshness review

Internal documentation is written once and never checked again, so people follow steps for a process that changed last year and lose an hour before they notice. Search then ranks the stale page above the current one, because freshness is not a signal anyone applies. The review makes ownership explicit. Every page has a named owner, a last-reviewed date, and an interval that matches how fast the process changes: monthly for anything operational, quarterly for policy, yearly for background reading. The pass works from usage rather than from a full read. Pages linked from recent support answers, from onboarding docs, and from the last three months of chat questions are checked first, because those are the pages people actually follow. Each one gets one of three verdicts: confirmed, revised, or archived. Archived pages are not deleted, they are moved out of the default search path with a pointer to whatever replaced them. A short changelog at the top of a page says what changed and when, which is often enough to answer the question that sent someone there in the first place. A person still decides whether a page is accurate, whether a change deserves a new page, and when a process is genuinely settled.