Most documentation problems are invisible until a user hits them. The health check surfaces them before that happens.
Answer six questions about how your documentation actually works. You will get an instant score across three dimensions with specific findings.
Your health check is complete.
The audit goes deeper.
The health check identifies where your documentation system is breaking. The Documentation Audit identifies exactly why, and delivers a written action plan to fix it — in five working days.
The health check tells you where the problems are. The paid audit tells you exactly why they exist and what to do about them.
Every link, every cross-reference, every dead end. I trace the paths a reader actually takes through your documentation and identify every point where the path breaks. Broken links are the visible failure. Missing links are the expensive one.
Whether the structure reflects the current product, not the product at launch. Documentation architecture drifts silently. Features get added, sections get orphaned, and the navigation stops making sense to anyone who didn’t build it. I map the gap between what exists and what your users actually need.
Whether the documentation system is built to improve or built to stagnate. Good documentation has a feedback mechanism. Most documentation doesn’t. I assess whether your system can learn from users and evolve, or whether it is structurally unable to change without a major rewrite.
Written audit report (PDF)
A full written diagnosis of your documentation system, structured by the three audit dimensions. Every finding is specific. Every problem has a page reference, not a vague summary.
Prioritised action plan
Every finding ranked by impact, not by how easy it is to fix. You know exactly what to address first and why. No open-ended recommendations. No generic best-practice lists.
30-minute walkthrough call
I walk you through every finding. You can ask questions, push back, and leave the call knowing exactly what happens next. Included in the fixed fee.
14-day follow-up check
Two weeks after delivery, I follow up to see which findings you have acted on and whether anything in the report needs clarification. The engagement does not end when the PDF is delivered.
Your product is scaling faster than your documentation. Every sprint ships. Your docs are one sprint behind, then two, then six. Your users are navigating by instinct and your support queue is the proof. The audit tells you exactly where the documentation system broke down and what to fix before the gap becomes structural.
Your support tickets reference the same documentation pages repeatedly. The same questions come up in Slack every week. Engineers are answering questions that should be answered by docs. The audit identifies which specific pages are failing, why users are not finding the answers they need, and what would have to change for the documentation to start deflecting tickets.
You inherited a documentation system you did not build and cannot fully trust. You do not know what is accurate, what is out of date, or what the original structure was trying to solve. The audit gives you a baseline: a complete picture of what exists, what is broken, and what a realistic improvement path looks like.
You send me the link to your documentation. I deliver the written report, prioritised action plan, and schedule the walkthrough call within five working days. The 14-day follow-up happens automatically after that. The entire engagement from first contact to final follow-up takes under three weeks.
A link to your documentation. That is it. I do not need access to your codebase, your internal tools, or your support ticket system — though if you want to share context about your product or your team, that is welcome. The audit is designed to be low-friction: you send a link, I do the work.
Then the report will confirm it and identify the specific areas where the foundation is strongest. That is genuinely useful: it tells you where to invest in maintenance and where you have structural debt you may not have noticed. If the audit does not surface at least three actionable findings, you pay nothing. That is not a marketing claim. It is the terms of the engagement.
The audit works on documentation at any stage. Pre-launch documentation has its own failure modes: structure built around how the product was conceived rather than how users will encounter it, getting-started guides that assume context no new user has, and ownership models that break the moment the team grows. Getting the structure right before launch is significantly cheaper than fixing it after.
You receive the written report and action plan, we run the walkthrough call, and two weeks later I follow up. After that, you own the findings and the plan. Some clients implement the action plan themselves. Others come back for implementation support. Either way, the audit report is designed to be self-contained and actionable without ongoing dependency on me.
If the audit does not surface at least three actionable findings, you pay nothing.