• contact@verticalserve.com
Home / Engineering / Post 65
Engineering Blog · Post #65

Claims Bordereaux Reminders: AI Reminds You 30 Days Before Renewal

Never quote a renewal without current claims data again. InsightUW watches the calendar so you don't have to.


The Problem

A renewal effective date is May 15. The UW starts working the file on May 1 — 14 days out. They request claims bordereaux from the broker. The broker takes 5 business days. The data arrives May 8. Now the UW has 7 days to analyze loss development, update pricing, and issue a quote. If they'd requested it 30 days out on April 15, they would have had 3 weeks.

The problem isn't that UWs forget — it's that with 50+ renewals in the pipeline, manually tracking "30 days before each effective date" is impossible.

The InsightUW Approach

InsightUW's AI assistant automatically scans all renewal submissions and sends a notification to the assigned UW when a renewal is 25-35 days from its effective date, reminding them to request updated claims bordereaux.

graph TD subgraph Scan["Daily Scan"] Check["Scan all renewal submissions<br/>with effective date in<br/>25-35 day window"] end subgraph Filter["Filters"] F1["Only source = 'renewal'"] F2["Not declined or bound"] F3["No duplicate reminders<br/>(idempotent check)"] end subgraph Notify["UW Notification"] Bell["Bell icon alert:<br/>'Claims Bordereaux Due:<br/>Apex Medical — D&O<br/>(renews in 30d)'"] Detail["What to request:<br/>• Current-year bordereaux<br/>• YTD loss run update<br/>• Late-reported claims"] end Check --> F1 F1 --> F2 F2 --> F3 F3 -->|"In window"| Bell Bell --> Detail

What the Notification Contains

When a renewal enters the 30-day window, the assigned UW sees:

Design Decisions

Feature Approach Why
Window 25-35 days (not exact 30) Avoids missing renewals due to weekends/holidays
Idempotent Checks for existing reminder Safe to run daily without duplicate alerts
Only active Excludes declined/bound No noise from already-resolved renewals
Production mode Daily Celery/cron job Runs automatically, no manual trigger

LOB-Specific Example

Umbrella for Constellation Hotels Group:

It's April 22. Constellation's umbrella renewal effective date is June 1 — 40 days away. Not in the window yet.

On May 2, the system's daily scan finds Constellation at 30 days out. The UW Mike Rodriguez receives a bell notification: "Claims Bordereaux Due: Constellation Hotels — Umbrella (renews in 30d)."

Mike immediately emails Marsh & McLennan requesting updated bordereaux. The data arrives May 9. Mike has 23 days to analyze, price, and quote — instead of scrambling with 7 days.

What This Means for Underwriters

  1. Never forget — the system watches the calendar for every renewal in your pipeline
  2. 30 days of lead time — enough time for broker response + analysis + quoting
  3. Specific guidance — the notification tells you exactly what data to request
  4. No duplicates — runs daily without repeating reminders already sent
  5. Accurate pricing — current claims bordereaux means accurate loss development, not stale data

What's Next

This completes the Submission Enrichment blog series. For more InsightUW capabilities, explore our Submission Intake, Corporate Clearance, or Submission Prioritization series.


Want AI watching your renewal calendar? Request a demo.

See InsightUW run on your data

A 45-minute working session with a real broker email and your LOBs.

Request a demo