Versatile AI Risk Assessment
Office work and knowledge management

Speech recognition and transcription

Also known as: Automatic speech recognition and transcription

Speech recognition automatically transcribes dictation, conversations and other recordings.

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?

The UK judiciary and Germany's Federal Employment Agency use speech recognition; BaFin reports smaller financial institutions transcribing customer conversations.

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

System design
Generative assistance
Ability to act
Provides results for subsequent use
Fields of use
judiciary, public administration, banking
Also known as
speech-to-text, dictation recognition, conversation transcript

How it works, step by step

System design and data flows

  1. Input data

    Dictation, a telephone call or another recording arrives as an audio track.

    Outsiders often also speak, such as telephone customers or hearing participants. Recordings and transcripts contain voices, names and people's statements.

  2. Processing

    Recognition converts speech into words and punctuation; specialist vocabulary supports medical or legal terminology.

    Speech recognition processes sections of the audio signal and assigns words to them. These sections form the transcript; depending on the tool, timestamps and speaker identification may be added. The transcript is an interpretation of the recording, rather than directly measured text.

  3. Results

    A transcript is available for human review and correction.

    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 transcript enters files, findings, decisions or consultation notes.

    The model supplies information for subsequent use. Selection, adoption or a professional decision in the following workflow is a separate step and should not automatically be attributed to the model.

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

8 review first7 clarify8 baseline threats

InputProcessingResultImpact Externalaccess 04 Input 30 Third-partycontent 00 AI model 00 Providerservice 11 Documentcollection 00 Memory 00 Training andfeedback 11 OtherAI agents 00 Tools andinterfaces 00 Result 20 Business appor equipment 00 person 10 Affectedperson 00 AI serviceswithout approval 01 Externalaccess 04 Input 30 Third-partycontent 00 AI model 00 Providerservice 11 Documentcollection 00 Memory 00 Training andfeedback 11 OtherAI agents 00 Tools andinterfaces 00 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: 8 to review first, 7 to clarify, 8 baseline threats.

Architecture as a list

How it differs from similar use cases

Data and information

Input data and information sources

Outsiders often also speak, such as telephone customers or hearing participants. Recordings and transcripts contain voices, names and people's statements.

Processing and operating environment

Recognition models usually come from providers; BenchNotes uses Azure Speech Services.

Storage and further use

Some deployers adapt recognition using their own recordings or specialist vocabulary. Corrected transcripts can feed back as new training examples.

Results and data sharing

Cloud services send audio recordings outside 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
  • 5 typical
  • 7 depending on the system
  • 8 additional threats for every AI system

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

Priority review points

  1. Factual Inconsistencies (Hallucinations)

    During a pause or unclear speech, the model inserts a sentence never spoken. In a finding or decision, it is later treated as the person's statement.

  2. Overreliance

    The transcript reads smoothly and looks complete. Approval without checking the recording misses misheard figures, names and negatives.

  3. Sensitive Information Disclosure

    Dictation and conversations contain health, case or account information. Provider retention or overly broad sharing exposes recordings and transcripts to unauthorised people.

5 further review candidates in the typical design

Other relevant threats

  1. Targeted Poisoning / Label Poisoning

    Falsified training labels can deliberately shift model outputs.

    Listed because of this characteristic

    • Learns from examples with correct answers
  2. 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
  3. Model Denial of Service

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

    Listed because of this characteristic

    • Generates its own text
  4. 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
  5. 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 7 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 7 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

  1. Learns from your own data1 threat, plus 1 only in combination with other characteristics
  2. Uses operational feedback1 threat

How your system is built

Does your organisation train or fine-tune the model itself using its own data?

Some deployers adapt recognition using their own recordings or specialist vocabulary.

If yes, add

Does operational feedback or output later feed into analysis or training?

Corrected transcripts can feed back as new training examples.

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?

Staff sometimes upload recordings to freely available services when no internal tool exists.

If yes, add

Controls and implementation

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

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

AI Act provisions

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

Generally does not apply

Art. 50 para. 2: Marking artificially generated content

The transcript reproduces speech and generally creates no new content.

Obligations and details for Art. 50 para. 2: Marking artificially generated content
The general condition is
Applies if the system generates synthetic text, images, audio or video.
Exception
Exceptions include ordinary editing assistance that does not substantially alter inputs or their meaning.
Points to consider
Systems marketed before 2 August 2026 must be updated by 2 December 2026.
Who bears the obligations
Provider, Product manufacturer, Provider of a general-purpose AI model

Detailed obligations

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 18 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