15.1 Roles, Limits, Proprietary vs Contract Staffing
Key Takeaways
- Officers, technicians, managers, and administrators are four staffing countermeasures, not one generic guard.
- Typical officer products are observe, report, delay when lawful, and customer service; arrest power is jurisdiction-specific and is not invented from a uniform.
- Use of force is a policy, training, documentation, and review topic, not a tactics catalog.
- Proprietary versus contract staffing trades control, cost, loyalty, surge capacity, liability administration, and licensing logistics; neither model erases the owner’s duty to specify the post.
- Keep a human post when judgment, challenge, or delay is required; a uniform in a chair with no purpose, radio, or backup is theatre.
Roles, Limits, Proprietary versus Contract Staffing
Independent OpenExamPrep teaching for published PSP Domain 3 Task 4 and Domain 2 Task 2 staffing knowledge is that people are a countermeasure, not leftover labor after the cameras are chosen. Chapter 7 already put an attendant in the operational requirement for Door 4. This chapter is where that person gets a role, a legal limit, a staffing model, and an honest answer to whether the post should exist at all.
Exam focus: Officers, technicians, managers, and administrators are four different countermeasures. Arrest power is not a universal gift of a uniform. Proprietary versus contract is a control-and-cost choice. A chair with a logo is not automatically delay.
Staffing as a designed countermeasure
A staffing countermeasure is a person—or a defined mix of people—assigned to produce deter, detect, delay, deny, or respond that hardware cannot finish. Presence can deter a casual thief. Observation and a radio can detect a propped dock. A trained officer in a choke point can delay someone who would walk through an empty lobby. Customer service at a badge desk can deny a visitor who has no host. Response is almost always a person: a console operator who dispatches, an officer who walks, a supervisor who locks down a wing.
If the residual pairing from Domain 1 still needs a human judgment call—challenge a stranger, hold a door closed, talk down a disorderly visitor, notice that the pharmacy anteroom is wrong—then omitting the post is a design decision, not a savings. The inverse is also true. If the pairing is fence-line detection at 03:00 on a dark perimeter, a bored officer in a hut with no radio coverage and no tour is theatre. Lighting, detection, and a real response force may be the honest layer. PSP-style items punish both errors: treating people as free, and treating people as magic.
Write staffing the same way you write a lock: purpose, hours, backup, fail state. “Security will handle it” is not a fail state. Lunch coverage is a fail state. A second officer on restock nights is a fail state. An empty post with a “back in 15 minutes” sign is an unlatched door wearing a uniform.
People also cost operating money every hour they stand. Chapter 6’s total-cost logic applies: wage, benefits or contract markup, overtime, training, equipment, supervision, and the vacancy that appears when someone calls out. A design that spends the capital line on cameras and leaves no funded post for the pairing that needs a challenge has not escaped the budget. It has hidden a detect-and-delay failure inside a pretty elevation.
Four role families, four jobs
Do not collapse “security personnel” into one generic guard. Domain 2 staffing as a countermeasure is a mix, the same way electronic measures are a mix of detection, assessment, and control.
Officers (and similarly titled posts: ambassadors, concierge-security, rover, console operator) stand or roam a defined area. Their typical lawful product is observe, report, delay when trained and authorized, and provide customer service. They enforce owner rules: who may enter, which door may be propped, how a visitor is signed, when a dock leaf may be unlatched. They are not a municipal police department because the company issued a shirt. Their value is early detection, lawful presence, and a human interface a lens cannot offer. “May I help you?” is often better delay than a tackle, and it creates a witness statement instead of a use-of-force file.
Technicians keep electronic and structural measures alive: cameras in focus, panels reporting, locks cycling, batteries tested, nuisance alarms diagnosed. A post that depends on a working radio and a supervised door contact is not staffed if the technician bench is empty. Technicians are a countermeasure against system decay, which Chapter 16 treats as lifecycle. In this chapter, remember that a proprietary or contract officer is a poor substitute for a certified technician, and the reverse is also true. Do not send the access-control tech to stand a lobby because you are short an officer, and do not send the lobby officer to “reboot the video wall” as if that were patrol.
Management designs the posts, the mix of proprietary and contract labor, the span of control, the escalation path, and the budget that keeps relief officers on the roster. Managers translate residual risk into headcount and hours. They also own the ugly decisions: which post is theatre, which post is non-negotiable, and when a camera plus a roaming supervisor replaces a 24-hour hut. A manager who cannot explain why a chair is occupied is running costume, not a countermeasure.
Administration is the unglamorous countermeasure that keeps the others legal: recruiting files, licenses, work-authorization documents, hours, payroll, insurance certificates, and the contract file if labor is outsourced. An officer who is not licensed where a license is required is not a countermeasure. That person is a liability event waiting for a plaintiff. Administration is how Domain 3 Task 4 actually gets implemented—not as a slogan on a slide, but as a hire that can lawfully stand the post on a holiday night.
| Role family | Countermeasure product | Typical failure if you skip it |
|---|---|---|
| Officers | Observe, report, delay, service, owner-rule enforcement | Empty choke point; nobody to challenge a tailgater |
| Technicians | Working systems, fewer nuisance alarms, tested hardware | Blind cameras, silent panels, radios that do not talk |
| Management | Posts, mix, supervision, escalation, funded relief | Theatre posts, no lunch coverage, no one to decide |
| Administration | Lawful hire, records, insurance, contract file | Unlicensed labor and an empty personnel folder |
Limits: do not invent police powers
Arrest, detention, search, and use of force are jurisdiction-specific. Private security authority is a creature of state or national statute, case law, license conditions, and owner policy—not of a shoulder patch. Independent study for this published task is explicit: do not invent police powers because the exam stem shows a uniform, a badge, or a firearm.
What officers can usually be trained and tasked to do, subject to local law and the post orders:
- Observe people, vehicles, and openings; remember and record what they saw, including times and directions of travel.
- Report to a console, a supervisor, law enforcement, or a client contact using the notification tree in the orders.
- Delay by presence, by locking a door they are authorized to lock, by asking questions, by standing in a lawful choke point—not by improvising a seizure in a parking lot.
- Customer service: badge desk, visitor processing, directions, a calm voice in a medical lobby. That service is security. It is how you learn who does not belong without turning every encounter into a confrontation.
What you do not assume as universal:
- The same arrest authority as a sworn peace officer in every city where the company has a site.
- A right to search bags or vehicles because “this is private property,” unless a posted, lawful, and trained policy actually authorizes that step.
- A right to chase off property, hold someone in a room, or use force beyond what policy, training, and that jurisdiction allow.
If a stem asks what the officer should do when a theft is in progress, the defensible cluster is usually observe, report, keep distance as trained, protect people first, and let law enforcement make the arrest unless the jurisdiction and the post orders clearly authorize more. The wrong cluster is “you are the police now.” A warehouse officer who tackles a thief in the street after the property line, or who locks a suspect in a break room “until police feel like coming,” has left the post’s legal envelope. The exam is testing whether you know that envelope exists, not whether you can quote a criminal-procedure treatise.
Use of force belongs here as a policy and training topic, not as a tactics manual. The professional questions are: Does the owner even authorize force tools on this post? Who is trained, how often, and to what documented standard? What does the law of this place allow a private person to do? How is every use reported, medically followed, and reviewed? Who collects the radio recording and the camera clip? This independent guide will not teach holds, strikes, or weapon handling. If an item dangles a “best takedown,” that is not PSP personnel implementation. The keyed idea is that force, if it exists at all, is a controlled exception with policy, training, and review—not a street improvisation and not a substitute for observe-and-report.
Proprietary versus contract
Proprietary staffing means the officers (and often the technicians) are employees of the protected organization. Contract staffing means a guard or security-services company supplies labor under a statement of work. Hybrid sites are common: proprietary supervisors and contract posts, or a proprietary SOC and a contract rover. The model is a design choice, not a moral identity.
Neither model is automatically cheaper or more loyal. They trade control, cost, loyalty, surge, liability administration, and licensing logistics.
Control. Proprietary staff sit inside the owner’s culture, identity rules, and labor relations. You can write a unique hospital visitor ritual and train it as an employee competency. Contract staff are easier to swap, but the contractor’s playbook and the owner’s playbook can fight unless the post orders and the contract say the same thing. If you need tight operational control—same faces, same clinical etiquette, same radio language—proprietary labor, or a very tightly specified contract, is the honest lean.
Cost. Proprietary looks expensive on a fully loaded wage: benefits, overtime, recruiting, workers’ compensation, supervision. Contract looks cheaper on a bid sheet until you count contract management, overtime surge clauses, posts billed as filled while vacant, and owner time spent directing someone else’s employees. A cheap contract that never fills the night post is not cheap. Price the vacancy, the overtime, and the supervisor who must babysit the vendor.
Loyalty and knowledge. Proprietary staff often learn the plant: which door is always propped, which physician always brings an uncle. That knowledge is a detection tool. It can also become complacency. Contract staff rotate; they may be fresher eyes and weaker site memory. Specify site-specific training and a stable post roster if you buy contract labor for a complex occupancy. Do not assume a warm body from last night’s concert knows your pharmacy anteroom.
Surge. Contractors can usually scale for a strike, a construction gate, a commencement, or a weather event if the contract says so and the bench actually exists. Proprietary forces surge by overtime and burnout. If the residual pairing is seasonal (retail inventory, campus move-in), write surge as a contract feature—or budget proprietary overtime honestly. Surge is not a surprise. It is a staffing requirement you either funded or pretended not to see.
Liability and insurance. Outsourcing labor does not outsource the owner’s duty to specify a safe post, a lawful task, and a competent contractor. The contractor carries employment coverage and often general liability; the owner still faces premises and negligent-selection theories if the file is empty. Proprietary staff put more employment liability on the owner and give the owner more direct control of training records. Either way, insurance certificates, additional-insured status, and training files are implementation artifacts, not decorations.
Licensing. Many jurisdictions license contract security companies and individual guards. Some also regulate proprietary officers; some do not. Do not invent a universal rule, and do not invent a nationwide training-hour quota as if every state used the same number. Confirm the place. The exam idea is that someone must hold the required license, and the owner must not staff a post with a person who cannot legally stand it. Contractors often track licenses as a service; the owner still verifies. Proprietary programs need the same verification with fewer vendor layers.
| Factor | Proprietary lean | Contract lean | Shared trap |
|---|---|---|---|
| Control | Direct culture and procedure | Must be written into the SOW and orders | Assuming the contractor “just knows” |
| Cost | Higher fixed loaded wage | Lower bid, higher management burden | Hours billed for empty posts |
| Loyalty / knowledge | Deep site memory | Rotation and a surge bench | Complacency versus ignorance |
| Surge | Overtime | Contracted extra posts | Surge with no trained bodies |
| Liability administration | Owner employment file | Contractor file plus owner oversight | “Not my employee” as a complete defense |
| Licensing | Follow local proprietary rules | Company and individual licenses | Inventing a nationwide hour quota |
When technology cannot replace a post—and when a post is theatre
Technology is excellent at continuous detection and recording. It is poor at hospitality, discretion, physical delay at a public desk, and a decision that is not in the rule engine. Keep a human post when:
- The opening is a public interface (lobby, emergency-department ambulance bay, school main office) where challenge and service happen in the same breath.
- The residual pairing needs immediate delay a camera cannot provide—a person walking a carton out a staff door during visiting hours.
- Life-safety or clinical judgment sits next to security (infant-abduction protocols, behavioral health, a fire-warden role that security shares).
- The system creates alarms that require assessment, not a pile of door-held events nobody will ever walk.
Cut or redesign a post when:
- The officer sits in a hut watching a monitor wall that is also recorded, with no patrol, no challenge authority, and no radio that reaches responders. That is a poor SOC, not a perimeter countermeasure.
- Hours are staffed on paper and vacant in the time clock.
- The only product is a uniform in a photograph for a board tour.
- A lock, a supervised contact, and a console would treat the pairing, and the person was added because someone was afraid to tell the owner the truth.
Worked hospital lobby: identification-grade cameras at the badge plane still do not replace a trained officer or receptionist who can refuse an unbadged visitor and call a host. The camera supports the investigation after the fact. The person is the delay during the walk-up.
Worked warehouse fence: a 24-hour hut that never walks the apron, never checks Door 4, and never answers the radio is theatre. Detection along the fence plus a roaming response is the real post. The hut was a comfort object.
The diagram below is the staffing decision, not a hiring slogan. Section 15.2 turns the people you keep into KPIs, discipline, and development.
A proprietary officer at a private warehouse sees a person loading staged electronics into a personal van after hours. Which statement best describes the officer’s typical legal and operational role?
An owner is choosing between a proprietary officer force and a contract guard company for a 24-hour hospital campus. Which comparison is most defensible when staffing is treated as a countermeasure?
When is a staffed post the honest countermeasure rather than a camera or a decorative officer?