service-manual 1 linked patterns checked
NHS App Design System: Timeline
Documents timelines for broad process understanding, including what has happened so far, the current point, and what is coming next, while cautioning against using timelines for dense detail.
Read with a purpose
What this source can teach
Use this source to study a complete public-service task and the guidance that supports its implementation.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Timeline | Choose timeline when the main user question is what happened, when it happened, who or what caused it, and what came next. | Each event has one stable identity, timestamp or date label, event title, and actor or system source when known. | NHS App supports timeline use for broad process understanding and cautions against dense stage detail. |
Comparisons supported by this source
- Timeline vs feed vs process list vs step navigation
NHS App guidance supports broad process understanding and warns against using timelines for dense detail.
Evidence Role
This source is treated as service-manual evidence. Its value comes from the specific claims and setting described above.
Publisher: NHS App Design System. Last checked: .