Versatile AI Risk Assessment
Office work and knowledge management

AI meeting minutes and conversation documentation

Also known as: AI meeting notes, ambient scribe

From recorded meetings and consultation conversations, the system drafts minutes or a case note with an action list.

Explore the interactive model

Export handout

A concise PDF covering how the system works, its data flows and points to investigate, ready to share.

The explanations and measures describe the typical system design. Extensive personal changes add an appendix.

Understand the use case

What defines this use case?

Social services and local councils use these tools. The UK's health service has dedicated guidance on them.

This page describes a typical system design. Actual data flows and permissions depend on your implementation.

System design
Generative assistance
Ability to act
Action permissions depend on integration
Fields of use
social services, local councils, healthcare
Also known as
meeting summary, ambient scribe, AI-generated case notes

How it works, step by step

System design and data flows

  1. Input data

    A meeting, session or consultation is recorded.

    Citizens, patients or meeting guests also speak during conversations. The recording and minutes document who said what.

  2. Processing

    Speech recognition transcribes it; a language model condenses the transcript using a template.

    Speech recognition first converts the audio recording into a transcript. A language model then organises the statements according to a template and formulates topics, agreements and action items. This produces a new text: the minutes are not a verbatim transcript, and a written action item is not yet a completed task.

  3. Results

    The system returns draft minutes, a case note or memorandum with an action list.

    A generated result is newly worded or created. To assess it, the instruction and context on which it is based must remain identifiable.

  4. Use and impact

    The approved draft becomes part of the record and determines what is later considered discussed and agreed.

    Integration determines whether the result is simply displayed, adopted after approval or written directly into a business application. These variants differ in their data flows and permissions.

Explore the system design: Select a component to see its task, incoming and outgoing data, and role in the use case. The guided walkthrough explains each phase. Then use Yes, Uncertain and No to represent your specific system variant.

How the system is built

12 review first12 clarify8 baseline threats

InputProcessingResultImpact Externalaccess 04 Input 31 Third-partycontent 10 AI model 40 Providerservice 11 Documentcollection 00 Memory 01 Training andfeedback 02 OtherAI agents 00 Tools andinterfaces 02 Result 20 Business appor equipment 00 person 10 Affectedperson 00 AI serviceswithout approval 01 Externalaccess 04 Input 31 Third-partycontent 10 AI model 40 Providerservice 11 Documentcollection 00 Memory 01 Training andfeedback 02 OtherAI agents 00 Tools andinterfaces 02 Result 20 Business appor equipment 00 person 10 Affectedperson 00 AI serviceswithout approval 01
  • Present
  • Depends on your system
  • Absent
  • Review first
  • To clarify

In this system design: 12 to review first, 12 to clarify, 8 baseline threats.

Architecture as a list

How it differs from similar use cases

Data and information

Input data and information sources

Citizens, patients or meeting guests also speak during conversations. The recording and minutes document who said what.

Processing and operating environment

Speech recognition and language models generally come from providers.

Storage and further use

Some tools consult earlier notes for the same case. Staff corrections can improve templates or the model.

Results and data sharing

Some tools place drafts directly in the case file or assign tasks; others only provide them for acceptance. With a cloud service, recordings and transcripts leave the organisation's environment.

Using a provider does not automatically determine where processing takes place. Storage location, subcontractors, deletion periods and use for training must be checked for the specific deployment.

Assess risks and determine measures

From understanding the system to analysing risks

  1. Define the system boundary

    Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.

  2. Investigate threats

    Relate review candidates to actual data flows: what could happen, and who would be affected?

  3. Assess risk

    Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.

  4. Provide evidence of measures

    Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.

Key threats in the application context

  • 3 particularly important
  • 9 typical
  • 12 depending on the system
  • 8 additional threats for every AI system

A total of 32 threats from the threat catalogue may be relevant to this use case.

Priority review points

  1. Factual Inconsistencies (Hallucinations)

    The language model attributes a statement to a client that they never made or adds a diagnosis. Once in the case file, the sentence is treated as established in later decisions.

  2. Overreliance

    The draft is ready immediately and looks complete. Under time pressure, staff sign it off without checking it against their recollection.

  3. Sensitive Information Disclosure

    Social care recordings contain health, family and financial information. Retention by the provider or overly broad access to minutes exposes it to unauthorised people.

9 further review candidates in the typical design

