Understand the Dashboard
The first screen: five counts with denominators, your programmes with the next step in each, one action queue, what Aria found, five gated items of work this week, the dates split honestly, and the regulatory updates.
Dashboard (the first screen under Position) answers one question: where do we stand, and what is next? Read it top to bottom; every count is a link to the register that produced it. The header carries the date, a one-line position — programmes running, evidence expiring, statutory dates missed — and 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.
The stat strip
Five counts with their denominators — no percentage, no gauge:
- AI systems — registered, with the high-risk count beneath.
- Obligations evidenced — of the total that apply.
- Expiring ≤ 30 days — evidence about to lapse, with how many have already lapsed.
- Statutory late — the only figure that turns red, and only when a statutory date has passed on an open duty. A planned window or a date the law has not set is never red.
- Programme steps done — of the total, across every programme you have switched on.
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.
Programmes and the action queue
Side by side. Programmes is one row per programme — the EU AI Act journey first (the system furthest behind, its phase, its next obligation), then each standard you enabled with its phase and next step. Action queue is one table of what is due inside a fortnight: obligations and dated programme steps together, soonest first, with requirement, reference, scope, owner, status and date. Overdue reads red; everything else is a date. Full register → opens Obligations.
Aria found something
A band that appears when Aria has proposals waiting — drafted, not applied. Review them in Aria's Inbox; nothing changes until you accept. Hiding the band does not touch the proposals.
Work · this week
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 panel shows five in dependency order, 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.
Dates, honestly
A table that keeps three kinds of date apart — statutory (the law set it), planned (a person set it) and the engine's own suggested pace — and answers overdue? only for the first two. One disbelieved date discounts every other date the product shows, so this panel refuses to call a suggestion a deadline. See Dates and deadlines: the Obligations timeline.
Approvals
Obligations on high-risk systems that a non-approver marked complete wait here for an Org admin or Compliance manager. The card hides itself when the queue is empty.
Regulatory updates
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. Where the Frameworks screen is available, the same feed promotes into the change register under Frameworks → Changes.
The foot of the page
The disclaimer footer, then Workspace setup and product tour — Replay tour and Finish setup — and, until it is done, the floating Get started with Veritome checklist.
What is not here
No score, no countdown, no press feed, no activity tail. The Dashboard shows what to do; the registers show the detail.