Insurance Claim Denied: When Missing Patrol Logs Turn One Break-In Into Two Losses

The Policy Language Still Says "Watch Clock"

Open a standard U.S. commercial property policy with a protective safeguards endorsement attached, and you will find a list of safeguards identified by symbol. P-1 is the automatic sprinkler system. P-2 is the automatic fire alarm. P-3 is the security service — described, in the current ISO form, as a service with a "recording system or watch clock," making hourly rounds when the premises are not in operation.

Read that again, because the entire industry walks past it every day.

The insurance contract does not ask whether a guard was employed. It asks whether the rounds were made and recorded. The watch clock — a mechanical device where a guard turned a numbered key into a paper dial to punch a timestamp — is still named in the policy language, because when these forms were written, that punched dial was the only artifact that could settle the question afterward.

This is the origin of the entire guard tour category, and it is worth being precise about it: patrol verification was not invented so supervisors could manage guards. It was invented because carriers refused to grant a premium credit for a round nobody could evidence. Everything since — the watch clock, the RFID wand, the modern electronic guard tour system — is the same instrument answering the same question with better technology.

The technology moved. The question never did.

What the Endorsement Actually Requires

Two ISO forms matter here, and security professionals should know the difference cold.

Protective Safeguards (CP 04 11) — the form that replaced the older IL 04 15 — makes maintaining the scheduled safeguards a condition of the insurance. If the scheduled safeguard isn't maintained, coverage for fire loss can be suspended. Burglary and Robbery Protective Safeguards (CP 12 11) works the same way for theft losses. That second one is the form standing behind most break-in claims at guarded sites.

Three characteristics of these endorsements make them dangerous in a way most operators underestimate:

• They are conditions, not suggestions. The insured warrants that the safeguard is maintained. This is the exchange for the premium credit the client received when the guard service went on the schedule.
• They are not causation tests. Disputes under these endorsements turn on whether the scheduled safeguard was maintained — not on whether maintaining it would have prevented the specific loss. A carrier does not have to prove the missed round let the burglar in.
• They travel into contracts you've never read. Builders risk policies routinely go further and warrant the security service explicitly: a watchman making no less than hourly rounds of the entire jobsite during nonworking hours, maintaining logs of those rounds. That obligation was accepted by the general contractor, priced by the carrier, and then quietly handed down to whoever posts the guard.

Now the part that concerns you directly. The endorsement sits in the client's policy. The obligation is the client's obligation. But the client did not walk the property at 2:40 a.m. Your guard did. Which means the client's ability to demonstrate compliance is entirely dependent on the records your company keeps.

You are not a party to the policy. You are the sole custodian of the evidence it runs on.

The Adjuster's First Question

Here is the sequence, compressed.

A break-in is discovered at 6 a.m. The client reports the loss. Within days, an adjuster is assigned and two investigations begin in parallel: one valuing the damage, one confirming coverage. The second one is the one nobody prepares for.

The coverage side asks for what the site is supposed to have had: alarm records, camera retention, access control history, and — where a security service is scheduled — the record of the rounds. Not a description of the rounds. The record.

Answering a client who challenges a single night is one problem, and usually a solvable one — a supervisor calls, context gets supplied, the relationship absorbs it. A coverage investigation is not that. Nobody calls. The file is read by a professional who was not there, has no relationship with your company, and is evaluating one question: does the documentation support what the policy assumed?

What most incumbent security companies send back is a scanned daily activity report. Consider what that document is, from the adjuster's chair:

• It was written by the guard whose performance is in question.
• It is self-reported, with no independent verification of time or place.
• It contains no evidence of when it was written — only what it says about when the round happened.
• It could have been completed at 3 a.m., at end of shift, or on Tuesday afternoon in the branch office. Nothing on the page distinguishes those three.

Be clear about the mechanism, because the fearmongering version of this article would get it wrong: no carrier denies a claim simply because a log is handwritten. Handwritten logs are accepted every day. What actually happens is quieter and worse. Your document doesn't rebut anything. It cannot contradict the carrier's reading of the file, it cannot establish that the 2 a.m. round covered the loading dock, and it cannot be checked against anything. The carrier's position on compliance goes unopposed — not because it's strong, but because nothing on your side is capable of answering it.

That is a very different failure from being wrong. It's being unanswerable.

Two Losses, Not One

The first loss is the property. The client's problem.

The second loss is what happens when the claim is reduced, contested, or denied — and this is where security company owners consistently underprice their exposure, because they assume a coverage fight is a matter between the client and the carrier. It isn't. It's a search for who is responsible for the safeguard the policy was priced on.

That search has a short list, and you are on it.

• Contractual liability. Your service agreement almost certainly obligates you to perform and document patrols. If the client's recovery fails on evidence you were contractually responsible for producing, the breach argument writes itself.
• Subrogation. If the carrier does pay, it can step into the client's shoes and pursue the party whose failure contributed to the loss. Your general liability and E&O carriers are now in the conversation — which means your own premiums are in the conversation, at your own renewal.
• The account. However the coverage question resolves, the client has now experienced your company as the reason a six-figure recovery became a legal argument. That relationship does not survive to renewal, and the reason it ends will be documented in a claim file the next bidder never has to mention.

Set against that exposure: a software-based patrol system, running on the phones your guards already carry, costs a fraction of one guard's monthly billing. There is no honest way to make that a difficult budget conversation. It's one bad night against one line item.

Building Records That Survive a Loss Investigation

Evidence cannot be assembled after the event. It can only be collected before one. The operational sequence below is deliberately mapped to what the endorsement language actually asks for, not to what a software feature list wants to sell.

FAQ