One project, two sets of rules, three units each with their own list of questions.
The business unit submits a project with a description that only outlines the purpose in broad terms. Compliance and data protection read the same description, classify it independently and arrive at different lists of questions. Until the classification is settled, the project goes back and forth between the units several times.
1projectThe business unit submits an AI system with a description of its purpose.
2sets of rulesOne asks about the risk class, the other about the legal basis and purpose limitation for the social data.
3rounds between the unitsCompliance, data protection and IT governance pass the project around until the purpose is described precisely enough.
1list of obligationsThe result is a list that has to be drawn up from scratch for the next project.
Once the purpose is classified against the same grid and the list of obligations derived from it, review effort falls by 50%.
The 50% reduction in review effort is this agent's headline figure. Two sets of rules and three coordination rounds describe a typical path to classification; they are not a measured value.