Operational Partnership Working With ICBs and NHS Trusts in Mental Health Services
Partnership working with NHS Trusts and system partners is judged most harshly at the points where things go wrong: delayed escalation, unclear accountability, unsafe handovers, and disagreements about thresholds. ICBs want confidence that providers can operate across these interfaces without creating unmanaged risk or constant friction. That confidence comes from day-to-day routines: shared escalation routes, consistent documentation, and governance that resolves recurring interface problems. This article builds on working with ICBs in mental health and connects to mental health service models and pathways, focusing on operational partnership practices that commissioners recognise as mature and defensible.
Where operational partnerships commonly fail
Most partnership failures are predictable and preventable. Common failure points include:
- Ambiguous eligibility and thresholds (referrals bounce or drift, creating delays and frustration).
- Interface handover gaps (information is incomplete, risk is not clearly communicated, or follow-up is inconsistent).
- Shared risk without shared processes (everyone assumes someone else is leading).
- Escalation that relies on individuals (good outcomes depend on personal relationships rather than repeatable routes).
- Performance discussions without traceability (metrics cannot be reconciled to operational evidence, so trust erodes).
A mature partnership approach designs these risks out through standard routines and evidence trails.
Operational partnership principles that actually work
1) Make interfaces explicit and train to them
Interfaces should be described in operational language: who does what, by when, using what documentation, and what happens if the expected response does not occur. Staff should be trained on these interfaces using scenarios (not just reading a protocol) so escalation is confident and timely.
2) Use consistent “handover quality” standards
Whether the interface is crisis escalation, discharge follow-up, or multi-agency safeguarding, the handover should include a minimum dataset: current presentation, key risks, what has changed, actions already taken, what is being requested, and what time sensitivity applies. Consistency reduces delay and dispute.
3) Build shared risk management into governance
Partnership governance should include regular review of interface incidents and delays, trend analysis, and action tracking. Importantly, it should separate operational learning (what to change) from blame (who to fault). Commissioners look for evidence that interface issues lead to improved processes over time.
Operational examples (partnership in action)
Example 1: Referral interface stabilisation with a Trust pathway
Context: A provider receives high volumes of referrals from a Trust team, with frequent ineligibility and incomplete information. This creates delays, pressure, and negative system sentiment.
Support approach: The provider and Trust agree a single referral checklist and a weekly 30-minute triage alignment call. The checklist specifies required information and clarifies thresholds for acceptance, step-up and onward referral.
Day-to-day delivery detail: The provider logs declined referrals with structured reasons and shares themes monthly. The weekly call reviews edge cases and updates guidance where repeated confusion exists. Internally, the provider trains staff to use the same language and thresholds so messages back to referrers are consistent. Governance monitors whether ineligible referrals reduce and whether time-to-first-contact improves for accepted referrals.
How effectiveness/change is evidenced: Reduced referral bounce, fewer incomplete referrals, improved time-to-start for appropriate cases, and clearer audit trails for eligibility decisions. Evidence includes referral logs, triage notes and trend reporting.
Example 2: Crisis escalation partnership that reduces duplication and delay
Context: Front-line staff report “ping-pong” between provider, Trust crisis services and other partners during deterioration. Escalations are delayed because information quality varies and accountability is unclear.
Support approach: The system agrees a standard escalation summary and an escalation ladder (front-line escalation, manager escalation, senior escalation). The provider introduces an internal requirement for manager review of repeat escalations and uses an escalation timeline note to support learning.
Day-to-day delivery detail: Staff use the standard summary so crisis services receive consistent, decision-ready information. Managers review repeat escalations weekly and identify whether delays were internal (late recognition) or interface-related (access/threshold issues). Interface issues are escalated through formal routes and tracked to resolution, with learning fed back into supervision prompts and templates.
How effectiveness/change is evidenced: Reduced duplication, clearer decision trails, improved timeliness of step-up actions, and fewer late-stage crises in the repeat escalation cohort. Evidence includes escalation logs, file sampling and governance action tracking.
Example 3: Shared safeguarding accountability without over-restriction
Context: Exploitation concerns involve multiple agencies. Staff become risk-averse and apply informal restrictions without clear review, while safeguarding actions drift due to unclear ownership.
Support approach: The provider uses a shared safeguarding action tracker that records owner, deadline and escalation route for each action. Any restriction must have a rationale, time limit and review date, plus evidence of least restrictive alternatives considered.
Day-to-day delivery detail: Weekly safeguarding huddles confirm actions are completed and record partner contact and outcomes. Supervision tests staff confidence in thresholds and proportionality. Governance reviews cases where restrictions persist and requires explicit step-down decisions when risks change, ensuring rights and safety are balanced transparently.
How effectiveness/change is evidenced: Higher safeguarding action completion rates, stronger multi-agency evidence in files, and reduced long-running restrictions. Evidence includes tracker outputs, audit samples and review decisions.
Explicit expectations that must be met
Commissioner expectation
Commissioners expect partnership working to be evidenced through reliable interfaces and controlled risk. They will look for clear accountability, auditable escalation routes, trend management of interface issues, and evidence that partnership problems lead to improved processes (not repeated disputes). They also expect performance reporting to reconcile to operational records.
Regulator / Inspector expectation (e.g. CQC)
CQC expects safe coordination and continuity of care across boundaries. Inspectors will test whether staff understand escalation routes, whether safeguarding is timely and effective, and whether learning from interface incidents changes practice. They will also examine proportionality and least restrictive practice where restrictions occur.
What mature partnership looks like over a contract cycle
Over time, mature partnerships show fewer repeated interface failures, clearer documentation, and faster resolution of disputes because escalation routes are formal and action tracking is routine. The practical aim is simple: when risk rises, everyone knows what to do, information is consistent, and governance ensures the system learns rather than repeating the same problems.