1. Home
  2. Blog
  3. Operations
Operations

How to build a company knowledge base for your SME

When a long-serving staff member resigns, the notice period is often the only time left to capture years of know-how. Here is how to build a knowledge base before you need it.

By the HumbleBear team · · 9 min read

Cover: How to build a company knowledge base for your SME
Short answer

A company knowledge base is one organised, searchable place where a business keeps the know-how its work depends on: procedures, product and pricing rules, customer and supplier notes, and answers to common questions. Build it by capturing the questions staff ask most, giving each topic an owner, using one simple structure, and reviewing it on a schedule.

Your most experienced staff member hands in her resignation. She knows which supplier gives credit, how to price a non-standard job, which customer must never be invoiced before the 25th, and where the warranty files are. Under the Employment Act 1955, unless her contract says otherwise, she may only have to give four to eight weeks' notice. Without a written record, much of what she knows leaves with her. A company knowledge base (in Bahasa Malaysia, pangkalan pengetahuan syarikat) is how you keep that know-how in the business.

What is a company knowledge base?

A company knowledge base is a single, organised and searchable collection of the information a business needs to run: how things are done, the rules behind decisions, and answers to questions people ask repeatedly. It is written for staff, not customers, and kept up to date by named owners.

It sits between two other things:

  • Records are evidence of what happened: invoices, contracts, bank statements. You keep them because the law and good bookkeeping require it. See record keeping in Malaysia.
  • Know-how is how and why you do things: how to quote a rush order, who to call when the forklift breaks, why a certain customer gets 60-day terms.

A knowledge base holds the know-how and points to where the records are. It shouldn't become a second copy of your accounts.

Why does a Malaysian SME need a knowledge base?

Because small teams depend heavily on a few people's memory, and that memory is lost through resignations, leave, illness and simple forgetting. A knowledge base shortens training, reduces repeated questions, and keeps work going when someone is away.

Notice periods are short compared with the years it takes to learn a job. Under section 12 of the Employment Act 1955 (Act 265), the notice period is whatever the written contract says; where the contract is silent, the minimum is:

