Why Security Contracts Go Bad
— and How to Spot It Early

Picture the overloaded ops manager's week. They're responsible for making sure only site-trained officers are deployed. They run recruitment interviews. They attend client meetings. They take calls from officers at any hour — relentless, often tedious calls. And one incident on a single site can swallow half a day: the investigation, the disciplinary, the paperwork.

So they triage toward the fires. And here's the counterintuitive part that kills contracts: the sites that are performing well get the missed management visit. No issues there, right? So skip it this week. And the next. Wrong — and this is where it unravels.

Because the officers on that "good" site notice. No visit, no communication, no sign of their manager. Morale drops. Complacency creeps in. Standards start to slip — quietly at first. Then the client notices: an officer arriving late, a scruffy uniform, patrols not being done. Then an officer raises a pay query, it doesn't get resolved quickly, and — this is the moment it goes public — the officer mentions it to the client.

Now the ops manager has a portfolio of flames. Several sites lit at once, all demanding attention they don't have time to give. They fire-fight, they burn out, they leave. Gardening leave, a fresh start somewhere else — and the new ops manager inherits the same impossible portfolio. The cycle repeats. None of it was the officers' fault. The structure made it inevitable.

Now you know the mechanism, you can catch it early. Watch for these:

• Management visits become less frequent — or you stop seeing your ops manager altogether.
• Communication goes quiet. You're the one chasing for updates, not the other way round.
• Small standards slip — timekeeping, uniform, patrols logged late or not at all.
• Your monthly review is all green KPIs but you can't point to anything that's actually improved.
• Officers seem unsettled, or you hear about pay or rota issues from the officers themselves.
• Faces change — officer turnover on your site climbs, and you keep meeting new people.

Any one of these on its own might be nothing. Two or three together is the spiral starting. Don't wait for the blow-out.

Once you understand the death-spiral, you understand why we run Risk Secured the way we do — and why we'll sometimes say no.

We only take on contracts that are the right fit for both of us: geographically serviceable, and well within my managers' and my own resources to deliver the level of on-site management that good security actually needs. We will not load ourselves past the point where the well-run sites start getting neglected, because that's the exact mistake that kills contracts. If a contract isn't right — too far, or beyond what we can manage properly — we'll tell you honestly, rather than win it and fail it.

It might sound strange for a security company to say it might turn your work down. But after thirty years, I'd rather do that than become another portfolio of flames. We're control freaks, not fail freaks. That selectivity is exactly what protects the clients we do take on.

Read our guide to ethical security procurement for the SIA's own checklist, or find out why clients choose us.