Official-source-backed technical resource
Build a transparency release evidence manifest
List the artifacts that show what was deployed, where and how it was checked. Includes a free implementation worksheet.
Short answer
List the artifacts that show what was deployed, where and how it was checked. Verify the manifest against the actual files before presenting it as a release record.
Download the blank working record (.md)
When to use this guide
A release pack contains screenshots but no build identifier linking them to the deployed chatbot.
This is a fictional implementation scenario. The procedure below is Article 50 Hub's suggested working method, not a prescribed legal form, a customer result or a claim that every step is an additional statutory requirement.
Review procedure
-
Record the release, environment and affected user-facing surfaces.
-
List notice versions, configuration references, test records and final artifact references.
-
Check that each manifest item is retrievable by an authorized reviewer.
-
Mark missing or superseded evidence explicitly and assign follow-up work.
What the example review finds
-
The screenshots cannot be tied to a build.
-
A linked test record belongs to an earlier release.
Keep these example observations separate from your own results. An unknown or untested state should stay open until the relevant evidence has been inspected.
Fields for your working record
-
Release ID
-
Surface
-
Artifact reference
-
Evidence version
-
Retrieval result
Use the downloadable blank worksheet linked on this page to connect the observed behavior with the deployed system. Add a reviewer, date, evidence reference, unresolved questions and a next action. The worksheet is editable locally and does not upload your records to Article 50 Hub.
Completion and handoff
Close the task only for the scope actually reviewed. Preserve the result that another authorized reviewer can reproduce, identify the owner of remaining work, and record a retest when the implementation changes. A completed worksheet is not a substitute for the underlying evidence.
Decision boundary
A complete manifest describes available evidence; it does not prove the controls are legally sufficient.
The official references below provide legal or technical context. Resolve applicability and exception questions with the responsible qualified reviewer; use the product's tools to organize implementation work within that assessment.
Official sources
- EU AI Act — legal text and contextEUR-Lex
- Commission FAQ — transparency obligations and scopeEuropean Commission
- Article 50 Service Desk — read with its amendment notice and current Commission guidanceEuropean Commission
Last reviewed: 2026-09-23. This is technical implementation information, not legal advice.