Ops & Chief of Staff · Audit & Maintain
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.
Works acrossConfluenceGoogle Docs
What you get.
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.
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.
What changes.
- 01Audit frequencyBefore · Never, or once a quarter when someone complainsWith Doe · First Monday of each month, automated
- 02Stale page detectionBefore · Discovered when someone follows an outdated runbook during an incidentWith Doe · Pages with deprecated references flagged before they cause problems
- 03Ownership assignmentBefore · Nobody owns documentation maintenanceWith Doe · Suggested owners based on codebase and team ownership
- 04PrioritizationBefore · All stale docs treated equallyWith Doe · Runbooks ranked critical, onboarding docs escalated before new hire start dates
How Doe audits your knowledge base
- 01Scans Confluence for stale pages, deprecated references, and broken linksConfluence2,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.
- 02Scans Google Docs for stale shared docs and outdated referencesGoogle 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.
- 03Prioritizes findings by impact and assigns suggested ownersDoeStaleness 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.
- 04RecurringFirst Monday of each monthMonthly audit with month-over-month trend tracking. Unfixed findings from the prior run get escalated. Staleness report in Doe.
Up and running in under ten minutes.
- 01Connect your toolsOne-click OAuth for each integration. No API keys, no engineering.
- 02Describe 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.”
- 03It runs on scheduleRuns on the first Monday of each month. Staleness report available in Doe.
Before you delegate.
- 01How does Doe know which references are deprecated?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.
- 02Can it scan Notion instead of Confluence?Yes. Doe supports Confluence, Notion, and Google Docs. Most teams have docs scattered across multiple tools, and Doe can scan all of them in a single audit run.
- 03Does it auto-fix stale pages?No. Doe identifies issues and suggests owners. Documentation updates require human judgment about what the correct content should be.
- 04What counts as "stale"?By default, any page not updated in 12 months is flagged. You can adjust this threshold per space or doc folder. Runbooks might use a 6-month threshold while policy docs might use 18 months.
- 05Can it track whether flagged pages actually get fixed?Yes. Each monthly run compares against the previous run. If a flagged page was updated, it drops off the report. If it was flagged two months in a row with no change, it gets escalated.