The platform uses a dual-layer status system: a database status field and a currentStep field. These combine to determine the pipeline stage, human-readable labels, and what action the adviser needs to take.
Journey Statuses
Status
Human Label
Short Label
Colour
pending
Hasn't opened the link yet
Link sent
Muted
in_progress
Working through the review
In progress
Primary
recommendations_sent
Watching your recommendations
Reviewing
Info
proceeded
Ready to apply
Protected
Success
parked
Thinking about it
Thinking
Warning
declined
Chose not to proceed
Not proceeding
Danger
follow_up
Follow-up scheduled
Check-in due
Warning
Journey Steps
Step
Description
risk_reality
Reviewing the report
risk_review
Answering the questionnaire
risk_snapshot
Viewing their risk snapshot
education
Exploring protection info
holding
Waiting for your recommendations
recommendations
Reviewing your recommendations
compliance
Pre-application compliance
decision
Making their decision
application
Application in progress
completed
Complete
Adviser Action Logic
The Focus Queue uses this logic to determine what Rob needs to do:
Condition
Action
Urgency
Step = holding, Status = in_progress
"Waiting for your recommendations — record your Loom video"
High
Status = pending, 7+ days since update
"Hasn't opened the link — send a reminder?"
Medium (High after 14 days)
Status = proceeded, 3+ days since update
"Ready to apply — track the application"
Medium
Client actively working through journey
No action needed
None
Recommendations sent, client reviewing
No action needed
None
Pipeline Stage Mapping
Pipeline Stage
Mapped From
Sent
status = pending
In Progress
status = in_progress AND step in (risk_reality, risk_review, risk_snapshot, education)
Ready to Advise
step in (holding, recommendations, compliance, decision, application, completed) OR status = recommendations_sent
