Knowledge base / regulation10.com product guide (EU AI Act)
Finding your EU AI Act obligation status
To see where you stand, open the EU compliance report for a system, or the EU obligation-status view. It lists each obligation applicable to that system, shows whether the supporting module run and evidence are complete, and marks what is still outstanding. Owners and admins can see the same status rolled up across every system from the operator EU-status view, which turns a portfolio of records into one answerable page.
The view exists to answer the question every stakeholder eventually asks: are we compliant yet, and if not, what exactly is left? Without a live status view, the honest answer to that question is an afternoon of archaeology across documents and spreadsheets, and the answer is stale the day after it is assembled. The status view answers from the record itself, so it is as current as your last module run or document upload.
The unit of the view is the obligation, not the task. Each line is one requirement that applies to the system given its risk classification and the role you hold for it, and behind each line sit the module runs and documents that support it. Complete means the supporting work exists in the record. Outstanding means it does not yet. There is no third state and no partial credit, which keeps the view honest: an obligation backed by a half-finished run is not complete, and the view will not tell you otherwise.
Use it as a checklist, because that is what it is. Each open item links to the module or document that closes it, so the path from seeing a gap to fixing it is one click, not a search. A sensible working pattern is to open the view at the start of a compliance work session, pick the outstanding items you can close with the people available that day, and let the view update as the runs complete.
The cross-system operator view earns its place when you manage more than a handful of systems. It shows which systems are close to complete and which are barely started, which is the information you need to sequence work, brief leadership, or prepare for an external review. It is also the quickest way to spot a neglected system whose owner has moved on, a failure mode every inventory eventually meets.
Two habits make the view more valuable. Keep the underlying records honest, because the status is only as truthful as the runs and uploads behind it; marking work done elsewhere but not recording it here produces a status that understates you, and the reverse produces one that flatters you, which is worse. And check the view before any external conversation about your compliance position, because it is the same record an evidence export will draw on, and it is better to know your outstanding items before a reviewer does.
The status view does not judge whether an obligation is legally satisfied; it tracks whether your supporting work is present and complete in the record. The legal judgement remains yours and your advisers'. This is informational only and not legal advice: the platform's regulatory content is a scaffold pending qualified-professional review, so confirm any obligation with a qualified adviser before you rely on it.