Job to be done · First assessment

EU AI Act risk assessment, from what you already use.

Start with an inventory, not a policy. Most organisations find more AI than they expected, and less high-risk than they feared.

No card · EU-hosted · 5 minutes to a first classification
ClassificationRecruitment assistant
Prohibited practicesNo — none of thoseArt. 5
Product lawNoArt. 6(1)
Annex III area4. EmploymentArt. 6(2)
Art. 6(3) exceptionIt profiles natural personsArt. 6(3)
Your roleWe use it as supplied — a finished tool somebody else providesArt. 3(3)–(8)
VerdictHighDeployerEvery step cites its article
Illustrative record · articles are real, the system is not
The reality

Why first attempts stall.

What we hear

“We started by writing an AI policy.”

What the product does

A policy written before the inventory is a guess. Classify first, then the policy has something to cover.

What we hear

“We only counted the models we built.”

What the product does

A scoring feature inside a bought HR suite counts. Deployer duties attach to it just as to your own.

What we hear

“We assumed everything was high-risk to be safe.”

What the product does

That only adds cost: an Annex IV file for a limited-risk chatbot spends effort the high-risk system needed.

What you get

What your first assessment leaves you with.

01

The Act's own order

Prohibited practices, Annex I, Annex III, the carve-outs, then the Art. 25 triggers: each answer shapes the next question.

02

GDPR in the same pass

Five data questions add the data-protection duties to the same register: one list, not two projects.

03

A decision you can reopen

When a system changes, reclassify it and the obligations regenerate around the work already done.

04

Free for the first system

Classifying one system costs nothing and needs no card.

In practice

Three first passes.

Use case 01

A 30-person agency listing its AI tools for the first time.

  • Eleven tools found; seven were on nobody's list.
  • Nine are limited or minimal risk: Art. 50 and Art. 4 only.
  • Two need a closer look: a client scorer and an HR screener.
ClassificationRecruitment assistant
Prohibited practicesNo — none of thoseArt. 5
Product lawNoArt. 6(1)
Annex III area4. EmploymentArt. 6(2)
Art. 6(3) exceptionIt profiles natural personsArt. 6(3)
Your roleWe use it as supplied — a finished tool somebody else providesArt. 3(3)–(8)
VerdictHighDeployerEvery step cites its article
Illustrative record · articles are real, the system is not
Use case 02

A scale-up that thought it had no EU AI Act exposure.

  • The bought recruitment tool lands in Annex III point 4.
  • Deployer duties apply: oversight, logs, the worker notice.
  • Their own product feature makes them a provider for it.
AI systems4 in the register
SystemRole · riskStageDone
Recruitment assistantDeployerHighBuild & document5/12
Credit-scoring modelProviderHighBuild & document8/25
Meeting summariserDeployerMinimalOperate & monitor2/2
Document searchDeployerMinimalOperate & monitor2/2
One register, each system its own role
Illustrative workspace · roles, tiers and obligations are the engine's
Use case 03

A public body preparing for scrutiny.

  • Art. 27 binds: a fundamental-rights assessment is required.
  • It builds on the existing DPIA and feeds the DPIA view.
  • Affected people informed under Art. 26(11), the notice dated.
AssessmentsEmergency triage assistant
Risk classificationArt. 6Done
DPIAGDPR Art. 35Done
FRIAStarted from the DPIA · EU AI Act Art. 27(4)Art. 27In progress
Conformity assessmentArt. 43Not applicable
Written once, reused where the Act allows
Illustrative record · articles are real, the system is not
Also included

What follows the first pass.

Straight answers

Questions about your first EU AI Act risk assessment.

Where does a first assessment actually begin?

With an inventory; the policy comes later. You cannot classify what you have not listed, and most organisations find more AI than they thought.

How long does it take?

The free check asks a short set of questions per system; a first pass over a small estate takes an afternoon. The evidence behind the obligations takes longer, and that is where deadlines bite.

What if most of our systems turn out to be low risk?

That is common, and useful: if eight of ten systems carry only Article 50 transparency and Article 4 literacy, the effort goes to the two that carry more.

Do we need to classify systems we are only piloting?

The EU AI Act attaches duties to putting a system into service, so a genuine internal pilot sits differently. Recording it now costs little and keeps the register right when it goes live.

What comes out at the end?

A register of systems, each with a role, a risk class and obligations citing their articles, plus a classification record you can reopen and a dated decision trail.