We have a document management system — isn't that our knowledge base?
Not quite. A document management system stores and controls documents: versions, approvals, access rights and retention. A knowledge base answers questions: it holds what people know, connected and sourced, so you find the answer rather than a file. You need a document management system for controlled documents. It is not a knowledge base, because most of the knowledge your company runs on was never written in a document.
What a document management system actually delivers
A document management system gives documents one home. The current version is clear, changes are tracked, approvals follow a route, and only the right people can open what they should. For contracts, drawings, certificates and controlled procedures, that is indispensable.
It manages files, not knowledge. It answers “where is the document?” well and “what should I do here?” only when a document happens to say so. A document management system is enough if what your people need to know is written down, current and findable — and the answer to their questions really is a document.
What a knowledge base actually delivers
A knowledge base is organised around questions and connections: this customer, that installation, the decision taken in a meeting three years ago and the reason for it. A living knowledge base also holds what was never written down — captured from conversations with the people who know — and shows where every piece of knowledge comes from.
It takes capture effort, and it does not replace the controlled documents your quality system and customers expect. It works next to them.
Knowledge base vs document management system: at a glance
| Criterion | A document management system | A knowledge base |
|---|---|---|
| Unit | A document | A piece of knowledge, connected to others |
| Answers | Where is the file, and which version is current? | What do we know about this, and on whose word? |
| Where content comes from | Documents people write | Documents, and conversations with the people who know |
| Knowledge never written down | Not covered | Captured with its source |
| Versioning | Document versions | What was known when, and what replaced it |
| Best for | Controlled documents, contracts, drawings | Judgement, history, exceptions, recurring questions |
What happens when you choose wrong?
An engineering firm moved all project files into a new document management system before its founder retired, so that nothing would get lost. The migration was a success: every drawing, calculation and email was stored, versioned and searchable.
Two years later a customer asked why a certain design choice had been made on an installation they wanted to extend. Every document from the project was there. The reason was not. It had been decided in a meeting and remembered by the founder — the one place the migration could not reach. (An illustrative example, not a client case.)
When do you need both?
Keep your document management system as the home of controlled documents. Let the knowledge base hold what people know around those documents, and point to the document where one exists. When someone asks a question, the answer comes from the knowledge base, and the controlled document behind it is one click away. When a document changes, the owner checks whether the knowledge around it still holds.
Where MentX fits
MentX is a personality-aware knowledge base. It captures the knowledge of a company's key person — from meetings and a guided intake track — into a living, temporal knowledge graph with full source attribution.
Your documents stay in the system you manage them in, and can serve as sources. What the knowledge base adds is the knowledge nobody wrote down, with full source attribution — so every answer shows where it comes from.
Questions people ask
Can't we just add an AI assistant to our documents?
It helps you find documents faster. Its answers are limited to what the documents say, it cannot tell which of two contradicting versions is current, and it knows nothing that was never written down. See why AI needs your business context.
Where should a new procedure live?
The controlled procedure belongs in your document management system. The knowledge around it — why it is the way it is, the exceptions, who to ask — belongs in the knowledge base, with a link to the procedure.
Is a company wiki the same as a knowledge base?
A wiki is a step closer: pages organised by topic, easy to edit. It still depends on people writing things down, and it rarely shows where a statement came from or whether it is still true. See company wiki vs personality-aware knowledge base.
