Behavioral health security should support a facility’s daily work without taking the place of clinical judgment or patient care. Administrators can build a safer, more respectful environment by defining the guard’s non-clinical role, planning communication with staff, and setting clear procedures for access, emergencies, and documentation.

Discuss security coverage for your facility

Call (833) 272-7247 to discuss facility security coverage.

What should behavioral health security accomplish?

A security plan in a behavioral health setting has to account for the people who use the facility, the staff who provide services, visitors, and the property itself. Its purpose is to help keep entrances and shared spaces orderly, notice potential safety concerns, communicate promptly, and support the facility’s established response procedures.

Security should not be presented as treatment, diagnosis, or a substitute for trained clinical staff. Guards do not make clinical assessments or decide a person’s care plan. The facility’s authorized personnel retain responsibility for clinical decisions. A security professional can observe what is happening, share relevant facts with the designated staff member, and follow the site’s approved instructions within the guard’s role and applicable law.

That distinction should appear in the written plan, post orders, orientation, and day-to-day conversations. It helps staff know whom to contact, helps the guard avoid acting outside the assigned role, and sets clearer expectations for visitors and patients. Administrators planning a broader physical security program can review ASAP Security’s overview of security guard services and adapt the discussion to the facility’s actual needs.

How can a visible presence remain respectful?

Visible security can help people find assistance and can make it easier to notice concerns early. But presence is not only about where a guard stands. Tone, distance, posture, word choice, and awareness of privacy all affect how an interaction feels. Administrators should describe the expected approach in plain language and discuss it with clinical and operations leaders before a post begins.

For example, the plan might direct guards to remain approachable near a reception point, avoid blocking a person’s path unless an immediate safety procedure calls for it, and speak in a calm, even tone. A guard can offer a simple direction or ask whether the person would like staff assistance, rather than pressing for personal details. The precise language should fit the facility’s policies and be reviewed by its leadership.

Respect also means recognizing that a person may not want to speak with security. A guard should know when to step back, when to notify designated staff, and how to avoid sharing sensitive information where others can hear. Do not use labels or assumptions in conversation or written reports. Describe observable actions and exact statements when relevant, rather than assigning motives or making judgments about a person’s condition.

Administrators can make the expected conduct concrete with short scenarios during orientation: a visitor who is unsure where to go, a person asking for help, a disagreement in a common area, or a concern raised by staff. The discussion should clarify whom to notify and what the guard may do under the site’s procedures. It should not teach clinical intervention or replace clinical training.

What does de-escalation mean for a guard’s role?

In a security plan, de-escalation is best treated as a communication approach and a defined limit on unnecessary confrontation, not as a promise that every situation can be resolved through conversation. Facility leaders should set expectations for calm communication, keeping a safe and appropriate distance, listening without arguing, and calling the designated staff member when a concern may require clinical attention.

Practical preparation begins with the facility’s own procedures. Which staff role should be called first? What channel should be used? What information is useful to share? Where should people go if staff initiate a response? Which actions are outside the guard’s authority? Written answers to those questions are more useful than vague directions such as “handle difficult situations.”

Guards should avoid making promises, threatening consequences, debating a person’s experience, or trying to compel cooperation beyond their assigned authority. If communication is not helping, the plan should identify how to create space, alert staff, and follow the facility’s escalation process. Any use of force, restraint, or other restrictive response is governed by applicable law and facility policy; administrators should not assume that a security provider is authorized to perform a clinical or restrictive intervention.

Before service starts, ask the provider to explain how it prepares staff for the specific post, what the guard will and will not do, and how concerns are raised when instructions are unclear. Training descriptions should be verified rather than assumed. The facility should also provide site orientation and document any local procedures the guard must know.

Call (833) 272-7247 to review non-clinical guard responsibilities.

How should access control protect privacy and safety?

Access control is not simply keeping people out. A well-designed process helps authorized visitors reach the right place while protecting private areas and limiting confusion at entry points. The plan should distinguish public areas, staff-only areas, and any other access zones the facility defines. It should also identify who can approve exceptions and how a guard verifies an instruction when unsure.

