Clinical Leadership and Decision-Making When Working With ICBs and Trusts
System partnership working becomes unsafe when clinical decisions are unclear: staff are uncertain about thresholds, escalation relies on personal relationships, or risk decisions are not recorded in a way that partners can act on. ICBs and Trusts want assurance that providers have clinical leadership that translates into consistent front-line decision-making, safe escalation and defensible practice around risk and restrictions. This article sits within working with ICBs in mental health and connects to mental health service models and pathways, focusing on how providers design clinical leadership, delegated authority and decision controls that commissioners and CQC recognise as credible.
Why clinical leadership is different in integrated systems
In a single-organisation service, clinical decisions are supported by one set of thresholds, policies and escalation routes. In integrated systems, clinical leadership must operate across interfaces where:
- Thresholds and response routes differ by service and locality.
- Responsibility can shift rapidly during escalation or handover.
- Information quality varies, creating disagreement about urgency and risk.
- Restrictions can be introduced informally in response to risk and then persist without review.
Clinical leadership therefore needs to create consistency: shared decision language, predictable escalation behaviour, and clear evidence trails that partners can rely on.
Core components of clinical leadership and decision control
1) Delegated authority and decision rights
Staff need to know who can make which decisions and when. Providers should define decision rights for: acceptance/eligibility; escalation to crisis services; safeguarding thresholds; adjustments to contact intensity; and use of restrictions where relevant. Delegated authority should be supported by clear documentation standards so decisions are auditable, not just made.
2) Supervision that tests real decision-making, not only reflection
In integrated settings, supervision should include scenario testing: “What would you do today if X changes?” and “What evidence would you record to support escalation?” This helps standardise decision-making across teams and reduces unsafe variation. Supervision should also review a small number of live cases where threshold decisions are contested or where risk has changed quickly.
3) Standard escalation summaries and decision records
When escalating to a Trust service or partner, providers should use a standard summary that includes what changed, current risks, actions already taken, what is being requested, and time sensitivity. The record must show why the decision was made and what happened next, so commissioners can sample and partners can act without delay.
4) Clinical governance verification
Clinical leadership is evidenced through verification: sampling of decision records, review of escalation logs, and audit of high-risk cases. Verification should test whether staff practice matches the intended operating model, and whether learning leads to sustained improvement (re-audit).
5) Least restrictive practice and positive risk-taking
Where restrictions are used, clinical leadership must ensure they are proportionate, time-limited, reviewed and stepped down. Positive risk-taking should be explicit: what risks are being taken, why, what mitigations exist, and how decisions are reviewed over time.
Operational examples (clinical leadership in day-to-day system working)
Example 1: Consistent threshold decisions across localities
Context: A provider works across two localities with different Trust interfaces. Staff in one locality escalate early; staff in another delay because they are unsure about thresholds. The ICB sees inconsistent escalation patterns and questions decision reliability.
Support approach: The provider introduces a threshold decision guide aligned to both locality interfaces and uses supervision to embed it. A monthly sampling process checks decision records for clarity and consistency. Managers track escalation timeliness and reasons for variance.
Day-to-day delivery detail: Team leads run brief weekly “decision huddles” reviewing edge cases: why escalation happened (or did not), what evidence was recorded, and what response occurred. Supervision focuses on scenario testing and reinforces documentation expectations. Where locality differences create genuine variation, leaders document the difference and provide staff with locality-specific escalation prompts so behaviour remains predictable.
How effectiveness/change is evidenced: Reduced unexplained variation in escalation patterns, clearer documentation trails, and improved staff confidence. Evidence includes decision sample results, escalation logs and governance minutes showing corrective action and re-checks.
Example 2: Clinical leadership for a repeat-crisis cohort
Context: A cohort experiences repeated crisis escalation and safeguarding concerns. Commissioners want assurance that decisions are proactive and not purely reactive.
Support approach: Clinical leadership introduces an early warning and escalation framework for the cohort: early indicators recorded at every contact, standard escalation summaries, and mandatory clinical review after each escalation to update plans and reduce repeat crises.
Day-to-day delivery detail: Staff record early warning indicators and actions taken. When thresholds are met, they escalate using the standard summary. After an escalation, the clinician or senior lead reviews the case within an agreed timeframe, ensures safeguarding actions (if required) are completed, and updates the care plan with learning (contact cadence changes, interface escalation if partner response issues occurred, step-down criteria). Governance reviews cohort trends monthly and samples cases to verify plan updates and proportionality of decisions.
How effectiveness/change is evidenced: Faster step-up decisions, improved post-crisis planning, fewer late-stage escalations and clearer evidence trails. Evidence includes cohort dashboards, sampled cases and action tracking with verification.
Example 3: Restrictive practice decisions controlled through time limits and step-down
Context: Following incidents, staff introduce informal restrictions (monitoring, limiting access, restricting community activity). Restrictions persist through handovers without review, creating rights risks and potential inspection concern.
Support approach: Clinical leadership introduces a restrictions standard: rationale, least restrictive alternatives considered, time limit, review date, and step-down plan. Restrictions are logged and reviewed monthly, with quarterly senior sampling focused on proportionality and outcomes.
Day-to-day delivery detail: Supervisors require explicit review decisions: continue, modify or step down, with rationale. If restrictions continue, staff must document what is being done to reduce underlying risk and what would trigger step-down. During handovers to partners, the minimum dataset includes restrictions and review dates so accountability is retained. Governance escalates any restriction that exceeds time limits without documented review.
How effectiveness/change is evidenced: Reduced duration of restrictions, improved proportionality documentation, and visible step-down decisions. Evidence includes the restrictions register, sampled files and governance minutes showing corrective action and re-checks.
Explicit expectations that must be met
Commissioner expectation
ICBs expect consistent clinical decision-making that is auditable and reduces system friction. They will look for clear delegated authority, predictable escalation behaviour, credible documentation of decision rationale, and verification through sampling and re-audit. They also expect evidence that variation is understood and managed, not ignored.
Regulator / Inspector expectation (e.g. CQC)
CQC expects effective leadership and governance that deliver safe, person-centred care and protect rights. Inspectors will test staff understanding of thresholds and escalation, quality of records, safeguarding responsiveness, and whether restrictive practice is least restrictive, time-limited and reviewed. They will triangulate leadership claims against file evidence and staff practice.
What to show during assurance or inspection
Strong providers bring a small set of anonymised “decision traces” that show how clinical leadership works in practice: early warning recognition, threshold decision, escalation summary, partner response, review decisions, and learning embedded. Combined with sampling results and re-audit evidence, this demonstrates operational control rather than relying on narrative.