Many problems inside security operations do not begin with bad people or poor intentions. They begin with unclear direction. That direction usually comes in the form of bad security post orders.
In many organizations, security post orders are treated like a formality. They are written once, placed in a binder, and handed to an officer when they start a new assignment. After that, they are rarely reviewed unless an incident forces someone to revisit them.
But post orders do far more than outline procedures. They influence how officers make decisions, how authority is exercised, and how a security company ultimately represents itself to the client.
A story from hospital security shows exactly what can happen when security post orders exist without a clear process behind them.
When Security Post Orders Replace Judgment
An armed security officer working at a large hospital was assigned to the main entrance.
This was not a quiet location. The hospital was a busy trauma center in a rough part of town where real security issues happened regularly. Situations ranged from behavioral health patients becoming aggressive in the emergency department to individuals wandering into restricted areas or vulnerable patients getting lost inside the building.
The officer was used to handling real security concerns that required awareness and good judgment. Then a new instruction appeared in the security post orders.The officer was told to stand at the main entrance and prevent hospital staff from entering through that door.
The reasoning had nothing to do with safety. Someone in management had decided that employees should enter through a different door so the main entrance would appear less crowded for patients and visitors. Doctors, nurses, cafeteria staff, janitors, and facilities employees were all redirected to another entrance. Anyone who refused would have their name documented and reported.
From the officer’s perspective, the assignment felt unnecessary. It pulled attention away from legitimate security concerns and replaced them with administrative enforcement that had little to do with protecting the facility. Still, the security post orders were clear. So he followed them.
When Intent Collides With Reality
One afternoon, a well-dressed man approached the hospital entrance with several executives walking behind him. They all wore employee badges and appeared to be touring the facility.
The officer stepped forward and informed them that employees were required to use the West entrance. The man leading the group questioned the instruction and attempted to continue toward the doors. The officer explained that he was simply enforcing the security post orders. If they chose to enter anyway, their names would have to be recorded for follow-up. So he began writing them down. Each name. Carefully.
When the security supervisor later reviewed the list, one name immediately stood out. The individual leading the group was the Chief Executive Officer of the entire health system. The CEO had been escorting potential investors through the hospital and had never been informed that employees were no longer allowed to enter through the main entrance.
The moment was embarrassing for everyone involved. Not long afterward, the policy quietly disappeared and staff were once again allowed to use the front doors.
Common sense eventually prevailed. But only after unnecessary friction and reputational damage.
The Real Problem Was the Post Orders
It would be easy to blame the officer in this situation, but he did exactly what he was instructed to do. The issue was not enforcement. The issue was how the security post orders were created in the first place.
Security post orders define how officers interact with their surroundings. When those instructions are written without understanding the site’s operational reality, officers are left enforcing rules that were never properly thought through. That creates situations where officers must choose between common sense and compliance. In this case, compliance exposed the weakness in their post order system.
Every instruction included in security post orders should answer a simple question. What problem is this meant to solve?
If a rule cannot be tied to safety, risk reduction, or operational control, it probably does not belong in security post orders. Personal preferences and internal administrative decisions should not be enforced through front-line security officers. Security personnel should not be responsible for implementing policies that lack a legitimate security objective.
Security Post Orders Should Be Validated With the Client
Security rarely operates in isolation. Most organizations involve multiple layers of leadership and operational ownership. Any security post orders that affect how people move through a facility, access entrances, or interact with staff should be reviewed with the client leadership responsible for that environment.
In the hospital example, the CEO was unaware of a policy that directly affected how employees entered the building. That disconnect guaranteed the rule would eventually fail.
Proper review and validation prevent these types of situations.
Officers Should be Included
Another weakness in many organizations is that the officers expected to follow security post orders are rarely involved in reviewing them.
Experienced officers often recognize immediately when an instruction will create confusion, conflict, or distraction from more important security responsibilities.
Allowing officers to provide feedback helps ensure that security post orders reflect the realities of the environment rather than assumptions made in an office.
Even well written security post orders become outdated over time.
Facilities evolve, client expectations change, and procedures that once made sense may quietly become ineffective. For that reason, security post orders should be reviewed regularly rather than only when an incident occurs.
Routine reviews allow security companies to update procedures before they create operational problems. If officers consistently work around an instruction to perform their duties effectively, the instruction itself likely needs to change.
Why Post Orders Matter for Every Security Company
When post orders are supported by a disciplined process, they provide clarity instead of confusion. Officers understand their responsibilities, supervisors spend less time managing avoidable conflicts, and clients experience fewer surprises.
Post orders are not simply documentation. They represent how a security operation is intended to function. When they are poorly constructed, the consequences become visible quickly. Sometimes quietly. And sometimes at the front door of a hospital while a CEO is holding his badge and wondering why he cannot enter his own building.
Either way, the lesson remains the same. Security post orders deserve far more attention than they usually receive.
By Courtney Sparkman
Courtney is the founder and CEO of OfficerApps.com, a security guard company software provider, specializing in security guard management software, and publisher of Security Guard Services Magazine. He is a renowned author and security industry syndicator who also hosts an active YouTube channel, helping thousands of his subscribers to grow their security guard services companies.
