How to use this result
Use the result as a first-pass triage. If the system affects rights, access, eligibility, safety, or public services, escalate to a qualified legal or compliance professional.
Free self-assessment
Start with a real product scenario, then adjust the answers. The tool turns everyday AI use cases into a practical EU AI Act triage report with risk signals, documentation steps, and source links.
The fixed questions are the legal risk signals. These scenario buttons translate common product ideas into those signals, prefill likely answers, and keep everything editable.
Use the result as a first-pass triage. If the system affects rights, access, eligibility, safety, or public services, escalate to a qualified legal or compliance professional.
No. It is a practical triage tool. Use it to find escalation signals and prepare better questions for a qualified adviser.
No. The current version runs in the browser and does not send questionnaire answers to a database.
Unclear EU scope, decision impact, or human oversight can change the classification. Unknown answers intentionally trigger review.
practical AI compliance self-assessment
EU AI Act Risk Classifier | Free AI Compliance Self-Assessment is maintained for founders, product managers, compliance owners, agencies, and small teams building AI workflows who need AI governance workflow. The goal is to help visitors complete a real task and leave with an AI inventory, risk note, disclosure draft, vendor question set, policy outline, or review workflow report, not only read a generic summary.
Start by naming the AI feature, users, decision impact, data categories, vendors, and the team member responsible for maintaining the review record.
Use the generated output as first-pass operational triage. Legal, medical, hiring, credit, education, biometric, and public-sector uses still need specialist review.
Save the output, assumptions, date, source links, and reviewer notes so the team can explain why a risk level, disclosure, or vendor question set was chosen.
Review record
A compliance tool is useful when it leaves a traceable record. The output should name the AI system, explain the assumptions, and show what the team still needs to verify with product, legal, security, or vendor owners.
Record the feature name, user group, decision impact, data sources, vendor dependencies, and the human owner. A generic "chatbot" label is rarely enough. A hiring assistant, support summarizer, medical triage bot, and product recommender can have very different risk profiles even if they all use language models.
Treat this page as first-pass triage. It can flag high-risk areas, transparency duties, missing evidence, and questions to ask a vendor. It should not be treated as legal approval, clinical advice, hiring approval, credit approval, or permission to launch without human review.
Save the generated result with the date, reviewer, source links, and unresolved questions. Update the record when the model, data, users, product flow, vendor, or region changes. This keeps the site useful for actual operators rather than only being a static explanation page.