Data · Guide
Before the chatbot: audit the knowledge it will use
A practical inventory that exposes ownership, gaps, and duplicate guidance before indexing begins.
Inventory decisions, not just files
A folder count is not a readiness measure. Begin with the decisions staff need help making: which onboarding form applies, who approves an exception, or when to escalate a service request. For each decision, identify the authoritative document, its owner, the audience, and the date its instructions were approved. The linked RAG documentation supplies technical context; this inventory is our suggested operating practice.
Use a small representative sample
For an illustrative consulting firm, inspect a current procedure, an old procedure, a checklist, a presentation, and several difficult client questions. Mark whether each answer is explicit, implied, missing, or contradictory. An assistant should not silently turn an employee’s informal workaround into company policy. Resolve a handful of important gaps before expanding the collection; an enormous index can conceal a surprisingly thin evidence base.
Workflow at a glance
Separate usable from quarantined
Create three states: approved for retrieval, reference-only, and quarantined pending review. Keep original files and record why an item was excluded. Sensitive material requires a separate permission decision rather than a convenient folder name. Put the inventory in the handover package so future employees know who can authorize changes. This also gives the project a visible backlog rather than an indefinite promise to clean everything later.
Define a readiness gate
A useful pilot gate is modest: named owners for the selected sources, a small set of answerable questions, documented exclusions, and a way to report missing knowledge. Do not claim that this proves completeness or compliance. Revisit the inventory when services, responsibilities, or client contracts change. Data readiness is an ongoing operating responsibility, not a certificate issued when the chatbot launches.
A bounded inventory workshop
Invite an operations owner and one frequent document user to map a single service. Finish with an approved-source list, unresolved questions, and named actions. If ownership remains unclear, postpone indexing that material rather than treating technical availability as approval.
Sources and further reading
Editorial approach
AI-assisted original writing, checked against linked public sources. Practical recommendations and illustrative scenarios are editorial analysis, not reported client results. Source dates and product details may differ from this collection’s preparation date.