Renewal workflow

How to Track COI Expiration and Renewal Dates

A useful COI tracker connects every policy expiration to a project, owner, evidence checklist, delivery destination, and follow-up date. A spreadsheet containing only vendor names and one expiration date is rarely enough.

By COI Workbench Editorial Team · Reviewed September 2026 · General U.S. guidance

Track evidence, not coverage conclusions. A date tracker can show when documents should be requested. It cannot verify that insurance is active, determine claim coverage, or replace direct confirmation from the agent or insurer.

The minimum useful renewal record

Field	Why it matters	Privacy note
Project or client reference	Connects the renewal to real work.	Avoid confidential descriptions in shared calendars.
Coverage line	Prevents one expiration from standing in for every policy.	No policy number is needed for a reminder.
Effective and expiration dates	Defines the displayed policy period.	Use the issued evidence as the source.
Internal request date	Creates processing and correction time.	This is an organizational deadline.
Client delivery deadline	Separates your follow-up from the external requirement.	Store portal credentials elsewhere.
Required documents	Tracks certificate and endorsement copies together.	Do not attach documents to a public calendar.
Responsible person	Prevents an ownerless reminder.	Use approved internal contact details.

Why one expiration column can fail

A contractor may carry general liability and umbrella policies with one renewal date, commercial auto with another, and professional liability with a third. A single “COI expires” field can trigger the wrong request or miss a separate renewal entirely. Track the coverage line first and the certificate package second.

King County’s contract guidance requires proof of active insurance throughout the contract and similar documentation at each renewal date. That public example illustrates why evidence management continues after onboarding.

Choose reminder intervals deliberately

There is no universal reminder period for every project. Work backward from the client deadline, agency processing time, internal approvals, portal review, and correction allowance.

Early review

Useful for complex renewals, multiple endorsements, or projects with strict portals.

Requirement check

Confirm entities, limits, project dates, and the current contract version.

Agent request

A common internal checkpoint, but not a promise of availability or timing.

Escalation

Recheck unresolved documents and client delivery status.

The COI Expiration Gap Planner lets you select one lead time and download calendar events for each tracked expiration. Adjust the reminder to the actual contract and workflow.

Separate four different statuses

Request scheduled: an internal reminder exists.
Request sent: the agent has received current instructions.
Documents received: a new certificate or endorsement package has arrived.
Client accepted: the intended reviewer has completed its own process.

Do not change “request sent” directly to “complete.” A document can be issued with an entity mismatch, old address, missing endorsement, or limit that no longer matches the requirement.

A renewal quality-control checklist

Compare the named insured with the contracting business.
Confirm each required policy has a new effective and expiration date.
Recheck every limit using the Coverage Limit Comparator.
Confirm the certificate holder and additional-insured entities separately.
Match endorsement references and policy terms with the new period.
Verify the project or contract identifier.
Submit through the required channel and preserve confirmation.
Schedule the next relevant renewal date immediately.

Handling projects that change

Extend the project end date when a change order, delay, warranty obligation, or continuing service period changes the timeline. Re-run the date comparison rather than assuming the original evidence plan remains sufficient. If the insurance requirement changes, send the revised written clause to the agent and preserve the client’s clarification.

Calendar privacy and security

A calendar event is convenient but may synchronize to personal devices or external services. Use a neutral project reference, coverage line, and internal action. Do not include policy numbers, full certificates, confidential contracts, claim facts, personal data, or portal passwords.

The planner’s .ics download is created locally. Importing it into another service is your decision and is then governed by that service’s privacy settings.

Frequently asked questions

Should I track the certificate issue date?

Keep it for document history, but renewal reminders should normally use the applicable policy expiration and the contract’s evidence deadline.

What if several policies expire on the same date?

Track them as separate lines so each returned certificate and endorsement package can be checked. The calendar can contain one event per line.

Does receiving a renewed certificate prove the client accepted it?

No. Record client or portal acceptance separately from receipt.

Can I rely on cancellation notice instead of tracking expiration?

No blanket assumption is appropriate. Notice depends on policy language and law. Maintain your own renewal workflow.

How long should records be kept?

Retention depends on contracts, law, claims, and company policy. Ask qualified counsel or a records professional for a rule appropriate to the business.

Sources and limits

Reminder intervals and examples are organizational suggestions, not statutory deadlines or insurance advice.