# Insurance renewals checked 60 days out — build checklist

Find the renewals that will go wrong while there is still time to do something about them.

Roughly three to four weeks. Getting data out of an agency management system is most of it.

## Before you start, read this

Do NOT build this if any of the following is true of you:

- [ ] You service fewer than about 200 policies. Your producers already know which renewals are hard.
- [ ] Your management system does not hold loss runs. Then step three is a person downloading PDFs, and that is the actual bottleneck.
- [ ] You are a personal-lines agency working off carrier-direct renewals — the carrier has already done this and you cannot change the outcome.

If none of those apply, carry on.

## 1. Prove you can hear the trigger

- [ ] Your agency management system: A policy expiration date falls 60 days from today
      Find what your vendor actually calls this event before you write any code.
      We have not verified the name, and guessing it wastes an afternoon.
- [ ] Email: A carrier renewal notice arrives in the shared mailbox
      Find what your vendor actually calls this event before you write any code.
      We have not verified the name, and guessing it wastes an afternoon.
- [ ] Log one real event end to end before building anything on top of it.

## 2. Build the steps, in this order

- [ ] 1. Daily sweep
      List policies expiring in exactly 60 days.
- [ ] 2. Score the risk
      Flag anything with a claim in the term, a premium change over your threshold, or a missing schedule.
- [ ] 3. Assemble the file
      Pull the loss runs, the current schedule, and last year's submission into one place.
- [ ] 4. Split the list
      Clean renewals go to a simple confirmation. Flagged ones go to a producer with the reason attached.
- [ ] 5. Producer works the flagged ones  (A PERSON DOES THIS — build the queue, not the decision)
      A person calls the client about the claim, the change, or the missing values.
- [ ] 6. Track to bound
      Anything not bound at 21 days escalates to a named person, not a queue.

## 3. Keep these jobs with a person

If your build quietly takes any of these over, you have built something else:

- [ ] Every conversation with a client about a claim or a premium increase.
- [ ] Deciding whether to remarket. The flag says something changed; it never says go to another carrier.
- [ ] Checking the assembled file is actually complete before it goes to an underwriter.

## 4. Before you turn it on

- [ ] Run it in report-only mode for a week and read every message it WOULD have sent.
- [ ] Decide who gets paged when it stops firing, and prove the page works.
- [ ] Write down what "it is working" means as a number you can check next month.
- [ ] Confirm you have consent for any message this sends to a customer.

---

Generated from the recipe at https://ustechautomations.com/recipes/insurance-renewal-60-day-pre-check
by seo/scripts/v1-gen-recipe-checklists.js — do not edit this file by hand.