ARTICLE 50 · FINAL-WEEK IMPLEMENTATION BRIEF
The EU AI Act's Article 50 transparency rules apply from 2 August 2026. This independent checklist separates provider and deployer work so a chatbot notice is not mistaken for synthetic-content marking—and a voluntary Code decision is not mistaken for compliance itself.
Source-checked 30 July 2026 · five printable A4 pages · no signup · planning aid, not legal adviceTHE FIRST CONTROL
The Commission's new Q&A describes four situations. The responsible actor, required action, exceptions, and evidence route differ. Start by recording uncertainty instead of forcing every use into one generic “AI label” task.
Read the official Article 50 Q&A ↗FOUR CASES · TWO PRIMARY ROLES
One system may create more than one workstream. These cards are routing prompts; the current Regulation, official guidelines, and facts decide the scope.
Inform the person that they are interacting with AI no later than the first interaction, unless this is obvious to a reasonably well-informed, observant and circumspect person.
EVIDENCE ROUTEFirst-interaction capture · copy approval · exception rationaleMark outputs in a machine-readable format and make them detectable as artificially generated or manipulated, subject to the Regulation's technical and proportionality conditions.
EVIDENCE ROUTEMarking method · detection test · technical limitation recordInform exposed natural persons that the system is operating, and handle personal data in line with applicable data-protection requirements.
EVIDENCE ROUTENotice placement · audience coverage · data-protection routeDisclose artificial generation or manipulation. For public-interest text, the human review or editorial-control exception and accountable party matter.
EVIDENCE ROUTELabel specimen · publishing control · exception decisionSIX CONTROLLED MOVES
Work from the live system outward. A policy sentence without a tested customer or publishing surface is still an open task.
List the system, output type, audience, provider/deployer role, launch surface, and owner.
Assign each use to case 01, 02, 03, 04, multiple cases, or unresolved—with the reason visible.
Place the interaction notice, machine-readable mark, exposed-person notice, or content label in the actual journey.
Capture first interaction, accessibility, localisation, output marking, label visibility, and exception behaviour.
Store the approved copy, test date, limitation, owner, source version, and evidence reference—not personal data.
Keep the voluntary Transparency Code signing decision separate from the underlying Article 50 work.
DO NOT MERGE THESE DATES
The 27 July 18:00 CEST time is the cut-off for inclusion in the initial public list of Transparency Code signatories. Signing is voluntary and remains possible later. The Article 50 transparency obligations apply from 2 August 2026.
Run the private signatory-readiness check →DO NOT GENERALISE THE GRACE PERIOD
The official Q&A describes a transition for the Article 50(2) machine-readable marking obligation for qualifying systems placed on the market before 2 August. It is not a four-month delay for every Article 50 duty.
Check the official conditions ↗FREE → EDITABLE → IMPLEMENTABLE
Route the four cases, control the T-72 to T-0 cutover, record the release decision, and retain inspectable evidence.
Download the five-page packet →Eight connected sheets, ten final-guideline QA scenarios, and an editable playbook for inventory, notices, evidence, literacy, and incident review.
Inspect the Launch Kit →Add the React disclosure components, official EU icon files, and the offline signatory-readiness room.
Inspect the Sprint Bundle →CONTROLLING PUBLIC SOURCES
Official guidance can change. Use these links to validate the live position, scope, exceptions, and technical detail before acting.