How to Capture What Your Best People Know Before They Leave

Short answer: To capture employee knowledge, start before anyone leaves. List the questions colleagues bring to that person, interview them in short sessions, write each answer in their words with the reason behind it, have the owner approve it, put it where staff already look, and give every answer an owner and a review date.

Every business has someone who gets the questions. The office manager who knows which supplier gives credit. The senior consultant who knows how a difficult client likes reports laid out. The technician who knows why the old machine needs warming up. Most of it was never written down because it never needed to be, until they hand in their notice.

This guide is a method that works in any industry. If you run a construction firm, our construction-specific version adds the site and regulatory side.

What knowledge is actually at risk?

The judgement and context that sits around your documented processes. Most businesses have some written procedures. What they lack is the layer that makes those procedures work in practice.

The common thread: this is knowledge people use to answer questions. That is the best way to find it.

Who should you start with?

Start with the person whose absence would hurt most next week, not the one leaving soonest. Leavers are urgent, but the bigger risk is often someone with no plans to go who is the only person able to do something.

A quick way to rank people:

1. Ask the team who they ask. "Who do you go to when you're stuck?" The same two or three names usually come up.
2. Look for single points of failure. Anyone who is the only person who can run a process, use a system or handle a client.
3. Check who is likely to leave. Retirement plans, a known move, a long leave coming up. Ask directly and kindly; most people appreciate being asked to pass on what they know.
4. Weigh the cost of a wrong answer. Knowledge tied to money, safety, legal duties or key clients goes first.

How do you capture knowledge without a big project?

Collect questions first, then interview, then write. Do not start with a blank manual and a table of contents. Manuals written from the top down are long, generic and rarely opened.

1. Collect the real questions. For a week, ask colleagues to note every question they take to the person. Use their exact words: "What do I do if the client's PO number is missing?" is better than "Purchase order procedure".
2. Group and rank them. Merge duplicates. Put money, safety, compliance and client-facing questions first. Aim for the top 20 to 30.
3. Book short sessions. Thirty to 45 minutes, two or three times a week. Long sessions tire people and the answers get vague.
4. Record, with permission. Ask before recording, explain it is to write up their answers, and say who will hear it. Don't try to write everything down while they talk.
5. Do it where the work happens. At their desk with the system open, at the machine, in the stockroom. People explain better when they can point.
6. Write up within two days. While the conversation is fresh, turn each answer into a short entry (format below).
7. Send the write-up back to them. Ask "is this right, and what did I miss?" They will often add the most useful detail at this stage.
8. Get owner approval before anything is published as the company's answer (see below).
9. Test with someone new. Give a newer team member five real questions and watch them find and use the answers. Fix what they trip on.

What questions should you ask in a knowledge interview?

Ask about decisions, exceptions and mistakes rather than the standard process. The standard process is usually written somewhere already; the judgement around it is not.

Questions that work in most businesses:

• "What do people ask you most often? What do you tell them?"
• "Walk me through the last time something didn't go to plan. What did you notice first?"
• "What do new people get wrong in their first month?"
• "When do you not follow the usual process? What has to be true?"
• "Which clients, suppliers or colleagues do you handle differently, and why?"
• "What's the most expensive mistake you've seen here? What stops it happening now?"
• "If you were off for a month, what would go wrong first?"
• "Where does that rule come from: a contract, a regulation, a manager's decision, or experience?"
• "Who else knows this, even partly?"

The source question matters. Some habits trace back to a contract clause or a legal requirement and should be written down with that reference. Others are preferences, which is fine, but they should be labelled as preferences so nobody mistakes them for obligations later.

Keep it in their words

Write the answer the way the expert said it, tidied but not rewritten into corporate language. Staff search using the words they hear at work. If the expert says "the Friday float", don't file it as "petty cash reconciliation procedure". Add the formal term as well if it helps searching, but keep the everyday one.

What format makes captured knowledge usable?

One question per entry, answer first. People look things up in the middle of a task, often on a phone, so the answer has to be quick to read.

Keep anything with steps short and numbered. Add a screenshot or photo where it saves words. If an answer runs past a screen, split it into two questions.

Why does the owner need to approve it?

Because writing something down turns one person's habit into company policy. That should be a decision, not an accident.

Approval does three jobs:

• Catches outdated or risky habits. An expert may have been doing something a particular way for years that no longer matches your contracts, prices or legal duties. The write-up is the moment to notice.
• Resolves disagreements. If two experienced people answer the same question differently, don't quietly pick one. Decide, record the decision and the reason.
• Makes it safe to rely on. Staff are more likely to use an answer if they know a manager has backed it.

Keep the approval light: a named person, a date and a yes. A sign-off process that takes weeks will stall the whole effort.

How do you make it findable?

Put it where people already look, and make it searchable by question. A perfect knowledge base in a system nobody opens is the same as no knowledge base.

• One place, not five. Pick the shared drive, intranet or tool the team already uses daily.
• Name entries as questions. "How do I refund a card payment?" is found; "Refunds v3 FINAL" is not.
• Link, don't copy. If the answer depends on a policy document, link to the current version rather than pasting it, so there is only one copy to update.
• Make it reachable mid-task. On a phone, from the shop floor, between client calls.

Search tools, including AI assistants that answer from your documents, help here, but only if the underlying entries are clear and current. Our guide to what an AI knowledge assistant is explains what to look for.

How do you keep it from going stale?

Give every entry an owner and a review trigger. Without them, people stop trusting the knowledge base and go back to asking the expert, who may by then have left.

Review an entry when:

• The contract, policy, price or regulation it relies on changes.
• Something goes wrong that the entry should have prevented.
• Someone says "that's not how we do it any more".
• The owner leaves or changes role. Reassign before they go.

Add a calendar review as a backstop, for example once a year for stable topics and more often for prices or anything regulated. And build a simple habit: at the end of each project or month, ask "what did we learn that isn't written down?" Add one or two entries each time.

What mistakes should you avoid?

• Waiting for the leaving date. Notice periods are short and busy.
• Recording but never writing up. A folder of long videos is not a knowledge base.
• Rewriting it in office language. If staff wouldn't phrase it that way, they won't find it.
• Publishing without approval. You may be making a bad habit official.
• No owner. Unowned answers go out of date within a year.
• Skipping the new-person test. If someone new can't use it, it isn't captured yet.

How does Verika help with this?

Verika is our product. It is built around this exact method: your experts write answers to real questions, the owner approves them, and Verika then answers the team by voice or text from those approved answers and your documents, showing which person or document each answer came from. When someone asks something nobody has covered, for example "what do we do if a client's direct debit fails twice?", Verika says it has no source rather than guessing and logs the question as a gap, so your expert answers it once instead of every time it comes up. That gap list is also a ready-made agenda for your next capture session. You can try it on your own documents on a 14-day trial with no card, or read more on the Verika home page.

Sources

This guide sets out a practical method and deliberately contains no statistics. We did not find survey figures on knowledge loss that we could verify at source for this article, so we have left them out rather than repeat numbers we could not check. Related reading on this site:

1. Verika Editorial, "Tribal Knowledge in Construction: Capture It Before They Retire" (construction-specific method with sourced workforce data). /blog/tribal-knowledge-construction
2. Verika Editorial, "What Is an AI Knowledge Assistant? A Plain-English Guide for Small Businesses", 7 October 2026. /blog/what-is-an-ai-knowledge-assistant