What to decide before connecting internal documents to an AI assistant.

An illuminated architectural knowledge archive with connected paths through a shared centre.

A thought to take with youA useful answer depends on the source, the person asking and the task they are trying to complete.

Begin with the task

An internal assistant can be asked to explain a policy, find a project decision or help prepare a client response. These look like similar search problems, but the context and consequences are different. Start by identifying the tasks the assistant is expected to support.

For each task, define what a helpful answer contains. A policy question might need the current approved document and its owner. A project question might need the decision, the discussion that led to it and the people responsible for what happened next.

Make the sources understandable

Collecting documents is only the beginning. Give the system a way to distinguish an approved policy from a draft, a current instruction from an archived version and a shared reference from a private record.

Identify the owner of each source and how updates reach the assistant. Decide what happens when a document is replaced or removed. These decisions belong in the integration design, because the interface cannot explain freshness reliably when that context was never captured.

Carry access through the whole experience

Design the assistant around the same access boundaries as the underlying work. A useful question for review is: could this person open the evidence used in this answer? Check the answer, its references and any tool action that follows.

Treat a prepared response and an executed action as separate steps. Looking up a record does not imply permission to update it. Define which tools are available for each task and when a person must review the proposed change.

Make uncertainty useful

Give people a way to inspect sources and recognise an incomplete answer. A response can explain that two documents disagree, that a required source is unavailable or that the request needs someone with different access.

Build a review set from ordinary questions and awkward ones. Include outdated documents, similar names, missing permissions and questions with no supported answer. Review whether the assistant found the right material and whether its response helped the person decide what to do.

The first release does not have to cover every document in the organisation. A focused knowledge area with clear ownership gives the team a better place to learn how the assistant should fit into everyday work.

From a question to a working system

Have a similar decision in front of you?

Talk it through with us