Treat the PERC exam as a boundary test. For every scenario, name what your registration allows, identify the license your work sits under, and choose the least intrusive lawful response - then document it. Drill the two scenarios below until the authority-then-action ordering is automatic, and use the force-decision table to confirm every escalation is justified before you commit to it.
Registration vs. License vs. Employer Authority: Naming the Right Card
The PERC registers you as an employee working under a licensed employer; it is not itself a contractor license. Questions about contracting, supervision, or company policy sit on the employer's side of that line.
Private security in Illinois runs on three layers that are easy to blend. The regulator sets the framework; a licensed contractor or agency holds the business registration that lets it offer security services; and you hold a permanent employee registration card that registers you as that employer's employee. Because the layers have different holders, they answer different questions. Before responding to any scenario, decide which layer the action belongs to - state framework, business authority, or registered-employee conduct.
Apply the split as a sorting exercise. Patrolling, observing, reporting, and protecting people and property as a deployed employee is your side of the line. Negotiating contracts, setting post orders, supervising other security employees, or representing the company as a business is the employer's side. When a scenario hands you an employer task - disciplining a coworker, amending the contract, deciding the company's policies - recognize the mismatch instead of answering it as if it were a duty of your card.
- PERC holder: a registered employee working under an employer's authority.
- Licensed contractor or agency: the business registered to offer private security services.
- Weapon authorization: a separate qualification question, not part of the card itself - confirm current requirements with IDFPR.
- Administrative details (applications, fees, card status): get them from idfpr.illinois.gov; this guide avoids restating figures that change.
| Layer | Who holds it | What it decides |
|---|---|---|
| State regulation | IDFPR | What private security work Illinois permits and how it is supervised |
| Employer's registration | The contractor or agency | Which services the business may offer and under what conditions |
| PERC | You, the employee | Your personal registration to work as that business's employee |
| Post orders or directives | Employer or client | What your conduct looks like on a specific post |
Private Security Powers vs. Police Powers: Where Your Authority Stops
A registered security employee is not a police officer. Your authority comes from the property interest you protect and limited statutory powers, while police derive authority from the state to detain, arrest, and investigate.
Police powers and private security authority differ in source, scope, and consequence. An officer acts for the state and can detain, arrest, and investigate under broad public authority. A security employee acts to protect a specific person, property, or site, and any detention or search authority is narrow and tied to specific legal conditions. In scenario questions, the reliable test is to ask what legal basis supports the action, not whether the action seemed reasonable or necessary.
Work the boundary with three verbs: detain, search, demand. Assume none of them is available to you until the scenario supplies a lawful basis, such as a witnessed offense on the property you protect or a person voluntarily agreeing to a bag check under posted site rules. If no basis appears, the defensible choice is observation, verbal engagement, and calling law enforcement. That default - observe, report, summon - is the safe anchor whenever no basis appears.
- Detention: police may detain under public authority; any private security detention depends on narrow statutory conditions - know the current Illinois rule before relying on one.
- Searches: security inspections rest on consent or posted site policy; police searches require legal process.
- Identification: an officer can compel it in defined situations; you can request it and, on private property, condition entry on it.
Use of Force: Building a Justification Before You Escalate
Force is justified only by what a subject is doing, only in increments, and only while the justification lasts. Name the behavior, pick the least intrusive response that can work, and stop the moment behavior stops.
Use of force is best studied as a matching problem, not a list of approved techniques. Each response must be supported by an observed behavior, must be the least intrusive option likely to control the situation, and must end when the behavior ends. That three-part structure - behavior, proportion, duration - is what a report must reconstruct afterward. Practice reading scenarios for each element: what did you actually see, what lower-force options remained, and what justified continuing once the subject stopped resisting.
Worked scenario: you see a person slip merchandise into a bag at a store you protect. The tempting mistake is immediate physical contact - grabbing the arm, blocking the exit, or applying wristholds - before you can state what you saw. The stronger decision is a calm verbal greeting, close observation of distinguishing details, and a radio call to police while watching the door. If the person drops the goods and leaves, no force was needed. The reason: an unjustified grab can create injury and criminal exposure for you and your employer.
| Subject behavior you observe | Least intrusive response to consider | What must be true before escalating | What to document afterward |
|---|---|---|---|
| Compliant or merely present | Presence and verbal contact | Nothing; no escalation is needed | Time, location, description, action taken |
| Verbal refusal to leave private property | Clear direction, repeat request, note refusal | You are on property you protect and the person has no lawful right to remain | Exact words used, refusals, witnesses, police notification time |
| Passive resistance | Continued verbal direction; await police | Physical control would be escalation; request law enforcement instead | Behavior observed, your words, who responded |
| Active aggression or imminent harm | Defensive action limited to stopping the harm | Lower-force options failed or are unavailable; harm is immediate | Each force increment, its duration, injuries, medical response, notifications |
Report Writing: Recording Facts Without Borrowing Conclusions
A defensible report contains observations, times, statements, and actions - not opinions about fault or guilt. Write what you perceived with your senses, quote statements, and leave conclusions to investigators and courts.
Reports carry three duties that are easy to confuse: accuracy, completeness, and neutrality. Accuracy means every sentence traces to something you perceived or did. Completeness means the reader can reconstruct the sequence without asking you a question. Neutrality means observations are described without verdicts. Words like 'drunk,' 'suspicious,' or 'reckless' are conclusions dressed as facts; replace them with the observations that produced the impression - the odor, the behavior, the speed - and let the reader draw the inference.
Worked scenario: after a visitor slips on a wet lobby floor, you write that the floor was dangerous and the cleaning contractor was at fault. The mistake is the verdict, not the concern. The stronger report records the time, the visible water, the absence or presence of warning signs, the visitor's statement in quotation form, first aid given, and who was notified and when. This matters because conclusions in your handwriting can be read as an admission against your employer, while a neutral record protects everyone by preserving what happened.
- Header discipline: who, what, where, when, and how you responded, in time order.
- Statements: quote them; never paraphrase a witness into saying what you expected.
- Corrections: strike through with a single line, initial and date - never erase or obliterate.
- Speculation ban: no causes, no fault, no predictions of what 'probably' happened.
Ethics Under Pressure: Directives, Confidentiality, and Conflicts
Ethical duties run to the public, the profession, and your employer - in that order when they collide. You must decline unlawful directives, protect confidential information, and avoid letting personal interests steer official actions.
Employer loyalty never converts an unlawful instruction into a proper one. If a supervisor tells you to 'clean up' an incident report, overlook a policy violation by a favored client, or hold evidence outside the notification chain, the ethical response is to decline the specific act, state the reason briefly, perform the duty correctly, and document the exchange. Reporting the concern through your employer's chain of command - or to the appropriate authority where required - is part of the duty, not an act of disloyalty.
Two quieter duties appear constantly in scenario form. Confidentiality: incident details, camera footage, client layouts, and personal information you learn on duty are not for social media, friends, or curious neighbors - release belongs to your employer and law enforcement. Conflicts: accepting gifts that could influence enforcement of site rules, working a second job that undercuts alertness, or using your position for private advantage all compromise judgment. The test in each case is whether a reasonable observer could see your judgment as purchased or divided; if yes, disclose or step back.
- Testimony: your answers must match your report; correct errors openly instead of defending them.
- Uniform enforcement: apply site rules the same way regardless of a person's status, mood, or relationship to the client.
Emergencies and Communication: Acting Inside Your Training
In an emergency your job is to execute the site plan: protect life first, summon the right responders, control access, and communicate calm, accurate information - never to improvise rescue or medical duties beyond your training.
Emergency questions test boundaries under time pressure. Fire response means initiating notification, guiding evacuation along the site plan, and accounting for people at the assembly point - not fighting the fire. Medical events mean summoning emergency services, providing only the first aid you are actually trained and authorized to give, and preserving the scene as far as safety allows. In each case the correct answer follows the posted plan and the notification chain; improvising a hero role is the first option to eliminate.
Communication is the least invasive tool you own, so use it early. Speak in short directives, explain what you need and why, and acknowledge frustration without conceding rules. Under public-relations pressure, know what you may say: you can describe your role and direct people to the right channel, but incident details, camera locations, and investigative status are not yours to release. The consistent pattern - calm tone, bounded information, documented contacts - keeps communication questions answerable with the same authority-first logic as everything else.
- Priority order: life safety, incident stabilization, property protection, documentation - in that order.
- Information release: refer media or bystanders to the employer's designated channel.
- Shift handover: brief the incoming officer on open incidents and notifications before you leave.
A Two-Week Practice Sequence with a Self-Check Rubric
Spend the first stretch learning the boundary vocabulary, the middle stretch on timed scenario drilling, and the final stretch on self-testing with the rubric below. Readiness means the rubric has no zero and your scenario answers survive an audit.
Practical exercise: take ten practice scenarios and answer each in three written lines before choosing any multiple-choice option - (1) which layer authorizes the action, (2) the least intrusive response that can work, (3) what must be documented. Score one point per correct line. A useful milestone is sixteen of thirty points across the set, with every miss explained in one sentence. If your misses cluster in force scenarios, re-drill the decision table; if they cluster in reports, rewrite your answers as pure observations and rescore.
Adaptable sequence for roughly two weeks of part-time study: days one and two, learn the layer model and write your own one-sentence definitions of registration, employer authority, and post orders; days three to five, drill force and detention scenarios against the decision table until justification precedes action in your answers; days six to eight, write and rewrite two incident reports, checking them against the neutrality rules; days nine and ten, cover ethics and emergency roles with the decline-and-document pattern; final days, full mixed sets under time and the rubric audit.
- One-sentence test: you can explain why the PERC is a registration rather than a contractor license.
- Force test: you can name the observed behavior, the least intrusive option, and the stopping point before justifying any response.
- Neutrality test: you can convert three opinion statements into observations on the first attempt.
- Chain test: you can list your emergency notification order from memory.
- Score test: your ten-scenario rubric score reaches sixteen of thirty with no zero lines - a learning milestone, not a prediction of your result.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.