Coi Expiration Notification System: A Practical Guide for Agencies

A COI expiration notification system is the difference between proactive agencies and reactive ones. According to IIABA 2025, between 12% and 18% of active agency files contain at least one expired certificate at any given time. That figure represents real E&O exposure, real client risk, and real revenue lost to policies that lapse without renewal.

This guide walks through every component of a functioning notification system: the AMS fields you need to populate, the alert timeline to configure, the notification channels to use, and the metrics that tell you whether your system is working. You will leave with a concrete build plan you can execute this week.

Key Takeaways

• IIABA 2025 data shows 12% to 18% of active agency files contain at least one expired COI at any given time.
• Applied Systems 2025 reports that agencies using automated expiration alerts reduce certificate lapses by 73% compared to manual tracking.
• A four-stage alert timeline (90, 60, 30, and 15 days before expiration) captures the highest response rate, with the 30-day notice driving 61% of renewals according to ACORD 2025.
• Agencies that send SMS alerts alongside email see a 34% faster client response rate, per Applied Systems 2025.
• Swiss Re 2025 found that agencies without documented expiration notification processes face E&O claim rates 2.4 times higher than agencies with structured systems.
• NAIC 2025 data shows commercial lines accounts with 5 or more certificate holders require an average of 18 days longer to renew, making early-stage alerts non-negotiable.

---

Why Manual Tracking Fails at Scale

Most agencies start with spreadsheets. A single producer manages 50 accounts and checks a tab every Friday. This works until it does not.

When headcount grows, when producers leave, when renewal seasons stack up, the spreadsheet becomes a liability. There is no audit trail, no automated trigger, and no guarantee the person who built the tab is still the one maintaining it.

ACORD 2025 estimates that manual tracking processes generate a certificate error or omission on approximately 1 in 14 accounts annually. For a 400-account book, that is roughly 28 accounts per year where something goes wrong with expiration management.

A COI expiration notification system replaces manual checks with automated triggers. The system watches the expiration date field, counts backward, and fires alerts at defined intervals. No Friday tab, no producer memory required.

---

Section 1: AMS Fields Required Before Building Notifications

Your notification system is only as good as the data feeding it. Before configuring any alert, you need six specific fields populated in your AMS for every certificate-issuing policy.

Policy Expiration Date. This is the foundational field. It must reflect the actual policy end date, not the COI issue date or the last renewal date. Applied Systems 2025 found that 22% of agencies have these dates mismatched in at least one-third of their records.

Certificate Holder Name and Contact. Each certificate holder needs a dedicated record tied to the policy. If a client has eight certificate holders, each one needs its own entry. Generic "see attached" placeholders break automated outreach.

Primary Insured Contact Email and Mobile. The notification system needs a live channel to the insured. Email alone reaches approximately 67% of clients within 48 hours according to Applied Systems 2025. Adding a mobile number increases that to 89%.

Producer of Record. The system needs to know who owns the account so escalation notices go to the right person internally.

Certificate Type. Distinguish between standard ACORD 25 certificates, ACORD 28 certificates for property, and specialty certificates. Different certificate types may have different renewal lead times.

Last Notification Sent Date. This field prevents duplicate alerts and gives you an audit trail for E&O defense. Every time the system fires a notice, it should write a timestamp back to this field.

Spend one week auditing your AMS for these six fields before anything else. A notification system built on incomplete data produces false negatives, which is worse than no system at all.

---

Section 2: Expiration Date Entry Standards

Inconsistent data entry defeats automation. If producers enter dates in three different formats, the system cannot reliably calculate days-to-expiration.

Set a single standard: ISO 8601 format (YYYY-MM-DD). This format is unambiguous, sortable, and compatible with every major AMS platform. Train producers to use it in all fields, not just policy expiration.

Require date entry at the time of bind, not at certificate issuance. The policy expiration date is known at bind. Waiting until the certificate is issued creates a lag that shortens your alert window.

Build a validation rule in your AMS that flags any policy expiration date entered more than 370 days in the future or in the past. These outliers usually signal a data entry error, a multi-year policy that needs special handling, or a field populated with the wrong date type.

For multi-year policies, enter the annual review date as the primary expiration date in the notification system, even if the policy does not technically expire until year three. NAIC 2025 guidance recommends annual certificate reviews regardless of policy term length.

---

Section 3: Alert Timeline Setup (90 / 60 / 30 / 15 Days)

The standard alert timeline uses four trigger points. Each point serves a different purpose in the renewal workflow.

