Free prioritization tool – No sign-up

Knowledge Gap Opportunity Prioritizer

Turn support-ticket demand, on-site search behavior, and existing coverage evidence into a transparent article opportunity queue. Keep ticket and search units separate, review every grouping decision, and carry selected work into drafting and governance.

By Knowledge Base Software Editorial Team–Methodology KBGOP-1.0–Updated August 4, 2026

Start prioritizing gaps

Demand stays attributableTicket volume, search volume, and friction rates remain separate and visible.

No fuzzy merging by defaultExact reviewed keys and compatible context control cross-source grouping.

Private and portableFiles are processed in this browser. Export a queue, evidence record, brief, or print report.

Step 1 of 4Set scope

Nothing is uploaded. Inputs remain in this browser tab unless you deliberately download a report.

Define the evidence boundary

Name the prioritization run, freeze one evidence window, and declare how the rows were counted. These settings travel with the report so another reviewer can reproduce the queue.

Project name *

Evidence window start *

Evidence window end *

Input row grain *Choose one grain for this run. Rows that contradict it are rejected instead of being combined silently.

Likely sensitive text handling *Pattern detection is a precaution, not a compliance guarantee. Remove sensitive data before import when possible.

Scope note

Review the comparison thresholds

Replace these defaults with the minimum and material demand levels that make sense for your evidence window. They are comparison rules for this run, not universal performance benchmarks, and every applied value is retained in the evidence export.

Ticket minimum demandThe smallest ticket count worth routing in this window.

Ticket material demandA ticket count that warrants near-term attention in this window.

No-result search minimumThe smallest no-result search count worth routing in this window.

No-result search material demandA no-result count that warrants near-term attention in this window.

Minimum friction rateThe source-specific rate worth routing for review.

Material friction rateA source-specific rate that warrants near-term attention.

Before importing: export the smallest useful set of fields, remove message bodies and notes, and prefer stable non-person identifiers. Do not include passwords, tokens, payment data, health data, or other restricted information.

Add ticket, search, and coverage evidence

Choose CSV or JSON files from your device. Ticket evidence and search evidence are imported as different units. Coverage is optional, but unknown coverage lowers confidence and creates a validation action.

1. Support tickets

Questions or problem summaries, stable IDs, explicit counts, escalation or repeat-contact evidence, impact, and context.

Ticket CSV or JSON Required unless search evidence is supplied.

No ticket file selected.

2. On-site searches

Search terms, stable IDs, explicit counts, zero-result events, refinements or exits, impact, and context.

Search CSV or JSON Required unless ticket evidence is supplied.

No search file selected.

3. Existing coverage

Optional article coverage, status, URL, last review, owner, and a human effort estimate linked by an explicit opportunity key.

Coverage CSV or JSON Optional. Missing values remain Unknown, never zero.

No coverage file selected.

No evidence inspected. Limit: 4 MiB and 5,000 rows per source, with 15,000 rows total.

Supported columns and grouping fields

Tickets

ticket_id, question, opportunity_key, ticket_count, escalations, repeat_contacts, impact, audience, product_area, locale, grain

Searches

search_id, search_term, opportunity_key, search_count, zero_results, refinements, exits, impact, audience, product_area, locale, grain

Coverageopportunity_key, coverage_status, article_title, article_url, owner, last_reviewed, effort

Import boundary: malformed rows, conflicting duplicate IDs, context-conflicting mappings, oversized fields, and likely sensitive rows are quarantined or excluded with a reason. The tool does not silently keep the first conflicting row.

Review the opportunity groups

Inspect the exact normalized groups before ranking. Ticket and search text are not cross-merged unless an explicit reviewed key connects compatible locale, audience, and product-area context.

Review groups0

Accepted rows0

Excluded rows0

Warnings0

Find an opportunity

Evidence source

Validation need

Review imported evidence before building the queue.

Swipe or scroll horizontally to review every grouping field.