• Set entry expectations. Identify the entrance to use, any check-in steps, and how the guard directs people who arrive at the wrong door.
• Define credentials and permissions. Explain what a guard may check, who can grant access, and what to do when a badge, list, or instruction does not match.
• Protect sensitive information. Limit what is spoken aloud or recorded at the entrance. Guards should not request or disclose clinical details unless a specific facility procedure and lawful role require a particular action.
• Plan for deliveries and contractors. Give staff a clear way to confirm expected arrivals without leaving the guard to make assumptions.
• Document exceptions. Specify which access issues should be recorded and who reviews them.

Walk the property with facility leaders before finalizing a post. Check sightlines, visitor flow, doors that should remain secured, and points where people may become confused. Include after-hours conditions and changes in staffing. A physical presence can support an access process, but it does not replace working locks, visitor policies, or staff oversight.

Some facilities may also consider cameras or monitoring as a separate layer. If evaluating that option, clearly define who reviews alerts and responds. ASAP’s pages explain its CCTV system installation and 24/7 CCTV monitoring offerings; administrators should confirm how any technology fits their own privacy, consent, and records policies before adopting it.

How should guards coordinate with facility staff?

Coordination works best when names, roles, and communication routes are known before a shift begins. The guard should know the designated on-site contact, the backup contact, and how to reach them. The facility should know who is assigned to the post and how to reach live dispatch if a concern needs operational support. Avoid making the guard guess which person has authority to change an instruction.

Write down the normal communication cadence. For example, the site may require a check-in at shift start, a report of a defined access issue, and a handoff at shift end. The exact cadence should be set by the facility based on operations, not imposed as a generic rule. Confirm radio or phone coverage in the areas where the guard will work, and have a backup method if the primary channel is unavailable.

Every handoff should share only information needed for the next shift’s duties. That may include an unresolved door issue, an expected contractor, or an incident reference for the staff contact. It should not become an informal exchange of sensitive personal or clinical details. Facility leaders should determine the appropriate recordkeeping and privacy rules for each type of information.

ASAP Security describes its service model as including 24/7 security coverage and a live dispatch line. Ask any provider how dispatch and on-site personnel communicate, what gets recorded, and how the facility receives updates. The provider should explain the process without suggesting that notification alone guarantees a particular outcome.

What belongs in emergency coordination procedures?

Emergency coordination must fit the facility’s established plan. Security personnel should not create a separate response system or decide clinical priorities. Instead, the post orders should identify how to notify the designated staff, when to contact emergency services under the facility’s instructions and applicable law, which entrances responders should use, and who will meet them.

Administrators can map a few operational scenarios without assuming clinical details: a fire alarm, a person needing urgent assistance, an unauthorized entry, a disruptive visitor, or an incident that affects more than one area. For each scenario, confirm the first notification, backup contact, communication channel, and the guard’s limits. Keep instructions concise enough to use under pressure and consistent with the site’s emergency plans.

Coordinate the written plan with the people responsible for clinical operations, facilities, privacy, and emergency management. Determine whether drills or briefings are appropriate, who leads them, and how changes are communicated. If a procedure changes, update the post orders and acknowledge the revision with the people assigned to the site.

Workplace safety resources from the Occupational Safety and Health Administration can be one starting point for administrators reviewing workplace safety responsibilities. A general resource does not replace legal advice, facility-specific planning, or consultation with qualified professionals.

What should security documentation include?

Useful documentation is timely, factual, and limited to what the facility needs to understand the security activity. A report should identify when and where an event happened, who was notified by role or name as allowed by policy, what the guard directly observed, what steps were taken under the post orders, and whether the matter was handed off or remains open.

Separate observation from interpretation. “At 8:10 p.m., the west entrance door did not latch after closing” is more actionable than “the door was unsafe all night.” If exact words matter, quote them accurately and distinguish a direct quote from a summary. Avoid diagnoses, speculation about intent, unnecessary personal details, and conclusions about treatment or care.

Before service begins, agree on where reports go, who can view them, how quickly the facility expects notification for different kinds of events, and how corrections are handled. Do not assume that a vendor’s reporting platform automatically satisfies the facility’s recordkeeping, privacy, or retention requirements. Have the appropriate facility personnel review those requirements.

