Artificial Intelligence Policy Tracker
Legal requirement Governance and accountability European Union Partially applicable

Deployers, distributors and importers must assume provider duties when they rebrand or substantially modify high-risk AI

Download: JSON · MarkdownUnder EU AI Act, Article 25(1) and 25(2)

Verified against the official source 26 Sep 2026 (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
No change recorded as of 26 Sep 2026 · official source last checked
On this page 9 sections

In brief

Deployers, distributors and importers must assume provider duties when they rebrand or substantially modify high-risk AI is a legal requirement under the EU AI Act in the European Union (Article 25(1) and 25(2)). It applies from 2 December 2027. The record carries 2 evidence examples and mappings to 2 frameworks.

Instrument
EU AI Act
Jurisdiction
European Union
Nature
Legal requirement
Source reference
Article 25(1) and 25(2)
Applies from
2 December 2027
Who it binds
Provider / developer, Deployer / user organisation, Importer, Distributor
Evidence examples
2
Framework mappings
ISO/IEC 42001:2023, NIST AI Risk Management Framework 1.0
Controls that meet it
3
Official source
Open official text
Verification
Verified against the official source 26 Sep 2026

What does it require?

A distributor, importer, deployer or other third party is treated as the provider of a high-risk AI system, with all Article 16 duties, if it puts its own name or trademark on a system already on the market, makes a substantial modification to a high-risk system that stays high-risk, or changes the intended purpose of a system so that it becomes high-risk. The original provider then ceases to be provider for that system but must cooperate and supply the information and access needed for the new provider to comply.

Practical action

Add a reclassification check to change control so that white-labelling, fine-tuning or repurposing a high-risk system triggers the provider workstream.

Who does it apply to?

Any organisation in the value chain that rebrands, substantially modifies or repurposes a high-risk AI system; original providers owe the cooperation duty.

Applies from:

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • satisfiesProcessRelease manager · at launch and on material change
    Model release and change-management gate

    Serves 5 recorded duties · evidence: Release or change approval record, Release and change-classification procedure

    The gate flags substantial modification, rebranding and repurposing and opens the provider duties.

  • supportsContractual termLegal counsel · once per ai system
    Contractual allocation of AI duties across the supply chain

    Serves 9 recorded duties · evidence: AI supplier clause set, AI customer or deployer clause set, Contract clause index against the AI register

    Contracts set out cooperation from the original provider.

  • supportsProcessAI governance lead · continuous
    AI system inventory and classification

    Serves 11 recorded duties · evidence: AI system register, Risk-tier classification sign-off, AI intake and classification procedure

    Inventory records the organisation's role for each system.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

All 12 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Change-control reclassification assessmentrecordDocumented decision on whether a modification or rebranding triggers provider status.
Cooperation clause with original providerdocument

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every European Union duty mapped this way →

Framework mappings table
FrameworkReferenceNoteConfidence
ISO/IEC 42001:2023Clause 4.1; Annex A.10.2Determining the organisation's role and allocating responsibilities along the chain.medium
NIST AI RMF 1.0GOVERN 6.1, MAP 1.1Roles across the AI supply chain and context of use.medium

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under EU AI Act (Article 25(1) and 25(2)).

Who must comply with this obligation?

Any organisation in the value chain that rebrands, substantially modifies or repurposes a high-risk AI system; original providers owe the cooperation duty.

When does this obligation apply?

It applies from 2 December 2027.

What evidence shows compliance?

A reviewer would expect: Change-control reclassification assessment; Cooperation clause with original provider.

Which frameworks map to this obligation?

It is mapped to ISO/IEC 42001:2023 Clause 4.1; Annex A.10.2, NIST AI Risk Management Framework 1.0 GOVERN 6.1, MAP 1.1. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

Contractual allocation of AI duties across the supply chain; AI system inventory and classification; Model release and change-management gate.

What should an organisation do in practice?

Add a reclassification check to change control so that white-labelling, fine-tuning or repurposing a high-risk system triggers the provider workstream.

Cite this record

AIPolicyTracker (2026). “Deployers, distributors and importers must assume provider duties when they rebrand or substantially modify high-risk AI (EU AI Act)” [AIPT-OBL-0029, verified 26 September 2026]. https://aipolicytracker.org/id/AIPT-OBL-0029 (accessed 8 November 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0029: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence, Official Journal of the European Union, https://eur-lex.europa.eu/eli/reg/2024/1689/oj.

BibTeX
@misc{aipolicytracker2026_deployersdistributorsand,
  author       = {{AIPolicyTracker}},
  title        = {{Deployers, distributors and importers must assume provider duties when they rebrand or substantially modify high-risk AI (EU AI Act)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-art-25-value-chain-becoming-provider}},
  url          = {https://aipolicytracker.org/obligations/eu-ai-act-art-25-value-chain-becoming-provider},
  urldate      = {2026-11-08},
  note         = {Data licensed CC BY 4.0. Accessed 8 November 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.