Internal knowledge search that shows its sources

The operating context

In a growing professional-services team, useful guidance can end up in project documents, operating procedures, meeting notes, and client-specific workspaces. Staff need answers quickly, but the right response may depend on a particular version of a policy or on context that should not be shared across projects.

The product problem

A search tool that returns a confident paragraph without its source can make it harder to check an answer than to find one. A safer design treats retrieval, permissions, freshness, and review as part of the answer rather than implementation details hidden behind a chat box.

A possible workflow

1. 01Search a question against an approved set of connected documents, applying the same access rules as the source repositories.
2. 02Return a short answer only when retrieved passages provide enough support; show the document title, relevant excerpt, and last-known update alongside it.
3. 03Let the reader open the source and report a stale or incomplete result without copying sensitive content into a separate feedback channel.
4. 04When evidence is missing or sources disagree, say what could not be established and offer a route to the document owner or a human reviewer.

Design decisions worth making early

• Keep citations attached to each claim so a reviewer can inspect the evidence in context.
• Make the search boundary visible, including which repositories and document types were queried.
• Treat permissions and document deletion as part of the retrieval pipeline, not a later filter on generated text.
• Separate a useful draft answer from approved policy or client advice. Do not present generated text as an authoritative decision.

Constraints to resolve before a build

• The source systems, permission model, document formats, and update frequency would need discovery before selecting an indexing strategy.
• Evaluation should include unanswered questions, conflicting sources, revoked access, and stale documents, not only queries with an obvious answer.
• This is a product-design concept. It does not claim an assistant has been built, connected to company records, or measured with real users.

Questions for discovery

• Which sources are approved for search, and who owns their access and retention rules?
• What evidence must be visible before staff can rely on an answer for internal work?
• Which questions should always go to a person instead of the assistant?