Never Miss a BOR Deadline: 5 Automated Notification Events from Issuance to Expiry

How InsightUW delivers five targeted notification events across the BOR lifecycle — ensuring underwriters and operations teams are informed at every critical moment without a single manual reminder.

The Problem

Broker of Record changes involve multiple stakeholders — the assigned underwriter, the operations team, the incumbent broker, and the new broker — and each needs to know different things at different times. In most carriers, BOR communication is ad hoc: someone sends an email when they remember, a team lead pings Slack before leaving for the weekend, or nobody says anything at all until the new broker calls asking why their quote request was ignored.

The consequences are serious. An underwriter who does not know a BOR is pending may quote the wrong broker. An operations team that misses the grace period expiry delays the broker transition by days. And when a BOR is contested, the assigned underwriter needs to know immediately — not when they happen to check a shared spreadsheet.

The InsightUW Approach

InsightUW fires five distinct notification events across the BOR lifecycle, each targeted to the right recipient at the right time. Notifications appear via the in-app bell icon in the header, with urgency-coded styling. A five day notified flag on the BOR record prevents duplicate notifications, and the check expired bors batch operation handles grace period expiry detection automatically.

The Five Notification Events

Each event is defined by its trigger condition, recipient, message content, and urgency level:

Event 1: BOR Created — Underwriter Alert

This is the most critical notification. It establishes the "no quoting" embargo for the assigned underwriter from the moment the BOR is created.

Event 2: Countdown Started — Operations Alert

Event 3: 5 Days Pass — Underwriter Notification

The five day notified flag is set to true after this notification fires, preventing duplicates on subsequent batch runs.

Event 4: Grace Expired — Operations Finalization Alert

Event 5: BOR Contested — Underwriter Escalation

Duplicate Prevention: The five_day_notified Flag

The five day notified boolean field on the Bor model ensures that Event 3 (5 Days Pass) fires exactly once:

Notification Delivery: In-App Bell Icon

All BOR notifications are delivered through the InsightUW header bell icon, the same channel used for submission assignments, compliance alerts, and system messages. Each notification includes:

• Urgency color — blue (normal), amber (warning), red (critical)
• Timestamp — when the notification was generated
• Action link — click to navigate directly to the BOR detail modal
• Read/unread state — unread notifications show a badge count on the bell icon

Batch Operation: check expired bors

The check expired bors function runs on a scheduled interval and can be triggered manually from the BOR dashboard:

1. Query: SELECT * FROM uwbor WHERE status = 'pending' AND grace_period_end < NOW()
2. For each matching record:
   - Update status to expired
   - If five_day_notified = false: send Event 3 notification to UW, set flag to true
   - Send Event 4 notification to ops team
   - Create audit trail entry: grace period expired
3. Return count of expired BORs for dashboard display

Cyber Submission: NovaPay Technologies

Scenario: Aon Risk Solutions files a BOR letter to take over the Cyber account for NovaPay Technologies, currently brokered by Gallagher Specialty Group. The assigned underwriter is David Kim. The BOR is created on Monday, April 20, 2026.

Notification Timeline:

What David sees in his bell icon throughout the week:

• Monday morning: Blue notification — "New BOR filed for NovaPay Technologies" — he knows not to quote Aon on this account
• Friday morning: Amber notification — "Grace period expired for NovaPay Technologies" — he can now engage Aon as the broker of record
• No duplicate notifications — the five day notified flag ensures the Friday alert fires exactly once

If Gallagher contests on Wednesday:

The timeline changes. On Wednesday at 2:00 PM, Gallagher files a contest. David immediately receives a red critical notification: "BOR CONTESTED for NovaPay Technologies (Cyber). Contested by Gallagher Specialty Group — Reason: Active binding authority, signed BOR not received." The countdown pauses, and David must review and resolve before the BOR can proceed.

What This Means for Underwriters

1. Zero manual reminders — five automated notifications cover every critical BOR moment from creation to expiry, eliminating sticky notes, calendar reminders, and ad hoc emails.

2. Right person, right time — each notification targets the specific recipient who needs to act: the UW for quoting decisions and contest reviews, the ops team for administrative finalization.

3. No quoting mistakes — Event 1 explicitly tells the underwriter "do not quote until grace period expires," preventing premature engagement with the new broker that could create E&O exposure.

4. Duplicate-free alerting — the five day notified flag ensures that batch operations never generate redundant notifications, keeping the bell icon signal clean and actionable.

5. Instant contest escalation — Event 5 fires immediately when a contest is filed, with red critical urgency, so the underwriter can pause all activity and review the dispute without delay.

What's Next

In the next post, we will explore the BOR contest and resolution workflow — how InsightUW handles disputes, status transitions, and account-level history tracking when an incumbent broker challenges a Broker of Record change.

InsightUW is an AI-powered underwriting workstation for P&C carriers. Request a demo to see BOR notifications in action.