Membership
Eligibility, verification, account controls and service terms
To be confirmedPeople, process and technology need to be prepared together before a capability becomes available.
The three announced dates set the launch roadmap. Each service will need its own confirmed scope, trained team, usable channel and appropriate information handling.
These are planned release conditions. This table does not announce a service as active.
Eligibility, verification, account controls and service terms
To be confirmedGroup rules, privacy choices, reporting and moderation
To be confirmedTrained intake, a responsible owner, updates and review
To be confirmedNamed providers, current information and clear terms
To be confirmedVerified participation, defined offers and fulfilment routes
To be confirmedLanguage quality, permission boundaries and human handover
To be confirmedWritten scope, named contacts and suitable information sharing
To be confirmedDescribe the service, intended users, eligibility, boundaries and actual contact channel. State what a member can expect and which outcomes depend on another organisation.
Assign a responsible lead, train the delivery team and establish cover, supervision and handover. Publish participation information when the relevant roles are ready.
Check identity and access where relevant, intake, routing, updates, review and closure. Test the journey using realistic scenarios before inviting members to rely on it.
Provide service-specific information, limit access, define retention and establish incident and recovery processes. Partner or institutional participation needs agreed responsibilities before shared access opens.
An initial scope can be expanded after reviewing member experience and team capacity. A feature can remain limited or pause if its delivery conditions are not met.
Announcements should identify the actual features and channels available at that stage. Until confirmed, the descriptions on this website remain an introduction to the planned platform.