Opportunity groups awaiting review
Candidate opportunity	Evidence sources	Reviewed key	Locale / audience / product	Coverage / action route	Effort	Review

Import ticket or search evidence to create review groups.

Review rule: reusing one key is an explicit merge decision, but incompatible locale, audience, or access context still blocks the merge. Choose an action route rather than assuming every gap needs a new article. Effort is always entered by a person as S, M, L, XL, or Unknown; it is never inferred from volume.

Knowledge gap opportunity queue

The report applies explicit decision rules while keeping confidence, editorial route, and effort separate so reviewers can see why each opportunity appears where it does.

Opportunity queue ready

Review Do now work, resolve Validate first evidence, and assign owners before drafting.

Opportunities0reviewed groups

Do now0material, actionable evidence

Validate first0confidence or coverage gaps

Known effort0%human estimate supplied

Do now0

Next0

Validate first0

Monitor0

Prioritized opportunity queue

Ordering uses a deterministic lexicographic cascade: decision category, material impact, material demand, material friction, confidence, then reviewed key. Categories come from explicit gates and do not forecast deflection, return, or article quality.

Find opportunity

Decision category

Action route

Confidence

Swipe or scroll horizontally to inspect the complete opportunity queue.

All prioritized knowledge gap opportunities
Order	Opportunity	Decision / route	Ticket evidence	Search evidence	Impact / coverage	Friction rates	Confidence / reasons	Effort / next check

Export a reviewable evidence package

Downloads include methodology version, thresholds, units, warnings, exclusions, and null values for Unknown. They exclude raw ticket or search text that was quarantined as sensitive.

Continue the evidence-to-publishing workflow

Select one reviewed opportunity before exporting its brief or opening the next tool. Data is not transferred between pages automatically.

Selected opportunity

Next: draft from evidenceKnowledge Base Article Generator

Use the exported brief to create an Article, FAQ, SOP, or How-to draft.

Open Article Generator View all free tools

Then: plan ownership and reviewGovernance Capacity and Review Planner

Turn approved opportunities into an owned review workload and capacity plan.

Open Governance Planner

View all free tools

From unresolved demand to an owned knowledge opportunity

The prioritizer connects three evidence types without disguising their different units or overstating what they prove.

Demand

Preserve ticket evidence

Repeated support questions show documented demand. Escalation and repeat-contact rates add friction evidence only when their denominators are known.

Findability

Preserve search evidence

Search terms show what people try to find. Zero results, refinements, and exits are evaluated as separate rates rather than combined with ticket counts.

Coverage

Choose create, update, or validate

Missing coverage can route to creation; partial or stale coverage can route to an update; unknown coverage stays a validation task.

Grouping

Make joins reviewable

Safe normalization supports exact grouping. Cross-source joins require an explicit reviewed key and compatible locale, audience, and product context.

Confidence

Keep certainty separate

A high-volume single source cannot become High confidence. Confidence reflects source diversity, explicit keys, known coverage, and complete denominators.

Execution

Hand off without hidden transfer

Export a selected article brief for drafting and a governance CSV for capacity planning. Nothing is sent to another service automatically.

Transparent decision methodology

KBGOP-1.0 uses explicit evidence gates. Decision category, confidence, action route, and effort stay separate so a reviewer can understand and override each part.

