The Contract Lost in 30 Days
The patrol logs were complete. The timeline was never assembled.
What Happened
A client commissioned a routine review of guard deployment logs against closed-circuit television footage at a commercial property. This wasn't triggered by a complaint — it was standard due diligence, the kind that happens quarterly.
The patrol logs showed guards completed their rounds on time, confirming presence at each checkpoint. The CCTV footage showed the post was empty at those times.
The client compared the two documents. No one internally had made that comparison first.
What the Documentation Looked Like
The Outcome
Contract terminated for cause — no severance paid
Former client refused to provide a professional reference
Insurance premiums increased at next renewal cycle
No legal recourse — the documentation spoke for itself
What It Would Have Looked Like With OpsCom
OpsCom correlates guard tour system data with CCTV timestamps automatically. If the post was empty at 22:00, that would surface during internal review — before the client asked.
At that point, the firm could have investigated why the post was unmanned, documented the actual sequence, and entered the client conversation with a complete picture. Instead, the client made the comparison first.
"The logs were filed. The timeline was never assembled internally. The contract was gone in 30 days."
The documentation that should have protected the firm became evidence of a gap they hadn't addressed.
The Lesson
This isn't necessarily about ghost patrol — it could be inattention, a system malfunction, a shift change gap. The issue isn't whether the gap exists. It's whether you can prove what actually happened — before the documentation defines the narrative for you.
Protecting your guard means protecting your company.When the documentation can't defend the guard's actions, the guard is exposed first — and then the company follows.