←All insights
04 · Professional services · UK

An AI Assistant for Your Firm's Documents: Where Should You Start?

How UK consultancies and service firms can build a useful internal knowledge assistant without turning client documents into a shared free-for-all.

Audience

Partners, operations directors and knowledge managers

Reading time

6 min read

Published

2 November 2026

Research

3 sources

From question to verifiable answer
01

Ask

Scoped question

→
02

Permit

User access

→
03

Retrieve

Approved passages

→
04

Check

Source + version

→
05

Use

Professional review

Citations help reviewers inspect evidence; they do not guarantee correctness.

The useful answer is the one a colleague can trace to a document they were already allowed to read.

The short version
  • 01Begin with approved, owned material and a narrow question set.
  • 02Enforce access at retrieval, not just at the chat screen.
  • 03Treat citations as a route to verification, not proof of accuracy.
02

Permissions must travel with the document

At ingestion, record the document owner, client or matter, version, access rules and review date. At query time, apply the user's current permissions to the source material before retrieval. A chat interface that hides a document in the user interface but retrieves it for the model has not protected that document.

Separate public templates from client-confidential work. Agree retention, deletion, access logs, vendor processing terms and whether prompts or outputs can be reused. The ICO notes that data-protection risks depend on the purpose and the information processed; the system owner needs to understand both.

03

Make uncertainty visible

A response should show the specific passage, source title and date, with a way to open the original. If the answer combines sources, make each contribution inspectable. If the assistant cannot find an approved answer, it should say so and route the question to the knowledge owner.

A citation can point to the wrong paragraph, an out-of-date version or a document that does not support the conclusion. Ask reviewers to check whether the source actually answers the question rather than counting the presence of a citation as a pass.

04

Pilot with real questions, not a sales demo

Collect questions staff have already asked, including ones with no documented answer. Agree a reference answer and permitted sources before testing. Assess retrieval quality, unsupported claims, access leaks and the time a colleague spends checking each answer.

A worthwhile pilot might reduce the time to find an approved template while leaving advice, client commitments and final deliverables with the responsible professional. Expand the collection only when someone is accountable for keeping it current.

Decision checklist

Use this before approving the work.

  1. 01Choose a narrow collection and a knowledge owner.
  2. 02Apply document permissions before retrieval.
  3. 03Show source passages and version dates.
  4. 04Measure unsupported answers and reviewer effort.
Sources and further reading

Research and references supporting this article. Interpretation and recommendations are Thalenor’s.

The consultancy workflow is a proposed application; survey data does not establish its performance.

Published and reviewed on 2 November 2026. This article provides general technology and operational information, not legal, tax, medical or regulatory advice.

Read next · 05

Before Your Support Agent Uses AI, Decide What It Can Actually Do

Continue to the next guide