15.2 Recruiting, KPIs, Discipline & Professional Development

Recruiting, KPIs, Discipline, and Professional Development

Independent OpenExamPrep teaching for published PSP Domain 3 Task 4 knowledge is that a post is not “staffed” because a name appeared on a roster. It is staffed when the person was lawfully hired, trained to the orders, measured on work that reduces residual risk, and corrected or removed when that work fails. Domain 2 asked for people as a countermeasure. This section is the human-resources machinery that keeps that countermeasure honest.

Exam focus: KPIs are response, reports, patrols, and alarm handling—not hours in a chair. Recruiting checks licenses, background, and work-authorization documents. Discipline is progressive and documented. Development includes training, manufacturer courses, and credentials such as PSP.

Recruiting is a security control

Treat recruiting like a lock specification. The residual pairing tells you what competence you need (lobby challenge, SOC assessment, vehicle gate, unarmed rover). The jurisdiction tells you what license a contract or proprietary officer must hold. The owner and the law tell you what background screening and right-to-work / work-authorization documents you must collect. Skipping any of those three is not a staffing shortcut. It is a known vulnerability in the personnel layer.

Licensing. Where a private-security license is required, verify current status before the first shift—not after an incident. Requirements differ by place: some regulate contract guards and not proprietary employees; some regulate both; some add firearms permits on top of a guard credential. Do not memorize a single statewide training-hour number as if it were universal. Independent study for this task is the method: identify the authority, read that authority’s rule, put the proof in the file. An exam stem that claims “every U.S. guard needs a fixed hour count” is bait unless the stem names a jurisdiction and a real rule. Inventing 40 hours, 8 hours, or any other figure as a nationwide constant is how candidates fail items and how programs fail audits.

Background screening. Typical packages include identity, a criminal-history search appropriate to the role, employment history, and—when the post or the law requires it—driving record, credit for certain cash or investigative posts, and drug screening. Match depth to risk and law, not to a brochure. A hospital infant-abduction post and a daytime parking rover are not the same residual pairing. Follow applicable fair-credit, ban-the-box, and equal-employment rules in that place; this guide does not invent a national rap-sheet recipe. The PSP idea is that screening happens before unsupervised access, and that disqualifying results are documented rather than waved through because the contractor is short on Friday night.

Right-to-work and work-authorization documents. In U.S. hiring this is the employment-eligibility file (commonly Form I-9 and supporting identity and work documents). Other countries have their own right-to-work checks. Do not confuse that file with U.S. “right-to-work” union-shop statutes, which are a different labor-law topic. The professional point for this task is: you cannot lawfully staff a post with a person you are not allowed to employ. Contract vendors still owe the owner a representation and, in a competent statement of work, audit rights. “They said they vet everyone” is not a document.

Other recruiting filters that belong in the requisition: ability to perform the essential functions of the post (with lawful accommodation), language needs at a public desk, driving if a mobile patrol is required, and a clean conflict with the site. You do not hire an untrained relative to watch the family warehouse and call it a background check. Job postings should describe observe, report, delay, service—not “act as police.” False advertising in a job ad becomes a training and liability problem on night one, because the new hire will try to perform the fantasy title.

Onboarding is the first patrol

Onboarding is not a video about parking. It is how a new officer becomes a site-specific countermeasure:

1. Identity and access. Badge, keys, radio ID, and system logins issued after the file is complete—not as a welcome gift on the loading dock.
2. Orders. General, post, and special orders (section 15.3) issued, walked, and acknowledged.
3. Site board. Assets that matter: Door 4, the pharmacy anteroom, the infant floor, the generator yard—whatever Domain 1 ranked.
4. Systems. How to call a duress, how to log a door-forced, how to radio the SOC, how not to prop a supervised leaf.
5. Limits. What this post may not do: no invented arrests, no force tools unless issued and trained, no chasing into the street because a camera looked exciting.
6. Relief and fatigue. How the post is handed over, what “on post” means, and that an empty chair is an incident, not a lunch footnote.

A contract officer who “has worked hospitals” still needs this hospital’s visitor rule. A proprietary transfer from the warehouse still needs the clinic’s dual-control restock. Onboarding hours are a performance requirement for the personnel system, the same way latch time is a performance requirement for a door. If you cannot say what the person was taught, you cannot later claim they violated a standard they never received.

Shadowing belongs here. A new lobby officer should watch a competent officer process a visitor, refuse a tailgate, and call a host—then do it under supervision. A new SOC operator should sit a quiet hour and a busy hour before taking the board alone. Skipping shadowing to “fill the post tonight” is how you staff theatre with a live person.

KPIs that describe protection, not occupancy

Hours stood is a payroll metric. It is not proof that residual risk moved. If you only count hours, you will reward the officer who occupied a theatre post and punish the officer who actually completed tours. Independent teaching for this published task uses operational KPIs:

