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

A renewal that lapses is not a paperwork problem. It is a coverage gap, an angry client, an E&O exposure, and — if the carrier non-renews because the application came in late — a lost account that took three years to win. Most agency service teams know this, which is why the better ones run renewals like a pre-flight: a fixed sequence of checks completed before the policy "takes off" into its next term, so that nothing critical is skipped under deadline pressure.

The problem is that the pre-flight usually lives in someone's head, or in a spreadsheet that one CSR maintains and nobody else can read. When that person is out, or carries 400 accounts, the checklist degrades into "did the renewal print, yes or no?" — and the exposure re-check, the loss-run pull, and the remarket decision quietly fall off. This guide gives the service team a concrete, ten-step renewal pre-flight checklist, plus the trigger dates, the owner for each step, and the point where automation earns its keep. It is written for commercial-lines and benefits service teams who want renewals to be boring again.

TL;DR

A renewal pre-flight checklist is a fixed, dated sequence of ten verification steps — exposure changes, loss runs, remarket decision, application, proposal, binding, and confirmation — that a service team completes before each policy's expiration so coverage renews on time and on the right terms. Start the clock 90 days out for commercial accounts, assign every step an owner, and let a workflow tool watch the dates so no account slips. The ten steps and a worked example are below.

What a renewal pre-flight actually is

Definition: A renewal pre-flight is the standardized set of checks a service team runs in the 30-to-120 days before a policy expires to confirm coverage, exposures, and pricing before the renewal binds.

The "pre-flight" framing matters because it changes how the work is sequenced. A pilot does not eyeball the plane and take off; they run a printed list in a fixed order, every flight, regardless of how routine. Renewals deserve the same discipline because the failure mode is identical — a small skipped check (an updated payroll figure, a new location, a lapsed certificate) becomes a large, expensive surprise after the fact.

The US property and casualty market is large enough that small process leaks compound fast. US P&C direct written premiums hit $1.07T in 2024, according to the Insurance Information Institute 2025 Fact Book, and the agencies servicing that premium win or lose on retention, not new business. A renewal that binds clean keeps the account; one that lapses or surprises the insured invites a shop.

This post is a BOFU resource — you are likely already comparing how to operationalize renewals, not asking whether to. So the checklist below is specific, and the back half compares an agency management system (AMS) doing the work natively versus an orchestration layer like US Tech Automations running the dated steps across systems.

Who this is for

This checklist fits a commercial-lines or employee-benefits service team inside an independent agency or brokerage — roughly 8 to 150 staff, $1M to $50M in revenue — running an AMS such as Applied Epic or Vertafore AMS360, with a renewal book large enough that "we just remember" has already failed once. If your CSRs each carry 200+ accounts and renewals cluster at month-end, this is for you.

Red flags: Skip the automation layer if you have fewer than 5 service staff, run a paper-and-PDF stack with no AMS of record, or write under $500K in commissions — at that scale a shared calendar and a disciplined CSR beat any tooling investment.

Independent agencies are not a niche, either. Independent agencies write roughly 87% of US commercial P&C premium, according to the Big "I" 2024 Agency Universe Study — so the renewal discipline below is the core operating motion for most of the commercial market, not an edge case.

The 10-step renewal pre-flight checklist

Each step below has a trigger date (days before expiration, "T-"), an owner, and the artifact it produces. Dates assume a mid-size commercial account; simple personal lines can compress to a 45-day runway, complex programs stretch to 150.

The table is the spine; the detail for each step follows.

Step 1 — Build the renewal list (T-120)

Pull a clean expiration report from the AMS, 120 days out, and reconcile it against the carrier download. The single most common pre-flight failure is an account that is simply not on anyone's list — a mid-term endorsement that changed the expiration date, a policy that downloaded under the wrong producer, or a manuscript form that never got an expiration coded. The list is the flight manifest; if a plane is not on it, nobody pre-flights it.

Step 2 — Send the exposure questionnaire (T-90)

Coverage is priced on exposure: payroll, sales, square footage, vehicle count, headcount. Send the insured a short, line-specific update request at T-90. The mistake here is renewing on last year's numbers — a contractor whose payroll doubled is materially underinsured for work comp, and the audit will claw the difference back painfully. Exposures move with the broader economy: according to the US Bureau of Labor Statistics, average hourly earnings rose roughly 4% year over year through 2024, which quietly inflates payroll-rated lines if you renew on stale figures.

Step 3 — Order loss runs (T-90)

Order current loss runs from every carrier, covering three to five years. Underwriters will not seriously consider a remarket without them, and they take time to arrive. Order at T-90 so a slow carrier does not blow the application deadline. Industry claim handling is not instant — the average auto P&C claim cycle ran about 28 days in 2024, according to the NAIC 2024 Claims Processing Benchmark, which is one reason recent open claims should be flagged and explained, not left to surprise an underwriter.

