The questions your own team asks, and who they interrupt to ask them
In most organisations the fastest way to find out something is to ask the person who knows, and that is precisely the problem: the cost lands on whoever is most knowledgeable, it is invisible because nobody records interruptions, and the answer never gets written down because asking worked. The documentation is not missing - it is unused, which is a different problem with a different fix.
The cost is concentrated, not spread
Internal questions do not distribute evenly. They converge on three or four people - the one who knows the billing system, the one who remembers why the process changed, the one who has been there longest - and those people are usually also the ones with the least interruptible work. Before buying anything, ask them to note for one week what they were asked and by whom. The list is almost always shorter and more repetitive than anyone expects.
Search failing is a finding, not a user error
People ask a colleague because searching did not work, and searching did not work for findable reasons: the document uses the official term and the person searched the everyday one, the answer is in a slide deck attached to an email, or three documents disagree and none is dated. An assistant that reads the same documents will fail in the same places, which is useful - its failures are a precise audit of which documents are unusable.
Decide what is allowed to be answered this way
This is the part that cannot be skipped. Salary bands, disciplinary matters, anything in a personnel file, commercially sensitive terms and anything an individual told HR in confidence must not be in the same pool as the expenses policy and the VPN instructions. The decision is about which documents are in scope and who may ask, and it is an access-control decision rather than a software setting. Make it before the first document is loaded, not after somebody asks an interesting question.
The unanswered log is the documentation backlog
What the assistant could not answer, ordered by how often it was asked, is the first genuinely prioritised documentation list most organisations have ever had - and it is prioritised by real demand rather than by whoever volunteered to write. Organisations routinely find the exercise was worth more as a knowledge audit than as automation.
Frequently asked questions
What is an internal knowledge assistant for?
How do we keep sensitive material out of it?
What if our documents contradict each other?
Will it work if our knowledge is in people's heads?
How do we know whether it helped?
Get in touch
Leave your details and we will reply. You do not need a sales call to get an answer.