Working renewals from Applied Epic? Test AI renewal files on accounts your desk already took to market.

In an Epic agency, renewal work arrives as a list with a stage beside each policy. The account manager pulls the expiring term, looks for every change since it was issued, asks the insured for new figures, gathers loss runs and decides with the producer whether to remarket. Then Renew copies the old term into a new one, line by line. Whatever was wrong or missing on the expiring term comes along unless someone catches it first.

For the test, AI reads copies of renewals your desk already marketed, with the Epic exports behind each one, and drafts the file your account manager would have started from: an expiring summary built from the current lines and the Service Summary, the changes since issue, the questions for the insured, a loss summary and a missing-items list. It renews nothing, moves no stage and sends nothing. Your reviewer compares each draft with the file that actually went out.

The list shows whatever the stages say. Each agency sets its own renewal stages in Renewals Manager Settings Configuration, and every stage decides whether a policy stays on the list after it expires, and for how many days. Renewals Manager events set a stage automatically when a policy is created, cancelled or renewed, and Epic requires one for Policy Created. One more setting decides whether an account manager sees every renewal or only those where they, or a colleague whose work they can view, hold a servicing role. A stage nobody moved makes a finished renewal look open, or an open one vanish. The draft records each policy's stage from your export and says which stage the file is ready for, in your agency's own stage names, for the account manager to set.

Some accounts never reach the list. Applied's help says Renewals Manager leaves out any policy whose first Service Summary row is In Process or Submitted. An application still pending, or one sent to the carrier and not yet issued, can hide an account from the renewal view during the very months its file should be built. The test starts from your list of expirations rather than the screen, so those accounts stay in the sample, and the draft names the pending row for your account manager to settle before marketing.

The Service Summary is the term's history. Every row records an action and the stage it left: In Process, Submitted, Issued, Cancelled, Migrated, Suspended or N/A. When Download delivers an endorsement out of order, Epic holds it as a Suspended row, a D row with DOWNLOAD in the Entered By column, until someone accepts or rejects it. A change on one line of a package writes N/A rows on the other lines to keep the numbering in step. Where Turn off policy download is checked, downloaded data no longer overwrites Epic's record. So the draft lists every row since issue, keeps a file open while a Suspended row is unresolved, reads a package line by line, and checks Epic's record against the carrier's own pages when download is off.

Renew carries the old term forward. The Renew window lists each line of the expiring policy with its details defaulted from the old term. A line can be deselected so it doesn't renew, the status is set to Renewal, the user picks agency or direct bill, and the profit center and issuing company default from the old term unless someone changes them. Epic also reminds the user to update any active multi-carrier schedule by hand. Up to 50 policies can be renewed together, in three modes, and each run saves a Bulk Renewal Log to the client's attachments listing failures and activities that never generated. The draft marks lines that may not belong in the next term, a multi-carrier schedule to rework, and any account the log shows as failed.

Where the answer key sits, and what your reviewer watches. Epic moves a policy to Expired/History 30 days after it expires, and older marketing submissions move to Marketed History on their own, so the sample comes from those two views. Epic's Market Appetite search, which draws on Ask Kodiak, is there for placement; the draft never runs it and never names a market. Your reviewer, often the commercial account manager who moves the most renewal stages, looks hardest at the change list, the Suspended rows and the missing items, because those decide whether a file is ready to market.

Meet the success criteria and the commercial policies coming up for renewal over the next 30 days or so get the same drafts.

A licensed account manager reads each file and does the Epic work: moving the stage, renewing the policy, building the submission and sending the exposure request. The AI renews no policy, updates no stage and sends nothing to an insured or a carrier.