Input data and information sources
Customer ratings and complaints that feed into performance assessments come from people outside the organisation. The system records who works where and when, and how quickly.
Software assigns tasks and shifts to workers, tracks what they do and evaluates their performance.
Understand the use case
The software takes over supervisory tasks: it allocates jobs, schedules shifts, measures speed and location, and uses these to generate ratings or bonuses. This is particularly familiar in delivery services. The Platform Work Directive (EU) 2024/2831 also regulates the use case under this name.
This page describes a typical system design. Actual data flows and permissions depend on your implementation.
System design and data flows
The system receives jobs, availability, locations and measurements of speed, acceptance and customer ratings.
Customer ratings and complaints that feed into performance assessments come from people outside the organisation. The system records who works where and when, and how quickly.
The software allocates jobs and shifts according to its objectives and calculates performance figures for each person.
Processing combines work and operational data with a specified objective, such as workforce scheduling. This produces assignments, assessments or recommendations. Whether these are merely displayed or directly implemented as binding instructions depends on their integration into the work process.
Workers receive assignments, shift schedules and performance figures, sometimes with bonuses or warnings.
The result describes the defined model task. A match, category or forecast acquires its professional significance only in conjunction with the underlying data and intended use.
Allocations and ratings determine workers' hours, income and career prospects.
Write or execution permissions allow the system to change a state within an application. Model responses, tool calls and changes actually executed must therefore be considered separately.
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.
8 review first8 clarify8 baseline threats
The diagram shows the typical architecture. Select a component to see what happens there and adapt its features to your system. Enable “Analysis guidance” to see which threats need reviewing for this architecture. The page's checklist continues to describe the typical case.
None yet. Each change will appear here.
In this system design: 8 to review first, 8 to clarify, 8 baseline threats.
External access: Depends on your system
To clarify
Input: Part of every AI system
Review first
Baseline for every AI system
Third-party content: Depends on your system
AI model: Part of every AI system
Review first
Baseline for every AI system
Provider service: Depends on your system
To clarify
Training and feedback: Present
Review first
To clarify
Result: Part of every AI system
Baseline for every AI system
Business application or equipment: Present
Review first
person: Part of every AI system
Review first
Affected person: Present
Unapproved AI services: Depends on your system
To clarify
Supply chain and technical foundations: 5 baseline threats applying to every AI system
Baseline for every AI system
AI-assisted candidate screening
Sorts and evaluates applications before an employment relationship exists
Infers emotions from faces, voices or behaviour
Customer ratings and complaints that feed into performance assessments come from people outside the organisation. The system records who works where and when, and how quickly.
The model processes the inputs. Whether it runs internally or with a service provider must be established for the specific implementation.
Operational measurements such as delivery times and acceptance rates influence future allocations and ratings.
The system assigns jobs and shifts itself and can set bonuses or suspend accounts.
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
Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.
Relate review candidates to actual data flows: what could happen, and who would be affected?
Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.
Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.
A total of 24 threats from the threat catalogue may be relevant to this use case.
Also review: whether the system disadvantages groups
Check whether selection, ranking or assessment disadvantages people with protected characteristics, such as sex, age or origin.
If the system prioritises short delivery times, it allocates jobs so tightly that little time remains for breaks. Delivery times fall, while drivers' health and safety suffer.
The system can withdraw shifts or suspend accounts when measurements fall below a threshold. A measurement error, such as an incorrect location, can then cost someone their income without a review.
Supervisors use performance figures in discussions and appraisals without knowing how they were calculated. Traffic jams or long waits at restaurants then go unaccounted for.
Operational measurements guide future allocations. Falsifying location data or deliberately rejecting jobs changes the values the system uses to assign work to everyone else.
Targeted Poisoning / Label Poisoning
Falsified training labels can deliberately shift model outputs.
Listed because of this characteristic
Targeted queries can recover some personal or protected training data from the model.
Listed because of these characteristics
Sensitive Information Disclosure
Confidential content can appear in answers, supplied context or logs.
Listed because of these characteristics
Exfiltration from ML Application
Protected data can leak through tools, network connections, storage or insiders.
Listed because of this characteristic
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.
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 your system is built
How you operate the system
If yes, add
If yes, add
These questions arise for almost every AI system.
If yes, add
In delivery services, workers receive assignments through a phone app.
If yes, add
If yes, add
If yes, add
If yes, add
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.
For every AI system Applies since 2 February 2025.
Depending on use Review trigger since 2 February 2025.
In typical use Review trigger from 2 December 2027.
Applies if staff or appointed representatives operate or use AI systems.
Applies since 2 February 2025.
Detailed obligations
Applies if the system allocates tasks based on behaviour or personal characteristics, monitors workers' performance and behaviour, or influences decisions on working conditions, promotion or dismissal.
Applies from 2 December 2027.
Detailed obligations
Applies if the system infers workers' emotions from their faces or voices, for example to detect mood or anger in a call centre.
Applies since 2 February 2025.
Detailed obligations
Directive (EU) 2024/2831
The Directive limits automated monitoring and decision-making in platform work and requires human review of important decisions. Member States must transpose it by 2 December 2026.
Classify your system with the quick checker All obligations in the obligations compass
Review these threats for every AI system, whatever its purpose.
If any of these features does apply to your system, add the listed threats.
Does the system generate its own text, such as answers, drafts or summaries?
The system produces allocations, measurements and ratings, rather than freely generated text.
If yes, add
Does the system generate or edit images, sounds, voices or videos?
If yes, add
Does the system create new content from open-ended requests that people read, see or hear directly? Translation, reading aloud and transcription do not count.
If yes, add
Can users give the system natural language tasks that it then performs?
The system works with jobs, shift schedules and measurements, rather than natural language instructions.
If yes, add
Does the system search its own collection of documents or records for relevant content?
If yes, add
Does the system formulate answers from retrieved documents?
If yes, add
Does the system use a knowledge graph storing concepts and their relationships?
If yes, add
Does the system remember content from earlier conversations or tasks and reuse it later?
If yes, add
Does the system call other programs, interfaces or search services itself, even if only to read?
If yes, add
Does the system determine its next steps itself based on earlier results?
If yes, add
Does the system delegate tasks to other AI agents or incorporate their results?
If yes, add
Is the system connected to tools or data sources through the Model Context Protocol (MCP)?
If yes, add
Do documents from several customers, departments or permission groups share one search store?
If yes, add
Can people outside your organisation use the system, including without login?
Only workers and their supervisors use the system, rather than the public.
If yes, add
Does the system process several input types together, such as text with images or speech?
If yes, add
Does the system generate code, scripts or database queries for further use?
If yes, add
Does the system execute programs, scripts or commands itself?
If yes, add
EU AI Act, Annex III, point 4(b)
The Act expressly lists AI systems that influence promotion or dismissal, allocate tasks, or monitor performance and behaviour in Annex III.
OECD.AI, Algorithmic management in the workplace, 2025
A survey of over 6,000 companies, including companies in Germany, shows that algorithmic management tools are already widespread.
IAB-Forum, Algorithmic management in app-based delivery services, 23 September 2025
The IAB surveyed workers at eleven delivery services in Germany.
AlgorithmWatch, Join the Ride Side, 19 March 2024
AlgorithmWatch describes the use of algorithmic management at Lieferando.
Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured