Understand the Dashboard
The first screen: your position under the EU AI Act, the GDPR beside it, the standards you run, what needs your attention, recorded progress, the dates split honestly, and the regulatory watch.
Dashboard — the first screen under Position, titled Overview on the page — answers one question: where does the organisation stand against the law it must follow, and against the standards it has chosen — and what is next? Read it top to bottom; every count is a link to the register that produced it. The header carries two actions: Export (the obligation matrix as CSV) and Register AI system.
A workspace with no systems yet shows one panel and one button — Register your first system — because that is the action that lights everything else up.
Your position under the EU AI Act
The spine, counted on its own — binding law, run per system. Four tiles:
- AI systems — registered, with the high-risk count beneath.
- Obligations done — EU AI Act obligations done, of the total that apply, with a bar. GDPR duties are never in this figure.
- Blocked at a gate — systems whose current stage is locked, and the gate they wait on.
- Next statutory date — the next date on which obligations that apply to your estate start to apply, with how many and the article.
Beneath them, Systems by stage shows the six stages — Classify · Scope & literacy · Build & document · Conformity assessment · Register · Operate & monitor — and how many systems sit at each. Open the register goes to AI systems.
If any system is classified Prohibited under Art. 5, a banner says so: the system must be withdrawn or reclassified before anything else here means much.
GDPR runs beside the Act
Binding law, counted apart from the Act: system duties done of total, across the systems that process personal data; organisation duties done of total — governance, the RoPA, retention, the breach and rights procedures — once the GDPR programme is switched on (until then the panel says so and points at Frameworks); and the state of your record of processing activities (Owed · Drafted · Approved · Issued). Open GDPR duties → opens Obligations filtered to GDPR.
Programmes
Shown only when you have switched a standard on: one line per standard — its tag, the next step, steps done of total, and a ↺ figure for the steps credited by EU AI Act work already done. When your plan includes a standard that is still off, a last line says so, with Add a standard. Open goes to Programmes. The EU AI Act is never a programme, and the GDPR — a programme you never switch on or off — has its own panel above, so neither appears here.
Needs your attention
Five items, sequenced and gated — not sixty-two. The engine generates dozens of duties per workspace, and a list of all of them sorted by date is not a plan. This card shows five in dependency order, numbered, and the first is a gate when one exists: while any duty has no owner, assign owners comes first and the rows beneath it render locked with no date, because a date on a duty nobody owns is fiction. Clear the gate and the same rows come back with their dates.
Recorded progress
EU AI Act obligations done of the total — the same figure as the tile above — with a bar. Evidence currency is a separate measure — how many files expire within 30 days and how many have already lapsed — and completion never certifies legal compliance. Explain the gaps asks Aria to explain what is still open; it drafts an answer and changes nothing.
Risk & assurance and Recent activity
Risk & assurance counts recorded risks, those still awaiting a residual assessment, open incidents and required assessments not yet complete; Open register ↗ goes to the Risk register. Recent activity lists the latest five audit-trail entries; View audit trail opens the full, hash-chained record. A role without audit-trail access sees a sentence saying so.
Needs attention
When Aria has prepared something — a policy draft, a supplier, a risk, a course assignment — the card opens with Prepared by Aria: the first three, each opening where it is reviewed, and a link to Aria's Today tab for the rest. Prepared means drafted, not applied: nothing changes or counts until you approve it.
Below it, one table of the gates, deadlines and reviews due inside a fortnight, from every source: obligations and dated programme steps together, soonest first, each with its source tag and reference, scope, owner, status and date. Overdue reads red; everything else is a date. Full register → opens Obligations.
The EU AI Act panel and Risk & assurance carry a small second figure, N prepared by Aria, apart from their counted figures, for the same reason.
Approvals
Obligations that someone without an approver role sent for review wait here for an Org admin or Compliance manager. The card hides itself when the queue is empty.
Regulatory watch
Two columns of two — the latest developments from the official sources (the Official Journal, the AI Office, the Data Protection Commission, the EDPB), each with an impact level. A sample item is labelled as one. Open the watch → goes to Regulatory watch, the change register where a development is assessed, planned and signed off.
The foot of the page
The disclaimer footer, then Workspace setup and product tour — Replay tour and Organisation details.
What is not here
No organisation score, no ring, no countdown, no press feed. The standards have their own panel rather than a tile, and the GDPR its own rather than a share of the Act's figures. The Dashboard shows what to do; the registers show the detail.