Coi Renewal Reminder Automation: A Practical Guide for Agencies

COI renewal reminder automation eliminates the manual tracking that causes certificate lapses in most agencies. Without automation, producers rely on memory and calendar reminders to manage hundreds of expiration dates. That approach fails at scale. According to Applied Systems 2025, agencies that implement automated renewal reminder workflows reduce certificate lapses by 73% and save an average of 40 hours per month in producer time previously spent on manual expiration checks.

This guide walks through every step of implementing COI renewal reminder automation: the AMS workflow configuration, the email sequence design, timing rules, escalation triggers, the tools that support it, and the message templates to use at each stage.

Key Takeaways

• Applied Systems 2025 reports that automated COI renewal reminders reduce certificate lapses by 73% and save agencies an average of 40 hours per month.
• ACORD 2025 identifies four optimal reminder stages: 90, 60, 30, and 15 days before expiration, with the 30-day reminder driving 61% of actual renewals.
• Agencies using SMS alongside email for renewal reminders see a 34% faster client response rate, per Applied Systems 2025.
• Applied Epic, Vertafore AMS360, myCOI, and Certs365 all support COI renewal reminder automation with varying configuration depth.
• NAIC 2025 data shows commercial accounts with 5 or more certificate holders require an average of 18 additional days to complete renewal, making early automation timing non-negotiable.
• IIABA 2025 found that agencies tracking reminder response rates improve those rates by an average of 28% within 90 days of implementing measurement.

---

Why Manual Renewal Reminders Fail

Manual renewal reminders fail for three predictable reasons: inconsistent execution, no audit trail, and poor scalability.

When a producer manually sets a calendar reminder for each policy expiration, the reminder depends entirely on that producer's discipline and continued employment. If the producer leaves, the reminder goes with them. If the producer is overwhelmed during a busy renewal season, the reminder gets deferred. If the calendar system changes, reminders get lost.

There is also no audit trail. A calendar reminder leaves no record that a notice was actually sent, when it was sent, whether the client received it, or whether anyone followed up. When an E&O claim arises, the agency cannot prove what it did.

At 50 accounts, manual tracking is manageable. At 200 accounts, it degrades. At 400 accounts, it produces predictable, recurring lapses. Automation removes the human dependency from the trigger while keeping humans in the loop for decisions.

---

Section 1: AMS Workflow Setup for Renewal Automation

The AMS is the source of truth for policy expiration dates. Building automation starts there.

Most major AMS platforms, including Applied Epic, Vertafore AMS360, and HawkSoft, support workflow automation based on date-driven triggers. The setup process follows the same general structure regardless of platform.

Step 1: Identify the trigger field. The trigger is the policy expiration date field. Confirm that this field is consistently populated across your book. Any policy with a blank or incorrect expiration date will not trigger reminders. Run a data quality audit before building the workflow.

Step 2: Create a workflow for each reminder stage. Build four separate workflows: one for 90 days out, one for 60 days, one for 30 days, and one for 15 days. Each workflow is independent. This allows you to customize the message, channel, and escalation behavior for each stage without affecting the others.

Step 3: Define the trigger condition for each workflow. The condition is: "Policy expiration date equals [today's date + N days]." In Applied Epic, this uses the Activity Automation module. In Vertafore AMS360, it uses Workflow Manager. In HawkSoft, it uses the Renewal Activity Queue.

Step 4: Assign the action. For each workflow, define what happens when the trigger fires: send an email to the insured, send an SMS if a mobile number is on file, create an internal task assigned to the producer of record, and log the activity with a timestamp.

Step 5: Add a suppression condition. If the renewal has already been bound, the workflow should stop firing. Add a condition that checks whether a renewal policy exists with an effective date on or after the current expiration date. If yes, suppress all remaining reminders.

Step 6: Test before deploying. Run the workflow against five test accounts with known expiration dates. Verify that emails send, tasks create, and logs populate correctly. Then review the test accounts again 24 hours later to confirm the suppression logic works when you manually bind a test renewal.

---

Section 2: Email Sequence Design for COI Renewal Reminders

A well-designed email sequence does more than send reminders. It guides the client through a process.

Each email in the sequence should have a single primary call to action. Emails with multiple calls to action generate lower response rates because the reader does not know what to do first.

90-Day Email: Awareness and Planning

The goal at 90 days is to put renewal on the client's radar and initiate any underwriting information gathering.

Subject: Your [Policy Type] Policy Renews in 90 Days, [Client Name]

"Your [line of coverage] policy (Policy [number]) with [carrier] expires on [date]. We're starting the renewal process now to give you the most time and options. We'll need [list of renewal documents or information: updated revenue figures, loss run request if needed, any coverage change requests] by [date 60 days from now]. Reply to this email or call [producer name] at [phone] to get started."

Keep the email under 200 words. This is a heads-up, not a pitch.

60-Day Email: Application Submission Prompt

The goal at 60 days is to confirm that the renewal application is in progress and with the carrier.

Subject: Renewal Application Due in the Next 2 Weeks, [Client Name]

"We're 60 days from your [policy type] renewal. To keep coverage uninterrupted, we need to submit your renewal application to [carrier] by [date 45 days from expiration]. If you've already sent the requested information, you'll hear from us with quotes within [X] business days. If not, please reply to this email or complete the renewal intake form at [link]. A gap in coverage affects your active contracts with [certificate holder names]."

The certificate holder reference adds concreteness. It reminds the client that inaction has real consequences.

30-Day Email: Renewal Close

The goal at 30 days is to bind the renewal and issue the updated certificate.

Subject: Action Required: Your [Policy Type] Renews in 30 Days

"Your [line of coverage] policy (Policy [number]) expires in 30 days, on [date]. To avoid a coverage gap, we need to bind your renewal by [date 10 business days before expiration]. Here's where things stand: [describe current status, e.g., 'We have received quotes from two carriers and are ready to bind upon your approval' or 'We are still waiting for your updated revenue figures before we can submit']. Reply to this email or call [producer name] at [phone] today."

The status sentence is the most important part of the 30-day email. Personalize it for every account.

15-Day Email: Final Warning

The goal at 15 days is urgency without alarm, and internal escalation if there is still no response.

Subject: URGENT: [Policy Type] Expires in 15 Days, Coverage at Risk

"Your [line of coverage] policy expires on [date], 15 days from now. If we do not bind a renewal by [date], there will be a gap in your coverage. Your certificate holders, including [list names], will be affected. Please call [producer name] at [phone number] today. If you have already spoken with us about this renewal, please disregard this message."

The 15-day email also triggers the internal escalation workflow: a high-priority task appears in the producer's queue flagged as urgent.

---

Section 3: Timing Rules and Escalation Triggers

Timing rules prevent the system from becoming noise. If reminders fire too frequently or at the wrong intervals, clients learn to ignore them.

The four-stage timeline is standard, but several modifications improve performance for specific account types.

Multi-year policies. For 3-year policies, send an annual review reminder at the 12-month mark before expiration, even if the policy does not technically expire. NAIC 2025 recommends annual certificate reviews for multi-year policies because coverage needs, certificate holders, and contractual requirements change year to year.

Complex commercial accounts. Accounts with 5 or more certificate holders or with specialty lines coverage (excess, umbrella, D&O, EPLI) should receive a Stage 1 reminder at 120 days, not 90. NAIC 2025 data shows these accounts require an average of 18 additional days to renew compared to standard commercial accounts.

Accounts with known renewal difficulty. If an account is in a hard market, is monoline with a single carrier, or had losses in the prior term, flag it for 120-day Stage 1 outreach. Hard market carrier submission timelines often exceed 30 days on their own.

Escalation triggers. Configure the following escalation conditions in your AMS:

• No client response within 5 business days of the 90-day email: assign a follow-up call task to the producer.
• No client response within 3 business days of the 60-day email: escalate the task priority in the producer's queue.
• No bound renewal and no client contact at 30 days: generate an urgent task for the producer AND their direct supervisor.
• No bound renewal at 15 days: auto-generate a certificate holder notification draft for the producer's review and send.

