Delegated authority is essential in community services: executives cannot personally authorize every operational decision, and boards must avoid micromanagement. But poorly governed delegation creates “shadow governance”—critical decisions made routinely without visibility, consistent criteria, or strategic alignment. Executive leaders working within Executive Leadership & Strategic Oversight are responsible for ensuring that delegation is structured, controlled, and reviewable. This sits within Board Governance & Accountability, where boards must be able to demonstrate that authority is exercised within approved boundaries.
In practice, delegation fails when decision rights are ambiguous, escalation triggers are unclear, or assurance focuses only on outcomes rather than decision quality. The result is inconsistent risk acceptance across programs and heightened vulnerability when incidents occur.
Clear decision-making structures are easier to maintain when supported by leadership and governance frameworks that enhance organisational capability and control.
What “Shadow Governance” Looks Like Operationally
Shadow governance is rarely malicious. It emerges when leaders intend to empower managers but do not specify the limits of empowerment. Over time, local practices become informal policy: admissions decisions, discharge thresholds, restrictive practice approvals, exception handling, and resource trade-offs vary by site. The board sees stable headline metrics while decision quality quietly diverges.
After a serious incident, investigations often uncover multiple prior decision points where escalation should have occurred but did not—because the authority model was unclear or culturally discouraged challenge.
Operational Example 1: A Living Delegation of Authority (DOA) Framework
What happens in day-to-day delivery
Executives implement a living Delegation of Authority framework that defines decision rights by role for key domains: safeguarding, clinical escalation (where applicable), financial commitments, staffing exceptions, restrictive practices, admissions/discharges, and service model deviations. The DOA is embedded into onboarding, reviewed quarterly, and published in an accessible internal location. Managers use short DOA checklists before approving high-stakes decisions, documenting rationale and any escalation steps taken.
Why the practice exists (failure mode it addresses)
This practice exists to prevent ambiguity-driven inconsistency. When decision rights are unclear, people either over-escalate (slowing response) or under-escalate (increasing risk).
What goes wrong if it is absent
Different programs develop their own informal rules. Decisions become person-dependent rather than system-dependent. Staff are unsure when to escalate, and executives cannot credibly assure boards that governance boundaries are being respected.
What observable outcome it produces
Decisions become more consistent across sites. Documentation improves. Boards gain assurance that authority is being exercised within defined limits, with auditable rationale for high-risk decisions.
Operational Example 2: Escalation Triggers That Override Hierarchy
What happens in day-to-day delivery
Executives define escalation triggers that override normal hierarchy, meaning staff can escalate directly to a higher level when certain conditions are met (e.g., immediate safeguarding risk, credible allegations involving staff, repeated threshold breaches, serious medication incidents, or acute capacity failure). The triggers are built into policies, shift handovers, and incident workflows. Leaders train managers to respond constructively to escalation rather than treating it as criticism.
Why the practice exists (failure mode it addresses)
This practice exists to prevent “stuck” decisions where frontline concerns cannot move upward due to cultural or structural barriers. It also prevents conflicts of interest—especially when local leaders are involved in the issue.
What goes wrong if it is absent
Staff hesitate to escalate, or escalation is delayed until the situation deteriorates. Incidents then appear as sudden failures rather than predictable escalation breakdowns.
What observable outcome it produces
Earlier executive visibility of high-risk situations, faster corrective action, improved safeguarding timeliness, and clearer evidence of organizational learning when issues recur.
Operational Example 3: Decision Assurance Audits, Not Just Outcome Audits
What happens in day-to-day delivery
Executives implement periodic decision assurance audits that sample a defined set of high-stakes decisions (e.g., admissions with complex risk, restrictive practice authorizations, exception staffing approvals, safeguarding thresholds). Audits examine whether the right person made the decision, whether criteria were applied consistently, whether escalation triggers were used appropriately, and whether documentation supports defensible reasoning. Findings are tracked to action plans and reported to the relevant board committee.
Why the practice exists (failure mode it addresses)
This practice exists because outcome-only oversight can miss dangerous decision drift. A service can appear stable while decision quality worsens, until a triggering incident exposes the weakness.
What goes wrong if it is absent
Executives lack early evidence of inconsistency or bias in decision-making. When failures occur, the organization cannot demonstrate that it had controls to ensure appropriate delegation and escalation.
What observable outcome it produces
Improved consistency, better documentation, earlier identification of training needs, and stronger defensibility under external scrutiny.
Oversight Expectations Executives Must Meet
Expectation 1: Boards must be able to evidence effective control of delegated authority. Governance bodies are often judged on whether they set boundaries, monitor compliance with those boundaries, and respond when boundaries are breached.
Expectation 2: High-risk decisions must have an auditable trail. Funders, auditors, and regulators routinely expect organizations to evidence not only what happened, but why decisions were made and whether they were authorized appropriately.
Practical Controls That Keep Delegation Safe
- Standardize criteria for high-stakes decisions so decisions are not personality-driven.
- Make escalation culturally safe by training leaders to reward timely challenge.
- Report delegation exceptions to the board (patterns matter more than isolated events).
- Review authority models after restructures because drift often follows organizational change.
Delegation should increase speed without reducing control. Executives achieve this by making decision rights explicit, escalation automatic where needed, and assurance focused on the quality of decision-making—not just end results.