If you are a hospital administrator, you have a workplace violence prevention plan, and it is probably a good document. It was written to satisfy accreditation and regulatory expectations, it has a risk assessment behind it, it names a committee, it describes training, and it lays out what staff should do when a patient or visitor becomes aggressive. Workplace violence in hospitals is one of the most serious risks you carry, and the plan on paper reflects that. What I want you to consider is that the plan on paper is almost never the plan that runs when a nurse is being threatened at the triage desk at three in the morning.
I have spent my career in law enforcement, fire service, private security, and federal government, and I have learned that every organization has two plans. One is written and reviewed and filed. The other is what people actually do under pressure, shaped by staffing, habit, fear, and whatever worked last time. In a hospital, the distance between those two plans is where nurses get hurt, where officers get blamed, and where the board learns after the fact that the program it approved was never really operating. This is a structural problem. The clinical staff and the contracted officers are doing their best with what the structure gave them.
What the Plan on Paper Says
The written plan typically says that staff will recognize warning signs, use de-escalation techniques, activate a panic alarm or call a code, and that security will respond within a defined time. It says that patients with a history of violence will be flagged in the record and that the flag will follow them. It says that behavioral health patients boarding in the emergency department will be observed according to protocol. It says that incidents will be reported, reviewed by a committee, and used to improve the program. It says that staff will be trained on all of this at orientation and annually.
Every sentence of that is reasonable, and a surveyor reading it will find a hospital that has taken the risk seriously. The document was built by people who understood the expectations and met them. That is precisely why it is dangerous, because a well-written plan produces confidence, and the confidence is not supported by anything that has been tested.
What the Plan That Runs Looks Like
On the night shift in the ED, the plan that runs looks different. The panic alarm at the triage desk rings at a security post that may be staffed by one officer covering the whole campus, who is at that moment in the parking structure or escorting a patient to behavioral health. The nurse who was trained in de-escalation eleven months ago is alone with a patient who has been boarding for two days and has just been told there is still no bed. The flag in the record was placed by a different hospital in the same system and does not display in this one. The charge nurse decides not to call a code because the last three times it took twelve minutes for anyone to arrive and the situation had resolved itself, badly, by then.
The incident is reported, or it is not, depending on whether the nurse believes reporting will change anything. If it is reported, it goes into a system that HR owns, and the guard vendor keeps a separate log, and the ED keeps its own notes, and the committee sees a summary a month later. The pattern that connects a specific patient, a specific hour, and a specific staffing level never becomes visible, because no one is looking at all three sources at once. This is the plan that actually runs, and it is invisible to the people who approved the one on paper.
Why Workplace Violence in Hospitals Resists the Written Plan
The written plan assumes a level of resources and coordination that the night shift does not have. It assumes officers are available, and the guard contract that facilities negotiated on cost was built around lobby coverage rather than ED response. It assumes flags follow patients, and the record system was configured by IT without anyone from security in the room. It assumes staff will activate the alarm, and staff have learned that the alarm produces nothing. It assumes training changes behavior, and training delivered once a year on a computer module does not survive contact with a real threat.
Most of all, the written plan assumes someone owns it. In most mid-sized hospitals, the workplace violence plan belongs to HR because it was written as an employment policy, the response belongs to a guard vendor that reports to facilities, the highest-risk unit belongs to the ED director, and the committee meets quarterly with no one at the executive level accountable for whether the plan works. A plan with five owners has none, and a plan with no owner is a document.
Until Tested, the Plan Is Only Assumed
The only way to find out which plan your hospital is running is to test it, and I mean test it in the conditions where it matters. My book Until Tested: Security Is Only Assumed is built on the principle that a control you have not tried to defeat is a control you are assuming, and the workplace violence plan is the most consequential assumed control in a hospital. Pick a night shift and, with the ED director’s knowledge and the vendor’s cooperation but without warning to the floor, activate a panic alarm and time the response. Walk the unit and ask a nurse to show you how they would flag a patient and where that flag appears. Ask the officer on duty what the post orders say about ED response and what the officer would actually do if the alarm went off while they were across the campus.
Then pull the last six months of incident reports from HR, the guard vendor, and the ED into one file and read them together. Look for the incidents that appear in one source and not the others, because those are the ones the committee never saw. Look for the time of day and the staffing level when they happened. What you will find, in most hospitals, is a program that is far weaker than the document and a set of staff who have known that for a long time and stopped saying so.
Closing the Distance Between the Two Plans
The fix begins with a single accountable owner at the executive level, someone who reports to the COO or CEO, who holds the plan, the response, the vendor, and the reporting as one program. That person should rewrite the post orders so that ED response is a defined duty with a defined time, and should renegotiate the guard contract if the current coverage cannot meet it. They should sit with IT and make the violence flag display everywhere a patient can appear. They should replace annual computer training with short, scenario-based practice run on the unit with the officers who will actually respond, so that nurses and officers have met each other before the night it matters.
They should also merge the incident data into one system and report it to the board quarterly, with the response times and the failed tests included. Boards do not need to hear that a plan exists. They need to hear how long it took an officer to reach the triage desk the last time someone tested it, and what changed as a result. When a hospital can answer that question, the plan on paper and the plan that runs have started to become the same plan. Until then, the hospital is asking its nurses to carry the difference.
Go Deeper
Owning the workplace violence program the way I have described is an executive job, and many mid-sized hospitals cannot fund it full-time. The fractional model exists for that situation, and I explain it in What Is a Fractional Security Director? The Complete Guide. My book Fractional Security Director lays out how a part-time executive takes ownership of a program like this, tests it, and gives the board a real answer.
Commissioner William Epps is a former elected Fire Commissioner, federal law-enforcement supervisor, and firefighter since 2006, with instructor credentials in Hazardous Materials response, Active Shooter preparedness, and Stop the Bleed®. He spent seven years in federal law enforcement in physical security, executive protection, and incident command, and now serves organizations as a Fractional Security Director. He is the author of The Spirit of Saul, The Spirit of Pharaoh, and other practical books on security, leadership, and faith, built around one idea: knowledge should be practical enough to use when it matters.
Leave a Reply