Back to the blog

Keeping what your company knows when people leave or join

· By Bee Flow · 5 min read

In the third quarter of 2026, 341,000 vacancies were filled in the Netherlands. How to turn manuals, work instructions and a retiring colleague's answers into a knowledge base new staff can ask, and keep its answers trustworthy.

A well-used notebook open on a workbench, its loose pages drifting into a tidy card index box with one amber tab

On 30 October, Statistics Netherlands (CBS) published its labour market figures for the third quarter of 2026. The market is slightly less tight (in Dutch): there were 92 vacancies for every 100 unemployed people, down from 95 a quarter earlier. At the end of September 375,000 vacancies were open, and construction had the highest vacancy rate of any sector, at 72 per thousand jobs.

The number that stayed with us is a little further down the same release: in those three months, 341,000 vacancies were filled. Behind each one is a person starting somewhere new, who spends the first weeks mostly asking questions. Sometimes there is also a person who left, taking what they knew with them.

Where a small company keeps what it knows

In a company of twenty or fifty people, most of what matters is not written down. Some of it is: supplier manuals, work instructions, a folder of last year's quotes. The important part lives in the heads of the people who have been there longest. They know which boiler needs a reset first when it shows a certain fault code, which form the insurer wants to see, and why a maintenance quote is built differently from a quote for new construction.

Every week new colleagues ask those questions again. Every week the same experienced colleague answers them. That works fine until that colleague retires or moves on.

An example (made up)

Installatiebedrijf Voorbeeld (Dutch for something like "Example Installers") does not exist, though its situation is common enough. It is an installation company of 28 people, nine of them service engineers. Gerard (also made up) has run the call-out service for thirty years and retires next summer. Two new engineers have just started, and they call him several times a day.

The owner wants those questions to keep getting answers after Gerard is out in his garden. The plan: one knowledge base, "Faults and service", that the new engineers can ask in plain language, with every answer showing the document it came from.

What to collect in the last months

Start with the questions, not the documents. Ask the new colleagues to write down, for two weeks, everything they ask Gerard. That list becomes the table of contents of your knowledge base, and it shows straight away what is not written down anywhere.

Then collect:

  • The manuals and work instructions you already have. Throw out what is out of date before you add anything, not afterwards.
  • The answers that exist nowhere on paper. Ask Gerard to write them down briefly, or record a few conversations in which he explains how he tackles a fault, and turn each into a short note per subject. Ask him first whether he is comfortable with that, and tell him where the recording is kept.
  • The exceptions. "Normally you do this, except on that model" is exactly the knowledge that disappears first.
  • Who to call for which problem: which supplier, which department. Roles and departments, no private phone numbers.

Start early. Six months before someone leaves is comfortable, three months is tight, and the last week is too late, because by then everyone is busy handing over current work.

Answers people can trust

A knowledge base that once cites an old procedure or makes something up will be ignored within a month. A few agreements prevent that.

Show the source. Every answer comes with the document it was taken from, so a new engineer can click through and read it themselves. An answer without a source cannot be checked.

Give each subject one owner. Not "the team" but a name: the work planner for quotes, the most senior engineer for faults. That person decides what goes in and is the first to hear when an answer is wrong.

Take old versions out. When a new work instruction arrives, remove the old one from the knowledge base straight away. Two versions side by side give two answers, and the AI has no way of knowing which one still applies. Put a date at the top of each document as well, so the reader can see how old it is.

Once a quarter, ask the questions from that first list again and check that the right document comes out on top. It takes an hour, and you see at once where something has drifted.

What stays out

A knowledge base for the whole company is not the place for personnel files, appraisals, salaries or medical information. Customer data usually does not belong there either: how to handle a certain boiler model, yes, the customer's name and address, no. Passwords and access codes never, not even for a while.

Anything meant for only a few people goes into a separate knowledge base for a smaller group. The rule of thumb we use ourselves: if you would not hand it to every new colleague on their first day, it does not belong in the knowledge base everyone can ask.

Onboarding with a knowledge base

The first weeks alongside an experienced colleague are still needed. What a knowledge base does is catch the repeat questions, so that colleague has time left for the hard ones. Let new people put three real questions to the knowledge base in their first week and go through the answers with whoever is showing them the ropes. They learn where the information lives. You see what the knowledge base does not cover yet, which is exactly what you add next.

It works the other way round too. A newcomer looking with fresh eyes is quicker than anyone to spot a work instruction that is no longer right. Make it easy for them to tell the owner of that subject.

An open folder of documents, with a thin amber line running from one highlighted line on a page up to an empty speech bubble

How Bee Flow helps with this

In Bee Flow you build a knowledge base from uploaded manuals and work instructions, pasted text, web pages, tables and the notes of recorded meetings. The sources appear as cards under each answer, and a click opens the original document. For each knowledge base you choose who may see it: only you, the whole organisation or specific groups. Anyone without access gets an answer without that knowledge base. The Test question tab shows which source answers a question before your team starts to rely on it, and Privacy Shield marks documents that contain personal data. Have a look at the platform or private AI chat, or get in touch and try it with your own manuals.

#knowledge #ai-at-work