When comparing providers, ask for a sample report with personal information removed. Look for clear timestamps, location, neutral language, notifications, and follow-up status. ASAP Security describes using GPS-tracked Daily Activity Reporting. Review how digital activity reports differ from traditional guard logs and decide whether the information and access controls match the facility’s needs.

How can administrators compare coverage approaches?

The right arrangement depends on the facility’s hours, layout, entry points, visitor flow, and internal response capacity. A guard post, patrol, or a combination may each address different operational needs. The following comparison is a planning aid, not a recommendation to use one model in every setting.

Compare the written scope, not only the label applied to a service. Ask for the post schedule, assigned duties, supervisory contact, dispatch process, reporting sample, and change-control approach. If you are weighing armed or unarmed coverage, make that decision through the facility’s documented risk review and applicable requirements. ASAP publishes the approved ranges of $28–$45 per hour for unarmed guards and $35–$65 per hour for armed guards; actual service scope and proposal details should be discussed with the provider. Do not assume that an armed assignment is appropriate for a behavioral health environment.

What should administrators ask a security provider?

A useful provider discussion tests whether the company can follow a facility’s rules, communicate clearly, and stay within the agreed assignment. Ask specific questions and request written answers where they affect service delivery.

• What tasks will the guard perform, and which tasks are expressly outside the assignment?
• How will the provider orient personnel to this facility’s entry rules, contacts, communication channels, and emergency procedures?
• What preparation will guards receive for calm, respectful communication, and how is that preparation verified?
• How does on-site personnel contact dispatch and facility staff? What is the backup if a channel is unavailable?
• What does an activity report contain, who can access it, and how are sensitive details limited?
• Who supervises the assignment, how are concerns escalated, and how are post-order changes acknowledged?
• How should the facility report an issue with performance, and how will the provider document follow-up?

Request references or examples only through appropriate channels and protect confidential information. Verify any credentials or claims that matter to your organization instead of relying on broad marketing language. ASAP Security states that it provides physical, manned guarding and has 24/7 live dispatch; its Southern California service-area page can help administrators check geographic fit. The company also describes a GPS-tracked activity reporting system and in-house training academy. Confirm the scope and terms relevant to your facility during the proposal process.

How can a facility prepare before the first shift?

Good onboarding reduces confusion for staff and the assigned guard. Use a short launch checklist and assign an owner for each item. Do not wait until the first shift to resolve an unclear contact path or an access rule.

1. Walk the site. Identify the post location, authorized routes, visitor entrance, restricted spaces, and any areas requiring special instruction.
2. Write the post orders. State routine duties, prohibited tasks, contacts, notification steps, report expectations, and handoff requirements.
3. Confirm communications. Test channels in the relevant areas and choose a backup. Share dispatch and facility contact details only with authorized people.
4. Orient relevant staff. Explain what the guard is assigned to do, how staff request assistance, and who can approve a change.
5. Agree on records and privacy. Identify what gets documented, where it is sent, who can view it, and how the facility addresses corrections.
6. Review the first shifts. Set a check-in with the provider and facility lead to discuss whether procedures were followed and what needs clarification.

Keep the plan current when doors, staffing, hours, or site procedures change. A simple version date and named facility owner can help prevent outdated instructions from circulating. If an issue occurs, record the concern, who received it, and the next step. Clear follow-through is more useful than assuming a message was received or resolved.

How should responsibilities be defined in writing?

Post orders should translate the service agreement into instructions a guard can follow on a shift. They should identify the purpose of the post, ordinary duties, access rules, reporting steps, facility contacts, and limits. Avoid instructions that leave critical decisions open to interpretation, such as “use judgment” without naming who can give direction or what action to take when staff cannot be reached.

Use role names as well as individual contacts where possible. A named contact may be unavailable, while a role such as the on-duty administrator provides a clear backup path. Include the approved communication method for routine questions and for urgent notifications. The facility should decide which events require immediate notice, which can be included in a routine report, and how the guard confirms that a message reached the intended person.

