15.3 Post Orders, Uniforms/Equipment & Non-Security Awareness

Post Orders, Uniforms and Equipment, and Non-Security Awareness

Independent OpenExamPrep teaching for published PSP Domain 3 Task 4 knowledge is that personnel fail in writing before they fail in the lobby. Orders tell the post what to do. Uniforms and equipment make the post visible, reachable, and limited to what policy issued. Security awareness for non-security personnel is how the rest of the building stops defeating the post with a smile and a held door.

Exam focus: General, post, and special orders are different documents with version control. A good post order has purpose, duties, emergency, notifications, and prohibited actions. Awareness for clerks and nurses is tailgating, clean desk, visitor challenge, piggybacking, and dumpsters—not a second police academy.

Three kinds of orders

General orders are the site-wide or program-wide rules that apply no matter which chair you sit in: code of conduct, radio discipline, use-of-force policy at a high level, visitor philosophy, what to do if you find a weapon, media rules, confidentiality, and the fact that you do not invent arrest powers. They change slowly. Every person on the security program acknowledges them. They are the constitution of the force, not the job description of the dock.

Post orders are the this-station document: why this desk, dock, SOC console, or rover route exists, what “good” looks like on a quiet Tuesday, and what is forbidden even if it would be convenient. If general orders are the constitution, post orders are the job description for one node in the defense. A lobby post and a generator-yard rover should not share a copy-paste paragraph that never names the asset.

Special orders are time-bounded instructions: a commencement gate, a construction fence, a VIP visit, a weather shutdown, a strike, a system outage that puts extra people on Door 4. They have a start and an end, or a clearly named trigger. When the trigger dies, the special order must retire so nobody is still running last year’s parade rule on an ordinary Monday.

Mixing the three is how officers inherit contradictory folklore. A special order scribbled on a pizza box, a post order last updated when the building had a different tenant, and a general order that nobody can find on the shared drive is not a personnel program. It is residual risk with a logo.

Version control is an integrity control

Orders are controlled documents. Implementation looks like this:

• A document owner (typically security management) and a review cycle.
• A version number and date on every page, including attachments and maps.
• Distribution to the posts that need them, including the contractor’s copy if labor is contract.
• Acknowledgment—signature or system attestation—when issued and when revised.
• Retirement of superseded versions so the night shift cannot choose the friendlier old page.
• A place the console and the supervisor can produce the current set at 02:00 without calling someone who is asleep.

If an incident happens, investigators and courts will ask which order was in force. “We talked about it in the briefing” is not version control. Briefings can highlight a special order; they do not replace it. A whiteboard note is a reminder, not a record.

Contract sites fail this often: the owner updates a PDF, the vendor’s local office prints last quarter’s binder, and the officer on post has neither. Put document control in the statement of work. Audit the binder the way Chapter 14 audits as-builts. If the issued set and the binder disagree, the post will follow whichever page is easier, and you will discover which one that was after the loss.

Proprietary sites fail it differently: a long-serving supervisor “knows how we really do it” and never writes the exception. That oral tradition is a special order that never expires. Write it or kill it.

What a good post order contains

A usable post order is specific enough to train and to discipline against. Minimum contents for PSP-style practice:

1. Purpose of the post. One or two sentences tied to residual risk: “This lobby post challenges visitors and protects the badge plane so unescorted strangers do not reach the clinic corridor.” If you cannot write a purpose, the post may be theatre (section 15.1). Purpose is how a new officer knows which duty to drop last when two radios call at once.
2. Duties in normal operations. Opening, relief, patrol pattern or fixed-point rules, visitor processing, package handling, key and card control at this station, logging, radio checks, who covers lunch. Name the doors. Name the hours. “Monitor the area” is not a duty.
3. Emergency actions. Fire, medical, workplace violence as defined by this site, infant abduction if applicable, power loss, bomb threat per the site emergency plan—pointers to the plan, not a novel. What this post does in the first minutes, and what it must not do. Do not search a bag because a rumor started. Do not turn a fire-evacuation post into an investigative hold.
4. Notifications. Named console, supervisor, facilities, law enforcement, client contact, after-hours tree. Time expectations where they are real (“notify the SOC immediately on door-forced”), not fantasies (“police will arrive in three minutes on a rural road”).
5. Prohibited actions. No props on supervised doors, no off-post wandering, no personal guests, no inventing searches or arrests, no force tools except issued and trained, no posting photos of incidents, no silencing alarms to “clean up the board.”

Add what the occupancy needs: a drawing of the area of responsibility, an authorized lockup list, vehicle-gate rules, dual-control restock, who may waive a visitor badge (almost nobody). Write in shall language the officer can fail. “Maintain a professional presence” without a duty list is a poster, not an order.

