Start here

Build your first EU AI Act draft

For companies developing or materially modifying high-risk AI systems for the EU market.

Step 1 of 10

Package path and applicability

Choose the package path first. Then complete only the applicability checks that matter for that path.

1. Choose the package path

Pick the package you are preparing today. Provider and deployer are full high-risk packages. Article 50 is a standalone transparency package.

Which package are you preparing?

Law source: Scope and classification gate

Choose the package path that matches the work you want to complete now.

High-risk AI system — provider package High-risk AI system — deployer package Standalone Article 50 package

Which Annex III category applies, if any?

Law source: Annex III category

Choose the closest Annex III category. Use Other / not an Annex III category when the package is not being prepared under an Annex III category.

2. Additional applicability checks

These checks decide whether Article 22, Article 26, or Article 27 records must be included.

Is the provider established in the Union?

Law source: Article 22

Choose No only when the provider is outside the Union and the package must include representative details.

Yes — provider is established in the Union No — provider is outside the Union

Which stage best matches this package today?

Law source: Package stage gate

Choose the stage this package is for. The answer stays in the package summary so reviewers can see whether the package is for first placement, an already deployed system, or a substantial modification.

Before placing on the market or putting into service Already in service or already deployed Substantial modification of an existing system

Your draft

Progress on this EU AI Act package

A field counts as started once you add any draft text. You can export this draft before every field is complete.

Whole package0 / 67 started

Current section0 / 4 started

Section status

Package path and applicability: Not started (0 / 4 started)
Article 50 scope and optional module: Not started (0 / 1 started)
EU AI Act Annex IV technical documentation: Not started (0 / 11 started)
EU AI Act Article 9 risk management system: Not started (0 / 3 started)
EU AI Act Article 10 data and data governance: Not started (0 / 4 started)
EU AI Act Articles 12 and 14: Not started (0 / 4 started)
EU AI Act Articles 13, 15, 17 and 72: Not started (0 / 4 started)
EU AI Act Articles 16, 22, 43, 47, 48, 49 and Annex V: Not started (0 / 11 started)
Evidence register and final approval: Not started (0 / 25 started)

Need the legal text?

Template pages for this section

Open the template page to read the legal text and full structure for this section.

Package path and applicability

Navigating the AI Act FAQ
Scope and classification gate, Package stage gate
Regulation (EU) 2024/1689
Annex III category
AI Act Service Desk — Article 22
Article 22
AI Act Service Desk — Article 26
Article 26
AI Act Service Desk — Article 27
Article 27

FAQ

Frequently asked questions

What does Builder produce?

Builder produces the first exported legal input for the selected EU AI Act package path. It captures role, scope, Article 50 choices, article-level answers, evidence references, and package-readiness notes before the team moves to any client-facing starter, full package, or standalone Article 50 run.

Is Builder a legal compliance assessment?

No. Builder is a drafting and packaging aid. It does not decide conformity, replace legal interpretation, or approve the final package.

When should I use Builder before the starter?

Use Builder first every time you want a client-facing run. The exported Builder file is the route gate for starter, full-package, and standalone Article 50 commands.

Does Builder upload my system data?

The public Builder stores the draft in the browser session for convenience. The technical evidence workflow is expected to run in your own environment when you move beyond the public draft.

What should I do after finishing the Builder draft?

Review the draft, export `eu-package-input.json`, choose the next step page, then either run the client-facing route that matches the exported path or request help reaching the first real package for one system.