Conformity assessment under the EU AI Act
Conformity assessment is the procedure by which the provider of a high-risk AI system demonstrates that the system meets the EU AI Act's requirements before it is placed on the market or put into service. This page defines the term, walks the two routes the regulation sets out, and shows which evidence an assessment actually reads.
Auditrek is not open yet, so anything on this page about what it does is what it is being built to do.
What conformity assessment means under the EU AI Act
Conformity assessment under the EU AI Act is the procedure a provider follows to demonstrate that a high-risk AI system meets the requirements of Chapter III, Section 2 of Regulation (EU) 2024/1689 before that system is placed on the market or put into service. The regulation sets the procedure out in Article 43, describes the two available routes in Annex VI and Annex VII, and names the outputs it produces: the EU declaration of conformity in Article 47 and the CE marking in Article 48.
The term is not new and was not invented for AI. It is borrowed from the EU's existing product legislation, where the manufacturer of a lift or a medical device assesses the product against harmonised requirements, records the result, signs a declaration and affixes a mark. The AI Act places high-risk AI systems inside that same machinery. One practical consequence matters more than the rest: an assessment of this kind is largely documentary. What gets examined is the technical documentation, the quality management system and the records the system produces in operation, not a live interrogation of model weights.
A worked example
A mid-market lender builds and runs a model that scores applicants for consumer credit. Creditworthiness evaluation of natural persons is one of the use cases listed in Annex III of the regulation, so the provider obligations, conformity assessment among them, are in scope before the system goes into service.
In practice the compliance officer assembles a set of documents: the technical documentation described in Annex IV, the risk management records from Article 9, the instructions for use that Article 13 requires a provider to supply to deployers, the human oversight measures under Article 14, and the automatically generated logs that Article 12 requires the system to keep over its lifetime. Under the internal control route, the provider assesses that set itself and signs the declaration. Under the notified body route, a third party reads the same set. Either way, the set of documents is the assessment. The question a supervisory authority can later ask is narrower and harder than a general question about compliance: it is "show me the records this system produced on the date in question, and show me they have not been edited since."
The elements the regulation names
| Element | Where it sits in Regulation (EU) 2024/1689 | What it produces |
|---|---|---|
| Internal control | Article 43, Annex VI | The provider's own assessment against the Section 2 requirements, recorded in the technical documentation |
| Assessment involving a notified body | Article 43, Annex VII | A third-party review of the quality management system and the technical documentation |
| Re-assessment after substantial modification | Article 43 | A fresh procedure where a system is substantially modified after it was assessed |
| EU declaration of conformity | Article 47 | A signed statement naming the system and the requirements it was assessed against |
| CE marking | Article 48 | The visible mark affixed once the procedure has been completed |
| Registration | Article 49 | Entry in the EU database for the Annex III use cases, before the system is placed on the market |
Why record-keeping shows up inside the assessment
Two of the Section 2 requirements produce evidence continuously rather than once. Article 12 concerns automatic recording of events over the system's lifetime, and Article 72 concerns post-market monitoring after the system is in service. Everything else in an assessment file can be written in a quiet week before a launch. Logs cannot: they either exist for the period under review or they do not.
That is the difficult join for most mid-market teams. The declaration is a one-off artefact, while the log is a running obligation whose value depends entirely on whether anyone can show it is the same log that was written at the time. A CSV exported from a data warehouse three years after the fact carries no evidence of its own integrity. A hash-chained record does, because breaking any link in the chain is detectable by recomputing the chain rather than by trusting a stored flag.
- The assessment reads documents, so the documents have to be assemblable per system and per date range.
- Logs are the only part of the file written by the system rather than by a person.
- Integrity of those logs is a separate question from their existence, and it is the question that gets asked late.
Related terms
- High-risk AI system. The classification that triggers the Chapter III, Section 2 requirements, and therefore the conformity assessment procedure. Covered in a separate glossary entry in this pillar.
- Notified body. A conformity assessment body designated by a member state to carry out third-party assessments under the Annex VII route.
- EU declaration of conformity. The provider's signed statement under Article 47, naming the system and the requirements assessed.
- CE marking. The mark under Article 48, affixed after the procedure is complete, familiar from other EU product legislation.
- Substantial modification. A change to an assessed system significant enough that the regulation points back to a fresh assessment.
- Post-market monitoring. The ongoing obligation under Article 72 to collect and review data on a system's performance after it is in service.
- Record-keeping under Article 12. The automatic logging obligation whose output ends up inside the assessment file. Our field-by-field guide in this pillar goes through what a log has to contain.
Questions
Is conformity assessment the same as certification?
Not quite. Under the internal control route in Annex VI the provider assesses its own system and signs the EU declaration of conformity, with no certificate from anyone else. Under the Annex VII route a notified body is involved and can issue a certificate. Both are conformity assessment; only one involves a third party.
Does conformity assessment apply to us if we bought the model from a vendor?
The obligation sits with the provider of the high-risk system. An organisation that deploys someone else's system has its own, different obligations. Article 25 describes the circumstances in which a deployer or distributor becomes a provider, including putting its own name on the system or substantially modifying it, at which point the provider obligations follow.
What is the difference between conformity assessment and CE marking?
The assessment is the procedure; the CE marking under Article 48 is the visible result. The marking is affixed after the procedure has been carried out and the EU declaration of conformity under Article 47 has been drawn up.
Do logs form part of a conformity assessment?
Article 12 record-keeping is one of the Chapter III, Section 2 requirements a high-risk system is assessed against, so the logging capability and the records it produces belong in the assessment file alongside the technical documentation. Our Article 12 guide walks the fields involved.
Does the assessment have to be repeated?
Article 43 points to a fresh procedure where a high-risk system is substantially modified after it has been assessed. Post-market monitoring under Article 72 runs continuously regardless, so the evidence base does not stop at the declaration.
When do these obligations start to apply?
The regulation phases its obligations in over different dates, and the high-risk timeline has been the subject of active discussion. We keep the dates and their caveats on the timeline page in this pillar rather than restating them here, because that is the page we update.
Can a tool carry out a conformity assessment for us?
No. The assessment is a procedure carried out by the provider, or by the provider together with a notified body. Software can hold and structure the evidence that procedure reads, which is what Auditrek is built to do for inference records, but it cannot perform the assessment or tell you whether your practices satisfy any obligation.