Check source ownership, freshness and permissions before adding conversational search.
Find competing answers
Ask several colleagues where the current policy lives. Different answers expose a source-management problem that AI will inherit. Identify obsolete versions and contradictory guidance. Decide which source is authoritative before improving retrieval. Finding the wrong document faster does not make the organisation better informed.
Assign freshness responsibility
Important documents need an owner and a review process appropriate to the subject. Preserve effective dates and withdrawal rules. An upload pipeline is only half the job: the product also needs a dependable way to stop serving content that should no longer guide decisions. Agree who checks the collection after a policy change.
Map access at source
Separate general information from client-specific or team-specific records. Check whether source permissions can survive indexing and retrieval. Do not assume every employee may access everything because the interface is shared. Start with a small collection whose ownership and permissions are straightforward.

Collect real questions
Build an evaluation set from questions people actually ask. Identify expected sources and conditions that change the answer. Include questions with no documented answer. If a task requires unwritten judgement held by one person, improve the underlying documentation instead of expecting a model to fill the gap convincingly.
Your next working session.
- Remove obsolete guidance
- Name source owners
- Test access boundaries
Bring one real, anonymised example to the discussion. Work through the choices above with the person responsible for the outcome, record the unresolved questions and agree who will investigate them.
Elite Apps editorial · Practical planning guidance. Examples and diagrams are illustrative; implementation depends on your requirements. Technical and supplier guidance can change.