Article 50 of the EU AI Act requires transparency about AI-generated content from 2 December 2026. If your firm's AI outputs go through a qualified human review before use, one document closes this gap — and most of the evidence is already sitting in your HITL procedure.
Article 50(1) of Regulation (EU) 2024/1689 requires that AI-generated text, audio, or other content is marked as AI-generated before use. Article 50(4) provides an exemption: where AI-generated content is subject to human review by a person who bears editorial responsibility for it, the marking obligation does not apply. If PROC-AIMS-HITL-001 is operative, the exemption evidence already exists. DOC-AIMS-ART50-001 is the document that labels it correctly under Article 50 so it can be found, presented, and audited.
It is 2 December 2026. Sophie Chen is reviewing a draft client advice letter that she generated using GPT-4o and then substantially amended. She is satisfied with the content — it is legally accurate, her amendments are reflected, and it represents her professional judgement. She sends it to Pemberton Capital LLP.
The next day, Priya Anand receives a query from a peer at another firm: "Are you Article 50 compliant? We have been told we need to label everything as AI-generated." Priya pulls up PROC-AIMS-HITL-001. Sophie's sign-off form is in the register: GPT-4o output reviewed, amendments documented, outcome: AMENDED. Priya opens DOC-AIMS-ART50-001 — the compliance statement she approved last week. It makes three things explicit: the obligation exists, the exemption applies, and the sign-off form is the evidence. Priya replies: "We are compliant. The exemption applies because our procedure is documented and operative."
The other firm has no procedure. They spend the next six weeks retrofitting AI disclosure labels to every outbound document before realising that the labels were never required in the first place — because their senior solicitors had been reviewing the content all along. They just had no document that said so.
Article 50 of Regulation (EU) 2024/1689 applies from 2 December 2026. A law firm that uses AI to generate client-facing content and has not documented its position under Article 50 — either by asserting the editorial responsibility exemption or by embedding AI disclosure labels — is operating outside the statutory framework from that date. The absence of a compliance statement is not a neutral position.
"Users of an AI system that generates synthetic audio, video, text or images, shall disclose that the content has been artificially generated or manipulated."
"The obligations laid down in paragraphs 1 and 2 shall not apply where the use or presentation of AI-generated content is subject to human review or editorial control by a natural person, who is editorially responsible for the content published."
The structure of Article 50 is binary for most law firms. The transparency obligation in Article 50(1) is the default. The editorial responsibility exemption in Article 50(4) is available where — and only where — a natural person reviews the AI-generated content and bears editorial responsibility for it. A qualified solicitor reviewing an AI-generated draft before sending it to a client is precisely the scenario Article 50(4) was designed to accommodate.
The critical word is "documented". The exemption does not require a separate marking system, a separate disclosure statement embedded in every document, or a technology change. It requires that the review process is real, that the reviewer is qualified, and that evidence of both exists. PROC-AIMS-HITL-001 produces that evidence on every sign-off event.
The EU AI Act does not apply directly in UK domestic law. However, UK law firms serving EU-based clients, including panel clients, counterparties, or correspondent firms, may be within the Act's extraterritorial scope. Additionally, Article 50 compliance is increasingly appearing in supplier governance questionnaires sent by EU counterparties to UK firms. The practical position for most UK law firms with EU client relationships is that the Article 50 question will be asked — and the answer should already be documented.
Under ITIL 4, the Article 50 sign-off maps to two practices simultaneously. As a Service Validation and Testing event, it confirms that the AI output meets the quality standard required before entering service. As a Relationship Management event, it ensures that client-facing AI-assisted outputs meet the transparency and accountability standards the client relationship requires. The HITL sign-off form is the service record that evidences both practices simultaneously — which is why it is sufficient for Article 50(4) purposes without creating any new service event.
If the nine-gap ISO 42001 series has been deployed, the Firm already holds:
| Control | Document ID | Art. 50 Coverage | Status |
|---|---|---|---|
| Human Oversight Procedure | PROC-AIMS-HITL-001 | Generates the sign-off record that activates the Art. 50(4) exemption — but was not labelled as such | Existing |
| AI Transparency Disclosure | DOC-AIMS-DISC-001 | Fallback for outputs not subject to HITL review — satisfies Art. 50(1) where exemption does not apply | Existing |
| AI Literacy Register | REG-AIMS-LIT-001 | Confirms reviewers hold Art. 4 training — supports the competency element of "editorially responsible" person | Module 1 ✓ |
| Article 50 Compliance Statement | DOC-AIMS-ART50-001 | The explicit statutory link — names the obligation, asserts the exemption, identifies the evidence. This is what was missing. | This Module |
The gap was not a missing control. It was a missing label. PROC-AIMS-HITL-001 was already producing the Article 50(4) compliance evidence on every sign-off event. What did not exist was a document that said: this procedure is operative, this is the obligation it addresses, and this is the assertion we are making under Article 50(4). Without that document, a regulator asking for Article 50 evidence would receive a HITL sign-off form with no statutory context attached to it. That is a comprehensible answer to a different question, not a compliance record.
This module is a document artefact, not a new infrastructure build. The three steps below should take no more than one focused session to complete.
Replace the Halstead & Cole scenario values in DOC-AIMS-ART50-001 with the firm's actual name, SRA number, COLP name, and AI systems. Section 1.1 lists every AI system in scope — update this against REG-AIMS-SYS-001.
Before the COLP signs, verify that the HITL procedure is actually being followed — that sign-off forms are being completed for AI-generated outputs. The assertion in Section 3.2 is only accurate if the procedure is live. Check the sign-off register for the last 30 days.
The COLP signs the document in their capacity as the individual with statutory compliance responsibility. The signed document is filed in the AIMS document register (REG-AIMS-DOC-001) and its record_id is noted. Annual review date: 25 July 2027.
DOC-AIMS-ART50-001 asserts the editorial responsibility exemption in respect of AI outputs that go through PROC-AIMS-HITL-001. It does not cover AI outputs that are generated and published automatically without a HITL gate — for example, automated n8n workflows that send AI-generated content directly to clients or publish it to a website. Those pipelines shall either be brought within PROC-AIMS-HITL-001 or have DOC-AIMS-DISC-001 embedded in their output before 2 December 2026. Section 4 of DOC-AIMS-ART50-001 documents this requirement.
The most important architectural insight in this module is one of labelling, not engineering. Every time a fee earner completes a PROC-AIMS-HITL-001 sign-off form, they are:
acting as the "natural person" with editorial responsibility described in Article 50(4); exercising the review and editorial control that activates the exemption; and generating a timestamped, database-backed record that a regulator could retrieve on request.
None of this requires a new workflow, a new database table, or a new frontend. The HITL sign-off log already exists. What was missing was a document at the firm level that explicitly said: this is what we are doing, this is why it satisfies Article 50(4), and this is the COLP's confirmation that the procedure is operative and being followed.
DOC-AIMS-ART50-001 is that document. It is six sections, a sign-off block, and a quality gate record. It takes one session to populate and sign. And from the moment the COLP signs it, the firm has a complete, auditable Article 50 compliance position — anchored to infrastructure that was already built.
| Module | Gap | Deadline | Status |
|---|---|---|---|
| EU Bridge 01 — AI Literacy Register | Art. 4 / REG-AIMS-LIT-001 | IN FORCE | Complete ✓ |
| EU Bridge 02 — Article 50 Statement | Art. 50 / DOC-AIMS-ART50-001 | 2 Dec 2026 | This Module ✓ |
| EU Bridge 03 — Annex III Classification Register | Annex III / Classification Register | 2 Dec 2027 (standalone) / 2 Aug 2028 (embedded) | Planned |
| EU Bridge 04 — FRIA (if high-risk) | Art. 27 / FRIA-AIMS-001 | 2 Dec 2027 (standalone) / 2 Aug 2028 (embedded) | Planned |
| EU Bridge 05 — Incident Notification Procedure | Art. 26(5) / PROC-AIMS-EUINC-001 | Dec 2027 | Planned |
| EU Bridge 06 — GPAI Vendor Verification | Arts. 25 & 53 / GPAI Record | Dec 2027 | Planned |
The following gates were checked before publication. All 10 gates pass. This record satisfies ISO 9001:2015 Clause 7.5.3 (control of documented information) for the EU AI Act Bridge Series.
DOC-AIMS-ART50-001 is available to Governance Academy members as part of this module — a fully formatted Word document, pre-populated with the Halstead & Cole scenario, ready to adapt and sign before 2 December 2026. One module per month. All documents owned permanently. £97/month.
Join the Governance AcademyThis article is published for educational purposes only and does not constitute legal advice or advice on compliance with Regulation (EU) 2024/1689 (the EU AI Act), ISO/IEC 42001:2023, or any other standard or regulation. Halstead & Cole LLP, Priya Anand, Sophie Chen, Pemberton Capital LLP, and all associated names are fictional constructs used for illustrative purposes. Any resemblance to real persons, firms, or SRA numbers is coincidental. All templates and controlled document examples require adaptation and qualified legal and compliance review before use in a live legal practice environment. · Document ref: ART-AIMS-EU-002 v1.1 · Published 25 July 2026 · Next review: 25 October 2026 · Retention: 7 years · UNUS London Ltd. · unuslondon.com/legal/eu-ai-act-bridge-02-article-50-transparency-statement