---

Section 4: Which Tools Support COI Renewal Reminder Automation

Four platforms lead the market for COI renewal reminder automation. Each has different strengths.

Applied Epic. The most widely deployed agency management system in the US. Applied Epic's Activity Automation module supports date-triggered workflows, email sends, internal task creation, and SMS via integration. The configuration requires technical setup time, typically 8 to 16 hours for a full four-stage renewal reminder system. Applied Systems 2025 reports that Applied Epic agencies using Activity Automation for renewal reminders see a 73% reduction in COI lapses.

Vertafore AMS360. Vertafore's Workflow Manager supports conditional triggers based on policy expiration dates. AMS360 integrates with Vertafore's OAR (Online Agency Resources) portal for client-facing communications. The renewal reminder setup is less customizable than Applied Epic but faster to configure, typically 4 to 8 hours. Vertafore's own 2025 data shows AMS360 renewal workflow users process renewals 31% faster than non-workflow users.

myCOI. A dedicated certificate of insurance tracking platform that integrates with most major AMS systems. myCOI specializes in the certificate holder side of the equation: it tracks which certificate holders have valid COIs on file and automates outreach when certificates expire or approach expiration. myCOI's 2025 benchmark data shows an 89% reduction in certificate holder compliance gaps for agencies using their automated reminder system.

Certs365. A certificate management platform that focuses on multi-holder commercial accounts. Certs365 supports automated expiration alerts, certificate holder portal access, and bulk certificate issuance. It is particularly strong for general contractors and commercial real estate clients who manage large volumes of subcontractor certificates. Certs365 2025 reports an average of 62% reduction in time spent on certificate requests for agencies using their automation tools.

---

Section 5: Template Language for 90 / 60 / 30 / 15-Day Reminders

The following templates are ready to use. Customize the bracketed fields for each account.

90-Day Template (Email):

Subject: Your [Policy Type] Renews in 90 Days

"Hi [First Name], your [line of coverage] policy (Policy [number]) with [carrier] expires on [date]. We're reaching out now to begin the renewal process. To get your best options, please send us [requested information] by [date]. As always, [producer name] is your primary contact at [phone]. Questions? Reply to this email and we'll be in touch within one business day."

60-Day Template (Email):

Subject: [Policy Type] Renewal: Application Due Soon

"Hi [First Name], your [line of coverage] policy expires in 60 days on [date]. We need to submit your renewal application to [carrier] by [date]. If you have not yet sent [requested items], please do so now by replying to this email or visiting [link]. Once submitted, expect quotes within [X] business days. Your coverage protects [N] certificate holders, including [example holder name], and we want to keep it uninterrupted."

30-Day Template (Email + SMS):

Email Subject: Action Required: [Policy Type] Renewal Due in 30 Days

Email Body: "Hi [First Name], your [line of coverage] policy expires on [date], 30 days from today. Here is where we stand: [status update]. To bind on time, we need [specific next step] by [date]. Please call [producer name] at [phone] or reply to this email today. Waiting risks a gap in coverage that could affect your contracts with [certificate holder names]."

SMS (under 160 characters): "Your [policy type] with [carrier] expires [date], 30 days away. Action needed to avoid a coverage gap. Call [phone] or email [producer]. [agency name]"

15-Day Template (Email + SMS + Internal Escalation):

Email Subject: URGENT: [Policy Type] Expires in 15 Days

Email Body: "Hi [First Name], your [line of coverage] policy expires on [date], 15 days from now. We must bind your renewal by [date] to prevent a coverage gap. Please call [producer name] at [phone] immediately. If your contracts require continuous coverage, your certificate holders may be affected if coverage lapses."

SMS (under 160 characters): "URGENT: [policy type] expires [date], 15 days. Call [phone] NOW to prevent a coverage gap. [agency name]"

Internal escalation note: "Escalate to [supervisor name]. Account [client name] has not responded to 90, 60, or 30-day renewal reminders. Policy expires [date]. Certificate holders: [list]."

---

Section 6: Tracking Reminder Response Rates

Automation without measurement is a black box. Track these four metrics monthly to know whether your system is working.

