Official-source-backed technical resource
Assign maintenance responsibilities after AI deployment
Specify who maintains notice wording, integration settings, marking controls and evidence after handover. Includes a free implementation worksheet.
Short answer
Specify who maintains notice wording, integration settings, marking controls and evidence after handover. Include change notifications and a route for unresolved issues.
Download the blank working record (.md)
When to use this guide
An agency assumes the client will maintain the notice, while the client expects the agency to monitor all model and platform changes.
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
-
List controls and dependencies that can change after release.
-
Assign operational owners and notification paths for each.
-
Define when a change requires technical retesting or renewed qualified review.
-
Confirm access to the relevant evidence without sharing private credentials.
What the example review finds
-
No party owns a notice change after a model switch.
-
The client cannot access the delivered test record.
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
-
Control
-
Maintenance owner
-
Change notification
-
Review trigger
-
Evidence access
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
An operational responsibility matrix does not replace contracts or determine legal roles.
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.