A certificate of insurance proves a policy existed on the day it was issued. It proves nothing about today. That single sentence is the whole problem, and it is why COI management is the quietest failure mode in carrier vetting.

The packet gets collected at onboarding. The COI goes in the file. The carrier hauls sixty loads over the next eight months. Somewhere in month three the policy lapses for non-payment, or the cargo limit gets reduced at renewal, or the certificate holder line stops naming you. Nothing in the process notices, because the process ran once.

Then a $180,000 load gets damaged and the gap becomes a discovery request.

Why this survives in otherwise disciplined operations

Carrier vetting is one of the areas where brokers have invested real effort. Authority checks, safety ratings, fraud screening, continuous monitoring — most decent-sized brokerages do all of it.

COI verification stays manual longer than the rest for three reasons:

It looks finished. A PDF in the carrier file feels like a completed control. Authority status obviously changes, so people check it. A certificate looks like a document, and documents feel static.

The failure is silent. An expired COI produces no operational symptom. The carrier still shows up. The load still delivers. The gap only surfaces at claim time, which may be a year later and is somebody else's problem by then.

The renewal date is inside the PDF. It is not a field in most systems. It is a line of text in an image, which means checking it requires someone to open the file.

What actually needs verifying, and how often

"Insurance is on file" is not a control. Five things need to be true simultaneously, and each fails independently:

• Policy is in force — Failure mode: Lapsed for non-payment mid-term · Detection window: Immediate, if monitored
• Expiration date — Failure mode: Renewed late or not at all · Detection window: Known in advance
• Cargo limit sufficient — Failure mode: Reduced at renewal, or below load value · Detection window: At renewal
• Auto liability limit — Failure mode: Below your contractual minimum · Detection window: At renewal
• Certificate holder named — Failure mode: Your entity dropped from the certificate · Detection window: At reissue
• Endorsements intact — Failure mode: Exclusions added at renewal · Detection window: At renewal

The pattern is clear once it is laid out: most of these fail at renewal, and renewal dates are knowable in advance. This is not a monitoring problem requiring exotic data. It is a calendar problem nobody owns.

How often should carrier insurance be verified?

Carrier insurance should be verified continuously rather than at onboarding — at minimum, re-checked before any load tenders to a carrier whose certificate is within 30 days of expiration, and re-read in full whenever a new certificate arrives. Point-in-time verification at onboarding leaves an unmonitored gap for the entire life of the relationship.

The operational version of "continuously" is three rules:

1. Block at expiry. A carrier whose COI has lapsed cannot be tendered a load until a current certificate is on file. Enforced in software, not in a rep's memory.
2. Chase before expiry, not after. Requests for a renewal certificate go out on a schedule ahead of the date, so coverage never actually lapses in your file.
3. Re-read every new certificate. A renewal is not a formality. Limits and endorsements change at renewal, which is exactly when nobody looks closely.

Where automation earns its place

This workflow has the profile that makes agents genuinely useful: it is document-shaped, high-volume, rule-driven, and the errors are recoverable. There is no judgement to preserve in reading an expiration date off a certificate.

The concrete steps an agent handles end to end:

• Extract the fields. Effective and expiration dates, cargo and auto liability limits, certificate holder, named endorsements — pulled from the certificate rather than typed by a coordinator.
• Compare against your requirements. Contractual minimums vary by customer and commodity. A $100,000 cargo limit is fine for most freight and not fine for high-value loads.
• Chase the renewal. The email to the carrier's insurance agent thirty days out, the follow-up at fifteen, the escalation at five. This is pure volume work.
• Flag the substantive changes. When a renewal arrives with a lower cargo limit or a new exclusion, that goes to a human. When it arrives identical, it files itself.

That last split is the important one. Automation here is not about removing the underwriter's judgement — it is about ensuring a human only spends attention on the certificates that actually changed.

The connection to fraud

There is a second reason this matters right now. Certificate fraud — forged COIs, certificates from agencies that do not exist, real certificates for policies already cancelled — is a known vector in cargo theft schemes. Debales has covered the identity verification side of carrier vetting in detail, and insurance documentation is one of the artifacts most commonly falsified.

Verifying a certificate directly with the issuing agency rather than accepting the PDF at face value is the control that closes it. It is tedious at volume, which is precisely why it gets skipped, and precisely why it is worth automating. The broader carrier vetting checklist treats it as a standing obligation rather than an onboarding step, and that framing is the right one.

Frequently asked questions

Is a broker liable if a carrier's insurance lapsed after onboarding? Liability turns on the facts and the jurisdiction, but the practical exposure is clear: a plaintiff will ask what your process was for confirming coverage remained in force, and "we collected a certificate at onboarding" is a weak answer when the loss occurred eight months later.

What cargo limit should we require? It depends on commodity value, and a single blanket minimum is the common mistake. The useful control is comparing the certificate's cargo limit against the declared value of the specific load being tendered, which requires the check to run at tender rather than at onboarding.

Can certificates be verified directly with the insurer? Yes, and it is the strongest control available. It is also the step most often skipped because it does not scale manually — which makes it a strong automation candidate.

What about carriers who use a monitoring service? Third-party monitoring services help and many brokers use them. They still leave the comparison against your contract-specific requirements, and the load-level value check, to you.

The bottom line

A COI is a snapshot. Treating it as a subscription is how a routine cargo claim becomes an uninsured loss, and the failure is silent right up until it is expensive.

Block tendering on lapsed certificates in software, chase renewals before the date rather than after, re-read every renewal for changed limits and endorsements, and verify with the issuing agency rather than trusting the PDF.

Debales deploys AI agents for freight quoting, order processing, ETA updates, and multi-channel customer communication — extracting and re-verifying carrier documents continuously, and escalating only the certificates that changed. Book a demo.