Apply / your decision record

Make the call.
Explain your decision.

Identify the facts that matter, any missing evidence and the next action. Name the responsible role and explain what would change your decision. Do not assume that an unmentioned approval, exception or assessment exists. Allow around 8–12 minutes.

One useful record

YOUR CASE / PROVIDER OR DEPLOYER

A consultancy buys a language-model API and builds its own branded recruitment-screening application for clients. It also uses an unchanged third-party meeting assistant internally. The API supplier says it accepts no responsibility for the consultancy's hiring workflow.

Your output / a practical record

Operator role and responsibility map

Make the next decision explicit. Connect it to evidence, unresolved questions and an accountable role.

Draft: Operator role and responsibility map

1. System and activity2. Brand, developer and intended-purpose owner3. AI Act operator role4. GDPR controller or processor analysis5. Change triggers and supplier dependencies6. Contract evidence, accountable owner and decision

Check your reasoning

I mapped the consultancy's branded recruitment application separately from its internal meeting assistant.I distinguished AI Act roles from data-protection roles and identified contract evidence gaps.I assigned responsibility for role-change analysis and supplier cooperation.I recorded purpose, branding, dependencies and triggers for reviewing the role map.

This is a self-review. Compare with the worked example if you need help. Every field needs a response of at least 10 characters; text length does not assess its quality.