Nearly every guide to keeping an internal wiki current lands on the same fix: name an owner, add a 'last verified' date, and review it on a cadence. Scribelet's own diagnosis goes furthest, naming the owner field itself as a claim that decays, since a departure never bounces a calendar invite. Sync-o's maintenance guide adds an escalation path for a quiet owner. Neither checks that name against who is still on the team, or ties staleness to whether the page held up the last time someone relied on it.
This pack checks both. On the worked example, Iveston Systems, an invented platform engineering team with 84 documented topics, cross-referencing every named owner against the current roster found 11 who had already left. Checking how many other people had ever substantively edited or reviewed each topic found 23 with a backup count of zero. Seven topics carried both flags, the highest-risk tier, ranked ahead of anything sorted by edit date alone.
The Staleness Report is the confirmation layer. This quarter's incident log showed 37 of 53 incidents consulted a topic from the register, and post-incident review flagged 9 of those 37 as not matching production. Two of the nine came from the seven-topic highest-risk tier, a 28.6 percent failure rate against 9.1 percent for everything else, 3.1 times higher from a slice that is only 8.3 percent of the register. Getting that knowledge out of one person's head before it ever reaches this register is the SME interview pack.
Internal Knowledge Base Template