Other relevant threats

  1. Backdoor ML Model

    Training data or an adopted base model can introduce hidden triggers for misbehaviour.

    Listed because of this characteristic

    • Uses another provider's model
  2. Sleepy Agent (Time/Event-Triggered Hidden Instructions)

    An instruction-following model can change behaviour at a particular time or event.

    Listed because of this characteristic

    • Performs natural language tasks
  3. Prompt Injection: Direct

    Users can override the system's working instructions through their inputs.

    Listed because of this characteristic

    • Performs natural language tasks
  4. Prompt Injection: Indirect

    A model can follow instructions in a document or tool result as if they were its own working instructions.

    Listed because of these characteristics

    • Performs natural language tasks
    • Processes content outsiders can write
  5. Jailbreaks

    People requesting generated content may try to bypass intended limits.

    Listed because of this characteristic

    • Performs natural language tasks
  6. Meta Prompt Extraction

    Carefully crafted queries can reveal system instructions, which must therefore contain no secrets.

    Listed because of this characteristic

    • Performs natural language tasks
  7. Model Denial of Service

    Complex or high-volume inputs can exhaust model computing resources.

    Listed because of this characteristic

    • Generates its own text
  8. Privacy Attacks

    Targeted queries can recover some personal or protected training data from the model.

    Listed because of these characteristics

    • Processes personal data
    • Processes confidential data
  9. Exfiltration from ML Application

    Protected data can leak through tools, network connections, storage or insiders.

    Listed because of this characteristic

    • Processes confidential data

Up to 12 further threats may apply, depending on your system design. Nine threats need to be reviewed for every AI system. One of these is particularly important here and is therefore listed above.

System features and open questions

Each Yes adds further threats to your checklist, up to 12 in total. If you cannot yet answer a question, include its threats in your review.

How many threats a Yes adds
  • Added by this Yes
  • Also requires a Yes to another question

How your system is built

Can the system change things itself, such as storing data, sending messages, initiating transactions or granting permissions?

Some tools place drafts directly in the case file or assign tasks; others only provide them for acceptance.

If yes, add

Does the system process several input types together, such as text with images or speech?

If yes, add

How you operate the system

These questions arise for almost every AI system.

Do staff also use AI services for this task that your organisation has not approved?

Participants sometimes bring their own unapproved note-taking tools into video meetings.

If yes, add

Controls and implementation

Measures for the priority review areas are expanded. Each linked measure explains how to implement it.

Review priorityFactual Inconsistencies (Hallucinations)3 measures
Review priorityOverreliance3 measures
Review prioritySensitive Information Disclosure3 measures
Backdoor ML Model2 measures
Sleepy Agent (Time/Event-Triggered Hidden Instructions)3 measures
Prompt Injection: Direct3 measures
Prompt Injection: Indirect3 measures
Jailbreaks2 measures
Meta Prompt Extraction2 measures
Model Denial of Service3 measures
Privacy Attacks3 measures
Exfiltration from ML Application3 measures

Controls for the remaining threats are available on their pages in the threat catalogue.

AI Act provisions

When AI Act provisions apply
  1. Art. 4: AI literacy

    For every AI system Applies since 2 February 2025.

  2. Annex III no. 5 point a: Public assistance benefits

    Depending on use Review trigger from 2 December 2027.

Applies to every AI system

Art. 4: AI literacy

Applies if staff or appointed representatives operate or use AI systems.

Applies since 2 February 2025.

Obligations and details for Art. 4: AI literacy
Who bears the obligations
Provider, Deployer, Product manufacturer, Provider of a general-purpose AI model

Detailed obligations

May apply in particular uses

Annex III no. 5 point a: Public assistance benefits

Applies if an authority uses generated case notes to assess, grant or reduce entitlement to social benefits or support.

Applies from 2 December 2027.

Obligations and details for Annex III no. 5 point a: Public assistance benefits
The general condition is
Applies if authorities or bodies acting for them use the system to assess eligibility for public benefits and services, or to grant, reduce or recover them.
Who bears the obligations
Provider, Deployer, Product manufacturer

Detailed obligations

Generally does not apply

Art. 50 para. 1: Disclosure of AI interaction

Participants speak with people rather than the system. The disclosure obligation for interaction with AI therefore generally does not apply.

Obligations and details for Art. 50 para. 1: Disclosure of AI interaction
The general condition is
Applies if people directly write or speak with the system and it is not obvious that they are interacting with AI.
Who bears the obligations
Provider, Product manufacturer

Detailed obligations

Other legal requirements

Classify your system with the quick checker All obligations in the obligations compass

Cross-cutting threats

Review these threats for every AI system, whatever its purpose.

Why these threats always belong on the checklist

Atypical system features

View 12 further questions

If any of these features does apply to your system, add the listed threats.

Sources

Related use cases

Also in the field of Office work and knowledge management

Often used together with

Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured