Knowledge Base · 6 min read
The Small Business Guide to Internal Knowledge Management
Internal knowledge management is how a business captures, organizes and shares what its people need to know to do their jobs. In a small business most of that knowledge ends up written down as policies, procedures and how-to guides, so an internal knowledge base is mostly a home for those documents, kept approved, current and read by the people they apply to.
If the documents your team relies on include policies that people must read, follow and acknowledge, our guide to small business compliance sets out the policies a company needs as it grows past 15, 50 and 100 employees.
What is an internal knowledge base?
An internal knowledge base is the private library where a company keeps what its own staff need to know. Unlike a help center, which answers customers, it is written for employees, and unlike a shared drive, it is organized so people find the right document and trust that it is current.
Here is what usually belongs in one, and which documents people have to confirm they have read.
| Document | What it does | Does someone have to confirm it? |
|---|---|---|
| Policies | State the rules: conduct, data security, leave, expenses, remote work | Usually, yes, by name and version |
| Procedures and SOPs | Explain how a task is done, step by step | Often, for the people who do the task |
| Employee handbook | Brings the core policies together for every employee | Yes, at hiring and after each change |
| Onboarding guides | Get a new person productive in their first weeks | Rarely |
| How-to guides and FAQs | Answer the questions people keep asking | No |
| Templates and forms | Keep recurring work consistent | No |
Look down the right-hand column and the pattern is clear: the documents that carry the most weight are the policies and procedures. That is why, for a small business, the internal knowledge base and the policy library are best treated as one thing.
Why a small business’s knowledge is mostly policy
Much of what a small team needs to know comes down to rules: how to handle customer data, how expenses are approved, what the leave policy says, how a task has to be done to pass an inspection. Some of those rules are your own choices, and many are required. When we catalogued the federal requirements that apply to US businesses, 39 of the 70 obligations called for a written policy. Our small business compliance guide walks through them.
A written rule only helps if people can find the current version and you can show they read it. That is the part a plain wiki or shared drive leaves to memory.
The hidden costs of poor knowledge management
Panopto’s Workplace Knowledge and Productivity Report found that employees spend more than five hours a week waiting for information from colleagues or recreating knowledge that already exists. In a small business the cost shows up in a few familiar ways.
The same question gets answered differently. When the answer lives in someone’s head, two people give two answers, and customers notice.
New hires take longer to become useful. Without written procedures, every new person learns by interrupting someone who is busy.
Knowledge walks out the door. When the person who knew how something works leaves, the business has to rediscover it.
Old versions keep circulating. A policy updated last month is no use if the old copy is still the one people find, and it is a real problem if a customer, auditor or court asks which rule was in force.
How to create your own internal knowledge base
A small business can set one up in a week of part-time effort. These seven steps keep the policy side under control from the start.
- List what you already have. Pull every policy, procedure and guide out of drives, inboxes and chat into one list, and note where each one lives today.
- Give every document an owner. One named person keeps each document current. If nobody owns it, it will drift. Our guide to policy owners covers how to choose them.
- Separate rules from guidance. Policies say what must happen, procedures say how, and guides help. Our explainer on policy vs procedure vs SOP shows where the lines fall.
- Organize by team and set access. Use folders that match how the business works, and decide who sees what, so people only open what applies to them.
- Approve before you publish. Send each policy through approval by the right person before anyone sees it, and keep the approved version as the only one people read.
- Ask for acknowledgment where it matters. For the policies people must follow, record who has read which version, and ask again whenever it changes.
- Set review dates. Give each document a date when its owner checks it is still right, so old guidance does not linger.
Key features to look for in an internal knowledge base
Most tools handle writing and storing documents. The difference is in what happens to the documents people have to follow.
How AllyMatter fits
We built AllyMatter as policy management software, and it works as an internal knowledge base of policies. Documents live in folders, tags decide who sees each one, and every document goes through approval before anyone can read it. Each approved change becomes a new version, with the full history kept and any two versions comparable.
When a policy is ready, you choose how it goes out: notify people, or ask them to acknowledge or e-sign it. Reminders follow on the cadence you set, you can see at a glance who has acknowledged and who has not, and review dates remind each owner when a document is due. When a customer or auditor asks, the record of approvals, versions and acknowledgments exports as a PDF or CSV.
Not ready for software yet? Start with our free Policy Acknowledgment and Signature Tracker for Google Sheets or Excel.
Frequently asked questions
What is internal knowledge management?
It is how a business captures, organizes and shares the knowledge its people need to do their jobs. In practice that means writing down policies, procedures and guides, keeping them in one place, and making sure the right people see the current version.
What is an internal knowledge base?
It is the private library where a company keeps that knowledge for its own staff. For a small business the most important documents in it are usually policies and procedures, because they are the ones people are expected to follow.
What is the difference between an internal knowledge base and a shared drive?
A shared drive stores files. An internal knowledge base for policies also controls who sees each document, keeps one approved current version with its history, and records who has read it. A shared drive can tell you when a file was last changed, but not who approved it or who acknowledged it.
Does a small business need policy management software or a knowledge base?
If most of what you keep is policies and procedures that people have to follow, the two are the same job. Look for a knowledge base that handles approval, versions and acknowledgment, which is what policy management software does.
How long does it take to set up?
In AllyMatter, setup takes about half an hour. Moving your documents in yourself takes about a day, and for a large volume the migration service on yearly plans usually finishes within a week and often sooner.
How much does an internal knowledge base cost?
Prices vary widely, so compare how each tool charges. AllyMatter charges for the people who write and manage documents, and everyone who only reads and acknowledges them is free. See pricing for the current plans.
Start your 30-day free trial of AllyMatter. No credit card to start, and a 30-day money-back guarantee if you subscribe and change your mind. Free migration.