Article 50 has applied since 2 August 2026. Enough has been written about what the text says. The question on the table now is a different one: who in your organisation changes what, and how will you know later that it happened.
This piece is about that translation. Not what Article 50 means, but what you do with it on Monday morning.
The four duties, by owner
Article 50 splits four duties across two roles. That is not a legal detail but decides who in your organisation is up.
The duty to make clear that someone is interacting with AI sits with the provider and lives in the design of the system. In practice that is your product team or your supplier. The duty to mark synthetic output in a machine-readable format also sits with the provider and is a technical change.
The duty to inform people about emotion recognition or biometric categorisation sits with the deployer and is usually a process change. And the duty to visibly disclose deepfakes and certain public-interest text also sits with the deployer, at publication, so it often lands with marketing and communications.
Most organisations occupy both roles at once. An insurer running a purchased chatbot is the deployer for that bot, but the provider for the customer portal it has built with a generative component inside.
Where the disclosure belongs
With chatbots we see three variants that do not meet the bar. A label such as digital assistant or service agent describes the function, not the nature of the system. A mention buried in a privacy statement does not reach the person at the moment that counts. And a disclosure that appears only on the first session misses everyone who joins later.
What works is a notice at the moment of interaction, in plain language, visible without anyone having to click through. The exception in the law applies only where it is obvious to a reasonably observant person that this is AI, and a wording that leaves the question open does not clear that bar.
For generated image and video there is a distinction that often gets conflated. Machine-readable marking is the provider's duty and is invisible to people. Visible disclosure of deepfakes is the deployer's duty and is meant precisely to be seen. You need both if you hold both roles.
The only transitional period there is
One provision has an extension, and it is narrower than usually assumed. Only the machine-readable marking, and only for systems already on the market before 2 August 2026, has time until 2 December 2026.
Everything else applies in full. That means the chatbot disclosure, the notice for emotion recognition and the visible disclosure of deepfakes should already be in order. Anyone who has set their planning on 2 December 2026 for the whole thing has read that transitional period too broadly.
Recording that you arranged it
Article 50 has no conformity assessment. There is no audit that documents your work and no registration in an EU database. That means your own record is the only evidence there is.
We keep four fields per system. Which paragraph applies and why. Whether you are the provider or the deployer. Which measure was taken and where it is visibly or technically implemented. And who established that, on what date.
That is deliberately short. A file that is too heavy does not get maintained, and a file that is not maintained is unusable within six months. Do attach a reassessment trigger, for example every release in which a generative feature changes.
Where organisations lose time
Two things cost the most in practice. The first is role determination for purchased software with AI features, because suppliers are not always clear about who carries which duty. Ask in writing and record the answer, even when the answer is unsatisfying.
The second is coordination between teams. The disclosure in a chatbot is a product change, the labelling of generated imagery is a communications agreement, and output marking is a technical change. Three teams, three roadmaps. Without one owner watching the whole, one part always stays behind.
How we approach this
If you want a first picture yourself, take the free AI transparency scan: seven questions, an immediate score with your biggest gap. The Article 50 transparency check then walks through your systems, determines the applicable paragraph and your role per system, and delivers the concrete changes plus the record. If the question is broader, for example because the register and classification are still missing, the AI governance scan at 2,950 euro is the logical starting point.
The legal breakdown per paragraph sits on the Praxikon. For the teams that have to recognise in their daily work when a disclosure is required, LearnWize provides role-based training.
Closing
Article 50 is not the heaviest obligation in the AI Act, but it is the first one an outsider can see you meeting. A visitor opening your chatbot can tell within two seconds whether you arranged it. That makes it a poor candidate to postpone and a good one to finish first.
