Public sample report

Example EU AI Act compliance output

This page shows the depth and structure of a realistic first-pass report. It is anonymized and shared publicly so teams can evaluate output quality before purchasing.

Overall risk

Medium-High

Findings

6

Estimated effort

2-4 weeks

Key Findings

Human oversight accountability is not explicitly assigned

High

EU AI Act Article 14

Gap: No clear owner is named for override, escalation, and decision review in high-impact scenarios.

Recommended action: Assign accountable roles, define escalation thresholds, and document override workflows.

Risk management lifecycle lacks traceability mapping

High

EU AI Act Article 9 / Annex IV

Gap: Hazards and mitigations are listed, but not linked to controls, owners, and review cadence.

Recommended action: Introduce a risk register with control IDs, owner mapping, and quarterly review checkpoints.

Post-market monitoring process is partially defined

Medium

EU AI Act Article 72

Gap: Monitoring exists for runtime metrics but not for compliance regressions after model updates.

Recommended action: Add compliance drift checks to release pipelines and document incident response timelines.

Data governance policy does not define retention by dataset class

Medium

EU AI Act Article 10 / GDPR Article 5

Gap: The policy describes lawful basis but not retention windows for training and inference artifacts.

Recommended action: Define retention schedules by data category and add deletion controls with audit logs.

User transparency notices are incomplete for AI-assisted outputs

Medium

EU AI Act Article 50

Gap: Public UI copy does not consistently indicate AI-generated outputs and user-facing limitations.

Recommended action: Standardize AI disclosure notices in product surfaces and add confidence/limitation messaging.

Technical documentation sections are present but fragmented

Low

EU AI Act Annex IV

Gap: Architecture docs are available across repositories but not bundled into one audit-ready package.

Recommended action: Publish a single compliance dossier with versioned references to design and control documents.

Pro Monitoring demo

See what changed since the previous scan

Pro Monitoring compares each snapshot with the previous scan so teams can spot new risks and resolved gaps immediately.

Measured GDPR score

71/100

+13 points

Week 1Week 4

Changes since the previous scan

1

New

0

Worsened

2

Resolved

When findings are new or become more severe, the weekly summary is sent as a compliance alert.

What teams usually do next

  • Map each finding to an engineering owner and a legal reviewer.
  • Prioritize High severity items before release milestones.
  • Re-run scans after remediation to verify closure.