Co-Production in Commissioned Mental Health Services: What “Good” Looks Like in Practice
Co-production is now routinely written into service specifications for mental health support, but many providers still treat it as an informal “engagement activity” rather than a governed delivery method. Commissioners and inspectors are rarely persuaded by statements that people were “involved” unless there is a repeatable system showing what was decided, how risk and boundaries were managed, and how learning changed practice. In this series on co-production and lived experience in mental health, we also signpost related pathway design content via mental health service models and pathways. The aim here is practical: what co-production looks like when it can be audited, defended, and improved over time.
Defining co-production in operational terms
In commissioned mental health services, co-production is best defined as: a structured method for sharing decision-making with people who use services (and, where appropriate, carers), with clear boundaries and governance, so that involvement influences design, delivery and improvement. That definition matters because it leads to testable components:
- Purpose and scope: what decisions can be influenced (pathway design, access standards, care planning, quality priorities) and what is out of scope (clinical responsibility, employment decisions, individual case decision-making unless formally agreed).
- Decision rights: who can decide, who can recommend, and who must sign off (including clinical and safeguarding oversight).
- Representation: whose voices are included and how exclusion is avoided (diversity, seldom-heard groups, people with fluctuating capacity, people in crisis).
- Safety and boundaries: role clarity, confidentiality, conflict of interest, safeguarding and escalation.
- Documentation: minutes, action logs, version control, change records and feedback loops.
Without these components, co-production becomes vulnerable to two common failures: tokenism (involvement without influence) and unmanaged risk (blurred boundaries, distress, safeguarding concerns, or staff uncertainty).
Where commissioners test co-production
Commissioners tend to test co-production where it intersects with system assurance and contract management. They will often look for evidence that co-production is embedded in:
- service mobilisation and pathway redesign
- care planning approaches and review practice
- quality governance (complaints learning, incidents, audit priorities)
- workforce development (training content, induction, supervision themes)
- outcome frameworks (what is measured and why)
Put simply: if co-production does not alter what the service does, how it does it, or what it measures, it is hard to defend as “real”.
Operational Example 1: Co-producing a crisis transition safety protocol
Context: A community mental health provider saw repeated near-miss incidents during transitions from crisis support back to routine care. People described inconsistent follow-up and confusion about who to contact when symptoms escalated.
Support approach: The provider established a time-limited co-production working group with agreed decision rights: lived experience members could shape the protocol content and wording; clinical leadership retained sign-off for risk and safeguarding elements; commissioners were observers for alignment with contract expectations.
Day-to-day delivery detail: The group reviewed three anonymised case timelines and mapped “failure points” (missed calls, unclear responsibilities, gaps between teams). They produced a single-page transition checklist used at every step-down meeting: named coordinator, 72-hour contact plan, medication queries route, relapse indicators, escalation triggers, and a standardised text/phone check-in sequence. Staff used the checklist in handovers and uploaded it into the case record as a required document.
Evidence of effectiveness: The provider tracked completion rates of the checklist, time-to-first-contact after step-down, and incident reports linked to transition failures. Monthly governance meetings reviewed exceptions (missed 72-hour contact) and logged learning actions. People’s feedback was collected at two weeks post-step-down and compared to baseline comments about “not knowing what happens next”.
Operational Example 2: Co-produced quality priorities that change audit practice
Context: Internal audits focused heavily on documentation compliance, while people using the service reported that “the record looks fine but the help doesn’t arrive when it matters”.
Support approach: A co-produced Quality and Learning Panel was created with formal terms of reference, including confidentiality agreements, trauma-informed facilitation, and a route to raise safeguarding concerns. The panel had authority to set two quarterly audit priorities alongside the Registered Manager.
Day-to-day delivery detail: For one quarter, the panel chose “responsiveness to deterioration” as an audit priority. Auditors sampled records for: evidence of early warning signs being noticed, escalation being followed, and the person being informed and involved. The panel co-designed an audit tool using plain-language questions that mirrored people’s experiences (for example, “When you said you were getting worse, what happened next?”). Audit findings were fed into supervision templates so team leaders routinely discussed responsiveness in 1:1s.
Evidence of effectiveness: The provider produced an audit report with action plans, then re-audited after eight weeks. Improvements were measured by reduced escalation delays and increased documented shared decision-making during deterioration. The panel also reviewed complaint themes to test whether the same issues continued to arise.
Operational Example 3: Co-producing workforce training that strengthens boundaries
Context: Peer-led involvement was increasing, but staff reported uncertainty about boundaries, and lived experience contributors felt pressured to share more than was safe.
Support approach: The provider co-produced a training module with lived experience staff, safeguarding lead, and HR. The module aimed to make boundaries explicit and consistent across teams, with clear escalation routes.
Day-to-day delivery detail: Training included scenario-based exercises: responding to out-of-hours messages, managing dual relationships, handling disclosures, and supporting choice while maintaining safety. A “boundary agreement” template was introduced for peer-support roles, setting expectations on contact methods, social media, gift-giving, and confidentiality. Supervisors used a short reflective checklist in monthly supervision to review boundary challenges and emotional impact.
Evidence of effectiveness: The provider monitored safeguarding concerns linked to boundary issues, staff confidence scores pre/post training, and supervision compliance. Where boundary incidents occurred, learning was recorded and fed into refresher sessions, showing an improvement cycle rather than one-off training.
Commissioner expectation: co-production must be evidenced and traceable
Commissioner expectation: Co-production should produce traceable outputs that link involvement to service change. In practice, that means commissioners expect to see minutes, action logs, version-controlled documents, and clear “you said / we did” reporting that ties changes to contract priorities (access, safety, outcomes, experience) and shows who approved what.
Regulator / inspector expectation: involvement must be safe, inclusive and governed
Regulator / Inspector expectation: Inspectors look for involvement that is genuine and safe, not performative. They will scrutinise whether people are supported to participate without undue pressure, whether safeguarding routes are clear, whether consent and confidentiality are managed, and whether the provider can demonstrate learning from feedback, complaints and incidents. Where co-production includes people who may be vulnerable, the governance around boundaries and emotional impact becomes central.
Governance that makes co-production defensible
Providers strengthen credibility by treating co-production like any other governance process:
- Terms of reference with scope, decision rights and escalation routes.
- Role descriptions for lived experience contributors, including support offered and boundaries.
- Risk assessment for involvement activity (including trauma impact and safeguarding).
- Records and action tracking with deadlines, owners, and evidence of completion.
- Review cycle (quarterly effectiveness review, including what changed and what did not).
When this infrastructure exists, co-production becomes a repeatable method that improves quality over time, rather than an occasional consultation exercise.