A community program has willing volunteers and a directory of local services. The difficult part is deciding what each volunteer is authorized to do, whether the participant still wants that contact, and whether the listed service can actually help today. A matching screen alone answers none of those questions.
Illustrative proposed implementation for an adult practical-support program. This is not a delivered community deployment, a mental-health treatment service or a clinical referral engine. Qualified program staff must determine suitability and safeguarding action where relevant, especially for vulnerable participants.
Separate participant choices from volunteer permissions
Ask participants which practical categories are welcome, their preferred language/channel, contact windows and frequency, and how they want to stop or change the arrangement. Offer an accessible offline alternative. Opting into one errand category must not become permission for unrelated contact or unlimited access to a personal history.
Volunteer authorization is a different record. The program must define screening, permitted activities, supervision, expiry and revocation for each role. A participant's consent does not make a volunteer qualified for a task. A volunteer's willingness does not establish the participant's consent.
The NHS England workforce framework for social prescribing link workers describes a formal role with training, supervision, defined practice and support. The current page is version 2 and was updated on 3 November 2026. It is a reference for bounded responsibility within that English service model, not a statement that every community volunteer is a link worker or has the same competencies. Do not copy its caseload or professional requirements onto an unrelated program without discovery.
Use a referral record that exposes unanswered questions
The NHS Social Prescribing Information Standard entry describes collaborative records and separates referral, the link worker's record and a message back to the referrer. It is listed as active, reference DAPB4066 Amd 108/2021. That illustrates the value of defined information boundaries; it does not certify a new program or its software.
The following is an original synthetic contract sketch, not that standard's payload, an adaptation of its specification or a claim of conformance:
{
"participant_id": "PERSON-DEMO",
"consent_scope": ["library-collection"],
"permission_version": 6,
"permitted_contact_window": "agreed-local-window-reference",
"request_category": "library-collection",
"coordinator": "COORD-DEMO",
"volunteer_scope": "grant-reference-with-expiry",
"referral_destination": "verified-directory-entry-reference",
"directory_verified_at": "2026-11-05T09:00:00Z",
"outcome_status": "awaiting-volunteer-acceptance"
}
The program would also need request identity, revision and audit events. Keep the permitted contact window tied to a named local time zone and the participant's current preferences. A time-zone string alone is not a coverage promise. Do not put sensitive free-text histories into a general task feed.
If the buyer operates within a setting covered by the NHS standard, it must examine the actual specification, applicability and implementation requirements with qualified owners. Our sketch neither implements that standard nor replaces that work. The directory entry also lists scope exclusions, including information requirements of local services receiving onward referrals; those services need their own information agreement.
Walk through a practical request with three independent gates
Fictional, non-medical exercise. An adult participant chooses help collecting reserved library books. A coordinator confirms that the library collection arrangement is available and that the task fits the program. An eligible volunteer is offered only the task details they need; they accept before the participant receives a confirmation of assignment.
There are three separate gates:
| Gate | Checked by | Why it can stop the match |
|---|---|---|
| Participant preference | The program's current permission process | Category, recipient or contact window is no longer agreed |
| Service availability | Coordinator using a current directory/contact check | The activity or collection arrangement is unavailable or the entry is stale |
| Volunteer authorization | Program's role and assignment controls | The task is outside scope, authorization expired or workload capacity is unavailable |
Recheck all applicable gates immediately before sharing details or confirming an assignment. The volunteer then records the practical action taken, and the participant can confirm completion or ask the coordinator for help. Keep “volunteer reported done,” “participant confirmed” and “coordinator resolved” distinguishable. A delivery receipt is not completion.
Periodically ask whether the participant still wants the same categories, frequency and recipients. Expired preferences should lead to an appropriate paused/review state, not automatic re-enrollment. Decide the renewal process with program staff rather than treating silence as continued consent.
Keep the directory current without inventing availability
Store when an entry was checked, who checked it and when it needs review. Include practical eligibility and contact information only after verification through the program's process. A directory import date is not proof that a service is open or accepting people.
Automatic matching and coordinator review distribute responsibility differently. An automatic suggestion can still turn stale details or a broad category into an inappropriate referral. Coordinator review adds workload and may limit the volume the program can operate. Start with a manageable scope and a directory the team can maintain; do not hide capacity problems behind a recommendation score.
If a service is unavailable, report that truthfully and let qualified staff consider appropriate options with the participant. A community directory is not clinical referral advice. Do not generate treatment suggestions or present an unverified destination as a suitable care provider.
Make opting out as operationally important as opting in
A participant must have a usable route to withdraw or narrow contact, including where they cannot use text. Update pending assignments and recheck permission before any further disclosure. Revoking a volunteer's grant must likewise stop new access and assignment, including direct record requests, not just remove a dashboard button.
Explain limits around copies already shared. Revocation can prevent further system access but cannot reliably erase a handwritten note or an already downloaded file from another person's possession. Minimize the original disclosure, train participants in the program's handling rules and define retention and incident procedures with appropriate reviewers.
Repeated non-response belongs in a human-reviewed contact state. It is not automatically a crisis signal and must not become an AI-generated safety judgment. If there is an actual concern, qualified program staff follow the program's safeguarding procedures and appropriate local routes. For immediate danger, use local emergency help rather than waiting for a volunteer or app queue.
Build workload limits into assignments. Show whether a coordinator is covering the program and when a request remains unassigned. Volunteers need clear boundaries, a way to decline and someone to contact when a task exceeds their remit. A software notification cannot supply supervision or guarantee anyone's response.
What can be learned from Wrynkle
Wrynkle provides an opt-in conversational pattern, described in its walkthrough and messaging guide. Parents agree for themselves, can send STOP, and family responses can be acknowledged. Its privacy information separates private conversation from shared information according to role.
A community program would require a new participant/volunteer authorization model, expiry and renewal controls, a safeguarding owner, directory verification, workload limits, accessible opt-out and an offline route. It also needs data minimization, retention rules and jurisdiction-specific privacy/security and service review. None of this establishes that the family product is deployed in a community service; the owned-product study separates the product from proposed adaptations.
Wrynkle is not end-to-end encrypted because servers and providers process content. Its terms exclude medical and emergency services, and AI can misunderstand. This proposed program does not provide continuous monitoring, diagnosis, medication changes, mental-health treatment, autonomous triage or emergency guarantees. No wellbeing effect is asserted.
Evaluate access, capacity and failed referrals
Use synthetic identities, task categories and a fake directory; block network and messaging during the first exercises. Agree expected states and pass/fail thresholds with program staff before a limited pilot.
- Expire or revoke a volunteer grant after a suggestion but before assignment. Test direct record access and disclosure suppression as well as the visible task list.
- Withdraw participant consent while a task waits. Verify that a queued notification cannot reuse an older permission version as authorization.
- Make the destination unavailable or change its contact details. Check directory review, truthful status and a coordinator-owned resolution, without inventing a substitute referral.
- Repeat a non-response and submit a request the volunteer cannot handle. Verify a human route and no automatic crisis classification or scope expansion.
- Include someone who cannot use text and a coordinator at their agreed workload limit. Check the offline process, unassigned queue and the program's ability to decline or pause new work honestly.
Report inappropriate disclosure attempts that succeed, expired grants used, stale destinations and coordinator workload. Keep those operational measures separate from loneliness, health or wellbeing outcomes, which need appropriate independent evaluation.
Explore custom web applications or discuss a community program's discovery scope. Use synthetic examples in an initial enquiry. For a provider-operated family access model, compare the distinct problem in the elder-care portal guide.
Sources and evidence limits
- NHS England link-worker workforce framework: formal role boundaries, training, supervision and support in England; not volunteer certification or proof of program capacity.
- NHS Social Prescribing Information Standard directory entry: collaborative records, defined record parts, applicability and exclusions; our synthetic sketch makes no conformance claim.
- Wrynkle walkthrough, messaging, privacy and terms: opt-in interaction and family-product limitations only.
Sources checked 5 November 2026. This is an original proposed design, not a delivered service, standard implementation, professional certification or outcome study.