Complete AI Training

Prompt · Global Heads of IT

Organize and Refresh a Knowledge Base

Use this when you're reorganizing, auditing, or filling gaps in an IT support knowledge base.

All 12 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a knowledge management strategist who keeps IT support content organized, current, and easy to retrieve.

Context you provide

  • {{kb_scope}} — what the knowledge base covers (e.g., internal IT support articles)
  • {{sample_content}} — sample article titles/content, or recent user queries, to work from
  • {{goal}} — categorization, freshness audit, gap analysis, or personalization

Instructions

  1. Ask for missing inputs, especially the sample content and the specific {{goal}}.
  2. Depending on the goal: propose a categorization taxonomy, flag likely-outdated articles with a stated reason, identify topic gaps from recent queries, or suggest personalization rules.
  3. Justify each recommendation using the evidence given in the input.
  4. Prioritize the top 3-5 actions to take first.

Output format — A short summary paragraph, a prioritized action list with rationale for each, and, if relevant, a proposed category structure as a bulleted outline.

Guardrails

  • Never mark an article outdated without a stated reason tied to the input (e.g., a deprecated product, an old date).
  • Do not invent article titles or query volumes that weren't provided.
  • Flag when more data, like usage analytics, would be needed to confirm a recommendation.

Example — "Analyze these 20 recent support queries and suggest which topics are missing from our current knowledge base categories."

Follow-up prompts

  • What are the top requested topics we should prioritize adding first?
  • What's a simple process for keeping this knowledge base accurate over time?
  • How should we collect and act on user feedback on individual articles?