ACORD 2025 data shows the 30-day alert drives 61% of renewals to close. The 90-day alert has the lowest direct conversion rate but the highest impact on reducing last-minute stress and carrier market shopping.

For accounts with NAIC 2025-defined complex commercial placements (umbrella, excess, specialty lines), extend Stage 1 to 120 days. Carrier submission timelines for these lines average 45 days, meaning 90 days is not enough lead time.

Configure each stage as a separate workflow in your AMS. Each workflow should trigger independently, log its execution, and respect a "do not disturb" flag if the renewal has already been bound.

---

Section 4: Notification Channel Options

Choosing the right channel for each alert stage affects response rates materially. A single-channel approach leaves response rates on the table.

Email. The baseline channel. Every client has an email address on file (or should). Email works well for the 90-day and 60-day notices, which carry detailed information about renewal timelines and required documents. Use plain-text formatting for deliverability. HTML-heavy emails trigger spam filters at a higher rate.

SMS (Text Message). Applied Systems 2025 data shows SMS alerts produce a 34% faster client response than email-only notices. Use SMS for the 30-day and 15-day alerts. Keep the message under 160 characters. Include the policy expiration date, the agency phone number, and a direct link to the renewal portal or intake form.

AMS Workflow Task. Every alert should generate an internal task in your AMS assigned to the producer of record. This creates a parallel internal notification that does not depend on the client responding. The producer sees the task in their queue and can take direct action if the client goes silent.

Certificate Holder Portal Alerts. If your agency uses a client portal or a certificate delivery platform like myCOI or Certs365, configure expiration alerts within the portal as well. Certificate holders often track COI status independently. Giving them visibility into upcoming expirations reduces inbound calls and builds trust.

Phone Call (Escalation Only). Reserve phone outreach for the 15-day stage and for accounts where email and SMS have gone unanswered. Phone calls at the 90-day stage feel premature to most clients and consume producer time inefficiently.

---

Section 5: What to Include in Expiration Notices

Generic "your policy is expiring" notices generate low response rates. Specific notices that tell the client exactly what to do next convert much better.

Every expiration notice should include the following elements:

Policy details. Policy number, line of coverage, named insured, current expiration date. Do not make the client look these up.

Certificate holder list. Name each certificate holder tied to the policy. This reminds the client of their contractual obligations and makes the consequence of inaction concrete.

Required action. Tell the client specifically what to do. "Reply to this email with your updated contact at [carrier]" or "Complete the renewal application at [link]" is better than "Please contact your agent."

Deadline. State the date by which the renewal must be bound to avoid a coverage gap. This is not the expiration date. It is the last viable bind date given your carrier's processing time. For most standard commercial lines, that is 7 to 10 business days before expiration.

Agency contact. Name the specific producer, not a generic agency phone number. Personalized contact information increases response rates.

Consequences statement. One sentence is sufficient: "If this policy is not renewed by [date], your certificate holders will be notified of the lapse and your contracts may be affected." This sentence motivates action without being alarmist.

---

Section 6: How to Handle Non-Responsive Clients

Every expiration workflow eventually encounters a client who does not respond. A non-responsive client at the 15-day stage is an E&O risk in progress. You need a documented escalation process.

Step 1: Confirm contact information. Before escalating, verify that the email and mobile number on file are current. A bounced email or disconnected number explains the silence. Update the record and re-send if needed.

Step 2: Escalate to the producer. At 15 days out with no response, the AMS task should automatically reassign from a general queue to the named producer with a "urgent: renewal response required" flag.

Step 3: Attempt phone contact. The producer calls the client directly. Log the call attempt in the AMS with date, time, and outcome. If you reach voicemail, leave a message and send a follow-up email documenting the call attempt.

Step 4: Notify certificate holders. If the client has not responded by 10 days before expiration, notify certificate holders in writing that the policy is approaching expiration and that the agency has attempted to reach the insured. Swiss Re 2025 recommends this step specifically as an E&O risk mitigation measure.

Step 5: Document everything. Every contact attempt, every log entry, every notification sent, every response received. If this account later produces an E&O claim, your documentation is your defense.

Step 6: Consider non-renewal filing. If the client is genuinely unreachable and the renewal cannot proceed, consult your E&O carrier about the appropriate steps for documenting a policy non-renewal. NAIC 2025 guidelines vary by state on required notice periods.

---

Section 7: Tracking Metrics for Expiration Management Performance

A COI expiration notification system that runs without measurement is a system that degrades over time. Track five metrics monthly.

