Minutes, Recorded: Writing an AI Notetaker Policy Before It Becomes Habit
Photo: Shixart1985, CC BY 2.0, via Wikimedia Commons
A notetaking assistant now joins meetings in most large UK organisations as a matter of course. In smaller firms the pattern is different and less orderly: one manager discovers the feature in a video platform, enables it, and within a month half the team assumes recording is normal. Nobody has decided anything. That is the problem.
Meeting recordings and AI-generated summaries are personal data processing. They capture what people said, sometimes what they implied, occasionally what they should not have said in front of a colleague. Under UK GDPR the firm needs a lawful basis, a transparent notice, a retention position and a contract with the supplier. None of that is exotic, but none of it happens by accident either.
Decide the basis before you choose the vendor
For most internal meetings, legitimate interests is the workable basis, supported by a short legitimate interests assessment that records why recording is useful and why it is proportionate. Consent is a poor fit for employment contexts because of the imbalance of power, though it may be the right approach for some external conversations.
Two further obligations need attention. If transcription is widespread and systematic, a data protection impact assessment is prudent and often expected. And if meetings can touch on health, ethnicity, trade union membership or similar, you are handling special category data, which requires a specific condition and considerably more care.
The notice takes thirty seconds
Announce at the top of every recorded meeting: that recording is starting, which tool is being used, the purpose, the retention period, where the output is stored, who can access it, and how to object. If someone objects, either pause the recording or exclude the sensitive segment.
For external attendees, state it in the invitation as well as at the start. For recurring internal meetings a standing note in the series is acceptable, but re-announce whenever a guest joins, because they have not seen the series description.
Meeting hygiene: some conversations should not be transcribed
A short no-record list is worth more than a long policy. One-to-ones, disciplinary and grievance meetings, HR investigations, legally privileged discussions, commercially sensitive negotiations, candidate interviews and anything covered by an NDA that prohibits recording. Require an explicit decision to record rather than an assumption of yes, and make the default for those categories a clear no.
It is also worth reminding people that the tool hears the side conversation at the door and the remark made while someone thought the microphone was muted.
Access controls that match the meeting
Store transcripts in a defined location, such as a specific SharePoint site or team, with permissions inherited from the meeting rather than copied into an open channel. Disable anonymous and public links. Prevent staff from joining work meetings with personal accounts on consumer tiers of these tools. Where possible, permit only approved tools to join, and log who exports or shares a transcript. A transcript in a public channel is a disclosure, not a convenience.
Retention: pick a number and enforce it
Distinguish three artefacts. The raw transcript is working material. The AI summary is a draft. The approved minute is the record. They do not need the same lifespan.
A defensible pattern for a small firm is thirty days for raw transcripts unless they are needed for a live matter, twelve months for summaries attached to a project, and retention of the formal minute in line with the firm's usual records policy. Automate deletion rather than relying on goodwill, and check that the vendor's own retention setting matches your policy instead of quietly overriding it.
Ten questions for the vendor review
Where is data processed and stored, and is a UK or EEA region available? Who are the sub-processors and how are changes notified? Are inputs used to train models, and can that be switched off in the contract rather than in a settings menu? What is the vendor's own retention, including backups? How is data encrypted and who manages keys? Which vendor staff can access customer content and under what controls? What are the export formats and deletion terms on termination? Which security certifications are held? What is the incident notification window? What are the liability caps?
Record the answers in one place. A short file with the contract, the security summary and the answers is sufficient for most SMEs.
Data residency, plainly stated
UK or EEA hosting is preferable and increasingly available. Where a tool processes in the United States, note the transfer mechanism relied upon, such as the UK extension to the EU-US data privacy framework or an international data transfer agreement, and record it alongside the contract. Check audio, transcript and summary storage separately, because some vendors treat them differently. If a client contract requires UK-only processing, confirm that before the tool is enabled for their meetings, not afterwards.
The policy itself: six paragraphs
- Scope and the approved list of tools.
- Notice and the approach to objections, including external participants.
- Meeting types that must not be recorded.
- Storage location and access permissions.
- Retention periods and deletion.
- Ownership, review date and how exceptions are approved.
Add a single line to the acceptable use policy pointing to it, brief team leads once, and review annually or whenever a vendor changes its terms. The point is not to discourage the tools. Used with a written position behind them, they save genuine time and produce a better record than the notes nobody took.