System Partnership Working in Mental Health: What Commissioners Look For
Commissioners do not measure “partnership working” by how often organisations meet; they measure it by how reliably the system functions when risk rises, thresholds are contested, or pathways are under pressure. Providers are increasingly assessed on whether they can operate predictably across boundaries, manage shared risks, and evidence that interface problems lead to real improvement rather than repeat friction. This article sits within working with ICBs in mental health and connects to mental health service models and pathways, setting out how commissioners evaluate partnership maturity, what good looks like in daily practice, and how to evidence it.
How commissioners evaluate partnership maturity in practice
Partnership maturity is usually assessed through a set of implicit tests that come out in contract management, mobilisation, and service review meetings. Common tests include:
- Interface clarity: do all parties understand thresholds, responsibilities and escalation routes, or is the system reliant on informal relationships?
- Shared risk management: can the provider describe which risks sit where, how they are monitored, and how they are escalated when partner response is slow?
- Information reliability: does the provider supply consistent, decision-ready information that supports timely step-up and safeguarding action?
- Learning and improvement: when interface failures occur, does the provider help redesign processes and evidence change, or does the issue recur?
- Operational credibility: do partnership claims reconcile to case files, escalation logs and governance decisions, or are they narrative only?
Commissioners are rarely looking for perfection. They are looking for control: early detection of issues, transparent escalation, and evidence of sustained improvement.
What “good system behaviour” looks like for a provider
1) Predictable threshold behaviour
Providers are expected to behave consistently around thresholds: when to step up, when to escalate safeguarding, when to request crisis input, and when to step down. Good threshold behaviour is evidenced in records: early warning indicators, rationale for decisions, and timely action. Inconsistent behaviour (or delayed action because staff are unsure) is a major partnership failure because it increases system pressure and erodes trust.
2) Risk ownership without risk dumping
Commissioners look for providers who own what they can control, and who escalate appropriately when risks sit at interfaces. “Risk dumping” shows up as frequent referrals or escalations without clear evidence of work attempted, or without a coherent escalation summary. Mature providers can show what has been done, what has changed, and what is being requested, in a consistent format.
3) Evidence-based challenge and escalation
System working involves challenge, but commissioners expect challenge to be grounded in evidence and delivered through agreed escalation routes. Effective providers document interface issues (for example, repeated delays in crisis response) and show follow-through: escalation, partner responses, and agreed process changes. This creates an audit trail and reduces reliance on individual relationships.
4) Improvement that is verified
Commissioners are increasingly sceptical of improvement plans that never change file-level reality. Mature partnership working shows verification: re-audit of interface processes, sampling of escalation cases, and trend improvement over time.
Operational examples (commissioner-recognised partnership maturity)
Example 1: Reducing referral “bounce” across a Trust interface
Context: A provider and a Trust team experience repeated referral bounce: referrals are rejected as out of scope, information is incomplete, and people wait longer than necessary. The ICB is concerned about access equity and pathway drift.
Support approach: The provider proposes a structured solution: a shared referral checklist (minimum dataset), an agreed set of eligibility thresholds, and a weekly short “edge case” huddle to resolve recurring confusion. Rejected referrals are logged with structured reasons so patterns can be evidenced.
Day-to-day delivery detail: Triage staff use the same eligibility language consistently. Where a referral is declined, the response includes a clear explanation and, where appropriate, a safer alternative route. The weekly huddle reviews the top three decline themes and adjusts guidance. The provider shares a monthly dashboard showing decline reasons and time-to-first-contact for accepted referrals, linked to operational logs.
How effectiveness/change is evidenced: Reduced incomplete referrals, fewer avoidable declines, improved time-to-start, and clearer pathway alignment. Evidence includes referral logs, huddle notes, and trend reporting that commissioners can reconcile to raw operational data.
Example 2: Shared risk management at the crisis escalation interface
Context: A high-risk cohort experiences repeated crises. Crisis access routes vary by time and locality, and escalation decisions are disputed. The ICB wants assurance that escalation is timely and that the provider is not escalating late due to weak early warning practice.
Support approach: The provider introduces a standard escalation summary and an internal “escalation timeline” record. Managers review repeat escalations weekly and identify whether delays are internal (late recognition) or interface-related (threshold/access issues). Interface issues are escalated formally and tracked.
Day-to-day delivery detail: Staff record early warning indicators and actions at each contact for the cohort. When escalation is needed, the standard summary is used so crisis services receive consistent, decision-ready information. Managers document senior review for repeat escalations and require care plan updates that reflect learning. The provider logs interface delays and escalates them through agreed routes, capturing outcomes and agreed changes.
How effectiveness/change is evidenced: Improved time-to-action from early warning indicators, fewer late-stage escalations, and clearer documentation trails. Evidence includes escalation logs, sampled case files and governance records showing corrective action and verification.
Example 3: Safeguarding partnership without over-restriction
Context: Exploitation concerns involve multiple agencies. Some staff respond by restricting access and increasing monitoring, but restrictions are not always time-limited or reviewed. Safeguarding actions can drift because ownership is unclear across partners.
Support approach: The provider implements a safeguarding action tracker with owner/deadline/escalation route fields and introduces a restrictions standard: rationale, alternatives considered, time limit and review date. Weekly safeguarding huddles track actions and multi-agency contact, with escalation of stalled partner response.
Day-to-day delivery detail: Each safeguarding case has named actions with deadlines. Supervisors check staff decisions for proportionality and evidence of least restrictive practice. Where restrictions are used, review decisions are documented explicitly: continue, modify or step down, with rationale. Governance reviews cases where restrictions persist and ensures safeguarding actions remain active rather than “containment” only.
How effectiveness/change is evidenced: Improved safeguarding action completion, clearer multi-agency evidence in files, and reduced long-running restrictions. Evidence includes tracker outputs, file sampling and re-audit showing sustained practice change.
Explicit expectations that must be met
Commissioner expectation
Commissioners expect partnership claims to be auditable and to reduce system friction over time. They will look for clear interface controls, documented escalation routes, shared risk management, and evidence that issues lead to verified improvement (re-audit, sampling and trend change). They also expect providers to explain variation and reconcile reporting to operational evidence.
Regulator / Inspector expectation (e.g. CQC)
CQC expects safe coordination and continuity across organisational boundaries. Inspectors will test whether staff understand escalation and safeguarding routes, whether risks are managed proportionately, and whether learning from interface incidents changes practice. File evidence and staff understanding must align with what leaders claim.
How to evidence partnership maturity in a contract review
A provider can usually evidence partnership maturity by presenting a short set of “assurance traces”: a small number of anonymised cases where the evidence chain is clear (early warning → action → escalation summary → partner response → review decision → learning embedded). These traces, supported by trend data and action tracking, are far more persuasive than narrative claims because they show how the system actually works.