Coordination with law enforcement is often treated as a binary choice: call the police or do not. In reality, safeguarding situations sit across a wide spectrum of risk, urgency, and legal complexity. Within Interagency Safeguarding Coordination, providers must design clear operational rules for when police involvement is necessary, how information is shared, and how provider responsibilities continue after law enforcement engagement. This work directly intersects with Restrictive Practices Governance, because poorly designed police interfaces often result in unnecessary restrictions, rights breaches, or avoidable criminalization.
Oversight expectations shaping police coordination
Expectation 1: Police involvement must be threshold-based, not fear-driven
Oversight bodies expect providers to demonstrate that law enforcement engagement is triggered by defined risk thresholdsâimminent danger, serious crime, or statutory requirementânot staff anxiety or reputational concern. Providers must evidence why police involvement was proportionate and necessary.
Expectation 2: Provider safeguarding responsibility does not end when police are involved
Commissioners and regulators expect providers to continue safeguarding activity after police engagement: stabilizing the person, coordinating follow-up care, and reviewing risk controls. âWe handed it to policeâ is not an acceptable endpoint.
Designing a lawful, practical police interface
An effective operating model separates three decisions that are often wrongly collapsed into one:
- Is there immediate danger requiring emergency response?
- Is there a suspected crime requiring police notification?
- What ongoing safeguarding actions remain the providerâs responsibility?
Clear separation prevents both over-policing and safeguarding drift.
Operational Example 1: Imminent violence risk in a supported living setting
What happens in day-to-day delivery: Staff observe escalating agitation, threats toward others, and access to potential weapons. The on-call supervisor conducts an immediate risk assessment using predefined criteria for imminent harm. Emergency services are contacted with concise, factual information: location, nature of threat, known triggers, and immediate risks. Simultaneously, non-police safeguards are activated: removing other residents from proximity, de-escalation attempts by trained staff, and clinical escalation if applicable. All actions are logged in real time.
Why the practice exists (failure mode it addresses): The model prevents the common failure of delaying emergency response while staff debate consent, or conversely calling police without first attempting proportionate de-escalation.
What goes wrong if it is absent: Delayed response can result in serious injury; premature police involvement can escalate distress, increase use of force, and damage long-term engagement.
What observable outcome it produces: Faster, safer crisis resolution, reduced injury risk, and documentation demonstrating proportionate escalation and parallel safeguarding actions.
Operational Example 2: Alleged assault by a family member
What happens in day-to-day delivery: A person discloses an assault by a family caregiver but is unsure about police involvement. Staff record the disclosure using objective language and assess immediate safety. The safeguarding lead explains options, including police reporting, APS referral, and protective planning. With consent, APS is notified. Police involvement is deferred unless required by law or safety escalation. Interim safeguards are implemented: alternative care arrangements, increased monitoring, and support planning. The decision not to involve police immediately is documented with rationale and review triggers.
Why the practice exists (failure mode it addresses): This approach prevents automatic criminalization while still ensuring protection and preserving future escalation options.
What goes wrong if it is absent: Automatic police referral can deter disclosure and fracture family systems; failure to plan safeguards can leave the person exposed.
What observable outcome it produces: Increased engagement, sustained safety, and a defensible record showing informed, proportionate decision-making.
Operational Example 3: Police involvement following property damage and behavioral crisis
What happens in day-to-day delivery: After significant property damage during a behavioral episode, staff assess whether a crime has occurred and whether there is ongoing risk. Police are contacted for incident documentation, not immediate enforcement. The provider shares minimum necessary facts and clarifies the personâs disability context and support needs. Following police departure, the provider convenes a multi-disciplinary review to adjust support plans, environmental controls, and crisis prevention strategies.
Why the practice exists (failure mode it addresses): Without clarity, police calls can substitute for clinical or behavioral planning, embedding a cycle of repeated law enforcement involvement.
What goes wrong if it is absent: Repeated criminalization, escalation of restrictive responses, and loss of housing or placement stability.
What observable outcome it produces: Reduced repeat police contacts, improved behavioral stability, and clear evidence of learning and plan adaptation.
Governance controls that prevent misuse
Strong providers audit police contacts quarterly, reviewing thresholds used, information shared, and post-incident safeguarding actions. Patternsâsuch as repeated calls from the same settingâtrigger system redesign rather than blame.
Key leadership test
If staff cannot clearly explain when police involvement is required, optional, or inappropriateâand what safeguarding continues afterwardâthe operating model is not yet safe.