Find the stale docs before someone follows them during an incident
Doe scans Confluence and Google Docs monthly, flags deprecated CLI commands in runbooks, catches broken links, and ranks every finding by impact. Incident runbooks get critical priority; onboarding docs escalate before new hire start dates.
Confluence and Google Docs scanned for pages not updated in 12+ months, deprecated tool references, broken links, and stale onboarding docs. Findings prioritized by impact (incident runbooks ranked highest) with suggested owners based on codebase ownership.
What changes
| Dimension | Before | With Doe |
|---|---|---|
| Audit frequency | Never, or once a quarter when someone complains | First Monday of each month, automated |
| Stale page detection | Discovered when someone follows an outdated runbook during an incident | Pages with deprecated references flagged before they cause problems |
| Ownership assignment | Nobody owns documentation maintenance | Suggested owners based on codebase and team ownership |
| Prioritization | All stale docs treated equally | Runbooks ranked critical, onboarding docs escalated before new hire start dates |
How Doe audits your knowledge base
Confluence2,147 pages scanned across 34 spaces. 892 pages not updated in 12+ months. 124 pages reference tools or services that no longer exist in the codebase. 47 pages have broken links. 18 runbooks reference deprecated CLI commands or old infrastructure.
Google Docs340 shared docs scanned in the Engineering and Operations folders. 89 docs not updated in 12+ months. 12 onboarding docs reference team structures that changed in the last reorg. 3 docs have "DRAFT" in the title but are linked from Confluence as if they are final.
Staleness report prioritized: 18 runbooks with deprecated commands (critical), 12 onboarding docs (high, new hires starting next month), 47 broken links (medium). Each finding includes the page URL, last editor, what is likely wrong, and a suggested owner by codebase ownership. Total: 167 pages need attention, down from 212 last month.
Half your wiki hasn't been touched in a year
Your wiki has 2,000 pages. Half haven't been touched in a year. New hires follow outdated onboarding docs. Engineers reference stale runbooks during incidents. Nobody owns "keeping docs current" so nobody does it.
During a P1 incident, the on-call engineer followed the payment-api runbook in Confluence. Step 4 referenced a CLI tool that was deprecated 6 months ago. Step 7 referenced an AWS region the team migrated away from in November. The engineer lost 15 minutes figuring out what was wrong with the runbook instead of fixing the incident. The page was last edited 14 months ago.
Get started in under 10 minutes
Connect your tools
One-click OAuth for each integration. No API keys, no engineering.
Describe what you need
“On the first Monday of each month, scan all Confluence spaces and shared Google Docs folders for pages not updated in 12+ months, references to deprecated tools or infrastructure, and broken links. Prioritize runbooks as critical and onboarding docs as high. Suggest an owner for each finding based on the team that owns the related codebase.”
It runs on schedule
Runs on the first Monday of each month. Staleness report available in Doe.
Knowledge Base Freshness Audit FAQ
Doe cross-references documentation content against your connected tools and codebase. If a runbook mentions a CLI command that no longer exists or an AWS region your team migrated from, it flags it. You can also provide a list of known deprecations.
Related workflows
Stop doing the work your tools should do for you.
Set it up once. Doe runs it every time.
