Official-source-backed technical resource

Prepare a transparency evidence export for a customer

Tailor the export to the delivered system and the customer's review purpose. Includes a free implementation worksheet.

Short answer

Tailor the export to the delivered system and the customer's review purpose. Include limitations and open tasks instead of presenting the pack as a certificate.

Download the blank working record (.md)

When to use this guide

An agency exports generic product screenshots for a client whose deployment uses a different notice and model configuration.

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

  1. Confirm the customer's actual deployment and requested evidence scope.

  2. Select artifacts linked to that build, configuration and user-facing surface.

  3. Remove unrelated tenant data and keep unresolved questions explicit.

  4. Verify the exported files and record the exact version shared through an authorized route.

What the example review finds

  • The screenshots show the agency demo rather than the client's site.

  • The pack includes an unrelated tenant's configuration.

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

  • Customer deployment

  • Requested scope

  • Included artifact

  • Open task

  • Export version

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 evidence pack supports review and does not certify the customer's system or authorize sharing confidential information.

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

  1. EU AI Act — legal text and contextEUR-Lex
  2. Commission FAQ — transparency obligations and scopeEuropean Commission
  3. 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.

Share this source-backed guideLinkedInEmail