Transparency is not a communication style. It is a set of specific obligations — with named recipients, required content, and enforceable deadlines. EAB tracks all of them.
From system-level transparency disclosures to user-facing information requirements, EAB turns transparency into a tracked obligation layer — not a policy statement.
Articles 13 and 50 specify who must be informed, about what, and under which conditions. EAB tracks each obligation separately — so compliance is measurable, not declared.
Article 13 requires high-risk AI systems to be transparent with deployers — providing instructions for use, information about capabilities and limitations, and human oversight guidance. EAB tracks each disclosure requirement as a separate governance action.
Article 50 requires that users be informed when they interact with AI systems in certain contexts — including chatbots and emotion recognition systems. The applicable obligations are determined by system characteristics, not manual selection.
Transparency obligations are determined from system characteristics and risk classification — not manually selected by the compliance team. Change the system, and the transparency obligation set updates accordingly.
Each transparency obligation has a named recipient — deployer, user, affected person, or authority. Knowing who must be informed is as important as knowing what must be disclosed. EAB tracks both.
Evidence that transparency disclosures have been made — instructions for use, user notifications, disclosure records — is uploaded and linked to the specific obligation. The record shows what was disclosed, to whom, and when.
Transparency obligations do not end at initial disclosure. As systems change, transparency documentation must be updated. EAB tracks transparency maintenance as an ongoing obligation — not a one-time completion event.
When a regulator asks for evidence that transparency obligations were met, the answer is in the governed record — not assembled from emails and document folders.
After AI Screening generates a risk classification, the applicable transparency obligations are determined automatically — based on system risk level, deployment context, and interaction type. No manual obligation mapping required.
Each obligation is completed with the required content — disclosure text, instructions for use, user notification format — and supporting evidence. Completeness is tracked per obligation, not as a single binary state.
Supervisor approval includes a review of transparency obligation completeness. Incomplete disclosures block approval. The approval record shows which transparency obligations were complete at sign-off.
System changes may require updated disclosures. EAB flags transparency obligations affected by system changes — so disclosures are maintained, not left as outdated documentation from the initial approval event.
Transparency is not a principle — it is a set of specific, enforceable obligations. EAB tracks each one: recipient, content, evidence, and completion status.
EU-hosted · Anchored to CELEX 32024R1689
Tell us about your organization and what you’re looking to address. We’ll follow up with the relevant information.
