Startup checklist

EU AI Act Checklist for Startups

Founders do not need to turn every AI feature into a legal project. They do need a reliable way to spot consequential use cases before launch.

Minimum viable compliance file

Early founder rule

If your AI changes what a person can access, buy, receive, qualify for, or appeal, treat it as a specialist-review use case.

Official sources

Last reviewed: 2026-07-03.

Start with the classifier

Implementation example

Example review record for EU AI Act Checklist for Startups

Use this example structure when saving a result from this guide into an internal AI compliance folder. The goal is to make the output specific enough that another teammate can understand the decision months later.

System summary

Name the AI feature, user group, deployment region, vendor, input data, output type, and business owner. A short summary prevents a guide result from becoming detached from the actual product behavior.

Risk and notice assumptions

List whether the system affects employment, education, credit, healthcare, biometric identification, public benefits, safety, or another high-impact area. If the page is used for transparency wording, record where the notice will appear and what users can do after seeing it.

Next review trigger

Set a clear trigger for review: model change, new vendor, new data category, new market, product launch, user complaint, policy update, or a change from internal-only use to customer-facing use.

Minimum record to keep

  • Date of review and reviewer name or role.
  • Generated output and any manual edits made before use.
  • Source links, unresolved questions, and the reason specialist review is or is not required.
  • Owner responsible for updating the record when the AI system changes.