Correctional Staff Safety in West Virginia: Plan the Response Behind the Button

Start with the facility and its responsibilities

West Virginia's Division of Corrections and Rehabilitation publishes separate facility information for its correctional settings. Use the appropriate facility and operating authority when assembling a project team; a generic statewide purchasing assumption is not a substitute for confirming ownership. Include custody leadership, medical leadership, facilities, IT, procurement, and staff representatives in the discovery conversation. Each should be able to explain what a successful alert means for their role.

Define the alert before choosing the device

Write down the approved purpose of the alert. Is it a staff request for assistance, a medical response request, or another facility-defined event? Decide which roles are notified and how escalation is handled when the first recipient is unavailable. Keep those routing details in controlled operational documents, not public marketing materials. A wearable and a fixed button can support different work patterns; neither should be selected without reviewing attachment, availability, cleaning, charging or battery procedures, and the facility's equipment rules.

Connect custody and medical response

The National Institute of Corrections' 2026 medical-emergencies webinar series emphasizes coordination between nonmedical correctional staff, supervisors, leadership, and medical services. Our planning recommendation is to turn that shared responsibility into a concise handoff: identify the event using approved terminology, establish who takes responsibility, and document when the response is closed. An alerting system supports trained staff and established clinical procedures; it does not provide clinical judgment or expand anyone's scope of practice.

Make the site test observable

Ask for an agreed test plan before accepting an installation. Verify the selected hardware and configured workflows in authorized test locations, across relevant shifts, with the people who will actually use them. Check whether location labels match the facility's naming convention and whether the intended recipients can acknowledge a test event. Record gaps, assign an owner, and repeat the affected tests after changes. Coverage, location behavior, integrations, and backup operation should be demonstrated for the proposed configuration rather than assumed from a brochure.

Budget for readiness after installation

A complete scope should identify onboarding, refresher training, replacement devices, software access, maintenance, and support responsibilities. Assign an owner to keep the authorized-user list and training records current. Plan how new staff learn the approved process and how a departing staff member's device and permissions are handled. These ordinary lifecycle tasks deserve the same attention as the first demonstration.

Bring a useful brief to the first conversation

Prepare a non-sensitive summary of your facility type, staff groups, existing communications tools, desired alert outcomes, and purchasing timeline. Do not send confidential layouts or response procedures through a public inquiry form. Alert Pro Solutions can discuss X-Wearable, fixed alert devices, and the XSponse ecosystem against that brief, with capabilities and integration scope confirmed during assessment.

Sources & further reading

Agency resources inform the context; the checklists above are Alert Pro Solutions' planning recommendations. They are not a facility operating procedure or a certification of compliance.

• West Virginia DCR facility directory
• National Institute of Corrections: Correctional Staff Response to Medical Emergencies