Knowledge Base Template for Shared Work and AI Context

A knowledge base template is a repeatable structure for explaining a subject, the facts people can rely on, and where to verify them. A useful work template also names the owner, separates approved decisions from open questions, and says when the entry needs review. Copy the structure below and fill it for one recurring question.

You can use it in a document or wiki. fenbs is another option for the current work context, Decisions and rules, and reusable prompt that connected assistants need. Keep long source documents in their existing homes and link to the relevant section instead of duplicating everything.

What can you copy into a new entry?

The template is designed for an internal answer that people will use while doing work. Replace each bracketed instruction with a specific statement, source, or named responsibility. If a fact has not been checked, leave it visibly unconfirmed instead of filling the space with a plausible guess.

Title: [The question this entry answers]
Purpose: [Who needs this answer and what they do next]
Scope: [Project, team, product, or situation covered]
Outside scope: [Cases this answer must not cover]

Approved facts:
- [Fact, supporting source, and date checked]
- [Important limitation or exception]

Decisions and rules:
- [Approved choice, person who decided, and reason]
- [Continuing instruction and its scope]

Sources:
- [Source title, original location, version, and owner]
- [Access needed and where to request it]

Working guidance:
1. [First useful action]
2. [Next action and what good looks like]
3. [When to stop and ask a person]

Ownership and review:
Entry owner: [Person or responsible role]
Last verified: [Date and what was checked]
Review trigger: [Change or event that requires review]

Open questions:
- [Unanswered question and person responsible]

Change note:
[What changed, why, and which earlier guidance it replaces]

Use a narrow title such as “Which design files are approved for the customer handoff?” rather than “Design.” Narrow titles make it easier to recognize when an entry answers the current question. They also discourage an assistant from treating a general explanation as permission to act in a specific case.

Do not force every field to be long. A two-sentence scope and a short, well-supported answer can be enough. The structure earns its place by preventing confusion, rather than by making each page look complete.

How do you separate facts, decisions, and instructions?

A fact describes something supported by evidence. A decision records a choice a person made. An instruction says how the work should proceed. Keeping them separate lets readers tell whether they need a better source, a new decision, or clarification of the process.

Record the origin of a statement as well as its wording. The W3C provenance overview↗ (opens in a new tab) describes how information about origin and production helps people assess reliability. For this template, a source reference and attribution give the reviewer a practical path back to the evidence.

When an entry contains a procedure people must follow, link to a dedicated SOP template rather than expanding this page into a full operations manual. Keep the reusable answer and the detailed procedure connected but maintain each in one authoritative place.

What does a filled IT entry look like?

Here is a hypothetical IT knowledge base template for an employee who cannot access an internal design folder. It helps the person report the problem safely and gives an assistant enough context to prepare a useful request. It does not grant the assistant administrative authority.

Title: How do I request access to the client design folder?
Purpose: Help a project member request the right access.
Scope: Members already assigned to the design project.

Approved facts:
- The source files remain in the approved file system.
- The project owner reviews access requests.

Rule:
Do not share passwords, sign-in codes, or private download links.

Sources:
- Current folder location: [internal source reference]
- Access instructions: [approved internal procedure]

Working guidance:
1. Confirm the correct work account is signed in.
2. Record the folder name and the visible access message.
3. Ask the project owner for the minimum required access.
4. Stop if the request involves another client’s folder.

Owner: Project owner
Review trigger: Folder moves or ownership changes
Open question: Which backup owner handles absence?

Make the account and access instructions match your actual systems before using this example. An entry about a denied request should explain where to get approval, rather than suggest a workaround that bypasses the owner. Leave sensitive details in the appropriate support system.

A service recovery procedure needs more detail about diagnosis, checks, and escalation; use a runbook template for that. This entry stays focused on a single employee question and its safe next step.

How should an AI assistant use the template?

Ask the assistant to work only from supplied, approved material and to name missing evidence. It can organize rough notes, identify contradictions, and propose clearer wording. A person still verifies the facts and approves any decision or continuing rule.

Use the knowledge entry structure to organize the supplied material.
Answer only the stated question and stay within its scope.
Separate supported facts, human decisions, instructions, and open questions.
Keep each fact connected to its supplied source reference.
Do not invent approvals, owners, review dates, or source contents.
List conflicts and missing evidence for a person to resolve.
Return a draft for review, followed by the unanswered questions.

Check the draft against the sources, rather than checking only its tone. Ask whether each claimed approval exists, whether the suggested owner is correct, and whether an exception changed meaning. A well-formatted entry can still be wrong.

How do you keep the entry useful after publication?

Give each entry a review trigger as well as an owner. A product change, moved source, new decision, or failed procedure can make the answer unsafe before its next scheduled review. When someone finds a problem, record what was wrong and which action needs rechecking.

Keep the current answer clear while preserving enough history to understand a change. The National Archives electronic records requirements↗ (opens in a new tab) cover maintenance, use, and metadata across a record’s life. Those federal requirements are not a universal private-business checklist, but they illustrate why upkeep belongs alongside initial capture.

For an entry with a recurring verification job, create a task with an explicit completion check. Our task list template helps turn “review the entry” into a concrete action such as opening the source, confirming ownership, and testing the stated next step.

In fenbs, keep the review task with the project and record a lesson if an outdated entry caused a repeated mistake. That makes maintenance part of the work rather than an invisible obligation attached to a document.

How to do this with fenbs?

1. Create a free account, free for one person with no credit card, and add the project that needs a repeatable answer.
2. Use the template fields to prepare focused context notes. Keep full source documents in their current systems and add the references the next session needs.
3. Record the person’s approved choices in Decisions and rules. Save the drafting prompt in Skills and prompts so connected assistants can reuse it.
4. Connect a supported AI app using the setup guide, ask it to read the project context, and have it draft one entry for review. Save the verified progress and remaining questions before stopping.

fenbs fits active project context and reusable instructions. It does not provide a public help-center publishing system or automatically index your documents; choose a dedicated knowledge-base publisher when those are the main requirements.

Keep the first entry small enough that another person can test it immediately. For selecting the material behind an answer, explore the context engineering collection. A template is successful when the next reader knows what to trust, where to check it, and what to do next.