Step 4 — Re-rate and flag the deltas (T-75)

Run the updated exposures through the rater or pull the carrier's renewal offer and compare it to expiring. A double-digit premium swing is a conversation you want to have at T-75, not a phone call the client gets at T-5. Flag any increase above your agency's threshold (10% is common) for producer review.

Step 5 — Make the remarket decision (T-75)

This is the judgment step, and it belongs to the producer. Given the renewal premium, the loss history, and the relationship, do you stay with the incumbent or shop the account? Roughly 84% of P&C personal auto and home policies are retained year over year, according to the III's market data — meaning most accounts should stay, and indiscriminate remarketing wastes the team's deadline runway. Shop with intent, not reflex.

Step 6 — Submit the application (T-60)

Build a complete, clean submission — application, supplements, loss runs, exposure detail — and get it to the incumbent and any remarket targets by T-60. Underwriters reward complete submissions with faster, better quotes; a missing loss run sends the file to the bottom of the queue.

Step 7 — Review the carrier quote (T-45)

When quotes return, do not just read the premium. Compare coverage forms, limits, deductibles, exclusions, and endorsements against expiring. A cheaper quote that drops a key endorsement is not cheaper — it is a coverage gap with a discount.

Step 8 — Prepare the proposal (T-30)

Turn the quote comparison into a client-facing proposal that shows what changed, why, and the options. This is where the service team converts diligence into a renewal conversation the client trusts. Clear proposals reduce last-minute renegotiation and the "why did my premium go up?" call.

Step 9 — Bind and issue (T-10)

On the client's go-ahead, bind coverage and issue the policy. Confirm effective dates, premium, payment plan, and any subjectivities the carrier required. The trap here is binding before a subjectivity (an inspection, a signed application, a prior-carrier cancellation) is cleared — which can void coverage exactly when it is needed.

Step 10 — Confirm and document (T-0)

Confirm the renewal in writing to the insured, send the invoice or evidence of coverage, and document the entire pre-flight in the AMS so the next renewal starts from a complete file. A renewal isn't done until coverage is confirmed in writing and filed, because an undocumented bind is an E&O claim waiting for a memory to fail.

A worked example: a 600-account commercial book

Consider a service team handling a 600-policy commercial book with an average premium of $11,400, renewals spread across the year, but with a heavy cluster of 70 accounts expiring January 1. Last year, three of those January accounts lapsed because the loss-run requests went out late during the holiday crunch, costing roughly $34,200 in lost annual commission at a 12% commission rate. This year the team wires the pre-flight to fire automatically: when the AMS posts an upcoming-expiration record, an expiration_date field crossing the T-90 mark triggers the questionnaire and loss-run tasks, and a workflow watches for the carrier's loss_run.received confirmation before advancing the file to re-rate. Of the 70 January accounts, all 70 cleared their T-60 application deadline, remarket decisions were logged on 11 high-delta accounts, and zero lapsed — turning a $34,200 leak into a clean retention quarter.

Where an orchestration layer runs the dated steps

The AMS holds the data, but it does not, by default, chase the dates across the steps and systems. That gap is where the pre-flight breaks. Here US Tech Automations sits above the AMS, email, and carrier portals and runs the calendar: it reads the expiration report nightly, and when a policy crosses T-90 it generates the exposure questionnaire to the insured, opens the loss-run request tasks per carrier, and stamps the AMS activity log — the work of Steps 2 and 3 happens without a CSR remembering to start them.

As quotes and confirmations come back, US Tech Automations advances the file: it parses the carrier quote into the comparison fields, routes a premium-delta over the 10% threshold to the producer for the remarket decision in Step 5, and holds the bind in Step 9 until every subjectivity is checked off. A service lead sees one agentic workflow dashboard showing exactly which of the ten steps each renewal has cleared and which are overdue — so an account stalled at Step 6 surfaces at T-58, not at T-2. For teams structured around service rather than data entry, pairing this with a customer-service AI agent means the insured's questionnaire reply is read and filed automatically rather than waiting in an inbox.

This matters most on the clustered renewal dates, where human attention is the bottleneck. The tool does not make the underwriting decisions — it makes sure every renewal reaches the human decision points on time, with the loss runs and exposures already gathered. The payoff is in time recovered: according to McKinsey, insurers can automate or augment a large share of routine processing tasks, freeing service staff for the judgment and client work that retention actually turns on.

US Tech Automations vs the AMS doing it natively

Both Applied Epic and Vertafore AMS360 have renewal and activity features. The honest question is where a native AMS workflow is enough and where an orchestration layer adds value. Native AMS workflow shines when every step lives inside the AMS; orchestration earns its place when the steps cross into email, carrier portals, raters, and the insured's inbox.

