Feature · Duties · Written by Yobel Tzegai · Last checked 20 October 2026

What does the Complipath requirements checklist create, and what does it leave out?

In Complipath (complipath.io), confirming a classification creates the requirements that follow from it, each with a status, an owner you fill in and a place for evidence. High-risk rows depend on the system's role, which must be recorded. A later, stricter classification adds no new rows unless you change the system's type or role.

Check your AI systems, free

What it does today, and its limits

Confirming a classification creates the obligations that follow from it, each with a status, a place for evidence and an owner you fill in, and high-risk rows need the system's role recorded. A later, stricter classification adds no new duties unless you change the system's type or role.

Illustration · not your dataRequirement Human oversight · Candidate RankingStatus and owner In progress · Ingrid HolmEvidence Link to the escalation procedure · note added

What it does

Confirming a classification creates the checklist. Nothing is created from a result no person has confirmed.
For a high-risk system the rows follow the recorded type or role: nine provider rows for one you built, one Article 26 row for one you use, both for one built on a model you fine-tuned.
The nine provider rows are Articles 9, 10, 11 with Annex IV, 12, 13, 14, 15, 17 and 49.
Transparency rows follow the Article 50 paragraphs your answers raised, one row each and can sit beside the high-risk rows. There can be none.
Each row has a status (Not started, In progress, Complete or Blocked), an owner chosen from your team, an evidence link and a note.
Every requirement has its own page, with the date its provision applies from.
On a confirmed high-risk system, changing the type or role adds the rows the new role needs. A row it no longer needs is retired, not deleted: it keeps its status, owner, evidence and notes.

What it does not do

It does not add rows when a later classification is stricter. Rows are created only while a system has none, and a later confirmation adds none.
A high-risk system with no type or role recorded gets no high-risk rows. Nothing is guessed; recording the type later adds them.
A prohibited result, or a case awaiting legal review, creates no checklist. No compliance route applies to either.
Owners are never filled in for you: every row starts Unassigned.
It holds only the rows listed here. It is not a list of every provision of the Regulation that could apply to your system.
Adding a file or a link records evidence. It does not change a requirement's status; you set that.

Which plan

Every plan, including the free first system.

Where it sits in the law

It is not an EU AI Act duty. It is a work list. Each row keeps the Regulation's own heading for its provision, which exports use and the guidance beside it is Complipath's, not the Regulation's.
Rows for a provider of a high-risk system point at Articles 9 to 15, Article 17 (quality management system) and Article 49 (registration).
The row for a deployer points at Article 26, obligations of deployers of high-risk AI systems.
For transparency: Article 50, one row for each of paragraphs 1 to 4 that your answers raised.
The nine provider rows do not all share one start date. Article 113, as amended by Regulation (EU) 2026/1744 (the Digital Omnibus on AI), sets Chapter III Sections 1 to 3 apart from Section 5, where Article 49 sits. Each requirement shows its own date.

Starter

€499 a month

Prices exclude VAT.

Up to 20 AI systems
Evidence and the audit log
Your first system is free, with no end date

Check your AI systems, free

All plans

Questions

When does the checklist appear?

When a person confirms a classification, not before. A high-risk system gets the rows for its role: provider rows for a system you built, one Article 26 row for one you use, both for a fine-tuned model. Limited and minimal results get only the Article 50 rows their answers raised, which can be none.

Why did a stricter classification add no new requirements?

Rows are created only while a system has none, so a later confirmation adds nothing. Changing the system's type or role adds the high-risk rows the new role needs, if the latest confirmed class is high-risk. Recording an Article 6(3) claim adds two rows, for Article 6(4) and Article 49(2).

Does attaching evidence complete a requirement?

No. You set the status yourself: Not started, In progress, Complete or Blocked. Adding a file or a link records evidence and changes nothing else. On a system's to-do list, a requirement counts as finished only when it is marked Complete and has an evidence link.

Which plan includes it?

Every plan, the free one included: the app lists it for every plan. Free holds one AI system, with no end date. Starter is €499 a month for up to 20 AI systems. Prices exclude VAT. Growth and Scale are not available yet, and nothing here waits for them.