
An internal knowledge base: who writes it and who keeps it current
Knowledge base software is quick to buy. The hard part comes after: who writes the procedures, who updates them when something changes, and how you notice an answer is no longer right. An internal knowledge base that nobody maintains is more dangerous after a year than having none, because people still believe it.
An internal knowledge base holds procedures and answers that someone maintains. News belongs on the intranet and work in progress in the collaboration workspace.
Every article has a named owner and a review date. Without those two the knowledge base goes out of date unnoticed, and people keep trusting it.
Start with the questions that already keep coming back, not with everything in people’s heads, and pick the software once you know who will write in it.
What an internal knowledge base is, and what it is not
An internal knowledge base is where staff find the answer without interrupting a colleague: how to submit an expense claim, what to do when a customer wants a return, how to set up a new supplier, who to call about a fault out of hours. What sets it apart from other places is one word: maintained.
- The intranet brings news. What is on it is old within weeks, and that is fine.
- The collaboration workspace holds work in progress: drafts, quotes, project folders.
- The IT documentation is for administrators: network diagrams, configurations, the password vault.
- The knowledge base holds what is valid until someone changes it, written for the people who have to do it.
That last point makes it more expensive to maintain than the rest. It is also why you should start small.
Start with the questions people already ask
The temptation is to gather “all the knowledge” first: everyone writes down what they know, and in three months it is all there. That produces hundreds of pages nobody searches, written by people who are busy.
Start the other way round, with the questions that keep coming back now:
- The service desk or the IT contact. Which questions appear in the tickets or the chat every week?
- HR and finance. Which emails do they get again and again, especially around leave, expenses and rotas?
- New starters. What did the last three ask in their first month?
Write the first twenty answers, let people use them, and watch what gets searched and not found. That is the list for the next round.
Every article has an owner and a date
A knowledge base does not go out of date all at once but article by article, on the day something changes and nobody updates the article. Two things prevent that.
- A named owner. Not “HR”, but the person who knows the process and knows when it changes. When that person leaves, their articles pass to a successor; that belongs in the leaver process, next to handing in the laptop.
- A review date. A procedure not looked at for a year triggers a reminder to its owner. Show the date of the last check at the top, so readers can see for themselves whether to trust it.
Agree who may edit an article, too. Anyone can report a mistake; the owner makes the change. Otherwise, after a year, there are three versions of the same procedure, each with a different exception.
Write answers, not a manual
People open a knowledge base with a question and a colleague waiting. Write for that:
- The question as the title, in the words staff actually use. If everyone searches for “book a day off”, the article is not called “Leave registration procedure”.
- One topic per article. A five-screen article is not read, and cannot be half updated without contradicting itself.
- Numbered steps where it is an action, and one paragraph of explanation where it is a rule.
- Screenshots sparingly. Every software update makes them wrong, and a wrong screenshot misleads more than none.
What does not belong in it
A knowledge base is widely read, which is why not everything belongs there.
- Passwords and access codes. Not even “just” the alarm code or the guest wifi for all staff. That is what a password vault is for, with permissions per person.
- Personal data. A procedure may say who to call, but not private numbers, National Insurance numbers or health details. Under UK GDPR you need to be able to say why a piece of data is where it is.
- Technical administration details. Configurations and admin accounts belong in the IT documentation, for the people who run it. How to set that up is in our article on IT documentation.
If part of it has to stay with a smaller group, such as finance procedures, put permissions on it rather than a separate knowledge base beside it.
Knowledge base software: what to ask before you choose
There are three common routes: a knowledge base in the collaboration workspace you already have, separate knowledge base software, or the knowledge base in the service desk’s ticketing system. Which fits depends on who searches it. The questions are the same for all three:
- How good is the search? Does it find “expenses” when the article is called “claims”, and does it search attachments? This is the feature that decides whether it gets used.
- Are there owners and review dates per article? With a reminder that goes out by itself, not a spreadsheet next to it.
- Is there version history? So you can see what it said yesterday and who changed it.
- Does it connect to your existing accounts? Single sign-on and permissions through groups, so leavers drop off automatically.
- Is it in the backup, and can you export? In a readable format, for the day you switch.
- Can you see what is searched and not found? That is the best source for the next article.
How to tell it is going out of date
Three signals to review every quarter, in an hour:
- Searches with no result. A list of questions with no answer yet.
- Articles past their review date. Grouped by owner, so it becomes a specific request rather than a general appeal.
- Questions that keep coming in. If the answer exists and people still ask, the title is wrong or the article cannot be found.
Remove or archive articles that nobody opens and whose owner cannot say whether they are right. A small knowledge base that is correct beats a large one where you have to guess.
Where our work stops
What we do. We handle the IT side: setting up or connecting the knowledge base in your environment, accounts and permissions through groups, single sign-on, backup and export, and configuring search so it works inside attachments too. If we manage your environment, we supply the steps for the IT questions in your knowledge base that match your systems.
What we do not do. We do not write your procedures and we are not knowledge management consultants. How an expense claim, a return or a leave request works in your organisation is something only you know, and the owner of those articles should sit with you. Nor do we supply knowledge base software; that comes from a vendor.
Questions about an internal knowledge base
The five we hear most.
What is an internal knowledge base?
An internal knowledge base is a collection of procedures and answers for your own staff, kept up to date by someone. Staff find out how something works without interrupting a colleague. What sets it apart from a shared folder is that every article has an owner and a review date.
What is the difference between a knowledge base and an intranet?
An intranet brings news and points to systems; what is on it ages within weeks, and that is intended. A knowledge base holds what stays valid until someone changes it. They can live in the same product, but they have a different rhythm and often a different owner.
Who should maintain the knowledge base?
For each article, the person who knows the process and knows when it changes, named rather than a department. On top of that, one person checks every quarter which articles are past their review date and which searches return nothing. IT keeps the software running but is rarely the right owner of the content.
Which knowledge base software suits a smaller organisation?
That depends on who searches it and what you already have. A knowledge base in the collaboration workspace or the ticketing system is often enough; a separate product pays off when search and review reminders fall short there. Look at search, owners per article, version history, connection to your accounts and export.
Do you write the content of our knowledge base?
No. Only your organisation knows how its processes work, and the owner of those articles should sit with you. We set up the IT side, and if we manage your environment we supply the steps for the IT questions.
Further reading
What sits next to the knowledge base.
Shall we make your knowledge base findable and maintained?
Tell us where your procedures live now and who searches for them. We will say how to make them findable, with permissions and an owner per article; the content stays yours.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.