1. Choose the team's questions
List the repeated questions and the work they support. Agree on the approved source collection, users and situations needing a person.
From documents to checked answers
Test what the assistant should answer and what it should not.
A useful pilot needs representative questions, source ownership and clear access rules.
2. Review the information
Identify current versions, conflicts, duplicates and restricted documents. Arrange protected access through the agreed process rather than collecting everything in a public inquiry.
3. Build the answer and review experience
Let users inspect the relevant source and report a problem. Make missing information and unavailable services understandable.
4. Evaluate representative cases
Check source-supported answers, incomplete sources, conflicting versions and restricted access. Use synthetic identities and controlled information where appropriate.
5. Pilot with an update owner
Agree on the initial users, cost limits, correction handling and refresh process. Review failures before adding more collections or actions.
Keep the source and model configuration with the test record.
Relevant changes need the agreed checks repeated. Use the pilot checklist.