This article is for anyone who deploys a high-risk AI system developed by another company. A deployer's obligations are in Article 26, and several of them cannot be met with what you have in-house alone: you need the provider to tell you things about the system. Here is what, why each one matters and what to do when the answer does not come.
First, the date, so as not to bring forward what is not yet due. Article 26 applies from 2 December 2027 for Annex III high-risk systems and from 2 August 2028 for Annex I systems; it does not reach Annex I, Section B products. Nothing that follows is an overdue obligation today. It is what you should have requested before it becomes one.
What depends on the provider
Four paragraphs of Article 26 depend, in practice, on information that only the provider has:
- Instructions for use (paragraph 1). You must take measures to use the system in accordance with its instructions for use. If you do not have the current ones for the version you deploy, you do not know what they are.
- Human oversight (paragraph 2). Oversight is assigned to persons with the necessary competence, training and authority. To organise it you need to know which oversight measures the provider has foreseen (Article 14).
- Serious incidents (paragraph 5). If you identify a serious incident, you immediately inform the provider first, followed by the importer or distributor and the relevant market surveillance authorities. You need its channel and its procedure before it happens, not on the day it happens.
- Logs (paragraph 6). You keep the logs that the system generates automatically and that are under your control for an appropriate period of at least six months, unless otherwise provided. You need to know what they are and how to access them.
On top of that comes a prior question: which conformity assessment procedure the provider has followed (Article 43) and whether the EU declaration (Article 47), the CE marking (Article 48) and the registration (Article 49) are in place, where applicable depending on the type of system, the applicable regime and the regulatory phase. It is not for you to carry out that assessment. You want to know where it stands before using the system in production.
The figure follows what happens when you ask the provider for a critical item. If it has it and answers, you record which version the evidence is for. If not, it is a gap, and there are four decisions: request it again with a deadline, escalate it to a management contact at the provider, record the risk on the system or record the decision to continue with the evidence outstanding, with a named person responsible, the justification, the mitigation measures and a review date. If the information may be legally required, that last one goes through a legal review first. All four end in writing, and they are method, not a requirement of the Regulation; the section on what to do when the answer does not come develops it.
It is a request, not an automatic right
It is worth saying early, because it changes the tone of the conversation with the provider:
This is a request for information. The provider is not necessarily required to supply every document requested. A "not available" response does not, on its own, establish non-compliance. However, missing information may prevent your organisation from properly assessing the system or meeting certain obligations. Review each case under the applicable law and contract. Listing an item as a request does not exclude that, depending on the case, the information may be legally required.
So the useful question is not only "will they give it to me?", but "what do I do if they don't?". And that has to be written down.
The version matters
A piece of evidence is valid for a specific version of the system. Instructions for use for version 1.0 say nothing reliable about 1.1. If the provider updates without changing the version reference, or if your team does not record which version it deploys, the documentation you hold is no longer tied to what you use.
Three habits solve it:
- Record the version you deploy and ask the provider for a unique reference for the system and for that version.
- Ask for a commitment to notify you of substantial modifications and non-conformities. A relevant change can invalidate what you hold and, in certain cases, affect your own obligations.
- When the version changes, review what you had already worked on, not only what was missing.
And a warning that runs the other way: if your organisation places its name or trademark on the system, or substantially modifies it so that it remains high-risk, it may come to be considered a provider. We explain it in the three Article 25 cases.
When the answer does not come
A gap is a critical item that the provider does not have or does not answer. For each one there are, in essence, four decisions: request it again with a deadline, escalate it to a management contact at the provider, record the risk on the system or record your organisation's decision to continue with the evidence outstanding.
The last one is the most delicate, and it should be done properly: with a named person responsible, the justification, the mitigation measures and a date to review it. That decision does not replace any legal obligation, does not show that the system complies with the Regulation and does not authorise continued use where applicable law requires the system to be suspended or its use avoided. What it does do is record that the gap was seen and who decided what. If the information may be legally required, it deserves a legal review before proceeding.
Where EN 18286 fits
EN 18286:2026 is a harmonised standard on the quality management system of providers of AI systems. Its reference was published in the Official Journal of the European Union by Commission Implementing Decision (EU) 2026/2274 of 12 October 2026, published in the Official Journal of the European Union on 14 October 2026. We have already explained why it is not yours: it is addressed to the provider, and if you deploy you do not have to implement it.
What it does do for you is describe, publicly and in an orderly way, what should exist on the other side. It is a good list of where to look: how the provider identifies its versions, what it says about data management, how it collects and handles incidents, how it communicates changes.
How we have built it into the product
In the high-risk module we have added Provider evidence: a proprietary catalogue of 17 documentary requests for high-risk AI systems, developed with reference to selected areas covered by EN 18286:2026.
For each high-risk system your organisation deploys:
- You prepare the request with a template in Spanish or English. You send it yourself: Alethexis does not write to the provider.
- You record each response with its status, its evidence level (from E0, no evidence, to E3, a document verified by an independent third party, as stated by the provider) and the version it applies to.
- You decide on critical gaps with one of the four decisions above, and each one is recorded with its date and who took it.
- You export a dossier in PDF, with its SHA-256 fingerprint recorded, or in Markdown.
There is no provider score and no traffic light. Each item carries a priority, critical or optional, which is our own methodological criterion, not a classification by the standard or the Regulation.
And what it does not do, stated just as clearly:
This tool allows your organisation to record requests for provider documentation, responses received and decisions taken. It does not perform audits, conformity assessments or legal verification of the provider's or AI system's compliance. Your organisation is responsible for assessing the documents and their sufficiency. Using this tool does not replace applicable legal obligations or professional advice where needed.
If you are choosing a provider or about to renew, the ten questions of serious due diligence are the step before this one. And the rest of what falls to you as a deployer is in Article 26, paragraph by paragraph and in the high-risk module.
This article is for information purposes and does not constitute legal advice.