Compliance reports in EAB are derived directly from the governance record — not compiled from separate documents. The report reflects the actual state of compliance, not a summary someone prepared.
Per system, per organisation, at any reference date. For the board, for the regulator, for the auditor — the same record, different views.
A compliance report produced in EAB is not a document someone writes. It is a structured export of the governance record — every screening result, every obligation status, every evidence attachment, every supervisor decision. The report is a view of what was done, not a description of what was done.
Per-system reports cover the full governance history: registration context, technical profile, Art. 5 review, risk classification with legal version, actor role determination, obligation set with evidence status, and the complete decision trail including bypasses. The report can be generated at any reference date — reflecting the state of the record at that point, not the current state.
Organisation-wide reports give a cross-system view: total systems registered, risk distribution, screening coverage, obligation completion rates, and systems pending re-screening after a legal change. This is the view the board and the compliance function need — not a per-system deep dive, but a governance-posture summary that can be defended if challenged.
Every report is derived from the governance record — no data entry, no manual compilation.
Complete PDF of the governance record for a single AI system — from registration through screening, obligation management, and evidence collection. Every decision, every version, every identity. Structured to CELEX 32024R1689.
Cross-system view: total registered systems, risk distribution, screening coverage, obligation completion rate, evidence gaps, and systems in the re-screening queue. One report for the compliance function and the board.
Every report can be generated at a chosen reference date. The export reflects the state of the governance record at that point — not the current state. An auditor can verify compliance as it stood on the date of a specific event, review, or legal change.
Structured PDF anchored to CELEX 32024R1689 article references. Every obligation area stated. Every evidence item referenced. Every non-applicability documented. Formatted for submission to a supervisory authority, not internal communication.
Board-level view of AI governance posture: risk exposure, obligation completion, re-screening backlog, and unresolved gaps. Derived from live governance data — not a quarterly estimate someone prepared.
Auditors can generate their own exports from the read-only workspace. The export reflects the frozen state of the record, not the current state. No request to the compliance team required.
When reporting reflects what was actually done — not what was prepared for the report — it holds under scrutiny from any direction.
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.
