Official-source-backed technical resource
Maintain a version history for transparency controls
Preserve the relationship between approved wording, configuration and deployed releases. Includes a free implementation worksheet.
Short answer
Preserve the relationship between approved wording, configuration and deployed releases. A current screenshot should not overwrite the only evidence of an earlier implementation.
Download the blank working record (.md)
When to use this guide
A team replaces its notice copy in a shared document, losing the wording that was deployed for the previous release.
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
-
Assign stable versions to notice text and material configuration changes.
-
Link each deployment to the versions it actually used.
-
Retain superseded records with dates and reasons for change.
-
Test retrieval of the evidence for one historical release.
What the example review finds
-
The current document has overwritten the old wording.
-
A release reference does not identify its configuration version.
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
-
Notice version
-
Configuration version
-
Release
-
Change reason
-
Historical evidence
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
Version history records changes; it does not validate the adequacy of any particular version.
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.