COI Expiration Alerts: How Contractors Stop Lapses
COI expiration alerts are automatic reminders that fire before a subcontractor’s or vendor’s certificate of insurance runs out, so you can collect a renewed certificate while the work is still covered. For a contractor, a good alert system does three things: it reads the expiration date from every policy line, warns the right people weeks ahead, and keeps chasing until a new certificate is on file. This guide shows where the dates live, when to alert, how to build the workflow, and where spreadsheets stop working.
TL;DR
- A COI lists an expiration date for each line of coverage, so you need one alert per policy, not one per subcontractor.
- Alert early. A 30-day diary is the long-standing minimum, and many teams add earlier and later steps on top of it.
- A certificate on file does not prove the policy is still active, so alerts support your risk process but do not replace it.
- Spreadsheets work for a handful of subs. Past that, link alerts to onboarding, payment and scheduling so a lapse actually stops something.
- Assign one named owner for every alert, and write down what happens when a renewal does not arrive.
Table of Contents
- What a COI expiration alert actually tracks
- What happens when a COI expires
- When to send COI expiration alerts
- Who should receive the alert and own the follow-up
- Build a COI expiration tracking workflow in six steps
- Spreadsheet reminders vs. automated COI tracking
- Common mistakes that let a COI lapse
- Our perspective: alerts belong inside the job, not beside it
- Put COI alerts in the same system as your jobs
- FAQ
- Sources
What a COI expiration alert actually tracks
A certificate of insurance is a summary document. ACORD explains that it provides information about insurance policies, is not a policy itself, and does not provide, endorse, amend, extend or alter policy terms. That matters for alerts: the date you track is the date the insurer printed, and the certificate cannot extend it.
On a standard ACORD 25 Certificate of Liability Insurance, policy effective and expiration dates sit in the coverages section, next to each line of insurance and its policy number. So the answer to “where is the expiration on a COI?” is: in the row for each coverage, not in a single box at the top.
For a typical subcontractor you will see several rows, and each can expire on a different day:
- Commercial general liability
- Automobile liability
- Umbrella or excess liability
- Workers’ compensation and employer’s liability
- Professional liability, for design-build or engineering scopes
If you track only one date per sub, you will miss the policy that lapses first. Track each line separately and alert on the earliest one.
What happens when a COI expires
The certificate itself does not “turn off.” The risk is that the policy behind it has ended or will end without a replacement, and nobody on your side noticed. Risk Management Magazine notes that if the underlying policy is cancelled, certificate holders may lack coverage even while a certificate remains on file.
In practice, an expired certificate can mean:
- A sub is on your site without proof of current liability or workers’ comp coverage.
- An injury or property damage claim lands on your own policy or your balance sheet.
- Your additional insured status is in doubt for the period after the lapse.
- Owners, lenders or your own insurer find a documentation gap during an audit.
If a sub has already worked through an expired period, document the lapse, then talk to your insurance broker and legal counsel about your exposure and whether any retroactive fix is possible. Do not assume the sub’s next renewal covers the gap.
The same article makes a second point worth keeping: certificate review alone cannot remove risk, because a policy can be cancelled or changed after the certificate is issued. Alerts reduce the chance of a quiet lapse. They are one control among several, alongside contract insurance requirements and endorsements.
When to send COI expiration alerts
The oldest rule of thumb comes from certificate review guidance: if a policy will expire before the contractual obligation ends, diary the certificate to 30 days before expiry and request a renewal certificate from the producer or the insured. Thirty days is a floor. Subcontractors often need time to reach their broker, and brokers need time to issue the certificate.
A practical schedule for a contractor with active jobs:
| Timing | Who gets it | What it asks for |
|---|---|---|
| 60 days before expiry | Subcontractor’s office contact and your compliance owner | Heads-up: send your broker the renewal request |
| 30 days before expiry | Subcontractor, plus the project manager on any active job | Renewed certificate due |
| 14 days before expiry | Project manager and operations lead | Escalate by phone, confirm the sub’s broker is working on it |
| Day of expiry, no renewal on file | Project manager, accounting | Decide: pause scheduling, hold payment, or documented exception |
The numbers are a starting point, not a standard. Adjust them to your scopes. A short-duration trade that finishes in three weeks needs a different rhythm than a mechanical sub on an 18-month job.
One more timing rule: compare the expiration date to the project end date at onboarding, not only to today’s date. If a policy ends mid-project, the alert should already exist on day one.
Who should receive the alert and own the follow-up
Most lapses happen because everyone received the reminder and nobody owned it. Split the roles clearly:
- Subcontractor or vendor: gets the request and the deadline, and is responsible for having their broker send a new certificate.
- Compliance owner: usually a project administrator or controller. Verifies the new certificate against your requirements and closes the alert.
- Project manager: is informed about every sub on their jobs, because they control whether that sub keeps working.
- Accounting: knows who is out of compliance before the next pay application is approved.
If only one person sees alerts, a vacation week becomes a coverage gap. Send a copy to a shared mailbox or a backup owner.
Build a COI expiration tracking workflow in six steps
The sequence below works whether you run it on a spreadsheet or in software. AGC’s guidance on preventing subcontractor default recommends requiring appropriate subcontractor insurance and ISO forms where appropriate, flowing key requirements down, and rechecking insurance before project commencement. Those three ideas shape the steps.
- Write your insurance requirements once. List required coverages, minimum limits and endorsements by trade or contract size, and put them in your subcontract template.
- Collect the certificate at onboarding, not at first invoice. No certificate, no site access, no purchase order.
- Enter every policy line with its own date. Record carrier, policy number, limits and expiration for each coverage.
- Check the certificate before mobilization. Confirm dates cover the work window and the limits meet your minimum. Our subcontractor onboarding checklist walks through the gates a GC should close before a crew arrives.
- Schedule the alerts. Use the 60, 30 and 14-day pattern above, and add a day-of-expiry alert that goes to the project manager.
- Define the consequence. Decide in advance whether an expired sub is paused, held from payment or allowed a short written exception, and who can approve it.
Step six is the one most teams skip. An alert with no consequence is a suggestion.
Spreadsheet reminders vs. automated COI tracking
A spreadsheet with a conditional-format column is a reasonable start. If you carry fewer than a dozen subs and one person owns the file, it can work. The trouble appears as you grow.
| Spreadsheet reminders | Automated COI tracking | |
|---|---|---|
| Alerts | Someone has to open the file and sort by date | Sent automatically on a schedule to the people you choose |
| Multiple coverage lines | Often one date per sub, so earlier lapses hide | One date per policy line |
| Follow-up | Manual emails and calls | Reminder sequences go to the sub until a certificate arrives |
| Audit trail | Edited cells, no history | Dated record of each request and upload |
| Link to work | None. Scheduling and payment ignore the sheet | Compliance status can gate scheduling, POs and payments |
| Maintenance | Breaks when the owner leaves | Shared and role-based |
The biggest gap is the last-but-one row. A sheet knows a sub is expired but cannot stop anyone from scheduling that sub or approving their invoice. Our piece on vendor compliance tracking for contractors covers how to pilot this in a few weeks so you can see the effect before rolling it company-wide.
Common mistakes that let a COI lapse
- Tracking the sub, not the policy. General liability may renew in March while workers’ comp renews in September.
- Alerting only the GC. The sub has to act, so the sub needs the reminder too.
- Accepting a renewal with lower limits. A new certificate is not automatically a compliant one. Check limits and endorsements each time.
- Forgetting lower-tier subs. Flow your requirements down in the contract so second-tier trades carry the coverage you expect.
- Treating certificates as proof of coverage. They are a snapshot. For high-risk scopes, ask your broker how to verify policy status and endorsements.
- Ignoring vendors who are not on site daily. Suppliers, haulers and equipment renters can create exposure too.
If you want a view of how COI fits into prequalification, see our guide to subcontractor prequalification gates, where insurance is checked before a bid is even leveled.
Our perspective: alerts belong inside the job, not beside it
We build construction ERP software, and we see the same pattern in contractor back offices. COI tracking lives in a spreadsheet or an inbox, project management lives somewhere else, and accounting lives in a third system. The alert fires, but the person who can act on it is looking at a different screen.
Our view is simple. A COI expiration alert should be connected to the things a lapse affects: the subcontract, the schedule, the pay application and lien waiver. When compliance sits in the same system as job costing and project management, “this sub is expired” becomes a visible status on the job, not a line in a file someone checks monthly.
That is why compliance automation, including certificates and lien waivers, is part of the platform alongside accounting, scheduling and field operations. We would rather you set up a plain, well-owned process this week than wait for a perfect one. Start with the six steps above, then automate the parts that depend on someone remembering.
— Keith
Put COI alerts in the same system as your jobs
If you are tired of reconciling a compliance sheet with your project and accounting tools, DesignFlow Build brings project management, job costing, scheduling, field operations and compliance automation into one construction ERP. There is a free plan with core features. Pro is $100 per month per office user, and field seats are $25 per month per user. Essentials has no published price, so check the pricing page for details, or look at the Construction ERP overview to see how the pieces connect. Start free and see how it fits your process.
Want to see how automation handles the handoffs between onboarding, compliance and payment? Read our explainer on automated subcontractor coordination, or our guide to lien waiver management, which pairs naturally with insurance checks at each pay cycle.
FAQ
Where is the expiration date on a COI?
On a standard ACORD 25 certificate, each line of coverage has its own policy number plus effective and expiration dates in the coverages section. Read every row, because general liability, auto, umbrella and workers’ comp can expire on different dates.
What is a COI tracker?
A COI tracker is a spreadsheet or software that stores each subcontractor’s certificate, records policy dates and limits, and reminds you before coverage ends. The better ones also send reminders to the subcontractor and connect compliance status to scheduling and payment.
What happens when a COI expires?
The certificate is only a record, so the real issue is whether the policy behind it is still active. If it lapsed, a claim from the sub’s work may fall on you. Document the gap and speak with your broker and legal counsel about exposure.
How far ahead should COI expiration alerts go out?
At minimum, 30 days before expiration, which is the diary date certificate review guidance recommends. Many contractors add a 60-day heads-up and a 14-day escalation so a slow broker does not cause a lapse.
Is a spreadsheet enough for COI expiration tracking?
For a small number of subs with one clear owner, yes. When you run many subs across several jobs, a spreadsheet cannot send reminders to the sub or stop a lapsed sub from being scheduled or paid, which is where automation earns its place.
Sources
- ACORD: Certificates of Insurance FAQ
- How to Read and Review Certificates of Insurance with ACORD Forms
- Risk Management Magazine: The Limitations of Certificates of Insurance
- AGC: Best Practices for Preventing Subcontractor Default