Assessment Workflow
Once a system is classified, ActLoom generates a tailored list of compliance requirements based on its risk category. The assessment workflow walks you through each requirement one by one.
What you gain from the assessment
A prioritized compliance baseline
You see which obligations are already covered, which are partially implemented, and which are missing entirely.
Evidence-ready answers
The workflow encourages you to attach proof while you assess, so you do not need to reconstruct evidence later for audits or customers.
A realistic remediation path
Scores, gap analysis, and AI-assisted plans help you decide what to fix first instead of treating every control as equally urgent.
| Operational aspect | What to know in ActLoom |
|---|---|
| Prerequisites | An AI system must already be registered and classified. Better results come when ownership, deployment stage, and legal role are already correct on the system record. |
| Main inputs | Requirement statuses, evidence notes, uploaded files, links, comments, approvals, and any framework-specific detail fields. |
| Main outputs | Requirement-level assessment state, compliance score, gap analysis, remediation candidates, and historical score snapshots. |
| Who typically uses it | Compliance operators, legal reviewers, system owners, and executives who monitor score trends. |
| Plan access | Assessment and scoring are available across plans. AI remediation and heavier downstream documentation depend on higher tiers. |
| Relevant routes | /api/compliance/assessments, /api/compliance/gap-analysis, /api/compliance/remediation, /api/compliance/score-history, /api/v1/assessments, /api/v1/remediation/plans |
Compliance Assessment Flow
Start Assessment
Select an AI system and begin the guided assessment wizard.
Evaluate Requirements
Answer Met / Partially Met / Not Met for each obligation.
Add Evidence
Attach notes, links, or files as supporting evidence.
Review & Submit
Review summary, score calculated automatically, submit assessment.
High-Risk Requirements (7 Core Obligations)
| # | Obligation | AI Act Article | Description |
|---|---|---|---|
| 1 | Risk Management System | Art. 9 | Establish and maintain a risk management system throughout the AI system lifecycle |
| 2 | Data Governance | Art. 10 | Training, validation, and testing data must meet quality criteria |
| 3 | Technical Documentation | Art. 11 | Comprehensive technical documentation before market placement |
| 4 | Record Keeping | Art. 12 | Automatic logging of events during operation |
| 5 | Transparency | Art. 13 | Provide clear information to deployers about system capabilities and limitations |
| 6 | Human Oversight | Art. 14 | Design system to allow effective human oversight |
| 7 | Accuracy, Robustness, Cybersecurity | Art. 15 | Achieve appropriate levels of accuracy, robustness, and security |
Assess: Recruitment AI
3 of 7Requirement #3: Technical Documentation
Art. 11 — Comprehensive technical documentation must be prepared before the AI system is placed on the market.
Does your system have technical documentation?
Auto-saved 5 seconds ago
Best inputs before you start assessing
- Have the current system description and deployment context confirmed in AI Systems.
- Bring system-specific evidence, not only generic policies.
- Know which controls are truly in operation versus planned.
- Decide who can approve ambiguous or borderline answers before scoring starts drifting.