The AMS is the system of record and should stay that way; the orchestration layer is the dispatcher that keeps the ten steps moving on schedule across the tools the AMS does not reach.

When NOT to use US Tech Automations

If your renewal book is small and lives entirely inside one AMS — say, under 150 active commercial accounts with no remarketing and no third-party portals to chase — the native Applied Epic activity templates or AMS360 workflow rules will do the job, and a separate orchestration layer is overhead you do not need. Likewise, if your team's real problem is upstream data hygiene (expiration dates miscoded, policies under the wrong producer), fix the AMS data first; automation will only fire dated tasks faster against bad dates. And if you handle a handful of jumbo accounts where every renewal is a bespoke, high-touch negotiation, a senior account manager with a calendar beats any templated pre-flight. Automation pays off on volume and repeatability, not on a dozen one-of-a-kind programs.

Common mistakes that break the pre-flight

• Starting too late. A 30-day runway on a complex commercial account guarantees a rushed bind. Start at T-90 to T-120.

• Renewing on stale exposures. Skipping the questionnaire renews last year's payroll and sets up an audit clawback.

• Treating remarket as default. Shopping every account burns runway; most should stay (Step 5).

• Binding before subjectivities clear. A bound policy with an open inspection can be voided — exactly the gap the client thinks is closed.

• No written confirmation. An undocumented renewal is an E&O exposure; close every file at Step 10.

Glossary

Benchmarks: a healthy renewal pre-flight

Use these as internal targets, not industry mandates — they are the operating numbers a disciplined service team can hit once the pre-flight is wired.

If you are running well below these, the fastest lever is usually not more staff — it is moving the dated steps off human memory. The companion insurance renewal automation checklist walks through wiring those triggers, and the 8-step automated renewal workflow guide shows a compressed variant for simpler books. Teams worried specifically about lost accounts should read why insurance teams save on retention loss.

Key Takeaways

• Run renewals as a fixed ten-step pre-flight with dated triggers and a named owner per step — start at T-90 to T-120 for commercial accounts.

• The two steps that quietly fall off — the exposure questionnaire (Step 2) and loss runs (Step 3) — are the ones that cause underinsurance and lapses, so fire them first.

• Make the remarket decision deliberate (Step 5), not reflexive; most accounts should stay, and shopping everything wastes runway.

• Keep the AMS as system of record; add orchestration only when the steps cross email, portals, and raters that the AMS does not reach.

• Close every renewal in writing at T-0 — an undocumented bind is an E&O claim waiting for a memory to fail.

Frequently asked questions

How many days before expiration should a renewal pre-flight start?

Start at T-90 for a typical mid-size commercial account, and T-120 for complex programs with multiple carriers or remarketing. Simple personal-lines renewals can compress to a 45-day runway. The driver is loss-run and underwriting turnaround — order loss runs early (Step 3) so a slow carrier does not blow the T-60 application deadline.

What is the difference between a renewal checklist and a remarket?

A renewal pre-flight checklist is the full sequence of steps to renew any policy; a remarket is one possible outcome of Step 5, the decision to shop the account to other carriers instead of staying with the incumbent. Most accounts complete the checklist and stay put — remarketing is the exception you choose when premium, losses, or coverage signal it is worth the runway.

Which renewal steps are safest to automate first?

The date-driven, repetitive steps automate first: building the expiration list (Step 1), sending exposure questionnaires (Step 2), and opening loss-run requests (Step 3). These fail through forgetfulness, not judgment, so a workflow that fires them on schedule removes the most common lapse cause. Keep judgment steps — the remarket decision and the bind sign-off — with a human.

Can an AMS like Applied Epic or AMS360 run the whole pre-flight?

Partly. Both can generate expiration reports and templated activities, which covers the in-system steps well. They struggle when a step crosses into email, carrier portals, or raters — chasing a loss run from a carrier website, parsing a returned quote, or routing a premium delta to a producer. That cross-system orchestration is where an external layer adds value over native AMS workflow alone.

How do I keep clustered renewal dates from overwhelming the team?

Clustered dates (January 1 is the classic) are where pre-flights break because human attention does not scale on demand. The fix is to push the dated, repetitive steps onto a workflow that watches expiration fields and fires questionnaires, loss-run requests, and deadline alerts automatically — so the team spends the crunch on judgment and client conversations, not on remembering which of 70 accounts still needs a loss run.

What is the single biggest cause of a lapsed renewal?

An account that was never on the renewal list (Step 1) — usually because a mid-term endorsement changed the expiration date, a policy downloaded under the wrong producer, or a manuscript form had no coded expiration. Nothing downstream matters if the policy is invisible. Reconcile the AMS expiration report against the carrier download at T-120 so every policy is on the manifest.

Ready to wire the ten steps to fire on their own dates? Compare plans and start the renewal pre-flight build.