KBGOP-1.0 decision categories and separate review fields
Output	Decision rule	Required review	What it does not prove
Validate first	Applied when grouping or identity conflicts remain, coverage is Unknown, material friction lacks a denominator, or the evidence is otherwise too incomplete to choose an accountable route.	Resolve the named evidence gap; do not let raw volume override Low confidence.	That the opportunity is unimportant.
Do now	Applied when reviewed evidence reaches the declared material demand level and shows material friction or high-impact consequences, with a known coverage state and an actionable route.	Confirm the route, source of truth, owner, and publication or non-content acceptance checks.	ROI, deflection, urgency outside this evidence window, or permission to publish.
Next	Applied when reviewed evidence reaches the declared minimum demand level and has a known coverage state and actionable route, but does not meet the Do now gate.	Schedule against available capacity while preserving the evidence window and assumptions.	That lower category means low user value.
Monitor	Applied when valid evidence remains below the declared minimum demand and no high-impact exception is recorded.	Keep the exact key stable and recheck after the next comparable evidence window.	That no knowledge or product problem exists.
Confidence	High, Moderate, Low, or Insufficient is calculated separately from category using explicit keys, compatible context, source diversity, known coverage, and complete denominators.	A single source cannot become High confidence through volume alone.	Decision category or factual accuracy.
Action route	A reviewer chooses Create, Update or expand, Improve findability, Consolidate or redirect, Non-content fix, or Investigate.	Verify that the selected response addresses the observed problem; not every gap needs an article.	That content creation is the default remedy.
Effort	A person supplies S, M, L, XL, or Unknown. The tool never derives effort from volume or wording.	Estimate with the team that will complete and approve the work.	Delivery date or available capacity.

Method boundaries: no fuzzy similarity merge is applied. Different verbs, negations, error codes, locales, audiences, and access contexts remain distinct unless a reviewer provides a compatible explicit key. Ticket and search counts are never added into one raw demand total. Exact duplicates are counted once; conflicting duplicate IDs are quarantined for review.

Local processing and safer evidence handling

The tool is designed for minimized exports, not raw support conversations. Files are read in your browser and the report excludes quarantined text.

Minimize

Export only useful fields

Prefer stable IDs, short issue summaries, counts, evidence states, and non-person context. Remove message bodies and internal notes before import.

Detect

Exclude likely sensitive rows

The safest mode excludes rows containing likely email addresses, phone numbers, payment-like strings, or secret patterns. Detection can miss data and can create false positives.

Retain control

Download deliberately

No account is required. The tool does not send files, store a project in browser storage, or transfer evidence to the next tool automatically.

Important: local processing and pattern screening do not make restricted data safe to use. Follow your organization’s data classification, access, retention, and legal requirements.

Knowledge Gap Opportunity Prioritizer FAQ

What data should I import?

Import a minimized CSV or JSON export containing short ticket questions or search terms, stable non-person IDs, explicit counts, friction counts, impact, and context. Coverage evidence is optional. Avoid message bodies, names, email addresses, phone numbers, tokens, payment data, or other restricted information.

Does the tool combine ticket counts and search counts?

No. Ticket and search volumes remain separate units. Decision gates compare each source with the user-declared minimum and material thresholds, but the report never creates a fictional combined raw total.

How are similar questions grouped?

Within a source, safe normalization supports exact grouping. Tickets and searches are not cross-merged by text alone. An explicit reviewed key and compatible locale, audience, product area, and access context are required for a cross-source group.

Is a Do now opportunity ready to publish?

No. Do now means reviewed evidence passed the declared material-demand and actionability gates. Confidence, coverage validation, action route, ownership, factual verification, effort, and editorial approval remain separate requirements.

Are my ticket and search files uploaded?

No. The tool processes selected files in the current browser tab. It does not require registration or automatically transfer evidence to another tool. Any downloaded report is saved only when you choose an export action.

What should I do after prioritizing a gap?

Export the selected article brief and use the Knowledge Base Article Generator to create a draft. After the opportunity is approved, export the governance handoff to plan ownership, review capacity, and recurring verification.

Method references: the demand-driven principle follows KCS demand-driven knowledge and its guidance to create knowledge in response to observed demand. Search-term evidence aligns with the Google Analytics search_term definition. These sources inform the evidence model; they do not endorse this tool or its decision thresholds.

Continue with free knowledge base tools

Use the opportunity queue as a bridge from measured demand to drafting, governance, search testing, and content maintenance.

This prioritizer supports evidence review; it does not verify user intent, diagnose root cause, promise ticket deflection, establish ROI, or replace accountable editorial and privacy review.