L1
Dashboard Pattern
Use L1 for orientation and prioritisation. It should help users understand where work is happening and route them into the right L2 list.
L1 anatomy
A dashboard should answer “where should I go?” rather than embed full operational workflows.
1
Workstream contextShow the current workstream, role, and scope before metrics.
2
Summary metricsUse only counts that change what a user does next.
3
Action alertsHighlight deadlines, blocked work, or records needing attention.
4
Routes into L2Cards and links should open lists, not duplicate list controls.
Dashboard rules
Use L1 for
- Workstream overview and role context
- Small metric groups with clear labels
- Alerts that route into a list or task
- Entry cards to Programmes, Projects, Requests, and Applications
Do not use L1 for
- Long tables or nested operational lists
- Full create, edit, or review forms
- Multiple competing primary actions
- Detailed audit history or row-level decisions
L1 routes into L2
When the user chooses a metric, alert, or work category, open the relevant L2 list with the right search, tab, or filter context already applied.
L1Dashboard3 requests need review
L2Project RequestsOpen tab + review-needed filterOpen L2 rules