Selected documents
Start with an approved folder and an agreed list of questions.
AI search
Ask a question. Get an answer linked to the relevant passage in your documents.
Discuss this task
When a person takes over: If no submission window is stated, send the question to an owner
When a person takes over: If guide versions conflict, show them for review
When a person takes over: If no relevant material exists, do not invent an answer
Start with an approved folder and an agreed list of questions.
Clarify material groups, access rules and who keeps them current.
Plan search across your sources after reviewing formats and access.
From materials you approve: documents, instructions or a knowledge base.
The workflow should mark the gap and send the question to a person instead of guessing.
That depends on your sources and access model, which need review during scoping.
That needs checking against the questions you want answered: which versions are current and whether the files, tables and scans can be read properly. Someone on your side needs to confirm the content.
The project needs a clear update process and a person responsible for it. Changing a file does not prove that search is using the new version, and removing it does not prove all copies have disappeared. If an essential update or permission cannot be confirmed, the affected answer should wait.
We agree what the solution needs to do, then check the actual version against that: you should be able to see what was tested, what worked and what still needs attention. A design concept shows an idea; a technical example only shows a tested result when tests were actually run, and neither replaces checks for your project. Accepting the work and putting it live are separate decisions.