Role · Provider

EU AI Act provider obligations, built from one register.

Put a high-risk system on the market under your name and the full Chapter III set is yours. Veritome derives it from one register.

No card · EU-hosted · 5 minutes to a first classification
Annex IV — Technical DocumentationRecruitment assistant
§1General DescriptionArt. 11
§2System Elements & Development ProcessArt. 11
§3Training, Validation & Testing DataArt. 10
§4Testing & Validation ResultsArt. 15
§5Human Oversight MeasuresArt. 14
§6Risk Management SummaryArt. 9
§7Cybersecurity MeasuresArt. 15
§8Pre-determined Changes & Continuous LearningProvider narrative · to write
Sealedsha256sha256 fingerprint e4d4b64e5aeabf734f6512c3249ff428c83229491c30f20c63c233614049e0227 of 8 filled from the register
Illustrative file · the sections are the builder's own; §8 is always yours to write
The reality

Where provider programmes stall.

What we hear

“We have the documents, but they contradict each other.”

What the product does

Documents kept by hand drift. Read from one record, the technical file, risk register and declaration agree.

What we hear

“We did not think Article 25 applied to us.”

What the product does

Branding or substantially modifying a high-risk system, or repurposing any system into high-risk use, makes you its provider.

What we hear

“The auditor asked how we decided. We had the outcome, not the reasoning.”

What the product does

Every decision carries who made it, when and the article behind it, in an exportable hash-chained trail.

What you get

One register, thirteen artefacts.

01

Annex IV that assembles itself

Built from live data, approved by a named person, then sealed. Changes make new versions.

02

Risk management as a lifecycle

Hazards, mitigations and residual rating, revisited as the system changes (Art. 9).

03

The QMS without a second system

Article 17 maps onto the ISO 42001 programme, so it ticks from work already done.

04

Post-market monitoring that runs

Monitoring and incident routing, with the Article 73 deadline counted from the date you knew.

In practice

Three ways companies become providers.

Use case 01

A SaaS company shipping a CV-ranking feature to EU customers.

  • Annex III point 4: high-risk, so the full provider set applies.
  • Annex VI internal control, with the standards applied recorded.
  • Registered under Art. 49 before it is placed on the market.
Annex IV — Technical DocumentationRecruitment assistant
§1General DescriptionArt. 11
§2System Elements & Development ProcessArt. 11
§3Training, Validation & Testing DataArt. 10
§4Testing & Validation ResultsArt. 15
§5Human Oversight MeasuresArt. 14
§6Risk Management SummaryArt. 9
§7Cybersecurity MeasuresArt. 15
§8Pre-determined Changes & Continuous LearningProvider narrative · to write
Sealedsha256sha256 fingerprint e4d4b64e5aeabf734f6512c3249ff428c83229491c30f20c63c233614049e0227 of 8 filled from the register
Illustrative file · the sections are the builder's own; §8 is always yours to write
Use case 02

A company white-labelling a vendor's scoring model under its own brand.

  • Art. 25(1)(a): the name on the product makes them provider.
  • The vendor's documentation feeds their file but cannot replace it.
  • The duty moves with the brand.
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 team fine-tuning an open model for a regulated decision.

  • Substantial modification or changed purpose: Art. 25(1)(b) and (c).
  • Art. 10 data governance covers the fine-tuning set too.
  • Art. 15 accuracy, robustness and cybersecurity evidence is now theirs.
Risk registerEthical
Shortlisting disadvantages a protected group
Critical+CriticalHighMediumLow
51015202548121620369121524681012345
RareUnlikelyPossibleLikelyCertain
Inherent
12 · Act now
Treatment
Mitigate · bias testing per release
Residual
4 · Accepted
Residual risk signed off Art. 9
Illustrative record · articles are real, the system is not
Also included

The parts a provider reaches for later.

Straight answers

Questions about EU AI Act provider obligations.

We only fine-tuned someone else's model. Are we really a provider?

Possibly. Branding a high-risk system, substantially modifying it, or repurposing a system into high-risk makes you its provider (Art. 25(1)). Fine-tuning can meet the second or third test; the classification asks which.

What does the provider set actually contain?

For a high-risk system: risk management (Art. 9), data governance (10), Annex IV documentation (11), logging (12), instructions for use (13), human oversight (14), accuracy, robustness and cybersecurity (15), a QMS (17), conformity assessment (43), EU declaration (47), CE marking (48), registration (49), post-market monitoring (72), serious-incident reporting (73).

Do we need a notified body?

It depends on the route. Most Annex III systems take Annex VI internal control, done by the provider. Annex I sectoral systems, and biometric systems without an applied harmonised standard, take the third-party route. The classification records which, and why.

How does the technical file get built?

Annex IV sections are assembled from the live record, and you edit and approve the draft. Sealing produces a hash-stamped version; nobody edits it, and a change makes a new version.

When is registration required?

Article 49: an Annex III high-risk system is registered in the EU database before it is placed on the market or put into service. Veritome pre-fills the Annex VIII fields and lists what is missing.