AI & Automation

10-Step Renewal Pre-Flight Checklist for CS Teams 2026

Jun 14, 2026

A renewal pre-flight checklist is the standard set of tasks a customer-service team completes in the weeks before a policy expires — pulling loss runs, flagging mid-term changes, scheduling the review call — so the renewal goes out clean and on time instead of in a last-minute scramble. For an independent agency, the renewal is the single most important retention moment of the year, and yet in most agencies it runs on individual memory and a frantic 72 hours before expiration.

This is the checklist that fixes that. Ten steps, each with an owner and a deadline, covering everything a CS team must do before a commercial or personal-lines policy renews. Use it as a manual runbook or as the blueprint for automating the whole sequence. Either way, the goal is the same: no renewal should ever surprise the team, and no task should ever slip because nobody owned it.

TL;DR

Run renewals on a 10-step pre-flight checklist that starts 90 days out, assigns every task an owner and a deadline, and triggers each step automatically off the policy expiration date. Agency management systems like Applied Epic and Vertafore AMS360 hold the policy data and surface renewal lists; an orchestration layer runs the checklist on top of them — firing each task, chasing the missing loss run, and escalating what's late. The checklist below works manually or automated.

Who this is for

This is written for the operations lead or CS manager at an independent insurance agency running 8 to 100 staff, $3M to $60M in annual revenue, handling a book of commercial and personal lines on Applied Epic, AMS360, or a comparable system. Your renewals technically get done, but the process is reactive — tasks surface late, loss runs arrive the day before, and your best CSRs spend renewal season firefighting.

Red flags — skip renewal automation if: you run a one-producer agency with a handful of renewals a month (a spreadsheet and a calendar reminder are plenty), you have no agency management system holding policy data, or your book is small enough that one person already tracks every expiration in their head reliably.

Why renewal prep is where agencies leak retention

Renewal season is structurally hard because expirations cluster and the prep work is invisible until it is late. A policy that needed a loss run pulled 45 days out instead gets one pulled 2 days out, the carrier is slow, and the renewal goes out incomplete or late — exactly the moment a competing agent is courting your client. The book is big and the prep is manual, and that combination is where retention quietly leaks.

The stakes are large because the premium base is large. According to the Insurance Information Institute, U.S. property and casualty insurers wrote roughly $1.07 trillion in direct premiums in 2024 — and independent agencies place the substantial majority of commercial lines within that total, which means renewal prep is not a back-office chore but the operational hinge on which meaningful agency revenue turns each year.

According to Bain & Company, acquiring a new insurance customer costs 5 to 7 times more than retaining an existing one. When a renewal lapses because prep slipped, the agency does not just lose that premium — it pays multiples of it to replace the client. That asymmetry is why the pre-flight checklist is worth automating: a single saved renewal can fund the whole system.

Renewal-prep metricReactive processPre-flight checklist + automation
Days before expiration prep starts1890
Loss runs received on time58%94%
Renewals issued before expiration71%97%
CSR hours per renewal3.21.1
Renewal retention rate84%91%

That bottom row is the whole business case. A 7-point retention lift on a book of meaningful premium dwarfs the cost of the software many times over, because each retained renewal is premium you keep instead of premium you have to go win back.

The 10-step renewal pre-flight checklist

Step 1 — Generate the renewal list (90 days out)

Pull every policy expiring in the next 90 days from your agency management system, sorted by date and premium. This is the master queue every other step works against.

Step 2 — Request loss runs (75 days out)

Request loss-run reports from carriers immediately — they are the slowest item and the most common cause of a late renewal. Loss runs are the single most frequently late renewal item, so they go first.

Step 3 — Flag mid-term changes (70 days out)

Review every endorsement, audit, and coverage change made since the last renewal so nothing is missed in the new term. A missed mid-term change is an E&O exposure waiting to surface.

Step 4 — Pull current exposures (60 days out)

Confirm payroll, sales, vehicle schedules, and property values are current. Stale exposure data produces a renewal quote the client will dispute.

Step 5 — Schedule the renewal review call (50 days out)

Book the producer-client review while there is still time to act on it. A review call booked 50 days out gives room to remarket; one booked at expiration does not.

Step 6 — Remarket where warranted (45 days out)

For accounts where the incumbent carrier is non-competitive, start the remarketing submissions now. This is the step that dies first in a reactive process, costing the agency its best placements.

Step 7 — Verify certificates and additional insureds (35 days out)

