Documents & Reports

Report Generation

Generate professional, audit-ready PDF reports with one click. Reports are automatically populated with your company data, AI system details, assessment results, and compliance scores. Your company logo and branding are included.

Why users come here

Export evidence quickly

Generate a shareable document when a customer, auditor, or internal stakeholder needs proof of your current posture.

Reduce manual drafting

Reports reuse data already captured elsewhere in ActLoom, so teams spend less time reformatting assessments into presentation-ready output.

Keep outputs consistent

Using standard templates means every report follows the same structure, references the same system record, and is easier to compare over time.

Document Generation Flow

Select Type

Choose from assessment report, risk management, technical doc, or transparency notice.

Select System

Pick the AI system the report covers.

Generate

AI engine compiles data and generates PDF (30–60 seconds).

Download

Download PDF or access from your document vault anytime.

Generate Document

Document type

Assessment Report

AI System

Recruitment AI

Include company branding

Generate Report

Estimated generation time: 30–60 seconds

Fig 17. Report generation — select type, choose system, and generate in one click.

Operational aspect	What to know in ActLoom
Prerequisites	A company profile must exist and the target AI system should already be registered. Richer reports also depend on completed assessments, evidence, incidents, dossiers, or monitoring records.
Main inputs	Company metadata, AI system record, assessment statuses, evidence links, monitoring data, incident records, governance records, and branding assets.
Main outputs	PDF reports, scheduled exports, locked reports, downloadable files, and controlled shared-report links.
Who typically uses it	Compliance leads, founders, legal, customer-facing teams, auditors, and procurement reviewers.
Plan access	Starter covers core reporting. Business and Pro unlock the heavier documentation workflows such as technical documentation, FRIA-linked reporting, and conformity-oriented exports.
Relevant routes	/api/reports/generate, /api/reports/schedule, /api/reports/[id]/download, /api/reports/[id]/share, /api/reports/[id]/lock, /api/v1/reports, /api/v1/reports/generate

Document Types

ActLoom generates four categories of compliance documents, each aligned to specific AI Act requirements:

📊

Assessment Report

20–30 pages · Art. 9, 10, 11, 13, 14, 15

Comprehensive compliance assessment including executive summary, system classification, scores, gap analysis, and recommended roadmap. 20–30 pages.

⚠️

Risk Management Documentation

10–15 pages · Art. 9

Pre-filled risk management templates with identified risks, mitigation measures, residual risk assessments, and review calendars.

⚙️

Technical Documentation

15–25 pages · Art. 11, Annex IV

Structured technical description covering system architecture, data sources, performance metrics, and testing procedures.

👁️

Transparency Notice

2–5 pages · Art. 50, Art. 13

User-facing notice informing individuals they are interacting with AI, including decision logic summary and human escalation contact.

ActLoom

Confidential

AI Act Compliance
Assessment Report

Recruitment AI · TechCorp Solutions

Generated Feb 28, 2026 · v1

Executive Summary

Risk Level

HIGH

Score

45%

Gaps

Key Findings

Met

3/7

Partial

2/7

Not Met

2/7

Pages

Page 1 of 24 · Generated by ActLoom

Fig 18. Sample assessment report — professional layout with company branding, executive summary, and detailed findings.

Document family	Typical trigger	Primary audience
Assessment and executive reports	Need to communicate current posture or progress	Leadership, procurement, auditors, customers
Risk and technical documentation	Need to evidence provider-side controls and system design	Legal, quality, notified bodies, regulators
Incident and post-market reports	Need to evidence monitoring, harm handling, or reporting discipline	Regulators, compliance, operations
Trust and public-facing reports	Need sanitized external communication	Prospects, partners, public trust readers

Choose the lightest document that answers the question

Not every stakeholder needs a full technical dossier. Customer due diligence usually needs a concise assessment or transparency notice, while internal readiness work often needs the deeper technical and risk-management exports.

Document Vault

All generated documents are securely stored in your encrypted document vault. Features include:

