One system, from registration to monitoring
Six screens from Aikraft, captured in the product. We take a CV screening model — a recruitment tool that ranks job applicants — and follow it through the path the EU AI Act sets out for a high-risk system.
01 Register the system
Every AI system enters the inventory once — what it is, what it does, and whether you are the provider or the deployer. That distinction decides which set of AI Act obligations applies to you.
02 Answer the questionnaire
Fifteen questions across five steps cover the Annex III high-risk categories, transparency duties and prohibited practices. The questions are about your system, not about the regulation.
03 Get the classification
The result carries its reasoning and the factor behind it, then turns the risk tier into a concrete obligation list — Annex IV documentation, conformity assessment, EU database registration, human oversight, post-market monitoring, logging and accuracy testing.
04 Run the impact assessment
The Fundamental Rights Impact Assessment opens as a versioned draft: six required sections, a rights register, sign-off tracking, and slots for the Article 27(3) notification record and the linked DPIA.
05 Monitor after launch
Post-market monitoring is continuous, not a one-off filing. Aikraft measures drift against a saved baseline and raises an alert into the activity log when it crosses the threshold you set.
Demo data Drift figures in this frame come from sample data seeded through the platform's developer tools to demonstrate the alert path. They are not representative of production drift magnitudes.
06 See the whole workspace
One overview: systems registered, how many are high-risk under Annex III, open monitoring and regulatory alerts, assessments still pending, and how much of the documentation is current.
Want the documentation step in detail? See how Annex IV technical documentation is generated →
Every frame is a screenshot of Aikraft. The workspace, the classification result and the monitoring alert were produced by running the flow shown here; sample values used to trigger the drift alert are marked where they appear.