Dashboards that keep people in the loop
Patterns for dashboards where people depend on a job and need to hear how it is going. Open code, installed with the shadcn CLI.
11 of 18 staff trained
- 11completed
- 4signed in, not trained
- 3not signed in yet
Who hears about it
One list. Each person can get an email as things happen, the overview, both, or neither.
Each finish0 / 5as staff complete
Digest2 / 5only when sent
mara@example.org
jules@example.org
No one is set to hear as staff finish, so those notices go to the admin team instead.
The story
A recommended order for a workflow screen: see it, decide who hears, act, confirm it worked, and record it. A path, not a standard; use the stages you need. Read the story.
- 1
See
What is happening?
Status strip - 2
Decide
What needs me, and who hears?
Recipient roster - 3
Act
Do it safely.
Save bar - 4
Confirm
Did it work, who knows?
Notify envelope - 5
Record
Can I prove who did what?
Audit timeline