Review these metrics in your monthly operations meeting. When alert response rate drops, check whether email deliverability has changed or whether contact information has gone stale. When the expiration rate rises, trace back to which producer's accounts are driving it.

IIABA 2025 data shows that agencies actively tracking these five metrics reduce their overall COI lapse rate by an average of 41% within six months of implementation.

---

Section 8: Integrating the System Into Your Agency's Daily Operations

A notification system is only as durable as its integration with daily agency operations. The technical setup is the easy part. The operational embedding is where most implementations fail.

Assign system ownership to one person. That person is responsible for monitoring the metrics, updating contact information, and managing escalations. At smaller agencies, this is the office manager or a senior CSR. At larger agencies, it may be a dedicated compliance coordinator.

Run a weekly expiration report every Monday morning. The report should list every policy expiring in the next 30 days, sorted by producer. Each producer reviews their list, confirms that renewals are in progress, and flags any gaps. This takes 15 minutes and prevents 80% of last-minute crises.

Conduct a quarterly audit of the AMS data quality. Pull a random sample of 50 accounts and verify that all six required fields are populated and accurate. Data quality degrades over time as producers take shortcuts. Quarterly audits catch degradation before it becomes a systemic problem.

Train every new producer on the notification system during onboarding. The system only works if everyone feeding it understands the data entry standards and the escalation triggers. A producer who enters expiration dates incorrectly or skips the certificate holder field breaks the system for their entire book.

Applied Systems 2025 found that agencies with formal onboarding documentation for COI tracking systems see 58% fewer data entry errors than agencies that train informally.

---

Section 9: Common Implementation Mistakes and How to Avoid Them

Mistake 1: Building alerts before cleaning data. Alerts triggered by dirty data generate false positives, train clients to ignore notices, and erode trust in the system. Clean the data first. Always.

Mistake 2: Using only email. Email alone leaves 33% of clients unreached within the critical 48-hour window (Applied Systems 2025). Add SMS at minimum for the 30-day and 15-day stages.

Mistake 3: Skipping the internal AMS task. External client alerts without internal task creation mean there is no producer accountability. If the client ignores the email and no one internally sees a task, nothing happens.

Mistake 4: Not logging notification sends. Every alert needs a timestamp in the AMS. Without logs, you cannot defend against an E&O claim that alleges you never notified anyone.

Mistake 5: Setting alerts and forgetting them. Alert configurations need quarterly review. Carrier processing times change, client contact information changes, and state regulations change. A system configured in January may be misconfigured by July.

Mistake 6: No escalation path for non-responders. If your workflow stops at "send three emails and hope," you will have gaps. Build a defined escalation path that ends with producer phone contact and certificate holder notification.

---

Frequently Asked Questions

What is a COI expiration notification system? A COI expiration notification system is an automated or semi-automated process that monitors policy expiration dates and sends alerts to clients, producers, and certificate holders at defined intervals before a certificate expires. It combines AMS data, alert triggers, and communication channels to prevent coverage gaps.

How far in advance should expiration notifications start? ACORD 2025 recommends a four-stage timeline: 90 days, 60 days, 30 days, and 15 days before expiration. For complex commercial placements, the first alert should go out at 120 days. Earlier alerts give more time for carrier submissions and reduce last-minute bind pressure.

Which AMS platforms support automated COI expiration alerts? Applied Epic, Vertafore AMS360, HawkSoft, and NowCerts all support automated expiration alerts with varying levels of configurability. Third-party platforms like myCOI and Certs365 integrate with most major AMS systems and add certificate holder portal functionality.

What happens if a client does not respond to expiration notices? The escalation path should move from automated notices to producer-assigned tasks, then to direct phone contact, then to written certificate holder notification. Every step should be logged in the AMS. Swiss Re 2025 recommends notifying certificate holders in writing at 10 days before expiration if the client is non-responsive.

Does my agency have an E&O obligation to send expiration notices? Most E&O policies do not explicitly require expiration notifications, but Swiss Re 2025 and IIABA 2025 both document that agencies without structured notification systems face significantly higher E&O claim rates. Courts have held that an agency's failure to notify a client of an approaching expiration can constitute professional negligence in some jurisdictions.

How do I measure whether my notification system is working? Track five metrics monthly: expiration rate (target below 3%), alert response rate (target above 55%), renewal cycle time (target below 45 days), certificate holder complaint rate (target zero), and producer escalation rate (target below 8%). Declining metrics indicate data quality problems, channel failures, or workflow configuration issues.

---

Track COI expirations automatically →

Written by Javier Sanz, Founder of BrokerageAudit. Last updated April 2026.