Cross-sector governance becomes fragile when it relies on goodwill instead of authority. The difference between “a partnership” and an operating system is decision clarity: who can decide, what evidence is required, and how disagreements are resolved without service disruption. For taxonomy context, see System Leadership & Cross-Sector Governance and Board Governance & Accountability.
Why decision rights matter more than meeting cadence
Many cross-sector arrangements over-invest in meetings and under-invest in authority. The result is “committee drift”: decisions are endlessly reviewed, risks are discussed but not owned, and frontline delivery absorbs the consequences. In community settings—where clients can deteriorate quickly and where housing, benefits, clinical input, and safeguarding may all be relevant—slow or unclear decision-making is not a neutral inconvenience. It is an operational hazard.
Two oversight expectations you should be able to evidence
Expectation 1: Decisions are attributable. Funders, system leaders, and boards generally expect that decisions affecting safety, rights, and contractual performance can be traced to named roles with appropriate authority. “The group decided” is not a defensible audit trail when outcomes go wrong.
Expectation 2: Escalation is designed, not improvised. Mature systems show pre-defined thresholds and timeframes for escalation (same-day, 72-hour, etc.), along with a dispute pathway that prevents service interruption while partners resolve disagreements.
The core design: a decision catalogue, not a generic RACI
A useful decision-rights framework starts with a “decision catalogue”—a short list of recurring decisions that drive quality and performance. Each decision should have: (1) the decision owner (role, not person), (2) who must be consulted, (3) minimum evidence required, (4) the timeline, and (5) the escalation route if the decision is blocked. This is more operational than a broad RACI chart because it aligns authority with real service moments: discharge acceptance, care intensity changes, shared risk controls, housing contingencies, and safeguarding responses.
Operational Example 1: Rapid care escalation across partners—authority that prevents delayed deterioration
What happens in day-to-day delivery. A community provider supports a high-risk client whose condition worsens (confusion, missed meds, reduced intake). The decision catalogue specifies a rapid escalation decision: the provider’s on-call supervisor can increase visit frequency immediately and trigger a same-day clinical review with the system’s designated clinician. The supervisor gathers minimum evidence (recent notes, vitals if available, medication list, red-flag screen), records the escalation in the shared log, and implements interim safety actions (wellness checks, family contact, transport arrangements) while awaiting partner input.
Why the practice exists (failure mode it addresses). The failure mode is “slow consensus” during clinical change—frontline staff wait for a meeting or for multiple approvals, and deterioration becomes a crisis. Cross-sector settings worsen this because clinical authority may sit with a different entity than day-to-day support.
What goes wrong if it is absent. Without delegated authority, staff hesitate. Escalation becomes dependent on finding the right person at the right time, and documentation becomes inconsistent. The client may present in the ED or experience safeguarding harm that could have been prevented by a rapid, authorized care-intensity change.
What observable outcome it produces. A working model produces auditable timeliness: time-to-escalation, time-to-clinical review, and completion of interim safety actions. Over time, providers can evidence fewer avoidable crisis contacts for the cohort and clearer escalation discipline that boards and system partners can review.
Operational Example 2: Housing contingency decisions—delegation that protects continuity without overpromising
What happens in day-to-day delivery. A client faces imminent eviction, threatening service continuity and safety. The decision catalogue defines a “housing contingency” decision: the provider’s program manager can authorize a time-limited stabilization plan (increased outreach, behavior support adjustments, safety planning) and convene a cross-sector conference within 72 hours. A separate decision right sits with the housing partner for tenancy enforcement, and with county partners for emergency assistance. The provider’s role is explicit: present documented risks, propose reasonable adjustments, and set interim delivery actions that do not require partner approval to begin.
Why the practice exists (failure mode it addresses). The failure mode is ambiguity: providers either promise outcomes they can’t control (e.g., “we will prevent eviction”) or they do nothing while waiting for housing decisions. Both create instability and reputational harm.
What goes wrong if it is absent. In the absence of clear rights, escalation becomes personal and inconsistent—different managers take different stances, and partners receive mixed messages. Clients experience service disruption, documentation becomes fragmented, and safeguarding risk increases because interim plans are not authorized and implemented consistently.
What observable outcome it produces. Mature delegation produces measurable continuity signals: fewer unplanned service breaks, documented case conferences within target timeframes, and clearer evidence of reasonable adjustments and interim risk controls. It also produces defensibility: the provider can show exactly what it controlled and what sat with partners.
Operational Example 3: Dispute resolution on performance metrics—governance that prevents “silent contract failure”
What happens in day-to-day delivery. A partner challenges the provider’s performance reporting (e.g., contact timeliness, engagement rates). The decision framework defines a dispute pathway: first-line reconciliation between analytics leads within five business days, then escalation to a joint operational governance lead if unresolved, and finally a steering-level decision with documented rationale. The minimum evidence is pre-defined: data definitions, inclusion/exclusion rules, and a small audit sample of case records. While the dispute is resolved, the provider continues to deliver to the stricter of the two definitions (time-limited) and logs mitigation actions.
Why the practice exists (failure mode it addresses). The failure mode is “metric drift”: partners use different definitions, performance appears worse than it is, and corrective action becomes political rather than operational. Meanwhile, real improvement work is delayed.
What goes wrong if it is absent. Without a dispute route, disagreements linger, relationships deteriorate, and the provider can be penalized based on unclear measures. Frontline teams receive contradictory targets, and leadership loses time to ad hoc negotiation instead of fixing root causes.
What observable outcome it produces. A designed pathway produces faster resolution times, fewer repeated disputes, and higher confidence in reported performance. It also creates a board-assurance narrative: governance can evidence how decisions were made, what data was tested, and how mitigation protected contractual delivery.
How boards and executives keep decision rights real
Decision rights only work if leaders enforce them. That means: training managers on what they can authorize; auditing whether decisions follow the catalogue; and tracking where decisions repeatedly escalate (a sign the framework is incomplete). When partners see consistent, documented decision-making, cross-sector governance speeds up—and accountability becomes clearer, not weaker.