All courses / AI Boss / Module 3 / Chapter 13
Learning objectives
After the lesson the participant can:
- Distinguish the data a management system requires from the further uses its by-products invite.
- Apply the criteria of the cited court and authority decisions to a monitoring arrangement.
- Compare the case for concern and the case for calm on monitoring and name the points on which they meet.
- Carry out a proportionality review that sets purpose, aggregation, access, retention and the route to M3 Consequence.
Key concepts
- Requires and invites
- A visit-routing system requires the start and end of each visit, not location between tasks. By-products invite further use: once times exist per person, a figure per person can be computed, then a ranking, then a pay input.
- Chilling effect
- When every action may enter an evaluation, helping a colleague or questioning a decision incurs an observable cost for an unobservable benefit. The chapter labels a lasting effect on voice in AI-managed workplaces as expected, not yet measured.
- Suited to monitor
- The German Federal Labour Court reads equipment intended to monitor objectively, so equipment is covered by co-determination when it is suited to collect information on behaviour or performance, whatever anyone intends.
- Aggregation by default
- Team or route before person, week before day. Individual figures need a written reason and a named role, every individual-level view is logged, and representatives may review the log.
- Retention by purpose
- Each data element is kept only as long as its stated purpose needs. The Conseil d'Etat upheld that keeping every indicator for every employee, undifferentiated, for 31 days breached data minimisation.
Interactive exercises
Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.
Interactive exercise 1 · Sort
What courts and authorities accepted
Sort each monitoring practice from Chapter 13 by the outcome the chapter reports for it.
Interactive exercise 2 · Scenario
A request for a ranking
Apply the conditions of the annex to Hansa Mutual's group works agreement KBV-IT-2024 to the situation below.
Teaching plan
| 10 min | The teacher asks participants to list what a routing or allocation system needs to know, then what it also collects, using the chapter's distinction between requires and invites. |
| 15 min | Case round: groups summarise one decision each (the two Grand Chamber cases, H&M, Amazon France Logistique) by what was found and the criterion that decided it. |
| 15 min | Staged debate in four steps, followed by the verdict and its labels. |
| 25 min | Exercise: groups run a proportionality review of one data stream, following the practical guide and Nordvik Region's review of visit registration. |
| 10 min | Debrief with the annex to KBV-IT-2024: who sees individual throughput, what is prohibited, and how the principle is applied in Switzerland and Poland. |
Discussion
- The H&M case involved no AI. Why does the chapter include it, and what does it show about what a management system could assemble routinely?
- The restaurant study found less theft and higher legitimate tips, while the factory study found concealment under constant observation. What differs between the two forms of monitoring?
- Mikael Strand keeps individual figures because he needs to see when a person's routes are consistently overrun. Where is the line between that use and evaluation of the person?
Written exercise
Exercise · 25 minutes
Proportionality review of monitoring data
Review the monitoring data used by one management system: the visit-registration data behind Nordvik Region's home-care dashboards, the throughput figures of Hansa Mutual's claims-triage agent, or a system of your own. Inventory each data element, including by-products, and state its purpose under M1 Direction, M2 Evaluation or M5 Care; an element with no purpose is not collected. Exclude what the chapter lists as forbidden. Set the aggregation level, the roles with access and the logging of individual views, and the retention for raw events and for planning aggregates. State for each element whether any route to M3 Consequence is closed or recorded, and how workers are informed before use.
Deliverable: A review table with purpose, aggregation, access, retention and route to M3 Consequence for each data element, the exclusions, and the date of the next review.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
What did Nordvik Region's review, recorded as AIDR-0604, do with the location trace the app stored between visits?
Show the answer
B. It stopped collecting it, keeping location only as confirmation at the start and end of a visit
The trace had been used to estimate travel times; the review replaced the estimate with route-level averages, set raw events to 60 days and route aggregates to 24 months, and closed the route from dashboard figures to pay, discipline or dismissal.According to the Commission's guidelines as the chapter reports them, which statement about Article 5(1)(f) of the AI Act is correct?
Show the answer
C. Inference from keystrokes, facial expressions or voice is inside it, and the safety exception does not cover stress or burnout detection
The guidelines place inference from text outside the prohibition and inference from biometric signals inside it; the medical or safety exception does not extend to stress or burnout detection, and the Omnibus left point (f) unchanged.Under the annex to KBV-IT-2024, who may see a claims handler's individual throughput figure?
Show the answer
A. The handler and the handler's own team leader
The annex limits visibility to the handler and their own team leader, prohibits ranking lists, retains figures for 13 weeks and has the works council review the access log quarterly.