Template
EU AI Act Article 47 - EU Declaration of Conformity Template
Article 47 requires the provider to draw up an EU declaration of conformity for each high-risk AI system. The declaration is not just a statement that compliance work exists somewhere else; it is a formal document tied to the relevant AI system and its conformity route.
Technical contribution: Evidence-backed scaffold
Who supplies what
What Article 47 expects, what the template can add, and what your team still owns
The template gives you a declaration section and a structure for the required references. It does not create a valid declaration by itself and it does not replace provider approval or signature.
| Article 47 expects | What the template can add | What your team still has to write | Practical output to keep |
|---|---|---|---|
| A declaration for each relevant high-risk AI system | A dedicated declaration section in the package. | State the declaration for the specific system and version. | A declaration draft tied to the system. |
| References to the conformity route and supporting materials | A structured place for the references that belong with the declaration. | Record the real references, standards, and conformity route used. | A referenced declaration record. |
| A formal provider statement | A clear place for the declaration wording. | Add the final provider statement and approval text used in practice. | A final declaration text for review. |
| Provider sign-off | A place to capture that sign-off still remains human-owned. | Record the approver, date, and signing function used by the provider. | A signature-ready declaration section. |
Manual fields
What your team still adds to Article 47
The template can structure the declaration section, but your team still has to provide the final declaration text, references, approver, and signature details.
| What you add | Why it is required | Practical format to use |
|---|---|---|
| Final declaration statement | Article 47 requires the provider to draw up the declaration. | A short declaration statement ready for internal review. |
| References to the conformity route | The declaration has to align with the actual conformity path used for the system. | A short list of standards, specifications, and related references. |
| Named approver and signatory | The declaration remains a provider-owned act. | A sign-off record with role and date. |
| Version-specific identification | The declaration has to identify the relevant AI system clearly. | A short system-identification block inside the declaration. |
FAQ
Frequently asked questions
What is the Article 47 - EU Declaration of Conformity template page for?
This page explains what the Article 47 - EU Declaration of Conformity template section usually needs to cover inside an EU AI Act package, which parts can be supported by structured evidence, and which parts remain owned by the provider, deployer, or legal reviewer.
Does this Article 47 - EU Declaration of Conformity template page create a complete EU AI Act package?
No. It is one section-level guide. A review-ready package still needs the selected role and scope, the other applicable article-level sections, linked technical evidence, owner completion, and final human review.
What evidence should be linked to the Article 47 - EU Declaration of Conformity template section?
Use evidence that is current, traceable to the relevant system version, and connected to real runs, retained records, or approved procedures. A weak package relies only on narrative text; a stronger package links the narrative to reproducible artifacts.
Who should review the Article 47 - EU Declaration of Conformity template section before handoff?
The technical owner should confirm the system facts and evidence links, while compliance or legal reviewers confirm whether the section is sufficient for the selected EU AI Act role, scope, and conformity path.