EU AI Act Article 16: Provider Obligations, Implemented in Practice
EU AI Act Article 16 bundles into twelve letters everything the provider of a high-risk AI system owes, from conformity with Section 2 to accessibility. Our answer: the twelve letters are a release checklist wired into the registration gate of the governance layer, and every letter has an artefact in the release record.
Article 16 is the table of contents of the provider obligations. It demands almost nothing itself; it points: to Section 2 with the requirements of Articles 8 to 15, to Articles 17 to 21 and to the procedure from conformity assessment to registration. It addresses the provider under Art. 3(3), whoever develops a system and places it on the market or puts it into service under their own name. And, through Article 25, anyone who becomes a provider later. Read Article 16 as a list and you already hold the release checklist.
The EU AI Act has been in force since 1 August 2024. The prohibitions and the AI literacy duty have applied since February 2025, the obligations for GPAI models since August 2025, the transparency obligations under Article 50 since August 2026. The obligations for high-risk systems under Annex III apply, after the postponement by the amending Regulation (EU) 2026/1744 (Digital Omnibus), from 2 December 2027, and for Annex I products from 2 August 2028. Article 16 belongs to these high-risk obligations. The Omnibus moved deadlines; it removed no obligation.
What EU AI Act Article 16 requires
One paragraph, twelve letters. Providers of high-risk AI systems must:
Point (a): ensure the system meets the requirements of Section 2, Articles 8 to 15, from risk management to cybersecurity.
Point (b): indicate their name, registered trade name or trademark and contact address on the system or, where that is not possible, on its packaging or accompanying documentation.
Point (c): have a quality management system in place under Article 17.
Point (d): keep the documentation referred to in Article 18: technical documentation, QMS documentation, notified-body documents and the declaration of conformity, for ten years.
Point (e): keep the automatically generated logs under Article 19, to the extent they are under the provider’s control, for at least six months.
Point (f): complete the conformity assessment procedure under Article 43 before placing the system on the market or putting it into service.
Point (g): draw up an EU declaration of conformity under Article 47.
Point (h): affix the CE marking under Article 48, digitally for systems provided digitally.
Point (i): comply with the registration obligation in Art. 49(1), registering themselves and the system in the EU database under Article 71 before placing it on the market.
Point (j): take corrective actions and inform under Article 20: on non-conformity, correct, withdraw, disable or recall immediately and inform distributors, deployers and importers; on a risk within Art. 79(1), investigate the causes and notify the market surveillance authorities.
Point (k): upon a reasoned request of a national competent authority, demonstrate conformity with Section 2; Article 21 adds language, log access and confidentiality.
Point (l): meet the accessibility requirements of Directives (EU) 2016/2102 and (EU) 2019/882.
The link in Article 25: whoever offers a high-risk system under their own name, substantially modifies it or changes its intended purpose so that it becomes high-risk is considered a provider under Art. 25(1) and carries every obligation in Article 16. The original provider must cooperate under Art. 25(2), after the Omnibus wording explicitly with documentation, known limitations and failure modes and targeted technical access.
The relief for financial institutions: under Art. 17(4) the QMS obligation is deemed fulfilled by complying with the internal governance rules of Union financial services law, except for risk management, post-market monitoring and incident reporting. Art. 18(3) and Art. 19(2) allow documentation and logs to be kept within the supervisory records.
The technical example
A software vendor supplies banks with a credit pre-check model: before the actual scoring it sorts applications into pass-through, follow-up question or manual review. Assessing the creditworthiness of natural persons is Annex III point 5(b), so high-risk. The vendor is the provider under Art. 3(3); the bank is the deployer under Article 26 with the fundamental rights impact assessment under Article 27.
The data flow: the bank’s application journey calls the policy gateway with a use-case ID, never the model. The gateway resolves the ID in the registry, checks the data zone, replaces name, address and account number with pseudonyms and passes the application features to the model. Back come a proposal and a confidence. Below the threshold the application goes to the reviewer queue. Every pre-check lands in the evidence log, every correction by a case handler flows back as a signal. The model runs in the vendor’s tenant; the bank sees only the gateway and the result.
The contrast: a second bank wants to fine-tune the model on its portfolio, with its own rejection data, its own product rules, its own threshold. Afterwards the model behaves differently from the assessed one. If that is a substantial modification under Art. 3(23), the bank becomes a provider itself under Art. 25(1)(b) and owes all twelve letters: its own conformity assessment, its own declaration, its own registration, its own QMS with the relief in Art. 17(4). Where does Article 16 bite? At release. Both vendor and bank have to prove before go-live that every letter is met, and again for every version.
How we implement it
At SIFAMO, Article 16 is not a lawyers’ list but the schema of the release record. The registration gate of the governance layer admits no version into the registry whose record is empty for any of the twelve letters. No registration, no route, so no release without evidence.
Twelve letters, one release record
The record is a build artefact of the pipeline; for each letter it points, with hash and signature, to the evidence. Simplified, for release 12:
We do not prove the requirements of Articles 8 to 15 with a statement but with the pre-deployment quality gates: evaluation on the business-owned set, regression against the previous version, adversarial tests, bias checks per group of persons, rollback plan. A Section 2 matrix maps each article to its gate and artefact: Article 9 to the risk register, Article 10 to the data sheets, Article 12 to the evidence log configuration, Article 14 to the oversight tier, Article 15 to the robustness tests. Business, risk and IT sign three ways. A red gate means the record is not written.
(b) to (e): model card, QMS, dossier, logs
The provider’s name and contact address sit in the model card, in the instructions for use under Article 13 and in the about dialog of the interface. The QMS under Article 17 is, for us, the process the gates belong to: release procedure, change management, incident procedure, versioned, with responsibilities under Art. 17(1)(m). The pipeline builds the Annex IV dossier per release and stores it write-once for ten years. The gateway writes the Article 12 logs to the evidence log, which lives in the provider’s tenant. That puts them under the provider’s control, so point (e) applies in full; we keep them ten years, not six months, because otherwise the documentation outlives its evidence.
(f) to (i): assessment, declaration, CE, registration
For Annex III point 5 the conformity assessment under Art. 43(2) is internal control under Annex VI. We run it as a review step at the end of the pipeline: QMS against Article 17, dossier against Annex IV, development and monitoring against the dossier, with a report signed by risk. The pipeline generates the EU declaration of conformity under Article 47 from the registry record as a machine-readable, electronically signed file with the Annex V content, reissued for every version because Art. 47(4) requires it to be kept up to date. The CE marking is digital under Art. 48(2), reachable from the interface, with a link to the declaration. Registration in the EU database under Art. 49(1) is its own gate step with the entry ID in the record; a version with a changed purpose or provider triggers an update.
(j) to (l): correction, demonstration, accessibility
Corrective actions under Article 20 are a runbook with us, not an intention: monitoring fires, the business owner pulls the kill switch in the registry, the gateway withdraws the route, deployers get the notice from a maintained distribution list, and the root-cause analysis runs on the evidence log. For point (k) there is a read-only portal for authorities: record, dossier, declaration, gate reports and, on request, log access. We test accessibility on the reviewer queue and the about dialog; the report is part of the record, and open findings block the gate.
The bank as provider
When the bank fine-tunes, it gets the same record, only with itself as provider. The vendor supplies the dossier, known limitations and test access under Art. 25(2), and the bank repeats the gates on its portfolio. Its QMS is, under Art. 17(4), the institution’s existing governance framework, extended by risk management, post-market monitoring and incident reporting under Articles 9, 72 and 73. My recommendation to banks: treat every fine-tuning as a substantial modification until the vendor’s dossier explicitly foresees it. More under AI Governance.
Typical mistakes
Article 16 is parked with legal. Points (f) to (i) are release steps. Caught up after go-live means: a non-conforming system in production.
The deployer thinks it is the deployer. Fine-tuning, own thresholds, new purpose: under Article 25 the bank is often the provider itself and only notices in the audit.
Logs at the deployer, duty at the provider. Point (e) covers only logs under the provider’s control. Ship the model on-premise and you must settle by contract who holds the logs, or nobody does.
Accessibility forgotten. Point (l) sits at the end of the list and is missing from almost every checklist.
Article 16 checklist
Is there a record per release that maps each of the twelve letters to an artefact with hash and signature, and does an empty cell block the registration gate?
Does a Section 2 matrix prove each of Articles 9 to 15 through a gate, signed three ways?
Is the QMS under Article 17 the documented process the gates belong to, with the Art. 17(4) boundary drawn for financial institutions?
Are dossier, QMS documentation and declaration of conformity stored write-once for ten years, and is it settled who holds the logs?
Is the Annex VI conformity assessment a documented step before every go-live, with a new declaration, digital CE marking and an updated database entry?
Is there a runbook for Article 20 with the kill switch held by the business owner and a maintained deployer distribution list?
Is it settled whether the deployer becomes a provider under Article 25 through fine-tuning or a change of purpose?
Open questions
What is a substantial modification? Art. 3(23) stays vague, and whether fine-tuning on customer data falls under it depends on what the vendor foresaw in Annex IV point 2(f). We treat it as substantial.
Harmonised standards. The standards on QMS and conformity assessment are still in progress. Until then, internal control under Annex VI is a self-assessment without a shared yardstick.
Control over logs. For hosted third-party models and for systems delivered on-premise it is open when logs are under the provider’s control. We settle it by contract and log in the gateway regardless of the answer.
Frequently asked questions
Does this apply to us as a deployer?
Article 16 addresses the provider. As a bank that buys a credit pre-check model and uses it unchanged, you fall under Article 26 and the fundamental rights impact assessment under Article 27. As soon as you fine-tune, substantially modify or change the purpose, you become a provider under Art. 25(1), and all twelve letters apply to you.
Do we need a notified body?
Not for creditworthiness under Annex III point 5. Art. 43(2) requires internal control under Annex VI. A notified body comes in for biometric systems under Annex III point 1 without full application of standards, and for Annex I products.
Do we have to reassess at every release?
At every substantial modification under Art. 43(4), yes. We do it at every release because the pipeline builds the assessment anyway. Pre-determined changes in the dossier are the way to ship routine updates without a new assessment.
EU AI Act Article 16: Provider Obligations, Implemented in Practice
EU AI Act Article 16 bundles into twelve letters everything the provider of a high-risk AI system owes, from conformity with Section 2 to accessibility. Our answer: the twelve letters are a release checklist wired into the registration gate of the governance layer, and every letter has an artefact in the release record.
Article 16 is the table of contents of the provider obligations. It demands almost nothing itself; it points: to Section 2 with the requirements of Articles 8 to 15, to Articles 17 to 21 and to the procedure from conformity assessment to registration. It addresses the provider under Art. 3(3), whoever develops a system and places it on the market or puts it into service under their own name. And, through Article 25, anyone who becomes a provider later. Read Article 16 as a list and you already hold the release checklist.
The EU AI Act has been in force since 1 August 2024. The prohibitions and the AI literacy duty have applied since February 2025, the obligations for GPAI models since August 2025, the transparency obligations under Article 50 since August 2026. The obligations for high-risk systems under Annex III apply, after the postponement by the amending Regulation (EU) 2026/1744 (Digital Omnibus), from 2 December 2027, and for Annex I products from 2 August 2028. Article 16 belongs to these high-risk obligations. The Omnibus moved deadlines; it removed no obligation.
What EU AI Act Article 16 requires
One paragraph, twelve letters. Providers of high-risk AI systems must:
The technical example
A software vendor supplies banks with a credit pre-check model: before the actual scoring it sorts applications into pass-through, follow-up question or manual review. Assessing the creditworthiness of natural persons is Annex III point 5(b), so high-risk. The vendor is the provider under Art. 3(3); the bank is the deployer under Article 26 with the fundamental rights impact assessment under Article 27.
The data flow: the bank’s application journey calls the policy gateway with a use-case ID, never the model. The gateway resolves the ID in the registry, checks the data zone, replaces name, address and account number with pseudonyms and passes the application features to the model. Back come a proposal and a confidence. Below the threshold the application goes to the reviewer queue. Every pre-check lands in the evidence log, every correction by a case handler flows back as a signal. The model runs in the vendor’s tenant; the bank sees only the gateway and the result.
The contrast: a second bank wants to fine-tune the model on its portfolio, with its own rejection data, its own product rules, its own threshold. Afterwards the model behaves differently from the assessed one. If that is a substantial modification under Art. 3(23), the bank becomes a provider itself under Art. 25(1)(b) and owes all twelve letters: its own conformity assessment, its own declaration, its own registration, its own QMS with the relief in Art. 17(4). Where does Article 16 bite? At release. Both vendor and bank have to prove before go-live that every letter is met, and again for every version.
How we implement it
At SIFAMO, Article 16 is not a lawyers’ list but the schema of the release record. The registration gate of the governance layer admits no version into the registry whose record is empty for any of the twelve letters. No registration, no route, so no release without evidence.
Twelve letters, one release record
The record is a build artefact of the pipeline; for each letter it points, with hash and signature, to the evidence. Simplified, for release 12:
Point (a): Section 2 is proven by gates
We do not prove the requirements of Articles 8 to 15 with a statement but with the pre-deployment quality gates: evaluation on the business-owned set, regression against the previous version, adversarial tests, bias checks per group of persons, rollback plan. A Section 2 matrix maps each article to its gate and artefact: Article 9 to the risk register, Article 10 to the data sheets, Article 12 to the evidence log configuration, Article 14 to the oversight tier, Article 15 to the robustness tests. Business, risk and IT sign three ways. A red gate means the record is not written.
(b) to (e): model card, QMS, dossier, logs
The provider’s name and contact address sit in the model card, in the instructions for use under Article 13 and in the about dialog of the interface. The QMS under Article 17 is, for us, the process the gates belong to: release procedure, change management, incident procedure, versioned, with responsibilities under Art. 17(1)(m). The pipeline builds the Annex IV dossier per release and stores it write-once for ten years. The gateway writes the Article 12 logs to the evidence log, which lives in the provider’s tenant. That puts them under the provider’s control, so point (e) applies in full; we keep them ten years, not six months, because otherwise the documentation outlives its evidence.
(f) to (i): assessment, declaration, CE, registration
For Annex III point 5 the conformity assessment under Art. 43(2) is internal control under Annex VI. We run it as a review step at the end of the pipeline: QMS against Article 17, dossier against Annex IV, development and monitoring against the dossier, with a report signed by risk. The pipeline generates the EU declaration of conformity under Article 47 from the registry record as a machine-readable, electronically signed file with the Annex V content, reissued for every version because Art. 47(4) requires it to be kept up to date. The CE marking is digital under Art. 48(2), reachable from the interface, with a link to the declaration. Registration in the EU database under Art. 49(1) is its own gate step with the entry ID in the record; a version with a changed purpose or provider triggers an update.
(j) to (l): correction, demonstration, accessibility
Corrective actions under Article 20 are a runbook with us, not an intention: monitoring fires, the business owner pulls the kill switch in the registry, the gateway withdraws the route, deployers get the notice from a maintained distribution list, and the root-cause analysis runs on the evidence log. For point (k) there is a read-only portal for authorities: record, dossier, declaration, gate reports and, on request, log access. We test accessibility on the reviewer queue and the about dialog; the report is part of the record, and open findings block the gate.
The bank as provider
When the bank fine-tunes, it gets the same record, only with itself as provider. The vendor supplies the dossier, known limitations and test access under Art. 25(2), and the bank repeats the gates on its portfolio. Its QMS is, under Art. 17(4), the institution’s existing governance framework, extended by risk management, post-market monitoring and incident reporting under Articles 9, 72 and 73. My recommendation to banks: treat every fine-tuning as a substantial modification until the vendor’s dossier explicitly foresees it. More under AI Governance.
Typical mistakes
Article 16 checklist
Open questions
Frequently asked questions
Does this apply to us as a deployer?
Article 16 addresses the provider. As a bank that buys a credit pre-check model and uses it unchanged, you fall under Article 26 and the fundamental rights impact assessment under Article 27. As soon as you fine-tune, substantially modify or change the purpose, you become a provider under Art. 25(1), and all twelve letters apply to you.
Do we need a notified body?
Not for creditworthiness under Annex III point 5. Art. 43(2) requires internal control under Annex VI. A notified body comes in for biometric systems under Annex III point 1 without full application of standards, and for Annex I products.
Do we have to reassess at every release?
At every substantial modification under Art. 43(4), yes. We do it at every release because the pipeline builds the assessment anyway. Pre-determined changes in the dossier are the way to ship routine updates without a new assessment.
This post is part of my series EU AI Act in practice. Here you find all articles at a glance.
Related: EU AI Act · All articles · AI Governance · AI Consultant
Recent Posts
Recent Comments