gap-analysis

Knowledge gap analysis identifies missing documentation by analyzing incident and case data to surface high-volume topics lacking adequate knowledge base coverage. It correlates unresolved incident categories with existing articles to pinpoint where self-service fails.

To find knowledge base coverage gaps, analyze incident and sn_customerservice_case records against existing kb_knowledge articles. This surfaces recurring incident categories that lack corresponding documentation, guiding targeted content creation.

Yes, performing knowledge gap analysis requires access to ServiceNow incident, sn_customerservice_case, kb_knowledge, kb_feedback, and search_log tables. These data sources aggregate to surface failed queries and missing topics accurately.

Analyzing search logs reveals failed queries and missing topics by tracking what users search for without finding relevant kb_knowledge articles. This data identifies specific areas needing article expansion to improve self-service success rates.

The best way to prioritize content creation is analyzing incident volume against knowledge base coverage gaps. Generating prioritized backlog items from high-volume unresolved incidents ensures authors focus on articles delivering maximum self-service impact.

Gap analysis fails to surface missing topics when MCP tools cannot properly aggregate incident, case, and search_log data. Incomplete permissions or missing access to kb_feedback and related ServiceNow reports restrict comprehensive coverage gap visibility.