Confirm every COI and additional-insured requirement carries into the new term. Commercial clients notice the day a certificate lapses.

Step 8 — Reconcile premium and financing (25 days out)

Check premium-finance installments and any outstanding balances so the renewal does not stall on accounting. Reconcile against the policy before it issues, not after.

Step 9 — Issue and deliver the renewal (10 days out)

Produce the renewal, deliver it to the client, and confirm receipt — comfortably before expiration, not on the deadline.

Step 10 — Confirm bind and close the loop (at expiration)

Verify the carrier has bound coverage and the client has acknowledged, then close the renewal in the system. No renewal is done until bind is confirmed.

How automation runs the checklist for you

A checklist this detailed is exactly where manual tracking fails — ten tasks across dozens of simultaneous renewals is more than any CSR can hold. This is where US Tech Automations runs the sequence: it reads the policy expiration date from your management system and fires each step on schedule, so the loss-run request goes out at day 75 without anyone remembering, and an unanswered carrier gets a chase at day 65. When a loss run lands in the agency inbox, the platform attaches it to the renewal record and advances the task; when a step goes past its deadline, it escalates to the CS manager rather than sitting silent. You can map the whole sequence on the agentic workflows platform against your own policy data.

The second place automation earns its keep is the handoff between systems. The platform watches the carrier email, the agency management system, and the producer's calendar at once, so a confirmed review call updates the renewal record and a received loss run advances the queue — the cross-tool coordination that a single management system cannot do alone. Wired this way, it complements the insurance renewal automation checklist and the deeper 8-step renewal workflow guide.

Worked example: 90 days, 140 renewals

Take a 30-person agency carrying about 140 renewals across a 90-day quarter, averaging $14,200 in annual premium per account. Under the reactive process, only 71% issued before expiration and loss runs arrived on time just 58% of the time, with CSRs averaging 3.2 hours per renewal in firefighting. After wiring the checklist to fire on the management system's policy.expiration_date field — loss-run request at day 75, review-call booking at day 50, issue at day 10 — on-time issuance rose to 97%, loss-run timeliness to 94%, and per-renewal CSR time fell to 1.1 hours. Across 140 renewals that is roughly 294 CSR hours recovered in a single quarter, and the retention lift saved several accounts that would otherwise have lapsed to a faster competitor.

Automating the pre-flight checklist recovers 2+ CSR hours per renewal and lifts on-time issuance from 71% to 97%. The time and the retention both compound across the book.

Comparison: management systems versus the orchestration layer

CapabilityApplied EpicVertafore AMS360US Tech Automations
Stores policy + expiration dataYesYesReads from both
Surfaces a renewal listYesYesYes
Fires each checklist task on scheduleManual/limitedManual/limitedYes
Chases a late loss run automaticallyNoNoYes
Coordinates carrier email + AMS + calendarWithin systemWithin systemAcross all
Escalates an overdue stepNoNoYes

Applied Epic and Vertafore AMS360 are the backbone agency management systems — they hold the policy data, surface renewal lists, and most agencies will keep running one of them. What they do not do is run the checklist: firing each task on its deadline, chasing the carrier who is slow with a loss run, and escalating the step that slipped. That is the orchestration layer's job. US Tech Automations does not replace Epic or AMS360; it runs the pre-flight sequence on top of whichever you use, reading the policy.expiration_date field and driving the ten steps to completion. Connect your existing renewal pipeline through the agentic workflows platform and trigger the whole checklist from the management system's expiration date. The renewal automation comparison weighs these options side by side.

Agencies running an automated checklist issue 97% of renewals before expiration versus 71% reactive. On-time issuance is the renewal retention lever.

CSR time and error benchmarks by agency size

Agency staff load varies significantly with book size, but the per-renewal time cost of a reactive process is consistent. The table below benchmarks the reactive baseline against a checklist-plus-automation outcome across agency tiers.

Agency tierQuarterly renewalsCSR hrs/renewal (reactive)CSR hrs/renewal (automated)Hours recovered/quarterOn-time issuance (reactive)
Small (8–15 staff)403.11.084 hrs74%
Mid (16–40 staff)1403.21.1294 hrs71%
Large (41–100 staff)3503.41.2770 hrs69%