Also state what the guard is not expected or authorized to do. Examples may include clinical assessment, treatment decisions, access to clinical records, or actions that belong to facility staff under the site’s policies. Have appropriate facility leaders review this language. If a staff member asks a guard to do something that conflicts with written instructions, the guard needs a safe way to pause, contact a supervisor, and seek clarification rather than silently changing the scope.

Keep the document usable. A concise quick-reference page can list emergency contacts, radio channels, and immediate notification steps, while a fuller set of post orders explains routine duties and reporting. Restrict distribution to people who need the information, and avoid placing sensitive personal or operational details where visitors can see them. Record when instructions were issued and when revisions were acknowledged.

How should shift changes and busy periods be handled?

Many facilities have different needs at arrival, visiting, meal, appointment, or closing times. Map the actual pattern of movement with facility staff instead of assuming that every hour is alike. Identify where queues form, which entrances are in use, and who can answer questions when several people arrive at once. A guard should know the priorities for the post and the staff contact to call when routine activity changes.

Shift handoffs deserve specific instructions. The outgoing guard can report unresolved maintenance or access issues, scheduled arrivals that have been confirmed by staff, and any open operational item that the next guard needs to know. The handoff should not become a casual discussion of patient histories or unverified reports. Facility leaders should set the permitted channel and minimum necessary detail for each type of information.

If relief is delayed or a guard cannot reach the post, the service agreement should say whom to notify and what interim steps are authorized. Managers should not assume that an absent person has been replaced until the provider confirms the coverage status. Similarly, when schedules change for a special program or building work, update the provider and the facility contacts through an agreed process and record the change.

Review the practical fit after the first shifts. Ask staff whether the guard was easy to identify, whether directions at entry were clear, and whether notifications reached the right person. Ask the provider whether any instruction was ambiguous or could not be followed as written. Use that feedback to clarify the plan, not to expand the guard’s role informally.

How should managers review whether coverage is working?

Review service against the written scope. Useful questions include whether the guard was present for the scheduled shift, whether required rounds or checks were completed, whether reports arrived through the agreed channel, and whether staff knew whom to contact. Review exceptions as well as routine activity. A quiet report does not by itself prove that a security plan is effective.

Agree on a practical review cadence with the provider and facility owner. For example, the first review can focus on orientation and unclear instructions; later reviews can examine recurring access issues, report quality, missed handoffs, or changes in site use. Keep the discussion factual and assign an owner to each action. Do not use a single incident count as a measure of success without considering reporting practices and context.

When a concern is reported, verify what happened, whether the designated person received the information, and whether follow-up occurred. Separate confirmed facts from items still under review. Update the post orders if the agreed process needs to change, and inform the people affected by the update. Managers can also consult ASAP’s security services FAQ and contact page when preparing questions about service scope.

Call (833) 272-7247 to discuss a coverage plan for your facility.

Request a discussion about facility coverage

Frequently asked questions

Can a security guard replace behavioral health staff?

No. Security is a non-clinical function. The facility’s authorized personnel remain responsible for care and clinical decisions. Define the guard’s role and escalation route in writing.

Should guards make clinical assessments?

No. A guard should report observable facts and contact designated staff under the facility’s procedures. Do not assign diagnosis, treatment, or clinical decision-making to security personnel.

Does every behavioral health facility need a fixed guard post?

No single coverage model fits every site. Consider operating hours, layout, access points, staffing, and the facility’s own risk review. Compare fixed coverage, patrols, technology, and internal procedures against the actual scope of need.

What information should a guard include in an incident report?

Follow the facility’s reporting rules. In general, agree in advance on the time, location, direct observations, actions taken under the post orders, notifications, and handoff status. Avoid speculation and unnecessary sensitive details.

How can administrators support respectful security?

Set clear conduct expectations, provide site-specific orientation, identify staff contacts, protect privacy, and review reports for factual, neutral language. Make sure guards know when to seek staff direction and what actions are outside their role.

How can you plan the next step?

Start by documenting what the facility needs security to do and what it must not do. Bring clinical, operations, facilities, and privacy leaders into the planning process, then compare providers on written responsibilities, communication, reporting, and follow-through. A clear, respectful plan gives staff and security personnel a shared understanding before coverage begins.