Documentation Decay Audit (QA)

Documentation Decay Audit (QA)

1. 01

   Pull a usage report for every knowledge base page touched in the last 90 days

   Sort by last-viewed date and flag anything with zero views since the previous quarter. A page nobody opens is either dead weight or filed where no one looks.

2. 02

   Cross-check high-traffic pages against the tools they describe

   If a runbook references a Slack channel, GitHub repo, or Linear project, confirm that destination still exists. Slite monitors connected tools like Slack, GitHub, and Linear specifically to catch this drift before it reaches a reader.

3. 03

   Interview the two people who own the most client-facing processes

   Ask each to walk through their last delivery without opening the wiki. Every step they describe from memory that is not written down is a gap.

4. 04

   Score each page on accuracy, ownership, and last-verified date

   Three columns, pass or fail. Pages failing two of three go into a rewrite queue with a named owner and a two-week deadline.

5. 05

   Retire or archive anything that has not been verified in two quarters

   Move it to an archive space rather than deleting, so institutional history survives without cluttering search results for the delivery team.

6. 06

   Publish the audit summary to the whole agency, not just leadership

   List what changed, what was cut, and which client retainer deliverables depend on the rewritten pages. Visibility is what keeps the next audit from being ignored.