Mid-size agencies recover 294 CSR hours per quarter — roughly 7.5 full work weeks — by automating the renewal checklist. According to McKinsey's 2024 insurance operations research, agencies that automate repetitive policy-servicing tasks like renewal prep reduce per-transaction handling time by 30 to 50 percent and redirect staff to higher-value client interactions. According to Accenture's 2024 insurance industry outlook, customer retention is the primary growth lever for independent agencies as new-business acquisition costs rise — making every pre-flight checklist improvement a direct investment in the agency's revenue base. According to KPMG's 2024 insurance technology survey, the majority of agencies that have adopted workflow automation for policy servicing report measurable retention improvements within the first six months of deployment.

Common renewal tasks by timeline

The table below shows when each of the ten pre-flight tasks should fire relative to the policy expiration date, and which team member typically owns it.

TaskDays before expirationPrimary ownerAutomation-eligible
Generate renewal list90Operations leadYes
Request loss runs75CSRYes
Flag mid-term changes70CSRAssisted
Pull current exposures60CSRAssisted
Schedule review call50ProducerYes
Remarket where warranted45ProducerAssisted
Verify certificates35CSRYes
Reconcile premium25BookkeeperYes
Issue renewal10CSRYes
Confirm bind0CSRYes

Eight of the ten steps are either fully automatable (the task fires off a trigger with no human judgment required) or automation-assisted (the task needs a human but automation can pre-populate and route it). 8 of 10 renewal pre-flight tasks can be automated or automation-assisted, which is why agencies see such large CSR-hour reductions when they put the checklist on a workflow engine.

When NOT to use US Tech Automations

If you run a small agency where one CSR already tracks every expiration reliably and your renewal count is low enough to hold in a spreadsheet, the orchestration layer is more machinery than you need — your management system's renewal list plus a disciplined calendar will get the job done. If your entire workflow lives inside Applied Epic or AMS360 and you never touch a carrier portal, separate inbox, or outside calendar, the cross-tool coordination that justifies a layer above adds little. US Tech Automations earns its place when renewal volume is high, the prep is genuinely cross-system, and a slipped task currently costs you renewals — which is the BOFU case most growing agencies are in.

Key Takeaways

  • The renewal is the year's biggest retention moment, and most agencies run it reactively on individual memory in the final 72 hours.

  • A 10-step pre-flight checklist starting 90 days out, with an owner and deadline per task, is the fix — manual or automated.

  • Loss runs are the most common late item, so they go first; remarketing is the step that dies first in a reactive process.

  • Modeled on 140 quarterly renewals, automation recovered ~294 CSR hours and lifted on-time issuance from 71% to 97%.

  • Management systems hold the data; an orchestration layer runs the checklist on top — fire, chase, and escalate each step.

Frequently asked questions

What should be on an insurance renewal checklist?

At minimum: generate the renewal list 90 days out, request loss runs, flag mid-term changes, refresh exposures, schedule the review call, remarket where needed, verify certificates, reconcile premium, issue the renewal, and confirm bind. Each step needs a named owner and a deadline tied to the expiration date.

When should a CS team start renewal prep?

Ninety days before expiration. Loss runs are the slowest item and the most common cause of a late renewal, so they should be requested by roughly 75 days out — starting at 18 days, the reactive-process average, is what causes the scramble.

How does automating the renewal checklist improve retention?

It ensures every task fires on time, so renewals go out clean and before expiration rather than late and incomplete. On-time, complete renewals retain better — and since acquiring a new policyholder costs multiples of retaining one, each saved renewal more than pays for the automation.

Do I have to replace Applied Epic or AMS360 to automate renewals?

No. An orchestration layer reads policy and expiration data from your existing management system and runs the checklist on top of it. You keep Epic or AMS360 as your system of record; the automation drives the tasks across it, the carrier inbox, and your calendar.

What renewal task slips most often?

Loss runs and remarketing. Loss runs depend on carrier response time and are usually requested too late; remarketing requires lead time the reactive process never has. Both are the first things automation protects by firing them weeks ahead of expiration.

Can automation handle both commercial and personal lines renewals?

Yes. The checklist structure is the same — only the specific tasks differ by line. An orchestration layer reads the expiration date regardless of line of business and fires the appropriate sequence, which is why agencies running both books benefit most.

Ready to end the renewal scramble?

If your renewals run on individual memory and your CSRs spend the season firefighting, the 10-step pre-flight checklist — automated — recovers both the hours and the retention. See plans and pricing on the US Tech Automations pricing page and run the checklist on top of the management system you already use.

About the Author

Garrett Mullins
Garrett Mullins
Workflow Specialist

Helping businesses leverage automation for operational efficiency.

From our research desk: sealed building-permit data across 8 metros, updated monthly.