Se2L
App manager
🗺️ Manage journeys

A journey is the full settlement path for one visa type in one UK region. Create it here first — a journey needs at least one phase before tasks can be assigned to it.

Days are counted from the newcomer's arrival date, e.g. 0–7 for "First week".

Existing journeys

Create a task

Add a new settlement task and assign it to a phase and visa type.

Hold Ctrl (Cmd on Mac) to select more than one. This task stays hidden from newcomers until every selected task is marked complete.

New tasks start as drafts. Use "Submit for review" and "Publish" in the list below to move a task through the workflow, or set it directly here.

If set, this task automatically switches to Published at this date and time — no need to come back and publish it manually. Only applies while the task is Draft or In review.

Existing tasks

↕️ Reorder tasks within a phase

This controls the order newcomers see tasks of the same urgency in a phase. Critical always shows before Important, and Important before Optional — reordering here only breaks ties within one urgency tier, so it can't bury a Critical task under Optional ones.

Analytics

A snapshot of how newcomers are actually progressing through your content.

Loading...

Active users by journey & phase

Where users currently sit, based on their arrival date and each phase's day range.

Loading...

Task completion rates by phase & visa type

Of users eligible for each phase's tasks (visa/region match, and they've reached that phase), the share who've completed them.

Loading...

Drop-off points

The phase with the biggest fall in completion rate compared to the phase before it — a likely place where people get stuck.

Loading...

Feedback ratings per task

From the 👍/👎 feedback users leave on each task's detail page.

Loading...

Email notification open/click-through rates

Not available yet — there's no open/click tracking wired up between the notification emails and this dashboard. That needs a webhook integration with your email provider (e.g. Resend's delivery-event webhooks) storing opens/clicks against each sent notification, which doesn't exist in the codebase yet. This section will populate automatically once that's built.