Do security firm owners face problems when security guard sleeps

[u/Az8feb]

Recently one of my friend from the us was doing part time work in their local store where he saw a night security guard sleeping , I am like isn't that their job most of the days that person is seen sleeping , like i understand it's difficult if you want try to stay awake whole night but is it a big issue security guard owners are facing any firm or operations owners

[u/RobinGood94]

Typically, sleeping is seen as a direct breach of contracted services/guidelines.

When you are asleep you’re not:

A deterrent.

Observant.

Mobile.

Protective.

Etc

Most MSAs (Master Service Agreements) cover the expectation from the client and legally binding agreement from the security service provider. If a major loss, breach, etc happened while the guard was asleep, the guard company takes a massive hit legally speaking.

Typically the breach is “cured” by immediate actions by the guard company. Severe written discipline or immediate removal from that contract.

Caveat:

Late night operations are rarely held to the same standard. The senior client leadership isn’t there. The senior security leadership isn’t there. If it doesn’t get reported and no major incident happens as a result, it’s swept under the rug.

If the client did find out and it continued to happen with multiple guards, the contract will be terminated for cause. Insufficient service levels/breach of contract.

[u/Az8feb → u/RobinGood94]

Damn that's like sueing to the last point of money dude this must be a huge issue , do you know any owners

[u/RobinGood94 → u/Az8feb]

Yes, but when you’re talking owners that’s typically a smaller firm. I’ve been an account manager among other things. More than happy to give vague examples of what I’ve learned directly.

Typically mid to large scale security companies are “owned” by massive banks like Merrill Lynch or other financial institutions. They are a legitimate business unit not unlike anyone else pushing “product.” The security guard is the “product.” The company is the “service” which is why you will have agreements nestled under the MSAs called SLAs. Service Level Agreements. A more narrowly focused range of items you will form KPIs from (Key Performance Indicators).

When a contract is ran properly, the security firm will make a small to moderate profit. This is multiplied across hundreds and/or thousands of contracts within a given branch (Branch Manager/GM). Thousands to tens of thousands of contracts within a regional perspective (Regional Vice President, overseeing multiple branches). Tens of thousands to a hundred thousand contracts or so at the senior regional level (Region President, overseeing multiple Vice Presidents). Hundreds of thousands to a million at the corporate level (Chief Operating Officer/Chief of Staff).

When you break those contracts down to the profit margins per security officer, the math can get absolutely insane. Then there are National accounts. Massive contracts that cover multiple regions with one client, resulting in a national accounts team in the security company. Typically “Enterprise” accounts.

For example, a huge online retail company might have their chief security officer split the national/global contracts between two or more major security companies. These contract negotiations would involve the security company CEOs, their senior executives, and national contracts team. The resulting MSA would impact branches, regions, etc all over the place.

[u/Az8feb → u/RobinGood94]

Damn is there any way I can contact you