Versatile AI Risk Assessment
Documents and casework

Text analytics for feedback and consultation responses

Also known as: Text analytics of feedback and consultation responses

The system summarises large volumes of free-text survey, complaint or consultation responses, identifies themes and classifies each response.

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?

It shows at a glance how often themes occur and which views predominate. The Scottish government tested such a tool on a consultation; the UK's Ofsted is trialling another.

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
public administration
Also known as
sentiment analysis, topic analysis, free-text analysis, complaint analysis

How it works, step by step

System design and data flows

  1. Input data

    Free-text survey, complaint or consultation responses arrive together.

    Texts come from citizens, customers, parents or associations outside the organisation. Free-text responses often name people, places or personal circumstances.

  2. Processing

    A model identifies themes and attitudes and classifies each response; a language model summarises themes.

    Texts are prepared for comparison and analysed by topic, category or other specified characteristics. Depending on the system design, a model classifies individual responses or a language model produces a summary. Individual classifications, aggregation and interpretation should remain distinguishable in the results.

  3. Results

    The tool returns a theme overview with frequencies, summaries and example quotations.

    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 overview feeds into reports, draft legislation or product and service decisions.

    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

12 review first8 clarify8 baseline threats

InputProcessingResultImpact Externalaccess 04 Input 30 Third-partycontent 10 AI model 40 Providerservice 11 Documentcollection 00 Memory 00 Training andfeedback 02 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 10 AI model 40 Providerservice 11 Documentcollection 00 Memory 00 Training andfeedback 02 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: 12 to review first, 8 to clarify, 8 baseline threats.

Architecture as a list

How it differs from similar use cases

Data and information

Input data and information sources

Texts come from citizens, customers, parents or associations outside the organisation. Free-text responses often name people, places or personal circumstances.

Processing and operating environment

The language model generally comes from another provider.

Storage and further use

Logging, retention periods and possible use for training must be established for the specific implementation.

Results and data sharing

Cloud services send responses 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
  • 9 typical
  • 8 depending on the system
  • 8 additional threats for every AI system

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

Priority review points

  1. Factual Inconsistencies (Hallucinations)

    The model summarises a theme barely present or presents a minority view as the majority. Readers relying only on the summary draw incorrect policy or product conclusions.

  2. Prompt Injection: Indirect

    An interest group submits many responses containing hidden instructions. Analysis then weights its position more heavily than the response count warrants.

  3. Overreliance

    The theme overview looks complete and is ordered by frequency. Rare but serious indications, such as danger, may never be read in full.

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. Jailbreaks

    People requesting generated content may try to bypass intended limits.

    Listed because of this characteristic

    • Performs natural language tasks
  5. 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
  6. Model Denial of Service

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

    Listed because of this characteristic

    • Generates its own text
  7. 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
  8. Sensitive Information Disclosure

    Confidential content can appear in answers, supplied context or logs.

    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 8 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 8 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. Uses operational feedback2 threats
  2. Learns from your own data1 threat, plus 1 only in combination with other characteristics
  3. Learns from examples with correct answers1 threat

How your system is built

Is the model trained on examples to which someone has assigned the correct answer?

Traditional sentiment analysis learns from labelled examples; language models often work without these.

If yes, add

How you operate the system

These questions arise for almost every AI system.

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 priorityPrompt Injection: Indirect3 measures
Review priorityOverreliance3 measures
Backdoor ML Model2 measures
Sleepy Agent (Time/Event-Triggered Hidden Instructions)3 measures
Prompt Injection: Direct3 measures
Jailbreaks2 measures
Meta Prompt Extraction2 measures
Model Denial of Service3 measures
Privacy Attacks3 measures
Sensitive Information Disclosure3 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. Art. 53 para. 1 point b, Annex XII: Embedded general-purpose model

    Depending on use Review trigger since 2 August 2025.

  3. Art. 50 para. 4: Labelling deepfakes and published texts

    Depending on use Review trigger since 2 August 2026.

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

Art. 50 para. 4: Labelling deepfakes and published texts

Applies if an authority publishes generated consultation summaries without human editorial review and responsibility.

Applies since 2 August 2026.

Obligations and details for Art. 50 para. 4: Labelling deepfakes and published texts
The general condition is
Applies if the system creates deepfakes or AI texts on matters of public interest are published without editorial responsibility.
Who bears the obligations
Deployer

Detailed obligations

Art. 53 para. 1 point b, Annex XII: Embedded general-purpose model

Applies if your organisation builds the tool itself using a large language model or another third-party general-purpose model.

Applies since 2 August 2025.

Obligations and details for Art. 53 para. 1 point b, Annex XII: Embedded general-purpose model
The general condition is
Applies if another provider's general-purpose AI model is incorporated, such as a large language model.
Points to consider
The model provider bears its obligations. It must give you the Annex XII information; use it for your own documentation.
Who bears the obligations
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 Documents and casework

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