If new hires keep asking the same questions, your knowledge base probably isn’t doing its job. Here’s the 7-step audit I’d use to make it faster to learn, easier to trust, and less painful to maintain.
A lot of businesses think they have an onboarding problem when they actually have a documentation problem.
I’ve seen this with small agencies, consultants, trades businesses, and growing service companies. The owner hires someone new, gives them access to a shared drive or a pile of Notion pages, and assumes the system is “documented.” Two weeks later, the new person is still interrupting senior staff for basic answers.
That’s expensive.
A good knowledge base should shorten the time between “first day” and “fully useful.” If it doesn’t, it needs an audit. Here’s the 7-step process I’d use.
1. Start with the onboarding goal
Before you review a single article, get clear on what faster onboarding actually means for your business.
For one company, it means a new admin can answer common customer questions without asking the owner. For another, it means a junior developer can ship simple updates in week one. For a plumbing company, it might mean a new office coordinator can book jobs, send invoices, and handle emergency call triage by day three.
Write down the top 5 to 10 tasks a new hire must perform confidently in their first 30 days. That list becomes your audit lens.
If a document doesn’t help someone complete one of those tasks, it may still be useful, but it probably isn’t onboarding-critical.
2. Map what exists and where it lives
Most teams don’t have one knowledge base. They have a messy ecosystem: Google Docs, PDFs, Slack threads, old Loom videos, saved emails, sticky notes, and “just ask Sarah.”
Your next step is simple: inventory everything.
Create a spreadsheet with these columns: document name, link, owner, last updated date, topic, intended role, and whether it’s still used.
This exercise alone usually reveals the real problem: the issue isn’t always missing information, it’s scattered information.
I worked with a small consulting business where client onboarding instructions lived in three places: a Notion workspace, an old Dropbox folder, and the founder’s inbox. New hires weren’t slow because they were incapable. They were slow because nobody could tell them which version was correct.
If your internal docs are hosted on a clunky, slow site, fix that too. Speed and usability matter more than people admit. Even basic infrastructure choices, like reliable hosting from Hostinger, can make internal resources easier to access if you keep documentation on a private company site.
3. Find the gaps by following real tasks
Now test the knowledge base against actual work.
Pick three to five core onboarding tasks and ask a recent hire, or someone unfamiliar with the process, to complete them using only the documentation. Watch where they hesitate, click around, or give up.
This is where the gaps show up.
Typical failures look like this:
- the article assumes too much prior knowledge
- screenshots are outdated
- steps are missing between “log in” and “complete the task”
- there’s no explanation of why the process matters
- the document tells people what to do, but not what “done correctly” looks like
A family-run plumbing company is a good example. Imagine they hire a new dispatcher. The knowledge base might explain how to use scheduling software, but not how to prioritize a no-heat emergency versus a routine leak, or what to say when no technician is immediately available. That’s the difference between software training and operational training.
4. Cut duplication and retire bad docs
One of the fastest ways to improve a knowledge base is to remove what’s hurting trust.
When new hires find three articles on the same process with slightly different instructions, they stop believing any of them. At that point, they fall back to asking people directly.
During the audit, mark documents as:
- keep
- merge
- rewrite
- archive
- delete
Be ruthless. Old documentation creates drag.
I’d rather see a small, reliable knowledge base than a huge one full of half-true instructions. If a page is outdated, vague, or clearly ignored, don’t leave it sitting there “just in case.” That just makes onboarding slower.
5. Rewrite for clarity, not completeness
A common mistake is trying to make every article exhaustive. That usually produces long, intimidating documentation nobody reads.
For onboarding, clarity beats comprehensiveness.
Each article should answer five things quickly:
- what this process is for
- who it’s for
- when to use it
- the exact steps
- what success or escalation looks like
Use plain language. Keep paragraphs short. Add screenshots only where they reduce confusion. If you need simple annotated visuals or quick process diagrams, Canva Pro is a practical option for making docs easier to follow without hiring a designer.
Also, separate beginner documentation from advanced reference material. A new hire doesn’t need your entire operational brain on day one. They need enough to do the next task correctly.
6. Fix navigation and search first
Even good documentation fails when people can’t find it.
Your audit should include structure, naming, and searchability. Ask yourself:
- are articles grouped by role or department?
- do titles match the words staff actually use?
- can someone find an answer in under a minute?
- is there a clear “start here” path for each new role?
This matters more than most teams expect. A well-written article buried under vague headings like “Resources” or “General Admin” is basically invisible.
If your knowledge base is public-facing or part of a client portal, analytics can help you see what people search for, where they drop off, and which pages get ignored. A lightweight, privacy-friendly tool like Fathom Analytics can be useful for spotting whether people are actually using key help content.
7. Assign ownership and a review schedule
This is the step that keeps your audit from becoming a one-time clean-up.
Every important article needs an owner. Not “the team.” A person.
That person is responsible for accuracy, updates, and periodic review. I’d also add a simple review cadence:
- high-change processes: monthly
- core onboarding docs: quarterly
- stable policy docs: every 6 to 12 months
Add a visible “last updated” date to every article. That small detail builds trust.
If you want to go one step further, ask every new hire one question at the end of week one: “What was hardest to learn from the docs alone?” That feedback is gold. It tells you exactly where onboarding friction still exists.
Final thought
A knowledge base audit is really about buying back time. Less interruption, fewer repeated explanations, faster ramp-up, and less stress for everyone involved.
If your team is growing and your systems are starting to feel messy, this kind of cleanup pays off quickly. And if your website, client portal, or internal resource hub is part of the problem, you can get an instant website estimate at juliusmason.com/#instant-quote or request a free website audit at juliusmason.com/free-website-audit.
Because in most small businesses, better onboarding doesn’t start with more meetings. It starts with better information in the right place.
