The EU AI Act’s Article 50 transparency obligations apply from 2 August 2026 and require any research chatbot, literature-review assistant or generative lab tool that interacts with people or produces synthetic content to disclose that it is AI. This duty is separate from the machine-readable watermarking requirement in Article 50(2), which the AI Omnibus provisional agreement has pushed back to 2 December 2026 for generative systems already on the market — so procurement teams cannot treat the whole article as delayed.
Article 50 of Regulation (EU) 2024/1689 is the EU AI Act provision that sets disclosure duties for AI systems that interact directly with people, generate synthetic content, perform emotion recognition or biometric categorisation, or produce deepfakes and AI-written public-interest text. For research offices, this covers a growing shelf of everyday tools: AI-assisted literature-review platforms, participant-facing chatbots, lab-based generative-image tools and AI drafting assistants used in public engagement.
- What does Article 50 actually require?
- What applies from August 2026, regardless of the watermarking delay?
- Which research AI tools are caught by Article 50?
- Does the research exemption cover the tools you actually use?
- Common questions on Article 50 and research AI
- What this means for research offices
- What happens next
What does Article 50 actually require?
Article 50 sets out four distinct disclosure duties, and a research tool can trigger more than one at once. Under Article 50(1), providers of systems intended to interact directly with people — chatbots, virtual assistants, conversational research interfaces — must design them so users are told they are dealing with AI, at the latest by the first interaction. Draft Commission Guidelines published on 8 May 2026 confirm that AI agents fall within this duty, and that disclosure must be repeated where a single notice at the outset would not be obvious later in the exchange.
Article 50(2) requires providers of generative AI to mark synthetic audio, image, video or text outputs in a machine-readable, detectable format. Article 50(3) requires deployers of emotion-recognition or biometric-categorisation systems to inform exposed individuals, alongside GDPR Articles 12–14. Article 50(4) requires deployers to label deepfakes and disclose AI-generated public-interest text, unless a named person holds editorial responsibility after substantive human review.
What applies from August 2026, regardless of the watermarking delay?
The full transparency regime enters into force on 2 August 2026. Only one obligation has been pushed back: the AI Omnibus provisional agreement of May 2026 gives generative AI systems already placed on the market before that date until 2 December 2026 to meet the machine-readable marking requirement in Article 50(2). Nothing else in Article 50 moves.
That means the disclosure duties most relevant to research offices are unaffected by the delay:
- Article 50(1) chatbot and virtual-assistant disclosure applies from 2 August 2026 in full.
- Article 50(3) emotion-recognition and biometric-categorisation disclosure applies from 2 August 2026 in full.
- Article 50(4) deepfake and public-interest text labelling applies from 2 August 2026 in full.
- Only the technical marking format under Article 50(2) has a grace period, and only for pre-existing systems.
A research office that assumes “the watermarking clause is delayed, so we have more time” is conflating one narrow technical carve-out with the whole article. The European Commission’s own Compliance Checker data indicates transparency obligations are the second most common compliance trigger after AI literacy, affecting around 33% of organisations that have assessed themselves against the Act.
Which research AI tools are caught by Article 50?
Most research-facing AI tools map cleanly onto one or more Article 50 provisions. The table below sets out the mapping research offices should use when auditing procured and internally built tools.
| Research AI tool type | Article 50 provision | Who must act | Deadline |
|---|---|---|---|
| Literature-review or systematic-review chatbot assistant | 50(1) — AI interaction disclosure | Deployer (institution), if using a third-party tool; provider, if built in-house | 2 August 2026 |
| Participant recruitment or survey chatbot | 50(1) — AI interaction disclosure | Deployer | 2 August 2026 |
| Lab tool generating synthetic images, audio or text (e.g. synthetic dataset generation) | 50(2) — machine-readable marking | Provider | 2 August 2026; pre-existing systems to 2 December 2026 for marking only |
| Emotion-recognition or biometric-categorisation research instrument | 50(3) — disclosure to exposed individuals | Deployer | 2 August 2026 |
| AI-drafted public engagement or press content | 50(4) — public-interest text labelling | Deployer, unless human-reviewed with editorial responsibility | 2 August 2026 |
Note that the same tool often needs two audits: a chatbot that also produces AI-written summary text for publication can trigger both 50(1) and 50(4).
Does the research exemption cover the tools you actually use?
Recital 25 of the AI Act exempts AI systems and models developed and put into service for the sole purpose of scientific research and development. This exemption is narrower than it sounds. It covers AI built as the object of research — a novel model a lab is developing and testing — not commercial or off-the-shelf tools that a research team merely uses to do research.
A university deploying a commercially available literature-review assistant, a general-purpose chatbot, or a vendor’s lab-imaging tool does not benefit from the Recital 25 carve-out for that deployment. The institution acts as a deployer under Article 50 the moment that tool interacts with people or generates in-scope content, regardless of the research being scientific in nature. Procurement teams should not assume “we’re a research organisation” is itself an exemption — the exemption attaches to the AI system’s development purpose, not the purpose of the team using it.
Common questions on Article 50 and research AI
What are the transparency obligations under Article 50 of the AI Act?
Article 50 sets four disclosure duties: providers of interactive AI (chatbots, assistants) must flag their AI nature at first contact; providers of generative AI must mark synthetic outputs; deployers using emotion-recognition or biometric tools must inform exposed individuals; and deployers publishing deepfakes or AI-written public-interest text must label it as such, unless human-reviewed.
What is the EU Code of Practice on AI-generated content?
It is a voluntary Commission-coordinated framework covering Article 50(2) and 50(4), setting a standardised EU visual label for AI content, a taxonomy separating fully AI-generated from AI-assisted material, and modality-specific labelling guidance. A second draft was published in March 2026, with a final version expected by June 2026.
Why has Article 50’s transparency obligation been criticised as insufficient?
Academic analysis, including work published via the University of Glasgow’s repository, argues that a simple AI-interaction notice does not stop users from over-trusting confidently worded but unverified chatbot output — disclosure alone does not compel verification behaviour, which matters directly for research assistants summarising literature.
Are AI systems built only for research exempt from Article 50?
Only narrowly. Recital 25 exempts AI developed solely for scientific research and development as the object of study. It does not exempt a research office’s use of commercial, off-the-shelf AI tools — those deployments remain subject to Article 50 in the same way as any other organisation’s use.
What this means for research offices
Research administration teams procuring or building AI tools should treat 2 August 2026 as the operative date for every disclosure duty except machine-readable marking of pre-existing generative systems. Practical steps:
- Inventory every AI tool used in research workflows — literature review, participant engagement, lab generation, public communications — and tag each against Articles 50(1)–50(4).
- Confirm vendor contracts assign responsibility: does the vendor act as provider, leaving the institution as deployer with its own disclosure duties?
- Check chatbot and assistant interfaces disclose AI involvement clearly at first use, not buried in terms and conditions.
- Do not treat the December 2026 marking grace period as covering anything beyond Article 50(2) technical marking of pre-existing systems.
- Review public-facing AI-drafted content (news releases, dissemination summaries) for the human-review and editorial-responsibility carve-out under Article 50(4).
Institutions with dedicated research administration functions are well placed to run this audit alongside existing research-integrity and data-governance processes, since the same tool inventory typically maps onto GDPR and funder AI-use disclosure requirements already in place.
What happens next
The Commission’s final Guidelines and the finalised Code of Practice are both due before 2 August 2026, and both will refine — not delay — the duties above. Offices waiting for the Code before acting on Article 50(1), (3) and (4) will miss the window, since the Code covers marking and labelling detail only, not the underlying legal duty to disclose. Institutions best placed by August will have already mapped their AI tool inventory against Article 50, rather than treating the whole article as paused.