• Response time. From alarm or call to on-scene or to a documented assessment (camera check plus dispatch). Separate technical report time (Chapter 7) from human response time. A sixty-second console acknowledgment and a twenty-minute walk to the dock are different clocks. Write both if both matter. A KPI that only says “fast” cannot fail a review.
• Report quality. Complete who, what, when, and where; facts versus opinions; notifications made; photo or video-clip identifiers; a timeline an investigator can use. A one-line “all quiet” after a door-forced is not a report. Sample reports in review the way you sample camera images in commissioning.
• Patrol completion. Tours actually closed against the required sequence and time window, with exceptions explained. A medical emergency is a reason; a cigarette break is not. Electronic tour devices help; they do not replace a supervisor who notices that every exception is “device failed.”
• False-alarm handling. How the officer assesses, resets, documents, and escalates nuisance or false events. The KPI is not “fewest alarms” (that produces ignored doors). It is correct classification and follow-up so technicians can fix causes and so real alarms still get a walk.

Other useful measures, used carefully: visitor processing time at a badge desk (service as delay), training currency, post vacancy rate, and use-of-force or complaint rates as quality and risk flags—not as a contest to collect arrests. Arrest counts as a bonus metric are how you buy overreach.

A hospital SOC example: if door-held alarms from the ED ambulance bay are classified as “nuisance” without a walk, you have trained the force to ignore the pairing that actually matters. The KPI should score correct handling, including a documented reason when a walk is deferred because a higher-priority medical event is in progress—not a raw count of how quickly someone hit silence.

A warehouse rover example: completing 100 percent of tour points by driving the same three easy doors and skipping Door 4 is not patrol completion. The metric has to name required points, including the residual openings from the assessment.

Performance review and improvement plans

A performance review compares the officer, technician, or supervisor to the post orders and the KPIs, not to a manager’s mood. Frequency should match risk: a new officer needs early checkpoints; a stable proprietary rover still needs a documented cycle. Reviews that never mention reports or tours are theatre, the same as an untested camera.

When performance misses, a performance improvement plan (PIP) is a time-bounded, written set of gaps, coaching, retraining, and measures. It is not a humiliation script and not a substitute for removing someone who is unsafe. Examples that belong in a PIP: incomplete incident reports, skipped tours, rude visitor processing that creates a tailgating workaround, failure to call the tree on a door-forced. Examples that belong in immediate removal rather than a leisurely PIP: violence, theft, working unlicensed, fabricating a tour, a use of force that violates policy.

Contract labor complicates the paperwork but not the standard. The owner directs the post. The contractor employs the person. Your statement of work should require the contractor to run reviews and PIPs you can audit, and to replace a person who cannot meet the post. Do not “counsel” a contractor’s employee as if you were the employer if your legal structure says you are not—coordinate. Do not ignore a dangerous officer because the invoice is convenient.

Reviews should also catch management failures wearing an officer’s name. If every night officer misses tours because the post is double-tasked to the SOC and the dock, the improvement plan belongs on the staffing design, not only on the person. KPIs without a possible schedule are how you manufacture discipline files.

Progressive discipline

Progressive discipline is a documented ladder: coaching, written warning, suspension or reassignment, termination—except when the conduct is severe enough to skip rungs. The point is fairness and a file that shows the organization treated personnel risk as seriously as a failed maglock. Inconsistency (friends get coaching, nights get fired) is how you lose both labor cases and control of the post.

Tie discipline to orders. If the general orders forbid phones in the infant-abduction zone and an officer is scrolling at the nursery door, that is not a “style difference.” If the orders never forbade it, fix the orders first, then train, then discipline. Ambiguous orders plus harsh discipline is how you teach people to hide problems instead of reporting them.

Document facts, notifications, and the employee’s or contractor’s response. Do not invent a police-style interrogation. This is employment and contract administration. The same professionalism you owe an incident report is owed to the discipline file: times, witnesses, the order cited, the prior coaching, the next step if the behavior repeats.

Professional development

Development is how the personnel countermeasure gains competence instead of aging into folklore.

• Training. New-hire, annual refresher, drills (fire, infant abduction, workplace violence as this site defines it), and after-action training when an incident shows a gap. Training must match this site’s orders, not a generic video that says “be alert.”
• Certification. Owner-required or jurisdiction-required credentials; first aid and CPR if the post’s medical role says so. Stop inventing a global hour count. Put the actual card or transcript in the file.
• Manufacturer and system courses. The SOC operator who cannot run the video wall, and the technician who cannot service a panel, are untrained layers. Factory or vendor courses are development, not a vendor holiday. They also reduce nuisance alarms that destroy officer KPIs.
• PSP itself as development. The Physical Security Professional credential is one way a practitioner demonstrates physical-security competence across assessment, design, and implementation. Independent OpenExamPrep material covers the published domains and tasks so supervisors, designers, and ambitious officers can study. It is not an ASIS publication and does not claim official approval, review, partnership, or exact equivalence with any ASIS course or item bank. Using PSP study as a development path is legitimate. Treating a passed exam as a substitute for site post-order training is not. A PSP holder who has never walked this dock still needs this dock’s orders.

A development plan belongs in the same notebook as KPIs: the officer who writes weak reports gets writing coaching; the technician who generates nuisance alarms gets sensor and cause-code training; the supervisor who cannot fill nights gets scheduling and contract-management mentoring. Career paths (rover to console, console to supervisor, technician to systems lead) are how you keep competence instead of paying only for turnover.

Section 15.3 puts the words they train to—orders, uniforms, and the awareness you still need from everyone who is not security.