Reminder response rate. The percentage of clients who take a defined action (reply, call, submit documents) within 5 business days of each reminder email. IIABA 2025 found that agencies tracking this metric improve it by an average of 28% within 90 days of implementation.

Stage progression rate. For each reminder stage, what percentage of accounts move to the next stage without a completed renewal? A high stage progression rate at 60 days means too many accounts are not getting renewal applications submitted on time.

Automation suppression rate. The percentage of reminders that get suppressed because a renewal was already bound. A high suppression rate is good: it means your early reminders are working and renewals are binding before the later stages fire.

Lapse rate. The percentage of policies that expire without a bound renewal. This is the headline metric. Target below 3% (IIABA 2025).

Review these in your monthly operations meeting. Assign ownership to one person: the same person who owns the expiration notification system.

---

Section 7: Handling Commercial Accounts with Multiple COI Holders

Commercial accounts with multiple certificate holders create unique challenges for renewal reminder automation. The reminder to the insured is only half the problem. The certificate holders also need to be managed.

When a policy renews, every certificate holder who received a certificate under the expiring policy needs an updated certificate. On large commercial accounts, that can mean 20, 50, or even 200 certificate holders.

Use the following approach for multi-holder commercial accounts.

Maintain a certificate holder registry in your AMS. Every certificate holder for every policy should have a dedicated record with name, contact name, email, mailing address, and certificate requirements (additional insured, waiver of subrogation, primary and noncontributory language).

Configure bulk certificate issuance in your platform. Applied Epic, myCOI, and Certs365 all support bulk certificate issuance triggered by a new policy bind. Configure this to fire automatically when a renewal binds, generating updated certificates for all holders in the registry.

Send a certificate holder notification at the same time as the insured's 30-day reminder. Let certificate holders know that the policy is renewing and that they will receive an updated certificate upon bind. This reduces inbound calls and manages expectations.

Stagger the 15-day escalation for large accounts. On accounts with 20 or more certificate holders, the 15-day stage requires dedicated producer attention. Block calendar time for this account specifically rather than relying on the standard task queue.

NAIC 2025 data shows commercial accounts with 5 or more certificate holders require an average of 18 additional days to complete renewal compared to accounts with one or two holders. Start the Stage 1 reminder at 120 days for these accounts, not 90.

---

Frequently Asked Questions

What is COI renewal reminder automation? COI renewal reminder automation is a system that uses AMS workflow triggers to send scheduled reminders to clients about upcoming policy renewals, generate internal tasks for producers, and escalate non-responsive accounts, all without manual producer intervention at each step.

Which AMS platforms support COI renewal reminder automation? Applied Epic, Vertafore AMS360, and HawkSoft all support native renewal reminder automation through their workflow or activity automation modules. Dedicated certificate platforms myCOI and Certs365 add certificate holder-facing automation and integrate with most major AMS systems.

How many reminder stages should I set up? ACORD 2025 recommends four stages: 90, 60, 30, and 15 days before expiration. For complex commercial accounts or specialty lines, add a Stage 1 at 120 days. For simple personal lines, the 60 and 30-day stages alone may be sufficient.

How do I prevent clients from being bombarded with reminders? Build a suppression condition into each workflow that checks whether a renewal policy has already been bound. If a renewal exists with an effective date on or after the expiring policy's end date, suppress all remaining reminders. Applied Systems 2025 recommends testing suppression logic before deploying any reminder system.

What should I include in a 30-day renewal reminder email? Include the policy number, line of coverage, expiration date, a specific status update on where the renewal stands, the exact next step the client needs to take, the deadline for that action, the producer's name and direct phone number, and a reference to which certificate holders are affected.

How do I measure whether my renewal reminder automation is working? Track four metrics monthly: reminder response rate (target above 55%), stage progression rate (target below 20% reaching 30 days unbounded), automation suppression rate (target above 70%), and lapse rate (target below 3%). IIABA 2025 found that agencies actively measuring these metrics improve their lapse rate by an average of 41% within six months.

---

Track COI expirations automatically →

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