Version history — Track all versions (v1, v2, etc.) when reports are regenerated
Encrypted storage — All files stored with AES-256 encryption at rest on Vercel Blob
Instant download — One-click PDF download for any document version
Audit trail — Full log of who generated, viewed, or downloaded each document

Document Vault

Search documents…

📊

Assessment Report — Recruitment AI

PDF·v2·Feb 28, 2026·2.4 MB

Download

⚠️

Risk Management — Recruitment AI

PDF·v1·Feb 27, 2026·1.8 MB

Download

⚙️

Technical Documentation — Fraud Detection

PDF·v1·Feb 25, 2026·3.1 MB

Download

👁️

Transparency Notice — Support Chatbot

PDF·v3·Feb 24, 2026·0.5 MB

Download

📊

Assessment Report — Fraud Detection

PDF·v1·Feb 22, 2026·2.8 MB

Download

Fig 19. Document vault — searchable library of all generated compliance documents with version tracking.

Vault capability	What it gives the team operationally
Retention and history	A time-sequenced record of generated artifacts rather than one mutable latest file.
Locking and integrity	The ability to preserve a report state for audit or board review without silent edits afterward.
Controlled distribution	A way to share the right output externally without granting dashboard access.
Traceability	A link between reports and the underlying AI systems, assessments, incidents, or governance records they summarize.

When to regenerate a document

After a material change to the system purpose, model version, or deployment context.
After completing a new assessment or closing a major remediation item that changes the score.
Before sending evidence to a prospect, regulator, or certification body so the export reflects the latest state.
After updating key company metadata such as legal name, logo, or published compliance contact.

Related Sections

Artifacts

Best next stop if you want the deliverable-by-deliverable map across reports, dossiers, incidents, trust assets, and certificates.

Trust Center

Go here when document outputs need to become curated external proof rather than internal-only files.

Conformity

Read this when documents must support high-risk provider obligations, declaration readiness, or registration work.

Feature Index

Use this to trace each generated output back to the feature or workflow that owns it.

Ready to get started?

Join hundreds of companies using ActLoom to simplify AI Act compliance. Start your free assessment today — no credit card required.

Start Free Assessment View Pricing

Questions? Contact us at support@actloom.com

Operational aspect

What to know in ActLoom

Prerequisites

A company profile must exist and the target AI system should already be registered. Richer reports also depend on completed assessments, evidence, incidents, dossiers, or monitoring records.

Main inputs

Company metadata, AI system record, assessment statuses, evidence links, monitoring data, incident records, governance records, and branding assets.

Main outputs

PDF reports, scheduled exports, locked reports, downloadable files, and controlled shared-report links.

Who typically uses it

Compliance leads, founders, legal, customer-facing teams, auditors, and procurement reviewers.

Plan access

Starter covers core reporting. Business and Pro unlock the heavier documentation workflows such as technical documentation, FRIA-linked reporting, and conformity-oriented exports.

Relevant routes

/api/reports/generate, /api/reports/schedule, /api/reports/[id]/download, /api/reports/[id]/share, /api/reports/[id]/lock, /api/v1/reports, /api/v1/reports/generate

Document family

Typical trigger

Primary audience

Assessment and executive reports

Need to communicate current posture or progress

Leadership, procurement, auditors, customers

Risk and technical documentation

Need to evidence provider-side controls and system design

Legal, quality, notified bodies, regulators

Incident and post-market reports

Need to evidence monitoring, harm handling, or reporting discipline

Regulators, compliance, operations

Trust and public-facing reports

Need sanitized external communication

Prospects, partners, public trust readers

Vault capability

What it gives the team operationally

Retention and history

A time-sequenced record of generated artifacts rather than one mutable latest file.

Locking and integrity

The ability to preserve a report state for audit or board review without silent edits afterward.

Controlled distribution

A way to share the right output externally without granting dashboard access.

Traceability

A link between reports and the underlying AI systems, assessments, incidents, or governance records they summarize.