Read the client dashboard and analytics

What the client dashboard answers

The dashboard answers four questions in one screen: how much of the portfolio is published, what needs attention, which dated rules are coming, and what changed recently.

The readiness panel shows published passports against the total, and the four cards below count products tracked, draft passports, the average rule score and evidence documents - each card links to the page that owns that number.

How to read the numbers honestly

The average rule score is calculated only over passports that have a validation run, so a portfolio where nobody has validated yet shows a low validated count rather than a flattering score. The card states how many passports it covers.

Documents expiring counts within 30 days. If a metrics endpoint cannot be reached the page says so instead of drawing zeros, so an outage never looks like an empty portfolio.

A five-minute routine

1. Scan the next-actions list and work the top item.
2. Open DPPs, filter the drafts, and validate anything that has never been checked.
3. Open Documents and review anything expiring soon.
4. Check the regulatory dates panel for rules landing in the next quarter.
5. Use Analytics for the trend, not the daily decision.

Analytics

Analytics shows products by category, passports by status, anonymized category benchmarks and localization readiness.

Benchmarks are aggregates across workspaces with no tenant identifiers, so they are a sanity check rather than a target. Localization readiness is advisory: it tells you which markets expect content in which language, and never changes a compliance score.

The admin dashboard

Owners and admins get a second overview under Admin: organization profile, people and permissions, plan capacity, recent audit activity and shortcuts into the management pages. Editors and viewers do not see it.

What should my team work on next?

Open Action inbox from Overview or the dashboard. It combines pending evidence reviews, evidence expiring within 30 days, unanswered supplier requests, current-version publication reviews, draft or reviewed translations, current validation work and unhealthy evidence links. Editors and administrators can assign an active team member, choose a UTC calendar deadline, set priority and leave an internal note; viewers can read the queue.

Filter by type, assigned to me, unassigned or overdue. Open workflow takes you to the record that owns the issue. There is no dismissal button: saving an assignment never certifies evidence or resolves a finding. Items disappear when their source state no longer needs that action. The overview reads up to 1,000 records per source and explicitly warns when it is limited.

Screen-by-screen reference

These pages were checked in the organization console on 8 October 2026 using an isolated sample organization. Controls can differ by role, plan, record state and configured providers. Each page below explains its purpose, a practical workflow, the visible controls and what to verify afterward.

Client dashboard (/dashboard)

The readiness banner compares published passports with the portfolio total. The four cards open their source lists; next actions, regulatory dates and latest passports point to the records that need attention.

Use the readiness banner and four metric cards to decide where to investigate, then follow the linked list to the underlying records. The next-action area highlights unresolved work, and regulatory dates signal when a rule-pack review is due. A count or average is a navigation aid; verify the passport and evidence behind it before making a compliance decision.

Counts are live organization data. A missing metrics response is shown as unavailable rather than zero.

Controls and options

• Action inbox opens the live task queue; assigning a task does not resolve its source issue.
• Add product starts a catalogue identity; Create passport starts the versioned declaration for an existing product.
• Use the metric cards to inspect product count, draft count, average score over validated passports, and evidence count. The score is not a legal compliance verdict.
• Regulatory watch opens dated rule changes; the latest-passport rows open individual versions.

Action inbox (/action-inbox)

The queue combines validation, evidence, supplier, translation, publication and remediation work from their source records. Each row keeps its type, priority, owner and due date visible.

Start with overdue and unassigned work, then open the source record rather than treating the queue as a separate task database. An assignment captures who will follow up and when; the row remains until its underlying evidence, validation, supplier, translation, or publication state changes. Revisit the queue after completing that workflow to confirm it cleared.

The queue may explicitly warn when one of its source lists is limited.

Controls and options

• Type, ownership and Overdue only filters narrow the visible work; dates use UTC calendar days.
• Open workflow takes you to the record that produces the task.
• Assign / schedule lets an editor or administrator choose an active owner, date, priority and internal note; Save assignment records coordination only.
• Complete the underlying review, validation or correction in its own page to clear the task.

Analytics (/analytics)

Portfolio totals are broken down by category, status, scan activity, supplier coverage and localization. Benchmark rows are anonymous aggregates and only appear when eligible data exists.

Read a chart together with its population and generated date. A category mix or status count helps locate records to work on, while exports give a snapshot for offline analysis. When a score or benchmark looks unexpected, open the underlying product or passport set before interpreting it as a compliance outcome.

Do not treat a benchmark as a certification threshold.

Controls and options

• The export buttons download product, passport, regulator and CSRD CSVs, subject to role access.
• Products by category and passports by status show the mix behind headline totals; click supported counts to inspect records.
• Read localization coverage as a language workflow cue, not a change to a passport's rule score.
• Compare the generated date and number of validated passports before interpreting an average score.