Revision 7T · Full Tutorial Edition · Updated 1 September 2026
PWR-249 · SUPERVISED full tutorial
Design and review a community-owned mutual-aid pathway without recruiting, matching or replacing public services
This lesson teaches the full supervised mutual-aid method: establish community mandate, define the support, obtain voluntary consent, separate requester and volunteer roles, protect confidentiality and safeguarding, match need with real capacity, and make reciprocity optional. You will also track hidden labour, provide refusal and complaint routes, hand needs to professional or statutory services, and review who was excluded. Practice uses fictional cases only.
What you will produceWith a legitimate community facilitator, the learner completes a fictional mutual-aid pathway record showing mandate, consent, capacity, safeguarding, burden, handoff, withdrawal and outcome for one invented request.
Method9 numbered Power-specific steps
Practice authorityFull method with qualified supervision where stated
Full step-by-step individual tutorial · TLU-PWR-249
With a legitimate community facilitator, the learner completes a fictional mutual-aid pathway record showing mandate, consent, capacity, safeguarding, burden, handoff, withdrawal and outcome for one invented request.
Learn how a legitimate mutual-aid pathway is governed and review fictional cases.
Ask whether participation, reciprocity, confidentiality, burden and exit are genuinely voluntary.
Recommend professional, statutory or emergency handoff when need exceeds capacity.
Qualified help is required for
Recruiting volunteers, verifying need, matching real people, safeguarding, care allocation and confidential data handling.
Any provision of health, personal care, childcare, transport, money, housing or emergency support.
Representation of a real community or decisions about public-service obligations.
Never do this from the page alone
Create a live mutual-aid group, promise help or collect a vulnerable person’s information from this lesson.
Make help conditional on equal repayment, political loyalty, disclosure or public gratitude.
Use mutual aid as a reason to withdraw statutory, clinical or professional support.
2 · Get ready
Gather what you need and check the starting conditions
What you need
Qualified community facilitator and supplied fictional mandate: the neighbourhood desk may coordinate prepaid ordinary-grocery collection in daylight; medication, cash handling, personal care, home entry and emergency response are outside scope and must use the named professional or statutory service.
Supplied request R1: invented requester Rina asks for one prepaid 2 kg grocery bag collected at 15:00, permits sharing first name plus text contact only, and declines reciprocity or public thanks. Capacity V1 offers one hour between 14:30 and 16:30, daylight walking, up to 5 kg and no cash or medication; V2 offers 30 minutes ending at 14:45 and therefore cannot match R1.
Failure card M1 says the bag is absent at 15:20: volunteer returns responsibility to the service desk and never visits a home. Boundary card S1 adds a medication request: stop matching and use the supplied qualified-service handoff. Also provide consent, burden, private complaint, withdrawal, outcome and exclusion sheets.
Before you start
Confirm every person, need, address and organisation is fictional; no recruitment or contact occurs.
Identify the community body that would own a real process and the facilitator’s scope.
Agree emergency/professional thresholds, privacy limits and how an actual concern ends the exercise.
3 · The method
Follow these steps in order
Establish community mandate
Write which legitimate group owns the process, purpose, area, duration and what it cannot provide.
Why: Goodwill does not create authority or capacity.
Check: The fictional mandate and exclusions are visible.
Define support and eligibility
Describe the exact ordinary support, who may request, priority approach and alternatives without ranking worth.
Why: Vague promises invite unmet expectations and hidden allocation.
Check: The request can be assessed against clear non-clinical limits.
Obtain voluntary participation
Separate consent to request, volunteer, share contact details, receive follow-up and offer reciprocity; allow refusal and withdrawal.
Why: Joining one mutual-aid task is not consent to publicity, reuse or repayment.
Check: Every role can say no without penalty or loss of unrelated help.
Screen safeguarding and privacy
Use minimum necessary information, role checks, safe contact rules, incident route and no-go activities.
Why: Informal support can still create vulnerability.
Check: The facilitator can identify when the case must stop or route out.
Match need to declared capacity
Compare task, time, location, access, skills, limits and backup; never assign outside the volunteer’s stated capacity.
Why: A nominal match can transfer risk to both people.
Check: Every matched field is compatible or explicitly supported.
Plan the handoff and confirmation
State who contacts whom through the approved channel, how completion or failure is confirmed and who responds to a missed task.
Why: Help is not delivered until the loop closes.
Check: The case sheet names requester, volunteer, coordinator and fallback service.
Track reciprocity and hidden labour
Record coordination, emotional, transport and follow-up work; reciprocity is optional and locally defined.
Why: Visible service hours can hide unequal burden.
Check: No participant owes repayment and coordinators’ work is counted.
Provide complaint, withdrawal and transfer
Give private accessible routes to stop, change helper, complain or move to statutory/professional support.
Why: Community care needs usable exit and remedy.
Check: The fictional requester and volunteer can both leave safely.
Review coverage and exclusion
Assess unmet need, latency, dignity, burden, continuity, no-shows and who could not access the process.
Why: Stories and volunteer hours cannot show equitable impact.
Check: The review identifies at least one excluded or unmeasured group.
4 · Worked example
See the whole method used once
Scenario
A fictional neighbourhood desk receives an invented request for one grocery pickup; a volunteer card offers one hour, daylight travel and no cash handling.
Walkthrough
The facilitator confirms the desk’s fictional mandate covers ordinary pickup but not medication, money or personal care.
The requester card consents to share first name and contact route only; reciprocity and public thanks are declined without effect.
The match fits time and transport, uses prepaid collection and includes a missed-pickup fallback to the service desk.
A burden review shows the coordinator spent more time than the volunteer; the pathway adds a coordinator capacity limit and an accessible complaint route.
Result
The fictional request completes within declared roles and reveals hidden coordination burden. No real matching, service promise or community-effect claim is made.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
Right and wrong comparison
Moment
Right / safer
Wrong / riskier
Why it matters
Inviting participation
Offer separate consent and easy withdrawal.
Treat joining once as consent to all future roles.
Joining one support task does not authorise publicity or continuing obligations.
Matching decision point
Check task, capacity, access and fallback.
Assign whoever is available because need is urgent.
Poor fit can endanger requester and volunteer.
Reciprocity decision point
Allow optional locally defined contribution or none.
Require equal repayment or gratitude despite different capacity and stated terms.
Mandatory reciprocity excludes people with less capacity.
Judging success
Track unmet need, dignity, burden and exclusion.
Report volunteer hours and positive stories only.
Activity can hide unfair coverage and burnout.
6 · Common mistakes
Spot the error and apply the correction
Common mistakes and corrections
Mistake
Fix
Goodwill is mistaken for a community mandate.
Identify the accountable community owner and exclusions.
A volunteer continues after need exceeds ordinary support.
Use statutory, clinical, safeguarding or emergency handoff rather than stretching volunteer roles.
Matching, follow-up and complaint labour remain invisible.
Record matching, follow-up, emotional and complaint work.
Support, data, publicity and reciprocity consent are bundled.
Separate request, data, follow-up, reciprocity and publicity choices.
A missed mutual-aid handoff has no owner.
Add confirmation time and a service-desk fallback.
The only complaint route exposes the requester publicly.
Provide a private independent channel and protection from loss of unrelated support.
7 · Practice
Turn the steps into a usable skill
First session
Review the fictional mandate, support limits and outward routes.
Process one invented request through separate consent and privacy screen.
Match it to a capacity card and write the closed-loop handoff.
Apply a missed-pickup or safeguarding card and use the correct fallback.
Review burden, unmet need and exclusion with the facilitator.
Repeat plan
The legitimate community provider sets training and review cadence. Repeat only with new fictional cases that test capacity, withdrawal or exclusion; never progress to live recruitment or matching from this lesson.
Progress when
Every fictional request stays within mandate and declared volunteer capacity.
Consent, privacy, confirmation, complaint and withdrawal routes work without coercion.
The review counts unmet need and hidden labour, not only completed tasks.
Do not progress when
A real request, person, address, vulnerability or service promise enters the exercise.
Safeguarding, confidentiality, emergency or statutory boundaries cannot be confirmed.
Participation, reciprocity or publicity becomes pressured.
8 · Check the result
Measure what changed
Governance and closure of one fictional mutual-aid request
Good result: A good result resolves every field and routes the request to completion or appropriate outward support without coercion or capacity breach.
This does not prove: It does not prove equitable impact, sustainability, community representation or adequacy as a substitute for public services.
Self-check
Which community body owns the process and what can it not provide?
What separate choices can requester and volunteer decline?
Who acts if the task is missed or need escalates?
Whose labour or unmet need is invisible in the headline activity count?
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
Stop if confidentiality, volunteer safety, consent or the accountable community owner is missing.
Seek emergency, clinical, statutory or professional help when a need exceeds ordinary voluntary support.
Accessibility and adaptations
Offer request, consent, matching, complaint and withdrawal in accessible formats and needed languages.
Include mobility, communication, sensory, cognitive, cultural and timing access in the capacity match.
Permit support people and no-reciprocity participation; do not make digital access or public disclosure mandatory.
10 · Evidence and limits
Why these instructions are here
primary research
Qualitative research documents collective-care and reciprocity meanings in mutual aid but does not establish equitable outcomes or sustainability.
Longitudinal mutual-aid participation research identifies group-related predictors while attrition and observational design limit causal and unmet-need claims.
No real group, request, volunteer or allocation is created.
Mutual aid complements rather than replaces emergency, clinical, safeguarding or public duties.
Activity and stories do not prove equitable coverage or sustainable burden.
Stories or volunteer hours cannot prove equitable, sustainable impact.
One study documents meanings and practice rather than outcomes; the other is a short observational volunteer panel with 49.8% wave-two retention and does not establish unmet-need coverage, fair burden or causal effectiveness.
Rotem Perach; Maria Fernandes-Jesus; Daniel Miranda; Guanlan Mao; Evangelos Ntontis; Chris Cocking; Michael McTague; Joanna Semlyen; John Drury · 2023 · Primary research
Progress is saved only in this browser on this device.
Step-by-step learner mode
Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.
01
Establish community mandate
Write which legitimate group owns the process, purpose, area, duration and what it cannot provide.
Why this step exists
Goodwill does not create authority or capacity.
Success check
The fictional mandate and exclusions are visible.
I’m stuck on this step
Reset: Re-read this authored instruction — “Write which legitimate group owns the process, purpose, area, duration and what it cannot provide.” — and its success check, then attempt only this step.
Possible snag: Goodwill is mistaken for a community mandate.
Correction: Identify the accountable community owner and exclusions.
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
02
Define support and eligibility
Describe the exact ordinary support, who may request, priority approach and alternatives without ranking worth.
Why this step exists
Vague promises invite unmet expectations and hidden allocation.
Success check
The request can be assessed against clear non-clinical limits.
I’m stuck on this step
Reset: Re-read this authored instruction — “Describe the exact ordinary support, who may request, priority approach and alternatives without ranking worth.” — and its success check, then attempt only this step.
Possible snag: A volunteer continues after need exceeds ordinary support.
Correction: Use statutory, clinical, safeguarding or emergency handoff rather than stretching volunteer roles.
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
03
Obtain voluntary participation
Separate consent to request, volunteer, share contact details, receive follow-up and offer reciprocity; allow refusal and withdrawal.
Why this step exists
Joining one mutual-aid task is not consent to publicity, reuse or repayment.
Success check
Every role can say no without penalty or loss of unrelated help.
I’m stuck on this step
Reset: Re-read this authored instruction — “Separate consent to request, volunteer, share contact details, receive follow-up and offer reciprocity; allow refusal and withdrawal.” — and its success check, then attempt only this step.
Possible snag: Support, data, publicity and reciprocity consent are bundled.
Correction: Separate request, data, follow-up, reciprocity and publicity choices.
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
04
Screen safeguarding and privacy
Use minimum necessary information, role checks, safe contact rules, incident route and no-go activities.
Why this step exists
Informal support can still create vulnerability.
Success check
The facilitator can identify when the case must stop or route out.
I’m stuck on this step
Reset: Re-read this authored instruction — “Use minimum necessary information, role checks, safe contact rules, incident route and no-go activities.” — and its success check, then attempt only this step.
Possible snag: The result from “Use minimum necessary information, role checks, safe contact rules, incident route and no-go activities.” does not yet meet this declared check: The facilitator can identify when the case must stop or route out.
Correction: Return to the start of “Screen safeguarding and privacy”, reduce complexity or pace, and repeat only the part needed to satisfy: “The facilitator can identify when the case must stop or route out.”
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
05
Match need to declared capacity
Compare task, time, location, access, skills, limits and backup; never assign outside the volunteer’s stated capacity.
Why this step exists
A nominal match can transfer risk to both people.
Success check
Every matched field is compatible or explicitly supported.
I’m stuck on this step
Reset: Re-read this authored instruction — “Compare task, time, location, access, skills, limits and backup; never assign outside the volunteer’s stated capacity.” — and its success check, then attempt only this step.
Possible snag: The result from “Compare task, time, location, access, skills, limits and backup; never assign outside the volunteer’s stated capacity.” does not yet meet this declared check: Every matched field is compatible or explicitly supported.
Correction: Return to the start of “Match need to declared capacity”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every matched field is compatible or explicitly supported.”
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
06
Plan the handoff and confirmation
State who contacts whom through the approved channel, how completion or failure is confirmed and who responds to a missed task.
Why this step exists
Help is not delivered until the loop closes.
Success check
The case sheet names requester, volunteer, coordinator and fallback service.
I’m stuck on this step
Reset: Re-read this authored instruction — “State who contacts whom through the approved channel, how completion or failure is confirmed and who responds to a missed task.” — and its success check, then attempt only this step.
Possible snag: A missed mutual-aid handoff has no owner.
Correction: Add confirmation time and a service-desk fallback.
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
07
Track reciprocity and hidden labour
Record coordination, emotional, transport and follow-up work; reciprocity is optional and locally defined.
Why this step exists
Visible service hours can hide unequal burden.
Success check
No participant owes repayment and coordinators’ work is counted.
I’m stuck on this step
Reset: Re-read this authored instruction — “Record coordination, emotional, transport and follow-up work; reciprocity is optional and locally defined.” — and its success check, then attempt only this step.
Possible snag: Matching, follow-up and complaint labour remain invisible.
Correction: Record matching, follow-up, emotional and complaint work.
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
08
Provide complaint, withdrawal and transfer
Give private accessible routes to stop, change helper, complain or move to statutory/professional support.
Why this step exists
Community care needs usable exit and remedy.
Success check
The fictional requester and volunteer can both leave safely.
I’m stuck on this step
Reset: Re-read this authored instruction — “Give private accessible routes to stop, change helper, complain or move to statutory/professional support.” — and its success check, then attempt only this step.
Possible snag: The only complaint route exposes the requester publicly.
Correction: Provide a private independent channel and protection from loss of unrelated support.
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
09
Review coverage and exclusion
Assess unmet need, latency, dignity, burden, continuity, no-shows and who could not access the process.
Why this step exists
Stories and volunteer hours cannot show equitable impact.
Success check
The review identifies at least one excluded or unmeasured group.
I’m stuck on this step
Reset: Re-read this authored instruction — “Assess unmet need, latency, dignity, burden, continuity, no-shows and who could not access the process.” — and its success check, then attempt only this step.
Possible snag: The result from “Assess unmet need, latency, dignity, burden, continuity, no-shows and who could not access the process.” does not yet meet this declared check: The review identifies at least one excluded or unmeasured group.
Correction: Return to the start of “Review coverage and exclusion”, reduce complexity or pace, and repeat only the part needed to satisfy: “The review identifies at least one excluded or unmeasured group.”
Stop / get help: Stop if immediate danger, safeguarding, health, care, money, housing or legal need appears; use the responsible service.
Correct versus incorrect execution
These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.
Inviting participation — Joining one support task does not authorise publicity or continuing obligations.
Correct / safer
Offer separate consent and easy withdrawal.
Wrong / riskier
Treat joining once as consent to all future roles.
Matching decision point — Poor fit can endanger requester and volunteer.
Correct / safer
Check task, capacity, access and fallback.
Wrong / riskier
Assign whoever is available because need is urgent.
Reciprocity decision point — Mandatory reciprocity excludes people with less capacity.
Correct / safer
Allow optional locally defined contribution or none.
Wrong / riskier
Require equal repayment or gratitude despite different capacity and stated terms.
Judging success — Activity can hide unfair coverage and burnout.
Correct / safer
Track unmet need, dignity, burden and exclusion.
Wrong / riskier
Report volunteer hours and positive stories only.
Method-structure checklist
10 of 10 structural checks present
✓ Ordered, Power-specific instructions — present
✓ Every activity has a success check — present
✓ Materials or supplied records are declared — present
✓ Measurement or assessment rule is present — present
✓ Tutorial-specific troubleshooting is present — present
✓ Stopping or escalation boundary is present — present
✓ Every activity has an adjacent alternative — present
✓ Correct-versus-incorrect comparison is present — present
✓ Evidence context is bound to the Power record — present
✓ Planning metadata is present — present
The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.
Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.