The questions your documents can't answer yet

Most knowledge tools can tell you what people read. Almost none can tell you what people looked for and didn't find. That second list is worth far more — it's a ranked backlog of documentation your team needs and doesn't have.

Where the gaps list comes from

AskMyDocs refuses to fake answers: when retrieval finds nothing relevant to a question, it says so. Every one of those honest misses is recorded, and the admin Insights screen collects them into a knowledge-gaps list — the actual questions your teammates asked, verbatim, that no document could answer.

Reading it feels uncomfortably specific. "What's the travel reimbursement limit for client visits?" asked three times in a week isn't an analytics data point; it's an assignment with a deadline.

The rest of the picture

• Queries per day and active users — is the team actually asking, or still pinging the one person who knows things?
• Most-cited documents — the pages doing real work; keep these current first.
• Answer feedback — thumbs up and down on answers, reviewable in one place.

A simple weekly loop

The workflow we see working: once a week, an admin opens Insights, takes the top three knowledge gaps, and gets the answers written into a document — a policy page, an FAQ, a runbook. Drop it into a synced folder and it's indexed within minutes. The same question next week gets a cited answer instead of a miss, and the gap disappears from the list. Documentation stops being a someday project and becomes a short weekly errand driven by real demand.