How to Track Carrier Insurance Certificates: A Broker's Workflow
If you book loads with carriers, tracking insurance certificates is one of those jobs that feels small until it isn't. A single expired certificate that slips through can turn into a covered claim that isn't actually covered. Most small brokerages handle this with a spreadsheet, a shared inbox, and someone's memory — and it works right up until the day it doesn't.
This is the workflow we recommend to brokers who want a system they can hand to a new hire without a two-hour explanation. It has four stages: capture, monitor, collect, and review. Each one does a specific job, and the whole thing runs on a weekly rhythm.
What "tracking" actually means
Tracking a certificate of insurance (COI) isn't just storing a PDF. It means knowing four things at any moment, for every carrier you use:
- What coverage they currently have on file (auto liability, cargo, general liability) and the limits.
- When the current certificate expires.
- Whether a renewal has been requested, and how many times.
- Who on your team last touched the record, and when.
If your current setup can't answer all four in under a minute, you don't have a tracking system — you have a folder. For more on the bigger picture, see our carrier compliance guide.
Stage 1: Capture the certificate correctly
Bad data at intake is the root cause of most missed renewals. When you onboard a carrier, capture these fields in a consistent format the first time:
- Legal carrier name and MC/DOT number (so duplicates don't sneak in as "Apex" and "Apex Logistics LLC").
- Insurance agent or carrier contact email — the person who actually sends renewals, not just the dispatcher.
- Coverage types and limits as written on the COI.
- Certificate expiration date in one date format (use YYYY-MM-DD internally to avoid 03/04 vs 04/03 confusion).
- The PDF itself, named so you can find it:
ApexLogistics_COI_2026.pdf.
If you're setting up a carrier from scratch, our carrier onboarding guide walks through the full intake. The key idea: capture the expiry date as structured data, not buried inside a PDF you'll have to reopen later.
Stage 2: Monitor expirations on a schedule
Monitoring is where spreadsheets quietly fail — they don't tell you anything until you open them and sort. Replace "remember to check" with a fixed cadence and a status view.
Use four status buckets
- Active — current certificate, more than 30 days to expiry.
- At risk — expires within 30 days, renewal not yet received.
- Expired — past the expiration date with no valid replacement.
- Pending review — a renewal came in but a person hasn't confirmed the new date.
Run a Monday review
Once a week, look at the "at risk" and "expired" buckets only. That's the actionable list. If you're using insurance certificate tracking software, this view builds itself; if you're on a spreadsheet, add a column that calculates days-to-expiry and filter on it every Monday morning.
Stage 3: Collect renewals before they lapse
The goal is to get a fresh certificate before the old one expires, not to scramble after. The reliable way to do that is a reminder cadence that starts early and repeats:
| Days before expiry | Action |
|---|---|
| 45 | First renewal request to the insurance contact |
| 30 | Second reminder; move carrier to "at risk" |
| 14 | Third reminder, flagged urgent |
| 7 | Final reminder + internal flag to pause bookings if no response |
Make it easy for the carrier to respond. Asking them to log into a portal, create an account, or fax something adds friction that delays the renewal. A single upload link that takes 30 seconds gets far better response rates. We go deeper on timing and wording in carrier renewal reminder best practices.
Stage 4: Review the new date before you trust it
When a renewed certificate arrives, do not let the system silently update the expiration. Automated extraction (OCR or AI reading the PDF) is a helpful suggestion, not a fact. A person should confirm:
- The certificate belongs to the right carrier and MC number.
- The coverage types and limits still meet your requirements.
- The new expiration date matches what's printed on the document.
- The certificate holder/additional insured is correct, if you require it.
Only after a person confirms should the carrier's status flip back to active. This single rule prevents the most embarrassing failure mode: a system that marks a carrier compliant based on a misread date.
Keep an audit trail without extra work
Every step above should leave a record automatically: certificate uploaded, reminder sent, date confirmed, status changed, by whom, and when. You don't need an enterprise system for this — you need each action to write a line to a log you can export. That record is your proof of process when it matters.
A realistic weekly rhythm
Put together, the workflow takes most small brokerages 20–30 minutes a week once carriers are loaded:
- Monday: review the "at risk" and "expired" buckets; confirm any pending renewals.
- Ongoing: reminders go out automatically on the 45/30/14/7 cadence.
- On upload: a person reviews and confirms the new date the same day it arrives.
- Monthly: spot-check a few carriers' coverage limits against your requirements.
That's the whole system. It's deliberately boring — boring is what keeps certificates current.