**Availability: blueprint example.** This article describes a possible tool, not a connected search service.

## The job

Find useful information in an approved collection and show the source behind an answer.

| Part | Example |
| --- | --- |
| Input | A question and a collection you are allowed to search. |
| Output | Relevant passages, source links and an optional draft answer. |
| Human review | Open the source and check whether it supports the answer. |
| Possible next step | Use the reviewed result in a report, procedure or draft response. |

## What makes the result useful

The collection needs clear ownership, access permissions and a process for updates or deletion. Search should respect those permissions. An answer should say when the available sources do not support a confident response.

## Questions to settle

Where do the files live? Who should see each collection? How fresh must the result be? Can the source be linked directly? What should happen after a source changes or is removed?

You can combine this idea with [document intake](/hc/productpat/articles/productpat-en-document-intake), but extraction and search solve different steps. Agree on the contract between them using the [connection walkthrough](/hc/productpat/articles/productpat-en-mix-and-match).