Journey select components
Use a journey select component to display existing journeys as cards, allowing a signed-in person to find and open an appropriate one. It is useful for services with saved drafts, editable completed work, workflow items or shared journeys.
Decide which journeys belong in the list
Filter the cards to the states that are meaningful at that point in the service: open work, completed but editable work, workflow items, closed records or cancelled items. Keep the list purposeful; showing every possible state can make it difficult to find the next action.
flowchart TD
A[Open journey list] --> B[Filter journeys by permitted state]
B --> C[Show clear card title and key information]
C --> D[Open, share or manage the selected journey]Choose whether the list includes journeys owned by the person, shared with them, or both. This decision must match the service access model and the sensitivity of the card information.
Design clear cards
Use a short dynamic title that lets someone identify the journey. Add only a few key/value rows—such as reference, status, last updated date or subject—to distinguish similar cards.
Avoid displaying sensitive personal information in card titles or values. Test Liquid-based titles and values with missing data, long values and multiple journeys with similar information.
Keep card density low enough to scan comfortably. One or two cards per row is usually easier to read than a dense grid; test the responsive layout on narrow displays.
Share and reveal actions
The component can allow sharing where the service authorises it. Enable sharing only when the ownership and access implications are clear. If cards are initially hidden under a reveal link, make the link text describe what will appear.
Test the list with no journeys, one journey, many journeys, shared and unshared journeys, each selected status, and a person whose access changes while a journey is open.