That table is the one to carry into items that ask which document to write. A new camera in the lobby is not automatically a new general order. A one-week strike gate is not a rewrite of the constitution. A purpose-less “be alert” paragraph is not a post order. If the stem describes a commencement weekend, look for a special order. If it describes how every officer talks on the radio, look for general orders. If it describes the dock attendant’s lunch relief and Door 4, look for post orders.

Uniforms and equipment

A uniform is a deterrent and an identifier. It tells the public who to ask and tells an adversary that the opening is watched. Appearance standards—neat, complete, credential visible—are not vanity. A sloppy or incomplete uniform reduces deterrent value and confuses staff who are supposed to challenge people out of uniform in restricted space. Contract and proprietary programs should not look like two different armies unless you intend that signal (for example, a clearly marked visitor-escort role versus an after-hours rover).

Uniforms also create impersonation risk. Control issue and recovery the way you control badges. A lost shirt with your logo is a social-engineering tool. Collect uniforms at termination with the same energy you collect keys.

Equipment is what makes the post able to observe, report, delay, and render aid—only as policy issues it:

• Communications. A radio or equivalent that actually reaches the SOC, with spare batteries and a check at the start of shift. A uniform without a working radio is an isolated person, not a network. Earpieces, spare batteries, and a backup phone path belong in the issue list if the building eats radio signal.
• Medical. Gloves, a kit the training matches, automated external defibrillator locations known. Do not write “provide trauma care” into orders if you did not train or equip it.
• Observation and recording. Flashlight, notebook or issued device, sometimes binoculars or a camera per policy. Personal phones are a leak and a distraction unless the program issued a managed device with a photo rule.
• Use-of-force tools (restraints, chemical spray, baton, firearm, conductive device): policy, licensing, training, inventory, storage, and after-action review—or they do not belong on the belt. This independent chapter does not teach tactics. The exam idea is that tools follow authorization, not officer preference. An unarmed post that “just bought a baton at a surplus store” is a discipline event, not a countermeasure.

Issue lists belong in the post order or an annex. Shift inventory—radio in, radio out—is a control. Broken gear is a work order, not a reason to stand a blind post silently. If the only radio is dead, the post’s fail state is the same as a camera with no recording: you either repair, replace the person to a working post, or accept residual risk in writing. You do not pretend the shirt was enough.

Appearance as deterrent still has a limit. A perfect uniform in a theatre hut (section 15.1) deters only the adversary who never tests the radio. Pair the look with the duty and the equipment.

Security awareness for people who are not security

Most tailgating is performed by employees being polite. Non-security awareness is therefore a personnel countermeasure even when the audience is nurses, clerks, faculty, and warehouse leads. It is not a mini-academy in detention. Domain 3 Task 4 includes this layer because electronics and officers lose when the culture holds the door.

Teach, drill, and measure a short list:

• Tailgating. Following an authorized person through a controlled door without presenting a credential. Staff should let the door close, not hold it for a stranger with coffee, and should not badge in a group as a favor. Tailgating is how a visitor becomes an insider without a host.
• Piggybacking. The cousin of tailgating: two people using one authorization event, often with social pressure (“I’m with her”). Same counter: one credential, one entry, challenge the second person. Vehicle gates piggyback too—two cars on one arm cycle.
• Visitor challenge. A polite “may I help you find your host?” in restricted corridors. Challenge is customer service plus detection. It is not a citizen’s arrest. Teach who to call when the answer is wrong, and teach that a badge under a coat is still a challenge opportunity, not a reason to start a fight.
• Clean desk. Badges, clinical lists, vendor invoices, passwords, and visitor logs do not overnight on a public workstation. This is residual information sitting in the physical layer. A rover who ignores an open badge printer is missing a post duty; a clerk who leaves the printer’s rejects in a tray is missing awareness.
• Dumpster and residual documents. Paper that missed shredding, badge-printer rejects, wristbands, shipping manifests. Dumpster diving is still a physical-security how. Awareness includes shred and control, not a lecture on forensics. Loading-dock dumpsters next to Door 4 are a pairing, not janitorial trivia.

Add what the site needs: shoulder-surfing at the badge desk, photographing screens, propping fire doors for smokers, following a vendor because the cart looks official. Measure with walk tests—does staff challenge a tester?—the way you field-test a camera. Do not measure with a once-a-year click-through that nobody remembers at the dock.

Awareness that tells clerks to fight, search, or arrest is the wrong product. Awareness that tells them not to participate in the bypass is the right one. Officers still own the post. Everyone else owns not holding the door.

Worked clinic: the best lobby officer in the city still loses if every nurse badges and then holds the leaf for anyone in scrubs. The awareness program is how you stop that courtesy from becoming the threat’s method.

Worked office tower: clean-desk and dumpster rules matter more than a decorative rover if the residual pairing is document theft. A night officer who walks a pretty lobby while confidential printouts sit in an unlocked recycle bin is protecting the wrong layer.

PSP practice questionsPractice questions with detailed explanations