Length of serviceMinimum notice (where the contract doesn't specify)
Less than 2 years4 weeks
2 years to less than 5 years6 weeks
5 years or more8 weeks

Either side may also waive notice. Plan on the assumption that you may have a few weeks, or none, to capture what someone knows.

There is also a safety angle. Section 15(2)(c) of the Occupational Safety and Health Act 1994 (Act 514) requires employers to provide the information, instruction, training and supervision needed to ensure, so far as is practicable, the safety and health of employees at work. Written, findable instructions for risky tasks help you meet that duty.

What should go into a small business knowledge base?

Start with the questions people actually ask, not with a blank template. If a question has been asked three times, its answer belongs in the knowledge base.

Typical contents for a Malaysian SME:

  • How-to procedures: issuing a quotation, receiving goods, closing the shop, handling a return. Detailed procedures become SOPs; see how to write SOPs your team will use.
  • Rules and limits: discount limits, who approves what, credit terms by customer type, when to escalate.
  • Product and service knowledge: specifications, common faults, compatible parts, standard lead times.
  • Customer and supplier notes: preferences, contact routes, special terms. Keep personal data to what the work needs.
  • Tools and access: which system is used for what, who to ask for access. Never store passwords in the knowledge base itself.
  • Onboarding: first-week checklist, who's who, where things are.
  • Lessons learned: what went wrong on a job and what to do differently.

How do I build a knowledge base step by step?

Build it in small pieces, starting where the risk of losing knowledge is highest, and make adding to it part of normal work rather than a one-off project.

  1. Choose one home. A shared drive folder, a set of shared documents or an internal wiki page. One place, linked from wherever staff start their day.
  2. List your "single points of failure". Which tasks can only one person do? Start there.
  3. Collect the top questions. Ask each team for the ten questions new staff ask most, and look through chat groups for repeated ones.
  4. Agree a simple structure. For example, one folder per department, and one page per topic with a clear title written as a question or task: "How do I issue a credit note?"
  5. Write short pages. One topic per page, steps numbered, a photo or screenshot where it helps. Aim for a page someone can follow while doing the task.
  6. Give every page an owner and a review date. The owner is the person who knows the topic best.
  7. Capture from conversations. When someone answers a question in chat, ask them to paste the answer into the knowledge base and share the link instead.
  8. Use it in onboarding. New staff learn from it and flag anything wrong or unclear. That's your cheapest review.

Example: A Kuching hardware trading company with 14 staff starts with the three tasks only its storekeeper knows: receiving goods against a purchase order, recording returns to suppliers, and the monthly stock count. Over four weeks, the storekeeper spends about an hour a week explaining each task while a junior writes it up with photos, then the junior does the task while the storekeeper watches. By the end, two people can do each task and the steps are written down.

How do I capture knowledge when an employee resigns?

Start the handover on the day notice is given, list everything only that person knows, and have them teach it to a named successor who writes it down. Don't leave it to the last week.

A practical handover checklist:

  • open jobs, quotations and orders, with their status and next step;
  • customers and suppliers they deal with, and anything unusual about each;
  • recurring tasks and their timing (weekly, monthly, year-end);
  • where their files are and which systems they use;
  • passwords and access transferred through your normal IT process, not written in documents;
  • "things I just know": shortcuts, workarounds and warnings.

Review the written handover with the successor before the last day, while questions can still be answered. For the meeting and handover habits that make this routine, see effective meetings and handovers.

How does the PDPA affect a company knowledge base?

If your knowledge base contains personal data, such as customer names, phone numbers or staff details, the Personal Data Protection Act 2010 (Act 709) applies to it like any other system. Two principles matter most here: Security and Retention.

  • Security Principle (section 9): take practical steps to protect personal data from loss, misuse, unauthorised access or disclosure. In practice, limit who can open which sections, and don't keep customer lists in pages everyone can see.
  • Retention Principle (section 10): don't keep personal data longer than the purpose needs, and destroy or permanently delete it when it is no longer required.

The Personal Data Protection (Amendment) Act 2024 (Act A1727) raised the maximum penalty for breaching the principles to a fine of RM1 million, imprisonment of up to three years, or both, and requires data controllers to notify the Personal Data Protection Commissioner of a personal data breach. The Commissioner's guidelines set that notification at no later than 72 hours. The simplest protection is not to put personal data in the knowledge base at all: write "see the customer record" and keep the details in your customer system.

How do I keep a knowledge base up to date?

Make updating part of the work: when a procedure changes, the person who changed it updates the page the same day. Then review every page on a fixed cycle, such as every six months, and delete what's no longer true.

Signs a knowledge base is dying, and what to do:

SignWhat it meansFix
Staff ask in chat instead of searchingPages are hard to find or not trustedBetter titles, one home, link answers back to pages
Pages contradict each otherNo owner per topicOne owner, one page per topic, delete duplicates
"Last updated" dates over a year oldNo review habitReview dates in the owner's calendar
Nobody adds pagesWriting feels like extra workAccept short pages; ten lines is fine

Keep the knowledge base separate from transactional data. Prices quoted, past orders and customer history belong in your business records. If those already sit in software such as HumbleBear, with quotations, invoices and a CRM in one place, staff can look them up there, and its AI Assist can answer questions about your own records, so the knowledge base only needs to explain how and why. For mapping the work these pages describe, see what workflow management is.

Frequently asked questions

What is the difference between a knowledge base and SOPs?

An SOP is a detailed, step-by-step instruction for one task that must be done the same way every time. A knowledge base is the wider collection that holds SOPs together with rules, product information, contacts and answers to common questions. Most SOPs live inside the knowledge base.

How long does it take to build a knowledge base for a small business?

A useful first version, covering the tasks only one person can do and the most common questions, can be built in a few weeks at an hour or two a week per contributor. It is never finished; it grows as questions come up and shrinks as old pages are deleted.

Who should write the knowledge base?

The people who do the work should supply the content, because they know the real steps. Someone else, often a newer staff member, can write it up and test it by following it. Each page needs one owner who keeps it correct.

Can I store customer details in the knowledge base?

You can, but it's usually better not to. Personal data in a knowledge base falls under the PDPA's Security and Retention Principles, and wide-open pages make that harder to meet. Keep customer details in your customer system and refer to it from the knowledge base.

What should I do if an employee leaves without notice?

Use what you can still reach: their files, sent emails, open jobs in your systems and colleagues who worked with them. Then treat it as a lesson and start capturing knowledge for every role that only one person can do, before the next resignation.

Sources