Tracking COI expirations across a portfolio
A certificate is a snapshot, not a standing proof. The real work of compliance is keeping ahead of expiration dates — and acting the moment one lapses. This guide sets out a cadence that works whether you manage five tenants or five hundred.
A renewal cadence that catches lapses
Run this timeline for every tenant, anchored to the certificate's expiration date — not the day you received it.
1.Send the renewal request to the tenant and copy their broker. Confirm the contact details are still current.
2.First reminder. If no response, escalate the tone — reference the lease obligation and a deadline.
3.Second reminder to the broker directly. Begin documenting non-response in case of a lapse.
4.Mark the tenant as expired. Notify the tenant in writing that coverage has lapsed and a replacement is required immediately.
5.Escalate to legal if unresolved. Track every notice on the tenant record so the timeline is defensible.
Seeing the whole portfolio at once
Spreadsheets break down because they sort by collection date, not expiration. The fix is a single view of every tenant's next expiration, filterable by property and status. In certflows the dashboard shows compliance counts at a glance — no COI on file, expired, expiring soon, compliant — and a calendar view plots every upcoming renewal so the next cluster is visible weeks ahead.
When reminders should stop
Reminders that keep firing after a tenant is compliant are worse than no reminders — they train tenants to ignore you. The right behavior is automatic: reminders run on your cadence for missing or expiring certificates, and switch off the moment a compliant replacement is verified. In certflows, reminder sends are logged on the tenant's activity feed, so you can see both that the chase happened and that it stopped.
What to do when a lapse happens
- Mark the tenant expired immediately. Don't wait for the next renewal cycle — a lapse is a lapse from the day coverage ends.
- Notify the tenant in writing. Reference the lease obligation and require a current certificate. Copy the broker.
- Notify ownership for material gaps. A short lapse in a low-risk suite may be tolerated; a lapse in a high-traffic or high-value unit should reach the asset owner.
- Escalate to legal if unresolved. Send the matter to your legal contact with the full notice timeline attached.
- Record a waiver if ownership accepts the gap. Time-boxed, with an end date and a counter-signature.
Every one of these steps — the notices, the escalation, the waiver — is timestamped on the tenant record in certflows, so the timeline is defensible if a claim is contested years later.
Frequently asked questions
When should renewal reminders stop?
The moment a compliant replacement certificate lands. Continuing to chase an already-compliant tenant is noise that trains tenants to ignore your messages — so reminders should switch off automatically once coverage is verified.
How do I track expirations across many properties?
Use a single diary keyed by expiration date, not by collection date. Sort by the earliest expiring certificate across the portfolio and work from the top. A calendar view of upcoming expirations is the fastest way to spot the next cluster.
What if a certificate arrives already expired?
Treat it as a lapse, not a renewal. The tenant was uninsured between the old policy's end and the new one's start. Record it, notify ownership if the gap is significant, and require a current certificate before marking the tenant compliant.
Looking for the basics first? Start with What is a Certificate of Insurance? or the per-tenant compliance checklist.