Knowledge Base Audit

One filtered view over your wiki that lists every page nobody opened in 90 days. You either update each page or archive it. The wiki stops rotting. Quarterly ritual, under an hour, keeps the whole thing trustworthy.

Wikis do not fail by being too small. They fail by being too large. Ten pages with current info beats 200 pages where 140 are wrong. This template makes deletion a scheduled action. The workspace that removes pages is the workspace that stays readable.

No new database. One filtered view of the existing Knowledge Base. Last edited 90+ days ago, sorted oldest first. Plus a status column (keep, update, archive) and an audit log of quarterly runs.

Once a quarter, the ops lead opens the audit view. Each row gets a status: keep (still correct), update (owner fixes it), or archive (no longer relevant). Keep pushes the review date forward. Archive moves the page to an Archive database. The wiki shrinks by 20-30% each audit and gets more trusted, not less.

The first failure is "keep" becoming the default. The ops lead runs out of time and marks everything keep. Nothing gets archived. Fix: the audit ritual has a budget. If you cannot audit all 40 flagged pages in one sitting, only the ones you audited keep; the rest auto-archive at the end of the quarter.

The second failure is archiving pages that were still being used by someone quiet. Fix: archive is a soft move to a separate database, not a delete. Anyone can rescue an archived page for 30 days.