Every ARIA app ships with a set of dashboards designed as narrative sequences — not widget dumps. Each widget in each dashboard earns its place by unlocking an insight the previous one raised. The matrix below is the architectural contract: 14 apps, 67 dashboard surfaces, one reading grammar.
KPI bar answers "what happened." Primary chart answers "where." Secondary breakdown answers "why." Drill-down structure answers "which one." Each widget unlocks the question the previous widget raised. This is the contract.
The KPI bar at the top is a contract: a reader should know whether things are good or bad before scrolling. No KPI bar, no dashboard.
KPI bar + primary + breakdown + drill-down. That's four. A fifth widget (usually a trend or a secondary chart) is allowed. A sixth means the dashboard should split into a main and a dependent.
Drill-throughs are free. Every main widget can link to a dependent dashboard that zooms in without cluttering the main. This is where ARIA's storytelling beats static reports.
Rows are apps. Columns are dashboard types. Cells contain the dashboard name and the ordered sequence of widgets that compose it. Widgets are numbered in their reading order. This matrix is the architectural contract: every app must declare its dashboard set before any code is generated.
| App | ● Main dashboardExecutive overview · homepage of the app | ● OperationalWorkflow boards · preparer daily home | ● DisclosureNote validation & export | ● DependentDrill-through deep dives | ● Context widgetsInside CRUD edit pages |
|---|---|---|---|---|---|
| IFRS 15 Revenue from Contracts with Customers SHIPPED |
Revenue Recognition Overview
|
Contract Lifecycle Board
|
Contract Balances & Notes
|
POB Performance Deep Dive
↑ from donut slice click
|
Event Timeline
→ inside contract edit page: signature → delivery → variation → invoice → payment
|
| IFRS 16 Leases SHIPPED |
Lease Portfolio Overview
|
Not applicable — leases have no active workflow board |
Lease Note Dashboard
|
Asset Class Deep Dive
↑ from donut slice click
Maturity Cohort Analysis
↑ from maturity ladder click
Discount Rate Sensitivity Lab
↑ linked from main (audit section)
|
Amortization Schedule
→ inside lease edit page: period-by-period interest/principal/balance
Event Timeline
→ inside lease edit page: modifications history
|
| IFRS 9 Expected Credit Losses SHIPPED |
Credit Risk Overview
|
Watchlist & Stage Migration
|
ECL Note Dashboard
|
PD/LGD Sensitivity Lab
↑ from ECL kpi click (model governance)
Stage 3 Deep Dive
↑ from donut Stage 3 slice click
|
Event Timeline
→ inside instrument edit page: stage migration history
|
| IFRS 2 Share-Based Payments SHIPPED |
Plan Portfolio Overview
|
Not applicable — no daily workflow |
IFRS 2 Note Dashboard
|
Valuation Sensitivity Lab
↑ from FV kpi click
|
Amortization Schedule
→ inside plan edit page: vesting period expense
Event Timeline
→ inside grant edit page: grant → vest → exercise
|
| IFRS 3 Business Combinations SHIPPED |
Deal Portfolio Overview
|
PPA Review Board
|
— goodwill disclosures live in IAS 36 |
PPA Component Deep Dive
↑ from waterfall bar click
|
Event Timeline
→ inside deal edit page: announce → close → PPA final
|
| IFRS 13 Fair Value Measurement SHIPPED |
Fair Value Overview
|
Not applicable — measurement is event-driven, not workflow-driven |
FV Note Dashboard
|
L3 Sensitivity Lab
↑ from L3 kpi click (governance)
|
No dedicated context widget |
| IFRS 18 Presentation (mandatory 2027) WAVE 2 |
New P&L Presentation Overview
|
Category Mapping Board
|
IFRS 18 Note Dashboard
|
MPM Reconciliation Deep Dive
↑ from MPM kpi click
|
No dedicated context widget |
| IAS 12 Income Taxes WAVE 2 |
Tax Position Overview
|
Not applicable — tax events are periodic, not daily |
Tax Note Dashboard
|
ETR Driver Analysis
↑ from ETR kpi click
|
Amortization Schedule
→ inside DTA edit page: reversal profile over periods
|
| IAS 37 Provisions & Contingencies WAVE 2 |
Provisions Portfolio Overview
|
Case Management Board
|
IAS 37 Note Dashboard
|
Uncertainty Sensitivity
↑ from provision kpi click
|
Event Timeline
→ inside case edit page: claim → assessment → ruling → payment
|
| IAS 36 Impairment of Assets WAVE 2 |
CGU Impairment Overview
|
Trigger Monitoring
|
Impairment Note Dashboard
|
CGU Sensitivity Lab
↑ from CGU click in tree (auditor view)
|
Amortization Schedule
→ inside CGU edit page: 5-year cash flow + terminal value
Event Timeline
→ inside CGU edit page: trigger → test → loss → reverse
|
| SOX / 262 Internal Controls Framework COMPLIANCE |
Control Framework Overview
|
Testing Workflow Board
|
Management Assessment
|
Control Exception Root Cause
↑ from exception column in kanban
|
Event Timeline
→ inside control edit page: design → test → remediate → re-test
|
| ESRS Sustainability Reporting COMPLIANCE |
Sustainability Overview
|
Datapoint Collection Board
|
ESRS Note Dashboard
|
Climate Risk Sensitivity
↑ from Scope kpi click
|
No dedicated context widget |
| M. 231 Italian Compliance Model COMPLIANCE |
231 Model Overview
|
Incident Management Board
|
OdV Annual Report
|
No dependent deep-dives planned in Wave 1 |
Event Timeline
→ inside incident edit page: detection → action → closure
|
| GDPR Privacy & Data Protection COMPLIANCE |
Privacy Overview
|
Data Subject Request Board
Breach Management Board
|
ROPA & Records
|
No dependent deep-dives planned in Wave 1 |
Event Timeline
→ inside breach edit page: detect → notify → remediate
|
Reading the matrix vertically reveals patterns that validate the blueprint as a real architectural contract, not just an inventory.
All 14 main dashboards use the same grammar: KPI bar → primary chart (waterfall or donut) → breakdown → hierarchical drill-down. Once a user learns one app, they know them all. This is how ARIA compounds its training investment.
Where there's a workflow, there's a kanban. The three apps without one (IFRS 16, IFRS 13, IAS 12) handle events that are periodic or snapshot-based — not continuous. The matrix makes this invariant explicit.
Every app except Modello 231 ships at least one dependent dashboard — a drill-through that zooms into a specific signal raised by the main. This is where ARIA beats static PDF reports: the story continues where the reader's curiosity takes them.
Every dashboard in this matrix is a YAML file waiting to be written. ARIA generates the React components. The design grammar — Z pattern, Main → Dependent, Context widgets — is enforced at the platform level. The killer feature isn't "we have dashboards." It's "every dashboard tells a story the same way."