Ops & Chief of Staff
Find the stale docs before someone follows them during an incident
ZeroTwo scans Confluence and Google Docs monthly, flags deprecated CLI commands in runbooks, catches broken links, and ranks every finding by impact.
What changes
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
Half your wiki hasn't been touched in a year
Your wiki has 2,000 pages. Half haven't been touched in a year.
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.
How ZeroTwo audits your knowledge base
Scans Confluence for stale pages, deprecated references, and broken links
Confluence2,147 pages scanned across 34 spaces. 892 pages not updated in 12+ months. 124 pages reference tools or services that no longer exist. 47 pages have broken links. 18 runbooks reference deprecated CLI commands or old infrastructure.
Scans Google Docs for stale shared docs and outdated references
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.
Prioritizes findings by impact and assigns suggested owners
GoogleStaleness report prioritized: 18 runbooks with deprecated commands (critical), 12 onboarding docs (high, new hires starting next month), 47 broken links (medium). Total: 167 pages need attention, down from 212 last month.
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 ZeroTwo.
Frequently asked questions
ZeroTwo 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.
Yes. ZeroTwo supports Confluence, Notion, and Google Docs. Most teams have docs scattered across multiple tools, and ZeroTwo can scan all of them in a single audit run.
No. ZeroTwo identifies issues and suggests owners. Documentation updates require human judgment about what the correct content should be.
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.
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.
Related workflows
- Customer SuccessSupport Knowledge Gap Finder
- Ops & Chief of StaffSprint Retrospective from Real Data
- Ops & Chief of StaffMeeting Commitments Tracker
Stop doing the work your tools should do for you.
Set it up once. ZeroTwo runs it every time.