How to track certificate of insurance renewals for clients without dropping a 60-day ball

The SiloBase team · 2026-09-05

Every certificate of insurance your agency issues is a promise that coverage evidence stays current — and every certificate has an expiration date. Track certificate of insurance renewals for clients poorly and the failure usually surfaces at the worst possible moment: a carrier asks for proof, a certificate holder flags a lapsed COI, or an errors-and-omissions review uncovers the gap. The good news is that the renewal problem is solvable with a simple, well-known cadence. The bad news is that most agencies run that cadence through the one tool that cannot actually enforce it.

The 60/30/14/7-day ladder, and why it exists

The standard recommendation is to touch each certificate four times before it lapses: at 60 days, 30 days, 14 days, and 7 days. E&O best-practice guidance from IIABA / Big I has long pushed this queue, and the logic is straightforward — each step is a different kind of action:

• 60 days out — open the renewal with the carrier and confirm the policy is on track to renew. Plenty of runway if anything is off.
• 30 days out — verify the renewal terms and flag any change in coverage, limits, or named insureds that will carry onto the new certificate.
• 14 days out — get the updated certificate issued and delivered to the certificate holder, so there is no gap on the effective date.
• 7 days out — final confirmation that the holder has the correct, current certificate and that nothing fell through.

Notice what this ladder is really for: it is a series of decision points, not just reminders. Each touch asks a specific question and has a specific owner. Treating all four as the same "ping the producer" reminder is how the ladder quietly fails.

Where the spreadsheet breaks

Most independent agencies implement the ladder in Excel or Google Sheets because it is free and everyone already has it. That is fine for listing renewal dates. It is not fine for running the queue, for three reasons:

1. No automatic triggers. A spreadsheet does not reach out at day 60 and ask whether the carrier was contacted. The renewal date sits in a cell until a person opens the file, scrolls to the right tab, and notices it.
2. No ownership or handoff. When a producer leaves or a CSR is out, the "who is following up on Coastal Builders?" answer lives in someone's head or in a cell comment nobody reads. Renewal tracking that depends on memory is not tracking.
3. No audit trail. After the fact, a spreadsheet shows that a date existed. It does not show that a reminder fired, that a certificate was re-issued on a specific date, or that a second person reviewed it — the exact record an E&O review will request.

The uncomfortable truth is that a spreadsheet does not drop the 60-day ball; a person does, and the spreadsheet merely fails to catch them.

A durable renewal process, step by step

Whether you adopt software or not, the highest-value change is to make each step of the ladder a named, recorded action:

1. One source of truth per certificate. Every COI has exactly one row that links the client, the policy, the carrier, the holder, the additional insureds, and the expiration date. No scattered tabs, no second "unofficial" list.
2. A named owner per renewal. Assign each certificate's renewal to one person. The owner is responsible for the 60-day carrier contact, not just for "watching" the date.
3. Automatic cadence, not a memory aid. The 60/30/14/7 reminders should fire on their own and surface as a short queue the owner works, rather than as a file they have to remember to open.
4. Record the action, not just the date. Log when the carrier was contacted, when the renewal terms were confirmed, when the new certificate was issued, and who reviewed it. That log is what turns a process into a defense.

The difference between a process like this and the spreadsheet approach is subtle on a good day and enormous on a bad one. On a good day, both get the certificate renewed. On a bad day — a missed renewal, a lapsed certificate, a claim — only the recorded process gives the agency a defensible story.

Why a purpose-built ledger changes the math

Certificate errors are a documented top E&O exposure for agencies. A tool that enforces verification before issuance, keeps a second-person review, and archives history is selling risk reduction, not just convenience. That is why a focused COI ledger — one that issues, tracks holders, and runs the 60/30/14/7 ladder automatically — is worth more than a free spreadsheet the moment the first renewal is missed.

Join the SiloBase early-access waitlist →