OR Security Guard common mistakes
OR Security Guard · Understand the traps and how to avoid them.
Treating the 'use of force' continuum as a ladder you must climb one rung at a time, so the candidate says a guard must verbally warn before any physical response even when a weapon is already being drawn.
Candidates memorize a linear list of force options from a classroom handout and never learn that the response must be proportional, immediately available, and reasonable given the threat-not sequential. Exam items that describe a sudden lethal threat punish the rote ladder answer.
What to do instead
Study use of force as a reasonableness test: threat level, available options, and totality of circumstances. Practice scenario items where the correct answer jumps straight to the highest available option because the threat is imminent. Write out why each lower rung was not feasible, not just why the chosen rung was.
Confusing detention with arrest and with a citizen's arrest, so the candidate answers that an unarmed guard may search a suspected shoplifter's bag or hold them in a back room until police arrive regardless of local law.
The terms are used loosely in training and in everyday speech. Candidates do not separate the legal authority to detain briefly for investigation, the power of arrest (which usually rests with police or a narrow citizen's-arrest statute), and the civil tort of false imprisonment.
What to do instead
Build a one-page comparison of detention, arrest, and citizen's arrest covering: who may do it, the required grounds, the time limit, and the force permitted. Rehearse the phrase 'detain for police, do not punish or search' and check the specific statute for the jurisdiction the exam targets.
Reporting observations in conclusory language-writing 'subject was drunk and aggressive' or 'he looked suspicious'-instead of recording time-stamped, sensory facts.
Candidates write reports the way people talk, compressing observations into judgments. They do not realize that a report is evidence and that conclusions invite cross-examination while facts survive it.
What to do instead
Practice the observation-to-fact conversion: replace every adjective with what you saw, heard, and smelled, plus time and location. Rewrite sample narratives until each sentence can be defended in court. Use the formula: who, what, when, where, how, and what you did next.
Treating an alarm activation as a confirmed crime and dispatching or escalating immediately, rather than verifying the signal and applying the response priority the account specifies.
New monitors equate 'alarm received' with 'emergency in progress.' They skip the verification step-call the site, check the zone history, confirm the passcode or call-list sequence-because they fear delay more than false alarms.
What to do instead
Memorize the standard sequence: receive, verify per account instructions, classify priority, dispatch or notify, document, follow up. Drill with accounts that have different call lists and verification rules. Learn to distinguish hold-up, panic, and intrusion signals and the different response each requires.
Failing to document the alarm event fully-omitting the zone, the time of call, the person contacted, the disposition, and the passcode verification-so the record cannot support the client or the responding officer.
Monitors focus on the live action and treat paperwork as an afterthought, and they may not know what fields the client contract or the central station standard requires. Rushed entries during a busy shift get abbreviated.
What to do instead
Learn the required data elements for an alarm event and use them as a checklist every time: account, zone, signal type, time received, verification method and result, parties notified, dispatch time, disposition, and monitor initials. Practice writing a complete entry from a short scenario under time pressure.
Sharing account information, call lists, passcodes, or site layouts with a caller who claims to be the owner or a family member without verification.
Candidates want to be helpful and fear being rude. Social-engineering scenarios are written to sound urgent and plausible, and untrained monitors treat a confident voice as proof of authority.
What to do instead
Adopt a hard rule: no protected information without the account's verification procedure, no exceptions for urgency. Practice refusal scripts that stay polite but firm, and learn to escalate to a supervisor rather than decide alone. Study the privacy and confidentiality obligations that apply to alarm and client data.
Assuming crowd management means standing at a post and watching, so the candidate misses the pre-event planning, ingress and egress flow, capacity counting, and communication with the event organizer.
Event work is taught as a posting assignment rather than a planning discipline. Candidates do not see that most crowd incidents are prevented by layout, timing, and communication before the doors open.
What to do instead
Study the event security cycle: risk assessment, site and layout review, staffing plan, briefing, live monitoring of density and flow, and post-event debrief. Learn capacity limits, queue management, and the triggers for slowing or stopping entry. Practice reading an event plan and identifying its weak points.
Failing to recognize and act on the early signs of crowd crush-density rising, flow stopping, people unable to move voluntarily-and instead waiting for a clear emergency before intervening.
Candidates picture crowd emergencies as panic and running. Progressive crowd collapse looks calm from the outside, so untrained guards see a stationary crowd and conclude nothing is wrong until people are already going down.
What to do instead
Learn the recognized indicators of dangerous crowd density and the countermeasures: open relief routes, stop ingress, reduce pressure points, communicate calm instructions, and extract people at the edges. Rehearse the decision to halt entry early, and study why 'let them in to relieve pressure' is usually wrong.
Answering supervisory items as a front-line guard-for example, personally handling an incident instead of describing delegation, notification, scene control, and post-incident review.
Candidates are usually experienced guards who have not yet worked as supervisors, so they default to the operational answer they know best. The exam tests the supervisor's role in directing, documenting, and protecting the organization.
What to do instead
Reframe every scenario: what does the supervisor do first, whom do they notify, what do they delegate, what do they document, and what do they review afterward. Study the supervisor's legal exposure for negligent assignment, failure to train, and failure to supervise, and practice distinguishing those from the guard's own duties.
Ignoring employment-law and licensing-compliance duties-post orders, licensing records, training records, and discipline-and treating the supervisory exam as pure security tactics.
Candidates assume management content is common sense and skip the regulatory sections. They do not realize that licensing boards test recordkeeping, hiring eligibility, and the supervisor's duty to enforce post orders and report misconduct.
What to do instead
Build a compliance checklist covering license status and renewals, required training hours, post orders, incident reporting, and disciplinary documentation. Study the supervisor's duty to report violations and the consequences of employing unlicensed staff. Practice items that ask which record or notification is required, not which tactic is best.