MI Security Guard common mistakes
MI Security Guard · Understand the traps and how to avoid them.
Treating a private security guard's authority as equivalent to a sworn police officer's, e.g., describing a guard as able to make a traffic stop, run plates, or compel identification on a public street.
Popular media and the visible uniform create a mental shortcut that blurs the statutory line between private citizen arrest powers and police authority; candidates then answer from intuition instead of the statute.
What to do instead
Study the Private Security Guard Act alongside Michigan's citizen's arrest framework and write out, in your own words, the two or three powers a guard actually has (e.g., arrest for a felony committed in the guard's presence, detention on the premises of the client) and everything a guard cannot do. Test yourself by classifying ten scenarios as 'guard may' or 'call police.'
Confusing 'detention' with 'arrest' and answering that a guard may hold a shoplifting suspect indefinitely until they confess or sign a statement.
Retail loss-prevention training and peer habits often normalize lengthy back-room interviews, so candidates assume the practice is lawful rather than understanding that detention must be brief, purpose-limited, and handed off to police.
What to do instead
Memorize the distinction: a detention is a temporary, investigatory hold to resolve a specific issue and summon police; an arrest is a formal custody based on statutory grounds. Practice writing the timeline of a lawful detention (observe, approach, identify, recover property, notify police, document) and identify the point at which the guard must release or transfer custody.
Describing a search of a suspect's person, bag, or vehicle as routine, without noting that a private guard generally acts on consent or a specific legal basis and that a refused consent cannot be overridden by force.
Guards see police search on television and assume a uniform confers search authority; the exam's search questions are usually testing exactly this boundary.
What to do instead
Build a decision tree: Was the item abandoned? Did the person consent? Is there a client policy or contractual right covering the area (lockers, employee bags)? Is there an immediate safety concern? For each branch, write the limit on what the guard may do if consent is withdrawn. Review the difference between a search by a private party and one conducted at police direction, which can implicate constitutional rules.
Choosing a level of force based on the outcome the guard wants (e.g., 'use whatever is needed to make them comply') rather than on the threat actually presented, and skipping de-escalation and disengagement options.
Candidates answer force questions emotionally, focusing on the guard's safety or the client's property, and forget that force must be proportional, objectively reasonable, and preceded by lesser options when feasible.
What to do instead
Learn the force continuum as a decision process: presence, verbal direction, soft empty-hand control, hard empty-hand, intermediate weapons, deadly force, with the rule that each step must be justified by the subject's actions. Practice articulating, in writing, why a specific response was reasonable given specific facts, and always include retreat/disengage and summon-police alternatives where they exist.
Assuming the guard's employer's post orders or a client's contract can expand the guard's legal authority, and answering that a guard may act because 'the site policy says so.'
New guards are trained on post orders far more than on statute, so they conflate contractual duties with legal powers.
What to do instead
Separate the two explicitly in your notes: post orders define what you are paid to do, the statute defines what you may lawfully do. Whenever a question cites a policy or contract, ask whether the underlying act would be lawful for a private citizen with no policy at all. If not, the policy does not save it.
Mixing up licensing requirements - e.g., stating that a guard may begin working alone immediately upon submitting an application, or that a guard's license transfers automatically to a new employer.
Licensing rules are administrative and detail-heavy, so candidates skim them and rely on what a friend or a previous employer did.
What to do instead
Create a one-page table of the licensing lifecycle: application prerequisites, required training hours, fingerprinting and background check, temporary or probationary status if any, issuance, carrying the credential while on duty, employer notification of changes, and renewal. Verify each cell against the current statute and the state licensing agency's published requirements rather than a training handout, and flag any figure you cannot confirm.
Writing incident reports in conclusion form - 'suspect was disorderly and resisted' - without the observable facts, times, exact words, and actions that support the conclusion.
Candidates write reports the way people tell stories, compressing events into judgments, and they underestimate how a report will be read later by police, a prosecutor, and a civil jury.
What to do instead
Practice the fact-conclusion discipline: for every judgment word in a draft report, write the observation that supports it. Replace 'aggressive' with the specific action, words, distance, and duration. Use chronological order, 24-hour times, full names and identifiers, and quote statements verbatim in quotation marks. Have someone else read your report and list what they still cannot picture.
Omitting or altering details in a report to protect the guard, a coworker, or the client, or adding facts learned later as if they were observed at the time.
Loyalty to the team and fear of discipline create pressure to sanitize; separately, memory consolidation makes later information feel like original observation.
What to do instead
Adopt the rule that reports record only what the writer perceived, with a clear line between observation and information received from others. If a mistake was made, document it accurately and factually - accurate reports are the guard's protection. Note the time a report was written and any supplementation separately rather than editing the original.
Freezing the emergency response at 'call 911' and failing to describe scene safety, preservation of the scene, first aid limits, and the handoff to responders.
Candidates treat emergency response as a single action and have not rehearsed the sequence, so they cannot order the steps under exam pressure.
What to do instead
Memorize a response sequence: ensure personal and bystander safety, notify via the site's protocol and 911, provide only the aid you are trained and equipped for, secure and preserve the scene (do not move items, note who touched what), identify witnesses, and brief arriving responders with a concise summary. Rehearse giving that briefing out loud in under a minute.
Relying on vague observation language in scenario questions - 'a suspicious male' - instead of describing behavior, and failing to note the limits of what the guard actually saw.
Guards are trained to trust hunches, and candidates import that habit into descriptive questions where the exam is testing whether they can separate observation from inference.
What to do instead
Practice rewriting descriptions so that every noun and adjective is observable: height, build, clothing with colors and logos, direction of travel, what the hands were doing, lighting conditions, distance, and obstructions. Add a line stating what you could not see. In scenario questions, choose the answer that reflects observed behavior plus stated uncertainty over the one that asserts a conclusion.