Template
EU AI Act Annex V - Declaration Content Template
Annex V sets out the content that belongs in the EU declaration of conformity. The useful job of the template is not to over-interpret the Annex, but to make sure the provider has a clear place to record the required identification, references, date, place, and signatory details.
Technical contribution: Evidence-backed scaffold
Who supplies what
What Annex V expects, what the template can add, and what your team still owns
Annex V is content-specific. The template gives you the structure, but your team still has to fill in the actual provider, system, standards, and signatory information.
| Annex V expects | What the template can add | What your team still has to write | Practical output to keep |
|---|---|---|---|
| Provider identification | A section for provider name and address details. | Fill in the provider identity exactly as it should appear in the declaration. | A declaration identity block. |
| Identification of the AI system | A section for system name, version, and identifying references. | Record the actual system identification used in the declaration. | A system-identification block. |
| References to standards, common specifications, or notified body details where applicable | A section for the references that Annex V expects in the declaration. | List the standards, specifications, or notified-body references that actually apply. | A references block inside the declaration. |
| Place and date of issue and signatory details | A section for final declaration issuance details. | Fill in the place, date, signatory name, and function. | A signature block ready for final approval. |
Manual fields
What your team still adds to Annex V
Annex V is declaration content. The template can lay out the fields, but your team still has to supply the actual identity, references, and signatory data used in the declaration.
| What you add | Why it is required | Practical format to use |
|---|---|---|
| Provider name and address | Annex V requires provider identification inside the declaration. | A short identity block. |
| System identification | Annex V requires clear identification of the relevant AI system. | A name, version, and reference line. |
| Applicable references | Annex V requires the relevant standards, specifications, or notified-body references where applicable. | A short list of references. |
| Issuance and signatory details | Annex V requires place/date and signatory information. | A dated signature block. |
FAQ
Frequently asked questions
What is the Annex V - Declaration Content template page for?
This page explains what the Annex V - Declaration Content 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 Annex V - Declaration Content 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 Annex V - Declaration Content 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 Annex V - Declaration Content 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.