Governing Co-Production in Mental Health Services: Roles, Boundaries, Safeguarding and Accountability
Co-production can strengthen safety, engagement and trust in mental health services, but only when it is treated as a governed practice rather than an informal “nice-to-have”. Within co-production, lived experience and personalisation, providers need clarity on roles, boundaries, safeguarding and accountability. This also has to align with wider mental health service models and pathways, because involvement affects triage decisions, escalation routes, risk planning and transitions. This article sets out a practical governance approach that is credible to commissioners and defensible to inspectors.
Why governance is the difference between “involvement” and operational credibility
Many services can describe co-production activity, but struggle to evidence how it is controlled, reviewed and used to drive change. Weak governance creates predictable risks: tokenistic involvement, role confusion, disclosure of identifiable information, contributor burnout, and decisions being “influenced” without a clear line of accountability. Strong governance makes co-production safe, repeatable and auditable.
In practice, governance means the service can answer simple questions clearly: Who is involved? In what capacity? With what boundaries? How are contributors supported? How is feedback logged and actioned? How do we evidence impact? Most importantly: who remains accountable for decisions about care, safeguarding, risk and clinical thresholds?
Core components of a co-production governance model
1) Defined roles and scopes
Define contributor roles in plain English, with examples of what is “in scope” and “out of scope”. A service might legitimately involve lived experience contributors in training, service design workshops, information review, interview panels or quality walkrounds. It should be explicit that contributors do not provide clinical advice, make risk decisions, or hold accountability for care planning decisions.
2) Safeguarding and confidentiality controls
Contributors should have a named safeguarding lead, clear guidance on handling disclosures, and boundaries around identifiable information. This includes practical controls such as anonymisation rules, avoiding discussion of live cases, and clear escalation routes if a session raises risk concerns.
3) Support, debrief and wellbeing arrangements
Co-production can be emotionally demanding. Providers should define how contributors are prepared, supported during sessions, and offered debrief or reflective support afterwards. The service must also set expectations on what contributors can reasonably deliver, including workload, timescales and communication routes.
4) Decision logs and “you said / we did” assurance
Good governance creates a traceable link between involvement and change. This does not require a marketing-style bulletin; it requires a simple decision log: the issue raised, what was decided, who approved it, when it will be reviewed, and how the service will evidence whether the change worked.
Operational Example 1: Governing a lived experience advisory group
Context: A provider created an advisory group to shape service accessibility and reduce complaints about unclear thresholds and inconsistent communication. Early meetings were productive but drifted into discussion of identifiable experiences with named staff and recent incidents, creating confidentiality risk and blame dynamics.
Support approach: The service introduced a governance framework: written terms of reference, session ground rules, and a facilitator role with responsibility for boundaries. A quality lead chaired the group and remained accountable for translating recommendations into governance decisions.
Day-to-day delivery detail: Each meeting used a structured agenda:
- Pre-circulated topic brief with a clear question (e.g., “How do we explain triage outcomes consistently?”).
- Reminder of confidentiality and “no identifiable cases” at the start of every session.
- Live note-taking using an action log template: theme, recommended change, owner, due date, review date.
Evidence of effectiveness: The provider could demonstrate a clear audit trail from advisory group themes to revised communication templates, updated staff prompts, and refreshed triage letters. Complaint themes relating to “unclear next steps” reduced over the next two quarters, and the action log showed completion and review of changes.
Operational Example 2: Safe involvement in recruitment and interview panels
Context: The provider wanted lived experience involvement in recruitment to improve relational quality and values fit. Managers were concerned about confidentiality, fairness and contributor wellbeing.
Support approach: The provider set a defined panel role: contributors would score values-based questions and communication scenarios, but would not access sensitive candidate data beyond what is shared in the interview. HR retained process accountability and ensured equality and bias controls.
Day-to-day delivery detail: Practical controls included:
- A panel briefing pack explaining the role, boundaries and scoring method.
- Structured scenarios (e.g., explaining a delayed appointment, responding to distress, clarifying escalation routes).
- Post-interview debrief: contributors could share observations on clarity and empathy, while HR and managers retained final decision accountability.
Evidence of effectiveness: Six-month probation reviews showed clearer feedback on communication and relational practice. Team leaders reported fewer early-stage performance concerns linked to values or attitude. The service could evidence how contributor scores correlated with successful recruitment outcomes.
Operational Example 3: Governing co-produced information and letters
Context: People using the service reported that letters following triage, review or discharge were confusing and anxiety-provoking, leading to repeat contact, complaints and, in some cases, escalation of distress.
Support approach: The provider co-produced letter templates and information sheets with lived experience contributors, but governed changes through a controlled document process (version control, approvals, and review cycles).
Day-to-day delivery detail: The service set up a “document clinic” every month:
- One template reviewed at a time against a plain-English checklist.
- Operational sign-off from the service manager and clinical sign-off where risk advice was included.
- Publication log capturing version, date, reason for change and next review date.
Evidence of effectiveness: The provider measured reduction in repeat calls related to “what happens next” and tracked fewer complaints about unclear decisions. Audit samples showed improved consistency in how outcomes and escalation options were explained.
Commissioner Expectation: Transparent governance and evidence of action
Commissioner expectation: Commissioners expect co-production to be more than consultation. They will look for clear governance (roles, ToR, action logs), and evidence that themes drive measurable improvements in access, safety, experience and outcomes.
Regulator / Inspector Expectation: Safety, confidentiality and accountable decision-making
Regulator / Inspector expectation: Inspectors will expect confidentiality and safeguarding to be protected within involvement activity, and will look for clear accountability: contributors inform improvement, but registered managers and clinical leads remain responsible for risk decisions and care delivery standards.
Practical assurance: what to keep on file
To make co-production inspectable, maintain a small set of core evidence: terms of reference, role descriptions, confidentiality guidance, support arrangements, action/decision logs, and examples of changes implemented and reviewed. This turns co-production into a defensible part of your quality management system.