Andrew Ritson & Co. All articles
Operations & Technology

Who Is Listening In? Governing AI Meeting Notes Before the First Client Objects

Andrew Ritson & Co.
Who Is Listening In? Governing AI Meeting Notes Before the First Client Objects

Photo by Photo by GB The Green Brand on Unsplash on Unsplash

Most firms do not decide to adopt meeting transcription software. One fee-earner does. A free trial, a better set of attendance notes, a colleague who notices the quality of the summary, and within a quarter there are eleven subscriptions across four teams, billed to individual cards, none of them recorded in the firm's software register. The technology is useful. The manner of its arrival is the problem.

The question for a UK professional firm is not whether AI notetakers should be banned. It is whether the firm could explain, to a client, a regulator or its professional indemnity insurer, why a particular meeting was transcribed, where the recording now sits, who can retrieve it, and when it will be deleted. That explanation should not depend on the memory of the person who signed up.

The confidentiality problem is older than the software

Firms have taken notes in client meetings for a century. What changes is that the note is now made by a third-party processor, on infrastructure the firm does not control, and often retained by default for longer than the firm retains the file. For regulated practices the usual obligations still apply: confidentiality, data protection, and — in legal and advisory work — the care needed to avoid any argument that privilege has been compromised by disclosure to an outside processor.

None of this makes the tools unusable. It makes them something to govern rather than tolerate.

Before the meeting

A short, consistent pre-meeting routine does most of the work.

Ask whether a transcript is necessary. A fifteen-minute catch-up rarely is. A complex instruction-taking meeting, a board interview, a lengthy negotiation — those are the cases where a transcript earns its keep.

Check who will be present. Internal colleagues, a client, an opposing party, a witness, a third-party adviser. The more parties, the more consent conversations are required.

Say it in the invitation, not in the meeting. A line in the agenda or the calendar entry — that the firm uses a transcription tool, what it records, where the output is stored and how long it is kept — gives people a chance to object before they are on the call.

Check the client's own position. A growing number of in-house teams prohibit third-party AI tools in meetings with external advisers. Ask once, record the answer, and route it to the client file so that it travels with every subsequent matter.

Consider the geography. The UK has no general prohibition on recording a conversation to which you are a party, but several jurisdictions require all participants to consent. If a client dials in from Germany or California, that matters.

During the meeting

Announce the tool at the start, and do it the same way every time so that it becomes unremarkable. Name it, say what it does, and invite objections. If someone objects, stop the tool rather than the meeting — that is the whole point of having a protocol.

Do not let a bot join a call silently, and do not leave one running in a room where a third party has not been told. Most of the reputational damage in this area comes not from the software but from the moment a client discovers, weeks later, that a meeting they thought was private had been transcribed and is searchable by keyword.

After the meeting

Three habits separate a defensible practice from a hopeful one.

Check the output before it is relied upon. Automated summaries mishear figures, misattribute remarks and occasionally invent a conclusion that nobody reached. A transcription is a note, not a minute. It should not become the authoritative record of a decision unless a human being has read it.

Set a retention default. Vendor defaults vary widely, from thirty days to indefinitely, and some free tiers retain content in order to improve their models. A firm default — ninety days for transcripts that are not part of the matter file, with exports retained in the file where they are — is usually enough. Turn off model training on customer data in the account settings, where that option exists.

Record provenance in the file. Tool name, date, participants and duration, filed with the matter. Six months later, when a client queries what was agreed, that line is worth more than the transcript itself.

Reading the terms as a firm, not as a user

A partner clicking "I agree" is not a data processing agreement. Before a tool is approved for client work, someone should be able to answer:

For most small and mid-sized firms the practical answer is to approve one or two tools on a business tier, document the review, and prohibit everything else.

When the client says no

Some will. Take it as an operational preference rather than a slight. The fallback options are straightforward: a human note-taker, firm-hosted transcription inside the firm's own Microsoft 365 or equivalent tenant, or no record at all beyond a written summary sent afterwards for confirmation.

Whatever is agreed, put a flag on the client record. Preferences held in a fee-earner's head are not controls.

A one-page policy that survives scrutiny

The finished policy need not be long. A permitted tools list, an approval route, a consent script, a retention default, a client flag and an annual review will cover the substance. Circulate it, and mention it at induction.

The test of a good policy is not how many tools it stops. It is whether any fee-earner in the firm can answer three questions without hesitating: was the client told, where is it stored, and when is it deleted.

All Articles

Related Articles

Twelve Months on a Single Sheet: A Lean Firm's Compliance Calendar for 2026

Twelve Months on a Single Sheet: A Lean Firm's Compliance Calendar for 2026

The Locked Screen and the Legal Clock: A Partner's First Morning After a Cyber Breach

The Locked Screen and the Legal Clock: A Partner's First Morning After a Cyber Breach

The Lost Proposal Is Not a Dead End: Learning from Silence in UK Professional Firms

The Lost Proposal Is Not a Dead End: Learning from Silence in UK Professional Firms