What is a knowledge base?
A knowledge base turns one technician's fix into something the whole team, and sometimes every user, can reuse. Most ticketing systems include one. An internal KB is for support staff and can hold admin procedures, server names and workarounds that should not be public. An external or public KB, often part of a self-service portal, answers common user questions such as how to reset a password or join the guest Wi-Fi. Vendors run large public knowledge bases as well. Microsoft, for example, identifies support articles and updates with KB numbers, which is why each entry in Windows Update history shows a KB identifier.
What a good KB article contains
- A title worded the way people search, including the exact error text or code
- Symptoms and scope, such as which OS versions, apps or devices are affected
- The cause, if it is known
- Resolution steps in order, with the expected result after key steps
- A workaround when no permanent fix exists yet
- Links to related articles, SOPs or known-issue records
- An owner, a last-reviewed date and the intended audience (internal or public)
How a KB works with tickets
- When a ticket arrives, the technician searches the KB by symptom or error code. Many ticketing systems suggest matching articles automatically.
- The technician applies the documented fix and links the article to the ticket, which shows how often each article is used.
- When a ticket is solved with a new fix, the technician writes a new article or updates an existing one from the resolution notes.
- Articles that are used often but fail to solve the problem are flagged for review.
Over time this cuts repeat work, gives new Tier 1 staff tested steps and reduces the number of tickets that need escalation. A public KB also deflects simple requests before they become tickets.
Keeping it accurate
A KB helps only if technicians trust it. Outdated steps, such as a menu path that moved after a Windows feature update, send people in circles. Assign each article an owner and a review date, retire articles for systems that no longer exist and collect feedback from readers. Public articles must not reveal internal hostnames, IP ranges or security settings, and no article should contain passwords.
Knowledge base vs similar documents
| Document | Purpose |
|---|---|
| KB article | Solve a specific problem: symptom, cause, fix |
| Standard operating procedure (SOP) | Perform a routine task the same way every time |
| FAQ | Short answers to common questions, often part of a public KB |
| Incident report | Record what happened during one specific event |
Knowledge base on the CompTIA A+ exam
Core 2 (220-1202) objective 4.1 covers ticketing, documentation and knowledge management, and knowledge base articles are one of the document types to know. If a question asks how to reduce repeat tickets or help new technicians solve common problems consistently, think knowledge base. If it asks what to do after solving a problem nobody had documented, writing or updating a KB article is a strong answer. If it asks where users can find answers without calling the help desk, think public KB or self-service portal. Vendor KB articles are also an authoritative source for checking a fix suggested by a forum post or an AI tool before you apply it.