← Field notes
What the client never sees,
There's a strange gap at the center of how event security gets sold and delivered, and once you see it you can't unsee it.
The client and the operator agree on a contract. So many posts, so many hours, signed, dated, billed. That's the promise. Then the event happens, and the entire delivery of that promise happens somewhere the client cannot see, on a whiteboard, in a trailer, in the heads of a few supervisors running radios. And then at the end, you send an invoice, and everybody trusts that the thing in the contract is the thing that happened on the ground.
Most of the time, it is. But "most of the time, on trust" is a thin place to be standing when money's involved.
Think about where the promise lives versus where the delivery lives. The promise is a contract, a spreadsheet, an email thread, sitting in someone's inbox. The delivery is a whiteboard that gets wiped at the end of the night, a stack of sign-in sheets, a supervisor's memory of a long shift. The promise is one kind of document. The delivery is a completely different kind, if it's a document at all.
The promise lives in a contract. The delivery lives on a whiteboard that gets erased. The two never meet, and you find that out the day someone asks them to.
And here's the part that always got me. The shift lead, the person actually responsible for delivering the promise, usually can't even see the promise. They're handed a schedule, not a contract. They know they're supposed to staff the posts on their list, but they often don't have line of sight to what the client was actually told they'd get. So the person most able to make sure the promise gets kept is working partially blind to what the promise even was.
I want to be straight with you, because these notes are useless if they're not honest. I have not personally been in a knock-down billing dispute where a client demanded proof of coverage and I couldn't produce it. I've been lucky, and I've worked with people who run clean operations.
But I've spent enough years close to this to know exactly how it would go, and to know it's a matter of when, not if, for the industry as a whole. A client gets a complaint, or an incident happens at a specific spot at a specific time, or a finance person decides to scrutinize an invoice. They ask a simple question. "Show me that this post was covered, continuously, for the hours we paid for." And the honest answer, on a whiteboard operation, is a shrug and a stack of sign-in sheets and a lot of "I'm pretty sure."
Pretty sure does not win that conversation. Pretty sure is how you lose a contract you actually fulfilled, because you delivered the coverage but you couldn't prove it. The work was real and the proof was air.
What really gets me is the asymmetry. You did the hard thing. You stood up the posts, you covered the breaks, you pulled people into overtime when the schedule came up short, you ran a clean event. All of that is real labor and real cost. And then the one artifact that would let you prove all of it, a clean record of who was on which post for which hours, measured against what the client signed off on, simply doesn't exist, because the tools you ran on couldn't produce it.
So you carry all the risk of the delivery and almost none of the evidence of it. That's a bad trade, and operators make it on every event without thinking about it, because there was never a tool that made the evidence a free byproduct of doing the work.
I wanted two things. First, I wanted the client to be part of the plan up front, to see the coverage, agree to it, and sign off, so the promise is explicit and shared instead of buried in an email. And second, I wanted the delivery to measure itself against that signed-off promise automatically, so that at the end I could hand the client a single clean view: here's what you signed off on, here's what we delivered, post by post, hour by hour.
Not a defense. A record. The difference between walking into that conversation with "I'm pretty sure" and walking in with "here's exactly what happened, against exactly what we agreed" is the difference between hoping you keep the contract and knowing you will.
The best part is that it shouldn't cost the operator any extra work. If the record is just a byproduct of running the site, of the moves you were already making, then proving coverage stops being a thing you scramble to assemble after the fact and becomes a thing you already have, sitting there, the moment anyone asks. You give up none of your control over operations, and you gain the one thing that settles a dispute before it starts.
Trust is great. Trust plus a clean record is how you stay in business.
Hand the client coverage of record, post by post, against what they signed off on. The proof writes itself.