Key Takeaways

Informal peer conversations produce impressions that die in budget meetings. A structured process with specific questions surfaces the operational metrics your COO needs to approve spending.
Matching peer facilities on security profile — facility type, acuity, campus layout — determines whether the evidence you collect is credible enough to justify investment at your organization.
A one-page findings summary that connects response times and coverage data to organizational costs gives executive leadership something they can act on immediately.

To build a budget case your COO will approve, you need peer security data from comparable behavioral health facilities. Impressions from a conference hallway won't survive the scrutiny. This guide gives you a repeatable process for collecting security safety outcomes from peer directors, interpreting what you hear, and packaging findings that connect to organizational costs.

What Structured Peer Outreach Produces

Structured outreach changes what you collect. Instead of impressions, you get specific numbers: response times, coverage percentages, false alarm rates, adoption data. ROAR deployments across 350+ behavioral health facilities show what those numbers look like when measured. In those facilities, 93% of incidents resolve in under two minutes [1].

Structured calls surface that kind of metric. Hallway conversations produce impressions.

Think of it like the difference between checking your bank balance and guessing what's in your account. One survives a budget meeting. The other doesn't.

Before you start, confirm these prerequisites:

Your own facility's incident rates, response times, and current coverage gaps (you need a baseline for comparison)
A list of 5-8 peer contacts from your IAHSS network or vendor reference lists
Calendar access for scheduling 3-5 calls over 2-4 weeks
A security supervisor available to assist with site visit observations

Can you name your own facility's average response time right now? If you can't, pull that number before your first peer call. You can't evaluate someone else's metrics without knowing your own.

Matching Facilities by Security Profile

A peer at a 20-bed psychiatric unit inside a 400-bed general hospital operates in a fundamentally different security environment than you do at a standalone facility. Regulatory requirements differ between standalone psychiatric hospitals and psychiatric units within general hospitals [2]. Matching on bed count alone produces misleading comparisons.

Psychiatric settings face 110.4 incidents per 10,000 workers, far above any other healthcare environment [3]. That severity makes precise matching essential.

Match on at least three of these five criteria:

Facility type: Standalone psychiatric hospital vs. psychiatric unit within a general hospital
Acuity and patient mix: Ratio of involuntary to voluntary admissions
Campus layout: Single building vs. multi-building, including outdoor transition areas and parking structures
Security staffing model: In-house vs. contracted, 24/7 vs. limited hours, armed vs. unarmed
Current technology: What duress or alerting systems are already in place, and whether coverage reaches every area of the facility

Verbal and physical abuse from patients accounts for 30.6% of top risks in behavioral health security [1]. Your peer facility should share that risk profile. If it doesn't, weight the evidence lower.

Can you name at least three criteria that make your selected peer comparable, and at least one way it differs? That distinction matters when you present findings.

Seven Questions for Peer Security Directors

On a 30-minute reference call, these seven questions surface metrics instead of impressions. Ask them in this order if time is short. The first three produce the most executive-relevant data.

#	Question	What It Surfaces	What a Strong Answer Sounds Like
1	What's your average time from alert to responder arrival?	Response time	"Under two minutes, verified by alert logs"
2	Are there any areas where staff can't activate an alert?	Coverage gaps	"Full facility coverage, including stairwells and parking"
3	What percentage of alerts turn out to be accidental or false?	False alarm rate	A specific percentage, not "very few"
4	Has the system gone down during an actual incident?	Reliability	"99.9% uptime, SLA-verified"
5	What percentage of staff carry or wear the device on a typical shift?	Adoption rate	A number above 85%, with context on privacy concerns
6	Did incident reporting rates change after deployment?	Reporting culture	Specific before/after numbers
7	What was the biggest unexpected result, positive or negative?	Implementation realities	Candid answer with specifics

Currently, 81% of workplace violence incidents in healthcare go unreported [4]. Question 6 matters because it reveals whether the system changed that pattern or left it intact.

See how one behavioral health provider documented these results across their facilities.

After each call, check: did you get a specific number for response time, coverage, false alarm rate, and adoption? Or just a general impression? If you got impressions, schedule a follow-up or find a better-matched peer.

When Peer Answers Raise Concerns

Two peers will sometimes give you opposite feedback. One reports fast response times and high adoption. The other describes staff resistance and unreliable coverage. The difference usually falls into one of three categories:

Category	Signals to Listen For	What to Do
Vendor problem	System failures during emergencies, coverage gaps the vendor promised to fix, unresponsive support	Ask a third peer. If the pattern repeats, it's the vendor.
Implementation problem	Low adoption despite good technology, inconsistent use across shifts, staff complaints about training or privacy	Ask about the rollout process and leadership support. Privacy concerns are the most common barrier to wearable safety technology adoption [5].
Environment mismatch	The peer facility doesn't match yours on three or more criteria from Section 2	Weight this feedback lower. Seek a better-matched peer.

One diagnostic signal stands out. 44.8% of nurses report that their employers ignore violence incidents after they're reported [6]. If a peer's staff say the same thing post-deployment, the system hasn't changed the culture.

When staff still feel ignored after deployment, the implementation failed. The technology worked as designed. Power outage resilience is another signal worth asking about. If a peer reports the system stayed live during an outage, that's a reliability indicator worth documenting separately.

Can you distinguish whether negative feedback reflects a vendor problem, an implementation problem, or an environment mismatch? If you can't yet, ask more questions before recording the finding.

A behavioral health safety specialist can help you identify matched peer facilities for your reference calls.

Presenting Security Safety Outcomes to Executive Leadership

Your COO and CFO don't need your raw call notes. They need a one-page summary that connects what you found to costs they already track.

Metric	Your Facility Baseline	Peer Facility Result	Cost Connection
Response time	[Your current average]	Under 2 minutes	Each minute of delay increases injury severity and workers' comp claims
Coverage	[% of facility covered]	100% facility coverage	Dead zones create liability exposure in areas staff avoid
Incident reduction	[Current trend]	40% reduction in staff assaults [1]	Fewer assaults reduce injury costs and overtime backfill
Staff retention impact	[Your turnover rate]	Measurable improvement: ask for before/after numbers	Healthcare workers frequently cite safety concerns as a reason for considering leaving their roles [6]

Fill in your baseline from your own data. Fill in peer results from your calls. The cost connection column translates operational metrics into language your CFO already uses.

Your job is to present the operational evidence with cost connections. Your CFO builds the financial model. You provide the inputs.

Task	Who Owns It	CSO's Role
Peer facility selection	Corporate security sets criteria	Approve final list based on comparability
Reference calls	Corporate security conducts	Personally conduct 2-3 calls to assess credibility
Site visit observations	Security supervisor documents	Personally observe response drills and staff interactions
Findings compilation	Corporate security compiles	Review, validate, and sign off
Executive presentation	CSO presents to COO/CFO	Own the presentation and answer operational questions

Compressed timeline (1 week): If your COO needs evidence before next month's budget meeting, match on acuity and bed count only. Conduct two phone calls using questions 1, 2, and 5. Ask for ranges if peers can't provide exact metrics. Flag assumptions clearly: "Based on 2 peer calls matched on acuity and bed count. Full matching to follow in Q[X]." Complete in five business days: Day 1 identify and schedule, Days 2-3 conduct calls, Day 4 compile, Day 5 finalize.

You don't need to fix everything by next quarter. Start with one well-matched peer call and one clean findings page.

You now have a process that turns peer conversations into documented evidence. Your next reference call has seven questions calibrated to your security priorities. Your next site visit has a checklist. And your next budget request has a one-page summary connecting security safety outcomes to costs your COO and CFO already track.

PEER EVIDENCE