Embedding Lived Experience Safely in Mental Health Service Delivery: Roles, Boundaries and Assurance
Lived experience roles can add credibility, trust and realism to mental health services, especially where people feel unheard or disengaged. But “having lived experience involved” is not automatically safe or effective. Providers need clear role design, boundaries, supervision, and governance that protects people using the service, lived experience contributors, and staff teams. In this series on co-production and lived experience in mental health, we connect lived experience practice to wider mental health service models and pathways, because roles only work when they fit the pathway: crisis, step-down, community support and longer-term care.
Start with role clarity, not enthusiasm
Many problems begin when lived experience is treated as a personal attribute rather than a job function. Safe embedding starts by defining:
- Role purpose: what the role is for (peer support, engagement, group facilitation, feedback and improvement, pathway navigation).
- Task boundaries: what the role will not do (clinical assessment, medication advice, lone crisis response, safeguarding decision-making unless trained and authorised).
- Accountability: who supervises the role, who supports wellbeing, and who holds risk oversight.
- Interface with the MDT: how information flows, what is recorded, and how disagreements are handled.
Role clarity is not bureaucratic; it prevents drift into unsafe expectations, especially when people are in distress and reach for whoever feels most trusted.
Boundaries and safeguarding: make the “grey areas” explicit
Boundary issues often arise around contact outside planned sessions, social media, gift-giving, transport, money, and disclosures. A safe model makes these predictable by using:
- Boundary agreements (shared with the person using the service where appropriate).
- Defined escalation routes for safeguarding and risk concerns.
- Clear recording expectations so the team can see what contact occurred and why.
- Reflective supervision focused on emotional impact, not just task completion.
Where services support people with trauma histories, the boundary framework must be trauma-informed: compassionate, consistent, and designed to avoid sudden withdrawal or punitive responses that can worsen risk.
Operational Example 1: Peer role in re-engaging someone after repeated missed appointments
Context: A person with severe anxiety and paranoia repeatedly missed community appointments and was at risk of discharge for non-engagement. Staff had made multiple attempts that were experienced as pressuring and led to further withdrawal.
Support approach: A lived experience engagement worker was allocated with a defined remit: short, consistent contact attempts; focus on trust and practical barriers; no clinical questioning; immediate escalation if risk indicators emerged. The care coordinator retained clinical responsibility.
Day-to-day delivery detail: The worker used an agreed contact plan: one weekly text at the same time, followed by a short phone call if no reply, and a low-demand offer (“Would it help if we met for 10 minutes at the café near you?”). The worker recorded each contact attempt and any response in the case record, using a short template so the MDT could see progress. Once contact was re-established, the worker attended the first re-engagement appointment to support communication and reduce anxiety.
Evidence of effectiveness: The provider tracked: engagement restored (attendance within 4 weeks), reduction in DNAs, and the person’s feedback about feeling less judged. The team also reviewed whether risk indicators (self-neglect, suicidal ideation) were escalated appropriately, demonstrating safe boundaries rather than “working around the team”.
Operational Example 2: Lived experience input into care planning without undermining clinical accountability
Context: People reported that care plans were “written about me, not with me”. Staff felt time pressure and defaulted to generic plans, leading to poor ownership and inconsistent follow-through.
Support approach: A lived experience facilitator supported care planning sessions with a structured method: the clinician led on risk and treatment; the facilitator ensured the person’s goals, warning signs and preferences were captured in plain language; the team agreed decision rights and sign-off.
Day-to-day delivery detail: The facilitator used a three-part prompt sheet: “what matters”, “what helps”, and “what to do when things worsen”. They supported the person to state preferred contact methods, what language to avoid, and who should be involved (carer, advocate). The outcome was a co-produced one-page summary attached to the clinical care plan, reviewed at each appointment and updated when circumstances changed.
Evidence of effectiveness: The provider audited a sample of plans for: presence of the one-page summary, evidence of review, and whether escalation triggers matched recorded incidents. Complaints about “not being listened to” were monitored to see if themes reduced over time.
Operational Example 3: Turning feedback into measurable quality improvement
Context: The service collected feedback, but people rarely saw changes and staff felt feedback was “too general” to action. Commissioners challenged the provider to show learning and improvement.
Support approach: A lived experience lead co-chaired a monthly Quality and Learning meeting with the Registered Manager. The group had a formal action log, and a process for selecting one improvement focus per month linked to pathway performance (access, responsiveness, safety, outcomes).
Day-to-day delivery detail: The group reviewed themes from feedback, complaints and incident debriefs and selected “responsiveness to deterioration” as the first focus. They redesigned the telephone triage script to include a clear safety-net message, created a standard callback time expectation, and introduced a simple “escalation completed” tick-box in records. Team leaders used supervision to check adherence and explore barriers.
Evidence of effectiveness: The provider reported: reduced callback delays, improved satisfaction scores on “I knew what would happen next”, and fewer incidents linked to missed escalation. Audit reports documented the change cycle: baseline, intervention, re-audit, and next steps.
Commissioner expectation: roles must sit inside governance and outcomes
Commissioner expectation: Commissioners expect lived experience involvement to be structured, sustainable and evidenced. They will look for role descriptions, training, supervision, and measurable outputs (engagement improvement, reduced complaints on specific themes, improved responsiveness metrics), not just activity counts or testimonials.
Regulator / inspector expectation: safety, boundaries and accountability are non-negotiable
Regulator / Inspector expectation: Inspectors expect clear safeguarding oversight, consistent boundaries, and accountability for decisions. They will scrutinise whether lived experience contributors are supported and supervised, whether confidentiality and consent are managed, and whether the provider can demonstrate that involvement strengthens (not weakens) risk management, record quality and responsiveness.
Supervision and support: protect the role to protect the service
Lived experience roles can carry additional emotional load, especially when supporting people in crisis or hearing traumatic histories. Safe embedding includes:
- Regular reflective supervision (not only case updates).
- Access to debrief after incidents, complaints or challenging contacts.
- Training on safeguarding, boundaries, confidentiality, and escalation.
- Clear stop points where the role must hand over to clinical staff.
When this support is in place, lived experience becomes a resilient part of the workforce model rather than an add-on that depends on individual heroics.