Unarmed Security Guard — On-the-job English
Study in your language — but on the job you'll speak English. These are the real phrases you actually say for this work, with a note in your language. Not a script; common situations workers report.
Quick drill — pick the best answer, see why. Saved on this device.
✍️ Practice theseShift start: the pass-down, your post orders & the radio check
Your shift doesn't start when you clock in — it starts when you take the pass-down. The guard you're relieving is supposed to tell you, out loud and in writing, what happened on their shift: what broke, who was asked to leave, which contractor is still inside. Ask 'anything to pass on?' every time, because pass-down disputes are one of the most common problems guards report, and the written record is what settles them. Then there are your post orders — 🔴 the written rules for your particular site. They tell you what you patrol, who is allowed in, and who you call. They are the single most important document in this job, because they define what you actually do here, and they are different at every site. Read them; don't assume this site works like your last one. Finally, do a radio check before you need the radio, not after.
- 🗣️ You say
Hey — anything to pass on before I take over?
The one question you always ask the outgoing guard. Simple, expected, and it's how you find out that the north gate lock is broken before you walk to it at midnight.
- 👂 You'll hear
Yeah — the north gate latch is broken, and there's a contractor still working in Building C. It's all in the pass-down log.
A real pass-down: what's broken, who's still on site, and where it's written down. Note both, and read the log yourself — don't rely only on what you were told.
- 🗣️ You say
Got it — north gate latch, contractor in Building C. Do the post orders say anything about after-hours contractors?
Repeat back what you heard so a mishear doesn't become your problem, then check the written rule rather than guessing. The post orders are the site's authority, not your instinct.
- 👂 You'll hear
They're in the binder at the desk. Anyone after hours needs to be on the access list — call dispatch if they're not.
Pointing you at the written rule and the escalation path. 'Call dispatch' is the answer to most uncertain moments on this job.
🧠 Skills this builds
- 🔴 Read your post orders and treat them as the rule. They are the written, site-specific instructions that define your scope on this post — what you check, who gets in, and who you call. When someone's casual advice contradicts them, the post orders win, and 'the post orders say...' is a completely normal, professional thing to say out loud.
- Take the pass-down verbally AND find the written one. Guards report constant disputes over what was or wasn't passed on, and the written log is what a supervisor believes afterward. Ask the question, repeat the answer back, and read the log yourself.
🇺🇸 US workplace note
- Asking questions at the start of a shift — 'anything to pass on?', 'where are the post orders?', 'is that still the rule?' — reads as professional in the US, not slow. The guards who get in trouble are the ones who guessed, not the ones who asked.
- Radio English is deliberately short and flat: 'radio check', 'do you copy?', 'copy that'. It isn't rude and you don't need full sentences. Everyone shares one channel, so brevity is politeness.
⚠️ Common mistakes
- Starting a shift without reading the post orders because your last site worked a certain way. — Post orders are site-specific and they define what you actually do here. Assuming instead of reading is how guards end up doing something their site never authorized.
- Taking only a verbal pass-down and never checking the written log. — Verbal pass-downs get forgotten and disputed constantly. Ask out loud, repeat it back, and then read what was written down.
- Skipping the radio check because the radio worked yesterday. — You discover a dead radio at the worst possible moment. Check it at the start of the shift, every shift.
🔖 Quick reference
Anything to pass on before I take over?
Your opening line to the guard you're relieving. The 'pass-down' is everything that happened on their shift that you need to know — a broken gate, a person who was asked to leave, a contractor still on site. Ask it every single time, even when the other guard looks like they're already walking out the door.
What's going on tonight?
A shorter, more casual version of the same question, and one guards use constantly. It invites the outgoing guard to tell you anything unusual before they leave. Two minutes here can save you an hour of confusion later.
No pass-downs — nothing happened on the shift.
The standard answer when your shift was quiet, and a line you'll both say and hear. It also goes in your written report. Say it only when it's true: if something happened and you say this, the written record now disagrees with reality — and the record is what people believe later.
Where are the post orders? I want to read through them.
🔴 Your post orders are the written rules for your specific site — what you patrol, when, who gets in, what you do about X, and who you call. They define your scope at that site. Every site's are different. Reading them is described by experienced guards as the single most important thing a new guard does.
The post orders say I call dispatch first — is that still right?
Checking your understanding of a written rule against what actually happens on this post. Asking is not weakness; it's how you avoid guessing at 3 a.m. When the post orders and someone's verbal advice disagree, the post orders are the rule — and you can say so politely.
Radio check — do you copy?
How you confirm your radio works at the start of your shift, before you need it. 'Do you copy?' means 'can you hear me?'. Never assume the radio works; a dead radio only announces itself when you're already in trouble.
Copy that.
Radio English for 'I heard and understood you.' Short is correct on a radio — you're sharing the channel with everyone else on site. 'Copy' confirms receipt; it doesn't promise anything else.
Access control: badges, the visitor log & politely refusing entry
Access control is most of the job on a lot of posts, and it's mostly one polite sentence repeated all day: 'Can I see your badge, please?' Behind that sentence is a rule — the visitor log. Every non-employee signs in: name, time, who they're here to see, and their escort, and they leave with a visitor badge and sign out again. The pressure you'll feel is toward convenience: a regular contractor who wants to just flash a badge, a manager who tells you to wave someone through, someone in a hurry who's annoyed at being asked. Apply the rule the same way every time — guards report being written up both for skipping an ID check and for applying it unevenly. And when someone isn't on the list, you don't argue and you don't decide. 🔴 You say 'I can't let you in without checking — let me call and confirm,' and you make the call. That's not a failure to handle it; that IS handling it.
- 🗣️ You say
Good afternoon — can I see your badge, please?
Greeting plus the ask. Warm and routine. Said the same way to everybody, it stops being a confrontation.
- 👂 You'll hear
I don't have it on me — I'm here for the 2 o'clock with Maria in Building B. I'm running late.
The most common pressure moment: a plausible story, no credentials, and a hurry. None of that changes the rule. The list and a phone call decide, not the story.
- 🗣️ You say
No problem — please sign in here and I'll call Maria to confirm and get you a visitor badge.
You refuse nothing and concede nothing. You route it: sign the log, call the person, issue the badge if it checks out. 'Let me call and confirm' is the most useful line in access control.
- 👂 You'll hear
Can't you just let me through? Everybody here knows me.
Push-back. Don't debate it and don't take it personally — say the rule once, evenly, and finish the call you already started. 'I have to check everyone the same way' is a complete answer.
🧠 Skills this builds
- 'Let me call and confirm' is your whole access-control toolkit. You don't have to win an argument, judge a story, or make a call above your pay grade — you sign them in and phone the person who actually knows. Routing beats deciding, every time.
- Apply the rule evenly and it stops being personal. The moment you make exceptions for people you recognize, every refusal afterward looks like a choice you made about that person — and the log stops being a record of anything. Same greeting, same question, same log, everybody.
🇺🇸 US workplace note
- Asking a stranger for ID in the US is completely normal at a controlled entrance and almost nobody is genuinely offended — the tone does the work. 'Good morning, can I see your badge, please?' is friendly and firm at the same time, and that combination is what the job is.
- You will get pressure to skip the log — from visitors in a hurry, from regular contractors, sometimes from a manager. The written policy, not a verbal 'just wave him through', is what you'll be judged against afterward. If someone insists, log the instruction and who gave it.
⚠️ Common mistakes
- Waving someone through because they seem to belong, are in a hurry, or someone vouched for them verbally. — 'Seems fine' isn't verification, and it's your name on the log. Sign them in and call to confirm; it takes a minute.
- Arguing with someone who's annoyed at being checked. — You're not there to win the conversation. Say 'I have to check everyone the same way' once, then go make your call. Arguing just gives them more time to stand there.
- Filling the visitor log in vaguely or after the fact. — A log with missing times or no escort name protects nobody. Fill it in as it happens, accurately, every visitor.
🔖 Quick reference
Good morning — can I see your badge, please?
Your standard access-control line. Greet first, then ask. The greeting makes it routine rather than an accusation, and 'please' costs nothing. You'll say this hundreds of times a shift; making it sound normal is the skill.
Are you on the visitor list for today?
How you check whether someone is expected. If they're on the list, you sign them in; if they're not, you don't improvise — you call the person they're here to see, or call dispatch. The list, not your judgment, decides.
Please sign in here, and I'll get you a visitor badge.
The formal step for every non-employee: name, time in, who they're here to see, and their escort. Filling the visitor log in accurately for every visitor is a real, documented part of the job — guards have been formally written up for skipping it.
Who are you here to see?
The question that turns 'a stranger in the lobby' into something you can verify. It's polite, it's expected, and the answer gives you someone to call. If the name doesn't check out, that's your answer.
Do you have a delivery order or a work order I can look at?
For a delivery driver or a contractor arriving. You're not being difficult — you're confirming they're expected. A real contractor has paperwork and won't mind; someone with no paperwork is exactly who the log exists for.
I'm sorry — I can't let you in without checking. Let me call and confirm.
🔴 Your line for refusing entry politely. Notice what it does: it declines without arguing, and immediately offers a next step that isn't you making the decision. You never have to win the argument — you just have to make the call.
I have to check everyone the same way — it's not personal.
For the person who's annoyed at being asked. Applying the rule evenly is the entire point; guards get in trouble both for skipping the check and for applying it inconsistently. Saying this out loud, calmly, defuses most of it.
Patrol, radio brevity & writing the DAR
Patrol is where two very different English skills meet. On the radio, short wins: 'All clear at the north gate.' 'Copy that.' 'Say again?' You don't need full sentences, and if you miss something, 'say again' is the correct word — not 'repeat'. Then there's the part nobody warns new guards about: 🔴 written English is a heavy, real, legally consequential part of this job. Every shift ends with a Daily Activity Report, and the DAR has a shape you have to learn: 'I observed…' plus what, where, and the time — and nothing else. No opinions. No conclusions about who did it or why. No 'he was being suspicious'; instead, 'at 0215 hours I observed a male in a red jacket in the loading dock; he left northbound on foot.' Guards describe the DAR as their real protection: when a supervisor, a client, or a police officer wants to know what happened, an accurate, factual, contemporaneous written record beats anybody's memory. Write the boring shifts too, because an unwritten quiet night reads exactly like a night nobody patrolled.
- 👂 You'll hear
BC233, do you copy?
A dispatcher's radio check to your call sign. Answer immediately with your call sign and 'copy' — short, so the channel stays clear for everyone else.
- 🗣️ You say
BC233, copy. All clear at the north gate.
Your call sign, confirmation, then your status and location. Three seconds of radio; everything dispatch needs.
- 👂 You'll hear
Copy that. Anything on the loading dock camera?
A follow-up question. If you didn't catch it, 'say again?' — don't guess. A wrong answer on a radio sends someone to the wrong place.
- 🗣️ You say
Nothing right now. At 0215 I observed the south window in Building C is broken — I'm noting it in my DAR.
Factual: what, where, when, and it's going in writing. Notice there's no theory about who broke it — that's not your call and it doesn't belong in the report.
🧠 Skills this builds
- 🔴 The DAR sentence is 'I observed [what] at [where] at [time].' Facts only — what you saw, where, when, and what you did about it. Never who you think did it, never why you think they did it, never 'he was being suspicious'. Your opinion is worthless in a report; your observation is evidence.
- Write the quiet shifts too. 'At 2340 hours I conducted a patrol of the parking structure. No incidents observed.' An unwritten patrol looks the same on paper as a patrol that never happened — and if something turns up later, the DAR is the only thing standing between you and someone else's memory.
🇺🇸 US workplace note
- Radio brevity is its own dialect, and it's deliberately blunt: 'copy', 'say again', 'negative contact'. Nobody will think you're rude for being short — the channel is shared, and long sentences block it for everyone.
- 'CYA' — writing everything down to protect yourself — is openly the culture in US security work, and it isn't seen as distrustful. Guards describe winning every dispute with a supervisor or a client by pointing at their own timestamped, factual report. The DAR is genuinely on your side.
⚠️ Common mistakes
- Writing conclusions instead of observations — 'he was clearly trying to break in.' — You don't know intent and you're not the one who decides it. Write what you saw: what he did, where, when, and what you did about it. A report full of opinions is a report a lawyer can take apart.
- Writing 'nothing to report' for a shift where small things happened — a scrape, a dent, a door left open. — Small things become big questions later, and an incomplete DAR reads as 'nothing happened.' If you're unsure whether it belongs, write it.
- Saying 'repeat' on the radio, or guessing at a message you didn't catch. — 'Say again' is the correct phrase, and guessing sends you to the wrong gate. Ask; it costs two seconds.
🔖 Quick reference
All clear at the north gate.
The standard patrol check-in: where you are and that nothing's wrong. Short and specific. 'All clear' plus a location tells dispatch both that the area is fine and that you're fine — the second part matters more than new guards realize.
Say again?
🔴 Correct radio English for 'repeat that' — on a radio you say 'say again', not 'repeat'. Use it the instant you don't catch something. Guessing at a radio message is how a guard ends up at the wrong gate.
Negative contact, calling out.
The brevity phrase for 'I tried this person on the radio and got no answer, so I'm escalating.' It creates a recorded attempt before you go to a supervisor — which is exactly why it exists. Guards use it after two tries with no response.
I observed a broken window on the south side of Building C at 0215 hours.
🔴 The core sentence pattern of the Daily Activity Report: 'I observed…' + what + where + when. Notice what's absent — no guess about who did it, no theory about why. Just what your eyes saw and the time on the clock.
At 2340 hours I conducted a patrol of the parking structure. No incidents observed.
🔴 A normal DAR line for an uneventful patrol. Yes, you write these down even when nothing happens: the DAR is the record that you were there, patrolling, at that hour. 'Nothing happened' unwritten looks identical to 'nobody patrolled'.
Does anyone know what to put in a daily activity report?
A real question new guards ask, because nobody trains it up front. The honest answer: times, locations, patrols, weather alerts, anything out of the ordinary — down to small things like a scrape or a dent. If you're unsure whether it belongs, write it.
I'm going to note that in my DAR.
A normal, professional thing to say out loud. It's not a threat — it's how the job works. Every shift ends with a Daily Activity Report, and it is the record that protects you when someone remembers the shift differently than you do.
🔴 Someone who shouldn't be there: the observe-and-report script
🔴 This is the chapter the whole pack exists for. Someone is on your property who shouldn't be, and everything you do next is verbal, from a safe distance, and ends with a phone call — not with you making anything happen. The shape is always the same: identify yourself → note it's private property → ask them to leave, ONCE → if they refuse, back off and call the police. That's it. Here is what you must understand about why: you are not a peace officer. A Guard Card gives you no police powers at all. Your only arrest authority is the same narrow private-person power any citizen has under Penal Code 837 — and most employers' post orders tell guards flat out not to use it. One guard quoted their own site's written post orders exactly: 'I am not there to minimize or stop theft. I am there for public safety and to observe and report.' That is your job description, in your employer's own words. So: don't touch anyone. Don't chase anyone. Don't debate the law with someone who tells you that you have no authority — they may even be right, and arguing changes nothing. Say it once, and if it doesn't work, call. If you go hands-on, you are a private citizen who put their hands on someone, and you personally carry the criminal and civil liability for what happens next — not your employer, not your badge. You.
- 🗣️ You say
Good evening — my name is Officer Chen with building security. Are you aware this is private property? I'm going to have to ask you to leave.
The whole script in one breath, said once, from a safe distance. Identify, inform, ask. Then stop and let them answer.
- 👂 You'll hear
This is public property. You're not a cop — you can't tell me to do anything.
🔴 The classic refusal, and here's the thing: arguing the law with him is a trap. You will not win it, and every sentence you add gives him a reason to stay. Don't debate. Move to the call.
- 🗣️ You say
You're right, I'm not — I'm not going to make you do anything. I'm just going to call the police.
🔴 Honest, calm, no threat, no argument, and it ends the exchange. In the real account this came from, the person left on their own as soon as the guard started dialing. You conceded the point and still did your job.
- 👂 You'll hear
Fine, I'm going. Whatever.
Compliance, delivered rudely — which is still compliance. Say 'thank you, I appreciate it' and stop talking. Don't get the last word; you already got what you needed.
🧠 Skills this builds
- 🔴 Say it once, then act — don't argue. Your script is: identify yourself, say it's private property, ask them to leave, once. If they refuse, you back off and call the police. As one veteran guard put it, every extra word gives them a reason to stick around; and the moment you get compliance, thank them and shut up. You are not there to win the conversation.
- 🔴 'I'm not going to make you do anything — I'm just going to call the police' is your most powerful line precisely because it's true. You're an unarmed private citizen with a radio, not a peace officer. Stating your actual limit out loud, calmly, ends more situations than any bluff — and a bluff is exactly what gets guards hurt.
🇺🇸 US workplace note
- 'Observe and report' isn't a slogan somebody invented to make the job sound small — it's literally what employers write into post orders. A real guard quoting his own site's written rules: 'I am not there to minimize or stop theft. I am there for public safety and to observe and report.' Following that is doing the job correctly, not failing at it.
- In the US a security guard has no police powers, and members of the public know it — some will tell you so to your face. That's not a crisis and it's not a challenge to answer. Your authority was never the point; your radio, your report, and 911 are the job.
⚠️ Common mistakes
- 🔴 Chasing someone off the property or following them. — You're not police. The moment you chase, you've lost your safe distance, your legal protection, and any control over what happens next — and no employer's post orders authorized it. Let them go; note the description and the direction they went, and report it.
- 🔴 Touching, grabbing, or physically detaining someone who won't leave. — You are a private citizen with your hands on another person, and you personally carry the criminal and civil liability for it — assault and false-imprisonment exposure is real, and no badge covers you. A guard who handcuffed a trespasser got a fight instead of a solution. Don't. Back off and call police.
- Arguing the law with someone who says you have no authority. — They might even be right, and it doesn't matter. Every sentence you add keeps them there longer. State the request once, then make the call.
🔖 Quick reference
Good evening — my name is Officer Chen with building security.
How you open. Identify yourself and who you're with, from a comfortable distance, before you ask for anything. It tells the person who you are and why you're talking to them, which removes half the tension before it starts.
Are you aware that this is private property?
The setup line in the real trespass script guards are trained on. Ask it as a genuine question, not an accusation — plenty of people honestly don't know. Sometimes this sentence alone ends the whole thing.
I'm going to have to ask you to leave.
🔴 The core sentence of this chapter. Say it once, clearly, from a safe distance, and then stop talking. Notice the shape of it: it's a request, not a command, and you're not going to make anything happen. If they go, you're done. If they don't, you call — you don't escalate.
I know you're in a rough spot, but unfortunately I do have to ask you to leave.
A real line guards use with someone who's homeless or sleeping on the property. It's the same request with the dignity left in. The guard who said this called police for the follow-through rather than touching him — in his own words, 'I don't go hands-on for liability reasons.'
Sir, I'm not going to make you do anything — I'm just going to call the police.
🔴 The most honest sentence in this pack, and a real one from a guard's own account. You are not a peace officer. You cannot make anyone do anything. What you can do is call — and saying so plainly, without threat in your voice, is very often the thing that ends it. In the real account, the person left on their own.
Thank you — I appreciate it.
What you say the moment someone starts complying, and then you stop talking. A veteran guard's actual teaching point: 'every word out of your mouth gives them a reason to stick around longer... once I gain compliance, I thank them and I shut up.' Winning the argument is not the goal. Them leaving is the goal.
Okay — I'm calling the police now.
🔴 What you say when they refuse, and then you back away and call. That's the whole plan. You don't repeat yourself, you don't debate whether it's really private property, you don't follow them, and you never touch them. You make the call and you let police handle it.
De-escalation: an angry or intoxicated person
Angry and intoxicated people are a normal part of this job, and verbal de-escalation is a core trained skill for it — California's mandatory Power to Arrest course spends real, legally-required time on de-escalation and tactical communication, and none on how to fight anybody. Here's what actually works, from a guard's real, successful encounter: an intoxicated woman was accusing him of stealing her vape pen and getting aggressive. He didn't argue and he didn't stand his ground — he backed away and said 'give me some space,' and then instead of defending himself, he pivoted: 'alright, let's look for your vape pen.' Her aggression dropped immediately, they walked the site together, and she left calm. That's the whole method: keep your voice flat, keep backing up, stop trying to win, and give the person something to do with you instead of against you. And know your exit. If it's getting worse, not better, you disengage — you say 'I'm going to leave it there and call my supervisor,' and you walk. 🔴 There is no situation at your post where standing in front of an escalating person is your job. Distance is free. Use it.
- 👂 You'll hear
You people are all the same! One of you took my bag — I know it was you!
An accusation, loud, probably intoxicated, almost certainly not really about you. Don't defend yourself; defending yourself is arguing, and arguing feeds it. Back up half a step and drop your volume.
- 🗣️ You say
Okay — give me some space, and let's look for it together. Where did you have it last?
🔴 Straight out of the real de-escalation. Ask for distance, refuse the argument, and hand her a task. You've turned 'you versus me' into 'us versus the missing bag' in one sentence.
- 👂 You'll hear
...It might've been by the benches. I don't know. I don't know.
The temperature drops the moment there's a problem to solve instead of a fight to win. Stay calm, keep your distance, and keep her moving toward the answer.
- 🗣️ You say
Let's start there. And if we don't find it, I'll call my supervisor and we'll take a report.
You've given her a next step and an escalation path that isn't a confrontation. If she turns aggressive again, the same line becomes your exit: you step back and make that call.
🧠 Skills this builds
- Stop trying to win. Almost every angry encounter you'll have is not really about you, and you cannot argue someone out of being drunk, scared, or furious. Lower your voice, back up, acknowledge them — 'I hear you' — and if you can, give them something to solve with you. The guard who said 'let's look for your vape pen' ended in two minutes what an argument would have run for twenty.
- 🔴 Know your exit and use it early. 'I'm going to step back' and 'I'm going to call my supervisor' are always available, and walking away is the trained move, not a failure. If it's escalating instead of calming, you don't need permission to disengage — nothing at your post is worth standing in front of.
🇺🇸 US workplace note
- De-escalation is a legally required part of California guard training — the mandatory course covers de-escalation, tactical communication, and mental-health considerations. Talking someone down and walking away IS the trained response; it's not you being soft on the situation.
- In the US, calm, slow, quiet speech reads as authority far more than volume does. Someone who matches an angry person's volume looks like a participant in the fight. Someone who stays flat and keeps their distance looks like a professional — and is much harder to fight with.
⚠️ Common mistakes
- Matching an angry person's volume or defending yourself against their accusation. — You're now in the argument, and there's no version of it you win. Drop your volume, back up, and pivot to a problem you can solve together.
- Standing your ground because backing up feels like losing. — Distance is your only real safety tool and it's free. Backing away while you talk is the trained response, not a retreat.
- 🔴 Staying in a conversation that's clearly escalating because you want to resolve it yourself. — There's no prize for finishing it. Break contact, get distance, and call your supervisor or dispatch per your post orders. That's the escalation path — you're not it.
🔖 Quick reference
Hey, is everything okay? I noticed you've been here a while.
The check-in before it becomes a confrontation. It's a genuine question and it treats the person as a person. A surprising number of tense situations never start because a guard opened with this instead of a challenge.
Give me some space.
🔴 A real line from a guard's own successful de-escalation with an aggressive, intoxicated woman — said calmly, while backing away. It asks for distance without threatening anyone, and distance is your actual safety tool. You can always keep backing up; nothing on this property is worth standing your ground for.
Okay — let's look for it together.
🔴 The pivot that ended that same real encounter. She was accusing him of stealing her vape pen; instead of continuing to argue that he hadn't, he said 'alright, let's look for your vape pen.' Her aggression dropped instantly. Giving someone a problem to solve with you beats winning an argument against them.
I'm not arguing with you — I just want to help you sort this out.
Naming what you're doing, out loud, when someone is spoiling for a fight. It's hard to argue with someone who's audibly refusing to argue. Keep your voice flat and slow; your tone is doing more work than your words.
I hear you. Let me see what I can do.
For someone who's angry about something real. You're not agreeing and you're not promising — you're acknowledging. A lot of anger is just someone who doesn't feel heard, and this sentence costs you nothing.
I'm going to step back and let you cool off for a minute.
Disengaging on purpose, and saying so. Walking away is not losing — it's the trained move. There is no rule that says you have to finish a conversation with someone who's escalating.
I'm going to leave it there and call my supervisor.
🔴 Your exit from any situation that's going the wrong way. Nothing at your post requires you to keep standing in front of an angry person. Break contact, get distance, and call your supervisor or dispatch per your post orders — that's the escalation path, not you.
🔴 Emergencies: getting safe, calling 911 & when NOT to intervene
🔴 This chapter has one rule that comes before everything else: get to a safe distance FIRST, then call. Not the other way around. A guard who had a gun pointed at him wrote his own lesson afterward — 'I shouldn't have approached the subject without having called 911 first.' Distance first. Phone second. Then 911 is simple: who you are, where you are, what's happening. Say the address early, describe people factually — clothing, build, direction they went, never what you imagine they're planning — and stay on the line. 🔴 And know when NOT to intervene, because this is the part that gets guards hurt. If a weapon is visible or you even suspect one; if you're alone or outnumbered; if violence is already in progress; if the situation is legally ambiguous — you withdraw, you observe, you call. That is the trained response and it's what the real accounts show working: guards going over a fence and calling in shots fired from a safe distance is the correct outcome. You are unarmed, you are not a peace officer, and nothing on that property is yours. Medical: you are not a medic — call 911, and act only within a certification you personally hold, like your own CPR card. Fire: follow the evacuation procedure in your post orders, call 911 for a real fire, and do not go back inside. There is no app and no panic button in this job — there's 911, and there's your supervisor or dispatch per your post orders. And drill 'Sorry, could you say that again?' until it's automatic, because an emergency is exactly when your English will feel hardest.
- 👂 You'll hear
911, what's your emergency?
The operator's opening. Answer in plain words — you don't need a perfect sentence, you need the address and what's wrong. Say those two things first in case anything goes wrong with the call.
- 🗣️ You say
I'm a security guard at 400 Harbor Street. There's a man at the north gate with a knife. I'm at a safe distance — I'm not approaching him.
🔴 Everything the operator needs, plus the sentence that tells them you're safe and staying safe. You got the distance BEFORE you dialed. That order is the whole chapter.
- 👂 You'll hear
Can you describe him? Stay on the line with me.
Give what you can actually see — clothing, build, direction of travel — and nothing you're guessing at. Then stay on the line; you're their eyes until officers get there.
- 🗣️ You say
Sorry, could you say that again? — He's in a grey jacket, walking east toward the parking structure. I'll stay on the line.
The lifeline, used the instant something didn't land, then facts only. Asking again is normal and expected. Guessing sends help to the wrong gate.
🧠 Skills this builds
- 🔴 The order never changes: get to a safe distance FIRST, then call 911. Then it's three facts — who you are, where you are, what's happening — plus a factual description if they ask: clothing, build, direction of travel. Never your theory about what someone intends. Stay on the line. There is no app and no panic button in this job; there's 911, and there's your supervisor or dispatch per your post orders.
- 🔴 Know your four withdraw triggers cold: a weapon visible or suspected, alone or outnumbered, violence already in progress, or anything legally ambiguous. Any one of them and the answer is identical — withdraw, observe from a distance, call. Guards who went over a fence and called in shots fired did the job right. You are unarmed, you are not a peace officer, and nothing on that property is worth your body.
🇺🇸 US workplace note
- In the US, calling 911 is free, expected, and you will never be in trouble for calling when there's a real emergency. For a security guard it is the escalation — there is no universal guard safety app, no panic button, and no industry hotline; whatever tools your specific employer gives you are theirs alone. Learn your own dispatch number and your post orders' escalation path before your first quiet night ends.
- 🔴 People will sometimes push you toward doing more than your job — even police did, in one real account, suggesting a guard 'bum rush' a trespasser who might return. The guard called his supervisor, who told him to find a spot and wait for law enforcement, and that's what he did. Informal advice, however confident the source, does not expand your authority or lower your risk. Post orders and 911.
⚠️ Common mistakes
- 🔴 Approaching first and calling second. — A guard who did exactly that ended up with a gun pointed at him, and his own conclusion was that he should have called 911 before approaching. Distance first, phone second. There is no emergency that gets better because you walked toward it.
- 🔴 Intervening in violence that's already happening, or approaching when a weapon might be present, because it feels like your job. — It isn't your job. You're unarmed, you're not police, and your post orders almost certainly say observe and report. Withdraw, observe, call 911, and give police a location and a description.
- Telling 911 or the police what you think someone was trying to do. — Speculation contaminates a report and can be wrong in ways that matter. Give what you saw: what they wore, what they did, which way they went. Let the police draw the conclusions.
- 🔴 Treating a medical emergency as something you should handle. — You're not a medic, and your guard training doesn't certify you to treat anyone. Call 911, keep the area clear, and act only within a certification you personally hold, like your own CPR card.
🔖 Quick reference
911, what's your emergency?
The first thing the operator says. Don't wait until you can build a perfect sentence — answer in a few plain words: 'There's a fire at my building' or 'Someone's hurt.' If you freeze or hang up, help isn't sent. Clear and slow beats correct grammar, always.
I'm a security guard at 400 Harbor Street. There's a man with a knife at the north gate.
🔴 The whole 911 opening: who you are, exactly where, and what's happening. Address first if you can — a call that drops after those two facts still gets help sent. Say the address before the story.
I'm at a safe distance now — I'm not approaching him.
🔴 Get to a safe distance FIRST, then call. This is the lesson a guard drew from having a gun pointed at him: 'I shouldn't have approached the subject without having called 911 first.' Distance first, phone second, and you tell the operator you're staying back.
What's your location?
The operator will ask, and it's the most important thing you say. Give a street address, a gate name plus a cross street, or a landmark. If you're unsure, describe what you can see. Don't just name the property — 'the north lot behind the blue warehouse on Harbor' beats 'the office park.'
He's a white male, maybe thirties, red hoodie and jeans — he's walking east toward the parking structure.
🔴 Describing someone factually: what you can see and where they're going. Clothing, build, direction of travel, vehicle. NOT what you think they're planning, NOT 'he looks like he's about to do something' — that's speculation, and it goes in nobody's mouth, not on the phone and not in your report.
I'll stay on the line.
Say it and mean it. Dispatchers keep you talking because you're their eyes until officers arrive, and because they want to know if things change. Don't hang up to go do something — stay put, stay safe, keep reporting.
Someone's hurt — we need an ambulance.
🔴 The moment anyone is injured, this is the call. Say it first, then the location. Getting an ambulance moving beats anything else you could be doing.
I'm not a medic — I've called 911 and they're on the way.
🔴 An honest, correct thing to say. A guard is NOT a medic. Your mandatory training covers responding to a medical emergency; it does not certify you to treat anyone. If you personally hold a current CPR or first-aid card, you act within that card and nothing beyond it. Otherwise: call 911, keep the area clear, and wait.
The fire alarm's going off in Building B — I'm following the evacuation procedure in my post orders.
🔴 Fire is a post-orders answer, not a heroics answer. Direct people out per your site's written evacuation procedure, call 911 if it's a real fire and not a test, and do not go back into a building to search for people. Your post orders and your training define the limit — nothing else does.
Shots fired at 400 Harbor Street. I'm getting to cover.
🔴 Active threat: get to safety, do NOT approach, call 911, give location and description. This is real — a guard's account of a party call that turned into gunfire ends with the guards going over a fence and calling 911 from a safe distance. That's the correct outcome, not a failure.
My supervisor told me not to approach — to find a spot and wait for law enforcement.
🔴 A real quote from a real guard, and the correct call. When police themselves suggested he 'bum rush' a trespasser if he came back, he and his supervisor declined — that informal advice would have exceeded his authority and put him at real risk. Follow your post orders and your supervisor, not somebody's off-hand suggestion.
I'm calling my supervisor — this isn't a 911 situation.
For everything short of a real emergency. There is no universal guard hotline and no app — your two escalations are 911 for a genuine emergency, and your supervisor or dispatch, per your post orders, for everything else. Know your dispatch number before you need it.
I don't feel safe — I'm withdrawing and calling it in.
🔴 The sentence that keeps guards alive. Weapon visible or suspected. Alone or outnumbered. Violence already happening. Anything legally murky. In every one of those, the answer is the same: withdraw, observe from a distance, and call. You never owe anyone a confrontation.
Sorry, could you say that again?
Your single most important line under stress. When a 911 operator or a police officer speaks fast and your mind goes blank, this buys a repeat without panic — native speakers use it constantly. 'Slower, please' also works. Never pretend you understood and guess; in an emergency, a wrong answer sends help to the wrong gate.