The member journey

Your experience, connected.

From discovering the community to contributing your experience, see how the planned parts work together.

Pre-launch edition · 3 min read · Updated October 2026
The idea, in focus

A member journey can begin with a conversation, an ambition or a need for support. The shared core is designed to keep identity, permissions and relevant progress connected.

Inside the connected system

One request.
A whole community behind it.

Follow a planned support journey. See how a member, service teams and an agreed provider connect without losing responsibility.

01 / A private concern starts with a choice.

A member begins.

The member describes the issue, chooses a safe contact method and decides what to share. The planned intake separates an urgent concern from a routine request.

Responsible participant
Member
What connects the work
A private request
02 / The desk connects the need to expertise.

The right route becomes clear.

Triage checks scope and urgency. A reference links the request to a lead officer; connected needs can involve another team without losing the main owner.

Responsible participant
Service desk
What connects the work
An assigned pathway
03 / A wing turns the request into actions.

People coordinate the work.

The responsible officer records the next action, gathers only relevant information and coordinates linked tasks. A supervisor can review waiting or overdue work.

Responsible participant
Service wing
What connects the work
Actions and updates
04 / A referral travels with permission.

Specialist support joins the journey.

Where an appropriate arrangement exists, a professional or institution receives the agreed information. Its reference links to the original request, while its decisions remain its own.

Responsible participant
Agreed provider
What connects the work
A linked referral
05 / Closure needs a clear explanation.

The member sees what happened.

The outcome distinguishes support completed, partial progress, onward referral or another stated reason. The member can confirm what helped and ask about review.

Responsible participant
Member + officer
What connects the work
An explained outcome
06 / Useful patterns inform better service.

Experience improves the system.

Suitable aggregate findings help teams update a guide, improve training or change a process. Personal case details do not automatically become public reports.

Responsible participant
Review team
What connects the work
A service improvement
Planned workflow illustration · No live case dataExplore the operating system
On this page
01

Begin with a purpose

Explore what the community offers, who it serves and which capabilities are available. When onboarding opens, review eligibility, the privacy information and the relevant terms before creating an account.

02

Create an identity you control

Complete the appropriate checks, choose profile visibility and add useful skills or interests. A member profile, optional subscription, professional credential and community appointment remain distinct parts of the experience.

03

Build meaningful connections

Discover groups, follow relevant people, join a learning activity or explore a professional introduction. Your public participation should reflect what you choose to share.

04

Ask for help through a private pathway

A support request receives a reference and a responsible next contact. Tasks and referrals remain linked so that a cross-team journey does not require you to restart your explanation.

05

Contribute at a suitable level

Share knowledge, mentor, join a defined volunteer programme or apply for a published role. Preparation, availability and clear responsibilities help make a contribution useful.

06

Review, adjust and continue

Give feedback on an actual experience, manage communication preferences and update your goals. A continuing membership should support changing needs over time.

Find your way.

Search the community, services, wings and practical questions.

Esc to closeExplore all pages →