Best knowledge base software for answers, a practical buyer's checklist
Most companies already have a knowledge base. It is just spread across shared drives, handbooks, past proposals and policy PDFs, and the search box returns a list of files instead of an answer. The best knowledge base software for this situation does not ask you to rewrite everything into wiki pages. It answers questions from the documents you already have, shows the source, and respects who is allowed to see what. This checklist covers what to look for, how to test each point in a trial, and how ChatDocument fits.
From a library of pages to answers with sources
The traditional internal knowledge base is a set of articles someone writes and maintains. It works when a team has the time to keep articles current, and it decays quietly when they do not. The newer approach starts from the documents that are already the source of truth: the signed contract, the approved policy, the final proposal. People ask a question in plain language and get an answer drawn from those documents, with a citation to the page.
The two approaches can coexist. But when you compare software, it helps to decide which problem you are solving: writing and publishing articles, or getting reliable answers out of existing files. This checklist is for the second.
Point one, cited answers for every statement
The answer is only as useful as your ability to check it. Look for a document name and page next to every statement, not one link at the bottom. Clicking the citation should open the document at the highlighted passage. Ask the vendor whether citations are verified against the page before the answer appears.
How to test it. Ask five questions you know the answers to. Click every citation. Count how many open the right passage.
Point two, honest refusals
A knowledge base that invents an answer when the documents are silent is worse than one that says "I don't know". Employees act on what it says.
How to test it. Ask three questions your documents definitely do not cover, such as a benefit you do not offer. The right result is a plain statement that the documents do not answer, ideally with the closest passages checked.
Point three, permissions and spaces
Not everyone should ask every document. HR files, board materials and client contracts need separate spaces with their own members. Look for roles that separate who manages documents from who only asks questions.
How to test it. Create two spaces, add a colleague to one only, and confirm they cannot get answers from the other.
Point four, connected drives
If documents must be uploaded by hand, the knowledge base falls behind within weeks. Check which drives connect directly, whether you can choose specific folders, and how often they sync.
How to test it. Connect one real folder, change a file in it, and see when the answer reflects the change.
Point five, file types and scanned documents
Real libraries mix PDFs, Word files, spreadsheets, slide decks and old scans. Check that each type is read, that spreadsheet citations point to a sheet and cell range, slide citations to a slide number, and that scanned PDFs go through OCR.
Point six, admin and audit
Someone will be asked who saw what and when. Look for an audit log, invites managed by an owner, and a clear way to delete a space with all its documents.
Point seven, privacy terms in writing
Ask whether your documents are used to train models, how data is encrypted, and what happens on deletion. Prefer written, specific answers over general statements. Avoid tools that claim certifications they cannot show you.
Point eight, published price and clear limits
Knowledge base pricing is often hidden behind a sales call. Look for a published price, a clear number of seats, questions and pages per month, and what happens when you reach a limit. Be wary of "unlimited" claims on anything that costs the vendor money to run.
A one-week trial plan
- 1Day one. Pick one real use case with a clear owner: HR policies, past proposals, or a contract archive. Gather 20 to 100 representative documents.
- 2Day two. Set up one space, connect the folder, invite three colleagues who will actually ask questions.
- 3Days three and four. Each colleague asks the questions they asked a person last month. Record whether the answer was right, whether the citation opened the right passage, and how long checking took.
- 4Day five. Run the refusal and permission tests from the checklist.
- 5End of week. Count right answers, wrong answers and honest refusals. A good result is almost no wrong answers, even if some questions end in "not in the documents".
How ChatDocument maps to the checklist
- Cited answers. Every statement carries a citation with document name and page (slide for decks, sheet and cell range for spreadsheets). Each cited passage is checked in code to exist and contain the quoted text before the answer is shown. See cited answers from documents.
- Refusals. When the documents do not answer, ChatDocument says so plainly and shows the closest passages it checked. It never fills gaps from general knowledge.
- Spaces and roles. Owners, editors and askers, invites, saved threads and answers shared by link. Team plans and above include roles; Business and Enterprise add an audit log. See AI document management.
- Connected drives. Google Drive, SharePoint and OneDrive, and Dropbox, with selected folders syncing on a schedule. Starter connects one drive; Team and above connect all three.
- File types. PDF, Word (DOCX), Excel (XLSX, CSV), PowerPoint (PPTX), plain text, Markdown and web pages by URL. Scanned PDFs are read with OCR.
- Privacy. Encrypted in transit and at rest, never used to train models, processed by AI model providers bound by contract not to train on your content. Documents and index are deleted on request or with the space, and removed from backups within 30 days. SSO (SAML) on Enterprise.
- Price. Published plans: Starter 49 USD per month for one seat, Team 149 USD per month for 5 seats with 2,000 pooled questions, Business 499 USD per month for 15 seats with widget and API, Enterprise 1,490 USD per month for 50 seats with SSO and SLA 99.9. Yearly billing halves each price. Full limits are on the pricing page.
Mistakes that sink knowledge base projects
- Loading everything at once. Old drafts and superseded policies give conflicting answers. Start with current, approved documents.
- No owner. Someone has to decide which folders are connected and remove outdated files.
- Judging by demos only. Test with your own documents and your own questions, including ones that should fail.
- Ignoring the refusal rate. A tool that never says "not in the documents" is guessing somewhere.
For the HR case in particular, the HR policy chatbot page shows how a policy space works in practice.
Test the checklist on your own documents
Start with the demo: one PDF, one question, a cited answer with the passage highlighted. No card needed for the demo. Then create your account, connect one folder and run the one-week trial with your team.