Official-source-backed technical resource
Review provenance and labels in generated PDFs
Inspect the final PDF as delivered, including visible labels, metadata and the generation record. Includes a free implementation worksheet.
Short answer
Inspect the final PDF as delivered, including visible labels, metadata and the generation record. Keep its technical provenance separate from any applicable visible disclosure decision.
Download the blank working record (.md)
When to use this guide
A report builder exports a PDF whose cover says manually prepared even though its substantive draft was generated and not reviewed.
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 source content, generation step and subsequent edits.
-
Inspect visible claims and metadata in the exported PDF.
-
Check any implemented provenance mechanism using a tool that supports the format.
-
Link the final file version to the review and disclosure decision.
What the example review finds
-
The cover claim does not match the workflow.
-
The recorded review applies to an earlier draft, not the exported PDF.
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
-
Source version
-
PDF version
-
Visible claim
-
Provenance result
-
Review decision
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 PDF label or metadata entry does not by itself satisfy every applicable marking or disclosure obligation.
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
- C2PA specifications — validation, assertions and provenanceCoalition for Content Provenance and Authenticity
Last reviewed: 2026-09-23. This is technical implementation information, not legal advice.