Role · Deployer

Bought, not built. Still yours to answer for.

Buying an AI system does not pass your EU AI Act deployer obligations to the vendor. See which duties stay with you.

No card · EU-hosted · 5 minutes to a first classification
Obligation registerDerived by the engine
12obligations applyDeployerHigh

12 obligations apply to a deployer of a high-risk system.

Classify1
Scope & literacy2
Build & document4
Conformity assessment0
Register0
Operate & monitor5
Art. 26(1)Use system per provider's instructions for use
Art. 26(2)Assign human oversight person(s)
Art. 26(5)Monitor operation; suspend and inform where use may present a risk
Art. 25(1)Watch for the changes that make you the provider
Computed by the engine for one system · switch the role to compare
The reality

What deployers get wrong first.

What we hear

“Our vendor is CE-marked, so we are covered.”

What the product does

The CE mark covers the provider's part. Oversight, logs and the worker notice stay yours.

What we hear

“We never received instructions for use, and nobody chased it.”

What the product does

Without them you cannot meet your own Article 26 duty, so the gap is yours too.

What we hear

“Nobody told the staff a model was scoring their work.”

What the product does

Article 26(7) fixes the order: tell workers and their representatives first, then go live.

What you get

Your EU AI Act deployer obligations, not the provider's.

01

Only the duties that are yours

No Annex IV file or conformity assessment: those belong to whoever built the system.

02

Instructions for use, receipted

Log what the provider supplied, dated. If nothing arrived, the register shows the gap.

03

A named person for oversight

The register records who has the competence and authority Article 26(2) requires.

04

AI literacy for everyone

Six role-based programmes track Article 4 completion per person, whatever the risk class.

In practice

From a list of tools to an auditable record.

Use case 01

An operations team running a bought CV-screening tool.

  • Annex III point 4: high-risk, so all of Art. 26 applies.
  • A named overseer with authority to override an output.
  • Worker notice dated BEFORE go-live; logs kept at least six months.
Obligation registerDerived by the engine
12obligations applyDeployerHigh

12 obligations apply to a deployer of a high-risk system.

Classify1
Scope & literacy2
Build & document4
Conformity assessment0
Register0
Operate & monitor5
Art. 26(1)Use system per provider's instructions for use
Art. 26(2)Assign human oversight person(s)
Art. 26(5)Monitor operation; suspend and inform where use may present a risk
Art. 25(1)Watch for the changes that make you the provider
Computed by the engine for one system · switch the role to compare
Use case 02

A support team using a vendor chatbot on the public site.

  • Not high-risk, but Art. 50 says people must know it is AI.
  • The disclosure notice is drafted from the record.
  • No Annex IV or conformity assessment raised.
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 03

A council deploying a benefits-triage model.

  • A public body, so an Art. 27 rights assessment is required.
  • It builds on the existing DPIA, under the DPIA's headings.
  • One record evidences both EU AI Act and GDPR duties.
Evidence · filed onceExample
Record · approved
Roles, responsibilities and authorities
One owner · one review date · hash-chained on approval
ISO 42001§5 Counts
ISO 27001§5 Counts
EU AI Act14Related · not counted
NIST AI RMFGOVERN 2.1Related · not counted

The record is credited only where it has been verified against both clause sets. The other clauses are signposted, and nothing is ticked on your behalf.

Also included

The parts a deployer reaches for later.

Straight answers

Straight answers for deployers.

How do I know whether I am a deployer or a provider?

You deploy a system you use under your own authority. Article 25 makes you a provider if you brand or substantially modify a high-risk system, or repurpose a system into high-risk. The register holds both.

What does Article 26 actually require of me?

Follow the provider's instructions; give oversight to competent people with authority; keep input data relevant and representative; monitor, and suspend use if a risk emerges; keep logs for at least six months; inform workers and their representatives before use at work; tell people when it makes or assists decisions about them.

Do the deployer duties apply if the system is not high-risk?

Some do: Article 4 literacy for every organisation using AI, and Article 50 transparency where a deployer publishes deepfakes or AI-written public-interest text, or uses emotion recognition. Article 26 itself is reserved for high-risk systems.

Do I need a fundamental rights impact assessment?

Article 27 binds deployers of Annex III high-risk systems that are public bodies or private entities providing public services, and deployers of Annex III creditworthiness and life-and-health insurance-pricing systems. It can build on your DPIA (Art. 27(4)); Veritome lays its answers under the DPIA's headings.

The vendor says their product is compliant. Is that enough?

No. Provider conformity and deployer compliance are separate: oversight, input data, logs, the worker notice and literacy stay yours. If the provider's Article 13 instructions for use have not arrived, chase them first.