Versatile AI Risk Assessment
Employment and education

Algorithmic management

Software assigns tasks and shifts to workers, tracks what they do and evaluates their performance.

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 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
Analysis and processing
Ability to act
Can act within applications
Fields of use
platform work, delivery services
Also known as
automated task allocation, employee performance monitoring, shift and workforce scheduling

How it works, step by step

System design and data flows

  1. Input data

    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.

  2. Processing

    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.

  3. Results

    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.

  4. Use and impact

    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.

How the system is built

8 review first8 clarify8 baseline threats

InputProcessingResultImpact Externalaccess 04 Input 30 Third-partycontent 00 AI model 10 Providerservice 02 Documentcollection 00 Memory 00 Training andfeedback 21 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 10 person 10 Affectedperson 00 AI serviceswithout approval 01 Externalaccess 04 Input 30 Third-partycontent 00 AI model 10 Providerservice 02 Documentcollection 00 Memory 00 Training andfeedback 21 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 10 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, 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

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.

Processing and operating environment

The model processes the inputs. Whether it runs internally or with a service provider must be established for the specific implementation.

Storage and further use

Operational measurements such as delivery times and acceptance rates influence future allocations and ratings.

Results and data sharing

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

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

  • 4 particularly important
  • 4 typical
  • 8 depending on the system
  • 8 additional threats for every AI system

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.

Priority review points

  1. Misalignment

    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.

  2. Excessive Agency

    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.

  3. Overreliance

    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.

  4. Training Data Poisoning

    Operational measurements guide future allocations. Falsifying location data or deliberately rejecting jobs changes the values the system uses to assign work to everyone else.

4 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

    • Uses operational feedback
  2. 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
  3. Sensitive Information Disclosure

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

    Listed because of these characteristics

    • Processes personal data
    • Processes confidential data
  4. 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. Learns from your own data1 threat, plus 1 only in combination with other characteristics
  2. Uses another provider's model1 threat

How your system is built

Does the model or its base model come from another provider, even if you host it?

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.

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. 5 para. 1 point e, f, g, h: Prohibited biometric practices

    Depending on use Review trigger since 2 February 2025.

  3. Annex III no. 4 point b: Employment decisions

    In typical 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 typical use

Annex III no. 4 point b: Employment decisions

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.

Obligations and details for Annex III no. 4 point b: Employment decisions
The general condition is
Applies if the system influences working conditions, promotion or dismissal, allocates tasks by behaviour or personal characteristics, or monitors workers' performance and behaviour.
Who bears the obligations
Provider, Deployer, Product manufacturer, Importer, Distributor, Authorised representative

Detailed obligations

May apply in particular uses

Art. 5 para. 1 point e, f, g, h: Prohibited biometric practices

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.

Obligations and details for Art. 5 para. 1 point e, f, g, h: Prohibited biometric practices
The general condition is
Applies if the system indiscriminately collects facial images from the internet or video, recognises workplace or educational emotions, categorises people biometrically by sensitive attributes, or identifies people in public spaces in real time for law enforcement.
Exception
Workplace and educational emotion recognition is permitted for medical or safety reasons. Real-time law enforcement identification has narrowly defined exceptions.
Who bears the obligations
Provider, Deployer, Importer, Distributor, Authorised representative, Product manufacturer, Provider of a general-purpose AI model

Detailed obligations

Other legal requirements

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

    Open the legislation Directive (EU) 2024/2831

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 17 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 Employment and education

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