Skip to main content

​
When a renewal opens

Underflow checks for expiring Bound and Issued policies during the workspace’s local six o’clock hour. The scheduler runs once per UTC hour, so a half-hour or quarter-hour zone runs at 6:30 or 6:45 local time. A policy within 90 days of expiration receives one renewal file unless one already exists. There is no manual Start renewal action and no setting for the 90-day window. The new file:
  • Starts in Received as an ordinary Book file.
  • Uses the expiring policy’s expiration date as its proposed effective date.
  • Keeps the program, agency, producer, insured, and prior-policy relationship.
  • Carries application answers forward after applying executed endorsements.
  • Records a renewal event and requests an Aurora turn.
The relationship is unique, so another sweep does not open a duplicate.
The Desk summary counts policies expiring within 30 days, while the calendar can show expirations up to 120 days ahead. Those windows are different from the 90-day renewal creation window.

​
Carried answers

Each carried answer keeps its original observation date and shows Expiring policy as its source on the new file. The answer does not expire automatically. Aurora sees its age and is expected to confirm material facts or record why it remains reliable. New answers use the same fact ledger as any submission. The latest recorded value is current, while disagreements and earlier sources remain visible.

​
Work the renewal

Once opened, a renewal follows the normal submission workflow:
  1. Review the carried application and open gaps.
  2. Collect changes and current evidence.
  3. Reassess appetite, external scan results, and subjectivities.
  4. Quote and bind the new term.
The Book does not currently display a dedicated renewal badge. The relationship is available to Aurora and recorded in the file history.

​
Issue a nonrenewal notice

On a Bound or Issued policy:
  1. Open the file’s Policies section.
  2. Enter an optional reason.
  3. Select Issue nonrenewal notice and confirm.
Blank reason uses “The program is not offering renewal terms.” The click is recorded in the actions ledger like a scheduled cancellation. Underflow generates a PDF, stores it on the policy, and proposes an email to the file’s counterparty, normally the producer, with the notice attached. On a direct-business file, the recipient can be the insured contact. The email follows the outbound email charter and may wait for approval. If no eligible recipient email exists, no delivery action is created. The state’s nonrenewal notice period is a figure a person entered from the statute on the verified state rule, alongside the cancellation periods; the tax feed does not supply it, and a state with none entered takes no nonrenewal notice. Underflow refuses the notice when fewer days remain before expiration than the state requires, or while a cancellation is scheduled on the policy, and a policy already noticed is not noticed twice. The notice prints the statutory period, and coverage still runs to the expiration date.
A nonrenewal notice does not change policy status or stop automatic renewal creation. If a renewal file already exists, close or manage it separately. Once the state’s period can no longer run before expiration, the policy is renewed or extended on its terms; there is no late notice.
There is no withdraw or reissue control after the nonrenewal notice is created.