Handling client complaints in security work
Handling client complaints: acknowledge fast, pull the records before the guard, answer in four parts, and fix the process that let it happen.

The property manager texts you a photo at 6:40am. Your guard, head back, mouth open, in the driver's seat of the patrol vehicle. What you do in the next two hours decides whether you keep the account.
Answer inside hours, not days. Get the facts off the logs before you get them off the guard. Say what happened without spin, name one specific fix with a date, then do it and go back and show them. Most clients who complain are asking to be persuaded to stay. The ones who never complain are already interviewing your competitors.
What do security clients complain about?
Three buckets, carrying very different weight.
The guard. Asleep on post. On the phone through a whole shift. Rude to a tenant. Turned up in a stained shirt and no tie. Did not follow the post orders on a lockup. Sleeping is the one that ends contracts, because the client is paying for attention and watched themselves not get it.
The service. Post uncovered at 6:15 when the shift starts at 6:00. Two of eight checkpoints missed. A replacement officer who did not know the gate code, the alarm code, or which door the client uses. Nobody told them about the incident until they heard it from a tenant.
The paperwork. An invoice with hours nobody worked. A daily activity report that says "all secure" on the night the fire panel tripped. A month of DARs that all read identically. These feel minor and they are corrosive, because they make the client wonder what else is not real.
Sort every complaint into one of those three before you respond. The bucket determines who investigates, how fast you can answer, and whether the fix is a conversation or a process change.
What do you do in the first hour?
Acknowledge, then shut up and listen. Those are separate steps and the second one is where people fail.
Acknowledgment is a reply that proves a human read it, sent fast enough that the client is not left wondering. Not a resolution. Not an explanation. "I've got this, I'm pulling the records now, I'll call you by noon" is the whole job at this stage, and the deadline in it is a promise you now have to keep.
Then let them finish. The instinct is to explain the staffing situation while they are still talking, and it reads as a company defending itself instead of listening. Take notes. Ask what time it happened and who else saw it. Read back what you heard before you go anywhere near a cause.
Do not commit to a finding on that first call. "That should not have happened and I will find out why" costs you nothing. "The guard must have been on a break" is a theory you will have to walk back, in writing, in front of the person you are trying to keep.
How do you investigate before you talk to the guard?
Records first, people second. Not because guards lie, but because a supervisor who arrives already holding the GPS trail and the scan log gets a straight account instead of a defensive one.
Then talk to the guard, and to whoever supervised them. Ask what happened, not why they failed. You are looking for the reason a normally reliable person did an unreliable thing, and about half the time it is yours: they were on hour 14 of a double because someone called out, or the post orders never mentioned the thing the client expected.
That second one comes up constantly. A client complains that the guard "never checks the rear stairwell," and the rear stairwell is not in the post orders. That is not a guard problem. That is a scope problem you wrote.
What do you say back?
Four sentences, in this order, on the phone and then in writing.
Notice what is absent. No blaming the guard as though they arrived from another company. No listing the industry's staffing problems. The client does not want you to be sorry. They want the thing to stop.
Step four rebuilds trust fastest, because it converts a promise into something the client watches happen. There is more on building that habit in client reports that win renewals.
When is a complaint also a regulatory problem?
Sometimes the client's complaint and a state filing deadline are the same event, and the deadline does not wait for your investigation.
California is the clearest example. The Bureau of Security and Investigative Services requires private patrol operators and security guards to file an incident report within seven business days of any physical altercation, firearm discharge or use, or use of a deadly weapon on duty. If a client is complaining about how your officer handled a trespasser, that clock is already running.
The client can also go around you entirely. BSIS accepts consumer complaints against licensees directly, online or by mail. A client who feels ignored has a regulator to call, and that call produces a file with your license number on it.
Other states run their own versions with their own deadlines. Know yours before the night you need it. Any complaint involving force, a weapon, an injury or an allegation of a crime goes to your counsel and your regulator first, and to the client second.
What counts as real corrective action?
Something that makes the same complaint impossible, rather than unlikely.
Pulling the guard is an immediate action, and it is necessary. It is not corrective. If the cause was a fourth consecutive twelve, the same thing will happen to the next guard on the same schedule. Fix the roster or you will be having this call again in March. Scheduling and overtime is where a surprising share of performance complaints actually live.
Ask what would have caught this before the client did. Usually the answer is a supervisor visit that never happens on nights, or a report nobody reads. Both are fixable. Post inspections exist for exactly this, and an unannounced 2am check finds things a 10am check never will.
If the cause was knowledge, the fix is training, and it applies to everyone assigned to that site rather than the one person who got caught. Building the training program covers the structure.
What do the complaints tell you a year later?
More than any client survey will. Log every one with the site, the date, the bucket, the cause you found and the action you took. Not for the audit trail. For the pattern.
Read a year of them and three things fall out. One site produces a third of your complaints, and it is either underpriced or understaffed. One category repeats across sites, which makes it a process, not a person. And a set of complaints cluster in the weeks after a schedule change or a supervisor left, which tells you what your operation is actually sensitive to.
Complaints are the only free data your clients will ever hand you about your own service. The silent accounts are the expensive ones. A client who stops complaining has usually stopped expecting anything to change, and the next thing you hear from them is the non-renewal. Keeping the clients you already have and the service habits behind renewals both start from that.
Key Takeaways
- Acknowledge within hours with a deadline you will hit. Do not diagnose on the first call.
- Pull the records before you talk to the guard: clock times, scans, GPS trail, the DAR.
- Answer in four parts: what happened, why, the fix with a date, and how they will see it.
- Force and weapons carry filing deadlines. California allows seven business days.
- Removing a guard is immediate action, not corrective. Fix the roster or the supervision.
Continue Reading

Client reporting that wins security renewals
Daily, weekly and monthly client reports each answer a different question. How to structure them, what to lead with, and how to build them from patrol data.

Parking enforcement procedures for security officers
Parking enforcement procedures for security officers: where your authority ends, warnings and citations that survive appeal, tow rules and accessible spaces.

Key control policy template for security teams
A key control policy template covering master key hierarchy, issuance records, card and code rules, lost-key response, key recovery and audit frequency.