The Progress tab
In the portal: Nothing. The page is assembled from what the participant holds.
What it is
Progress is the tab where a participant looks back at themselves. It has three sections, always in the same order, and it is assembled from what that person actually has rather than laid out in advance.
This page is assembled, not authored. It is built from what that participant has been given and what they have answered, so the decisions that shape it are made upstream in the content rather than on a dashboard.
What it looks like
Three sections, top to bottom.
| Order | Section | What is in it |
|---|---|---|
| 1 | Journeys | Every journey the participant holds, whatever state it is in. |
| 2 | Your responses | One row per sequence they have answered at least once. |
| 3 | Health | One row per kind of health data their phone has shared. |
Each section shows four items, then a See all link with the full count in it, such as "See all 11". Tapping a row opens a detail page for that one thing. Four is the cap and it is fixed, so the page stays the same length whatever a participant is carrying.
A section with nothing in it is not shown at all. There is no heading and no "nothing here yet" line. A participant on their first day sees a page with only the sections that have something in them.
When all three are empty the page shows one message.
Nothing to show yet Your journeys, responses and health data appear here.
When it matters
A worked example. A tenancy runs a twelve week programme with a weekly mood check-in and a one-off consent form at the start. Twelve weeks in, the participant opens Progress and sees their journey in the first section, their mood check-in in the second with the latest score on it, and their step count in the third. The consent form is not there, because it was marked untracked when it was authored, and a consent form is not something anybody wants to see trended. See Tracked and untracked for how that is decided.
What the three sections show
A row is labelled with the content's own name, and an unnamed journey or sequence shows its internal code instead. The app does not substitute a friendly noun when a name is missing, on purpose, so that the gap is visibly wrong rather than quietly plausible. Name every journey and every sequence, and check the names after any import, before you enrol anyone. See Tracked and untracked.
Journeys. Every journey the participant holds appears here, whether it is running, finished or cancelled. The row carries the journey name, its picture if it has one, and its state. The detail page adds the description and the dates, and offers up to two actions.
The row appears the moment somebody assigns the journey, rather than waiting for the participant to do anything, so assign a journey when you are ready for them to see it. A cancelled journey stays on the page as well: cancelling stops the activities and keeps the record.
| Action | When it appears |
|---|---|
| Start again | Only on a journey that has finished. |
| Cancel this journey | Only on a journey the participant enrolled themselves in, and only while it is still running. |
There is no percentage and no progress bar on a journey. A journey is a set of branches and loops rather than a straight line, so a percentage across one would be invented. The participant reads the state of each journey instead: running, finished or cancelled.
Your responses. One row per sequence the participant has submitted at least once. Only content that captures a value gets here: a sequence made entirely of reading material has nothing to record, so it never appears however it is marked. See Charts. Each row leads with one value, chosen in a fixed order: the score if the sequence is scored, otherwise the value from the only capture in it, otherwise the first captured value. Anything else it holds is summarised as "+2 more". A scored sequence with bands also shows its band beside the score.
Two rows read differently.
- A sequence with nothing that can be reduced to a single value shows Recorded.
- A sequence whose definition has been taken out of the catalog shows Unavailable and is dimmed. The answer itself is kept, so tidying the catalog never erases what somebody recorded.
Health. One row per kind of health data, showing the latest value with its unit and how recently it arrived. This section is populated by the phone's own health data, so it appears only where the participant has connected it.
How it behaves
It is read from the phone, not fetched. Opening Progress makes no network call. Everything on it was already on the device from the last sync. A participant with no signal still sees their whole history.
It refreshes on three triggers: opening the tab, coming back from a detail page, and a sync landing while they are sitting on it. Recording an answer and returning updates the number above the chart rather than leaving it stale.
The section names are fixed. Every participant reads "Journeys", "Your responses" and "Health", so use those three words when you write or talk about this tab.
Worked settings
Hide the tab entirely. Progress is one of the five tabs, and a tenancy can hide it. That is the right move for a programme with nothing worth trending, so the participant only gets the tabs their programme uses.
Show journeys only. Mark every sequence untracked and leave the journeys tracked. The participant gets a clean record of what they are on without a list of individual answers.
Show responses only. Mark the journeys untracked. Useful where the journeys are delivery machinery and the answers are the thing that matters to the participant.
Next
Three sections, in a fixed order, assembled from what that person actually holds. You shape this page by deciding what is tracked and by choosing the atom types that capture the values worth looking back at.
Tracked and untracked is the one setting that decides which journeys and which sequences appear here.
Charts is what opens when a participant taps a row.