Engineering Blog · Post #22

Renewals and New Submissions in One Queue: Why the Unified Work Queue Treats Them Differently but Shows Them Together

How InsightUW displays 3 Commercial Property renewals alongside 2 new submissions in a single prioritized work queue — with renewal-specific columns for prior premium, rate change, loss ratio, and days-to-expiry — using an urgency scoring algorithm that ranks a flagged renewal above a clean new submission every time.

The Problem

Underwriting teams handle two fundamentally different types of work: new business submissions and renewal processing. In most organizations, these live in separate systems, separate tabs, or separate queues — and this separation creates blind spots.

The common approaches all fail in specific ways:

Separate systems: Renewals live in the policy admin system. New submissions live in the submission intake platform. The underwriter toggles between two screens, two login sessions, two sets of filters. Work falls through the cracks when the most urgent item is in the other system.
Separate tabs in one system: Better, but the underwriter still must decide which tab to check first. A renewal expiring in 3 days sits in the "Renewals" tab while the underwriter works through the "New Business" tab because that is where they happened to land.
Combined queue with no differentiation: Some systems dump everything into one list but treat renewals and new submissions identically. The renewal-specific context — prior premium, loss history, expiry urgency, rate adequacy — is invisible. The underwriter cannot tell at a glance which renewals need rate action and which are clean.
No urgency scoring: Items appear in submission-date order or alphabetical order. A renewal with a deteriorating loss ratio and 5 days to expiry sits below a clean new submission that arrived 10 minutes earlier.

The result: missed renewal deadlines, reactive instead of proactive renewal management, and no single view that answers the question "what should I work on next?"

The InsightUW Approach

InsightUW implements a unified work queue that combines renewals and new submissions in a single prioritized view. Both types share common queue infrastructure (priority scoring, SLA tracking, assignment, filtering), but renewals carry additional context columns and weighting factors that reflect their unique urgency signals.

graph TB subgraph Sources["Work Item Sources"] A["New Submissions (Email / Portal / API)"] B["Renewals (Policy System Sync + Auto-Generation)"] end subgraph Scoring["Unified Urgency Scoring"] C["Base Priority (LOB + Account Size)"] D["SLA Pressure (% Elapsed)"] E["Renewal Signals (Expiry + Loss Ratio + Flags)"] F["Composite Urgency Score (0–100)"] end subgraph Queue["Unified Work Queue"] G["Single Sorted List Renewals + New Submissions"] H["Type Badge Renewal | NEW"] I["Renewal Columns (Prior Premium, Rate Change, Loss Ratio, Days to Expiry)"] J["Common Columns (Priority, SLA, Assigned, Status, LOB)"] end subgraph Actions["Queue Actions"] K["Filter by Type (All / Renewals / New)"] L["Sort by Urgency Score"] M["Bulk Assignment"] end A --> C B --> C B --> E C --> F D --> F E --> F F --> G G --> H G --> I G --> J G --> K G --> L G --> M

What Is the Same: Shared Queue Infrastructure

Renewals and new submissions share core queue attributes. This is what makes the unified queue work — the common foundation that allows them to be sorted, filtered, and assigned using the same rules.

What Is Different: Renewal-Specific Context

Renewal items carry additional fields that new submissions do not have. These fields are rendered as extra columns in the queue table, visible only when a renewal row is displayed.

The Unified Queue Table

Here is what the underwriter sees — a single table with type badges, renewal-specific columns, and urgency-based sorting:

The Urgency Scoring Algorithm

The urgency score (0–100) determines queue order. It combines signals that apply to all items with renewal-specific signals that only apply when type = RENEWAL.

graph LR subgraph Common["Common Factors (All Items)"] A["Account Size / TIV Weight: 15%"] B["SLA Pressure (% elapsed) Weight: 25%"] C["Priority Level (Rush/High/MED/LOW) Weight: 15%"] end subgraph Renewal Only["Renewal-Only Factors"] D["Days to Expiry Weight: 20%"] E["Loss Ratio Trend Weight: 10%"] F["Flag Count Weight: 10%"] G["Retention Risk Weight: 5%"] end subgraph Score["Composite Score"] H["Urgency Score (0–100)"] end A --> H B --> H C --> H D --> H E --> H F --> H G --> H

Why Flagged Renewals Always Rank Above Clean New Submissions

The math is deliberate. A new submission can score at most 55 points (common factors only: 25 + 15 + 15). A renewal with even one flag and moderate expiry pressure will score 60+. This means:

Flagged renewal (Harbor Point, score 92): High SLA pressure (25 * 0.75) + large TIV (15 * 0.75) + high priority (15 * 0.75) + 22 days to expiry (20 * 0.67) + deteriorating LR (10 * 0.80) + 3 flags (10 * 1.0) + retention risk (5 * 0.30) = 92
Clean new submission (Meridian Tower, score 65): High SLA on-track (25 * 0.36) + very large TIV (15 * 1.0) + high priority (15 * 0.75) + no renewal factors = 65
Clean new submission (Cascade Storage, score 42): Low SLA pressure (25 * 0.15) + small TIV (15 * 0.20) + medium priority (15 * 0.50) + no renewal factors = 42

The Scenario

The Commercial Property team manages a mixed workload: 3 policies up for renewal in the next 30–70 days, plus 2 new submission requests that arrived this week. The team has 2 underwriters (Rachel Torres and David Chen) and a manager (Samantha Lee) who uses the queue dashboard.

The Queue View (Monday Morning)

Rank	Type	Insured	TIV	Status	UW	SLA Left	Prior Premium	Rate Chg	LR (5yr)	Expiry	Flags
1	RENEWAL	Harbor Point Logistics	$78M	FLAGGED	R. Torres	18h	$412K	+18%	72%	22d	3
2	RENEWAL	Oakridge Industrial	$42M	IN_REVIEW	R. Torres	24h	$285K	+12.5%	48%	41d	1
3	NEW	Meridian Tower Dev	$120M	EXTRACTED	D. Chen	36h	—	—	—	—	0
4	RENEWAL	Greenfield Commerce	$31M	QUOTED	D. Chen	40h	$198K	+3%	32%	68d	0
5	NEW	Cascade Self-Storage	$8.5M	SUBMITTED	R. Torres	52h	—	—	—	—	0

What the Manager Sees

Samantha Lee opens the queue dashboard and immediately understands:

Harbor Point is the fire. Three flags, 72% loss ratio, 22 days to expiry, and SLA at risk. Rachel needs to prioritize this today.
Oakridge is next. One flag (TIV increased 15%), but a stable loss ratio and 41 days to expiry. Needs attention this week.
Meridian Tower is a large new account. $120M TIV, high priority, but no renewal urgency. David is on it, SLA is healthy.
Greenfield is nearly done. Already quoted, clean loss history, 68 days to expiry. Low urgency.
Cascade is routine. Small account, new business, plenty of SLA time.

Without the unified queue, Samantha would need to check the renewal system for items 1, 2, and 4, then switch to the submission system for items 3 and 5. The cross-system priority comparison would be impossible.

Queue Filtering and Views

The queue supports multiple filter combinations:

All items: Default view — renewals and new submissions together, sorted by urgency score
Renewals only: Filter type=RENEWAL to focus on the renewal book
New business only: Filter type=NEW to see new submission pipeline
Flagged renewals: Filter type=RENEWAL&flags_min=1 to see renewals that need attention
Expiring soon: Filter type=RENEWAL&days_to_expiry_max=30 to see renewals expiring within 30 days
SLA at risk: Filter sla_status=AT_RISK across both types

SLA Tracking: Same Framework, Different Targets

Both renewals and new submissions use the same SLA tracking framework, but with different targets reflecting their different urgency profiles:

Metrics: Before and After the Unified Queue

Metric	Before InsightUW	After InsightUW	Improvement
Time to identify highest-priority item	10–20 min (check two systems)	Instant (top of sorted queue)	99% faster
Renewal deadline misses per quarter	4–8	0–1	85% reduction
Flagged renewals missed / discovered late	30% discovered after broker follow-up	0% — flags surface immediately	100% improvement
Cross-type priority comparison	Impossible (separate systems)	Automatic (unified scoring)	New capability
Manager time on workload review	45 min/day (two systems + spreadsheet)	5 min/day (single dashboard)	89% faster
Underwriter context switches per hour	8–12 (toggling systems)	2–3 (single queue)	70% reduction
SLA compliance rate (combined)	72%	94%	31% improvement
Renewal retention rate	78%	86%	10% improvement

Key Takeaways

Separate queues create blind spots. When renewals and new submissions live in different systems, the underwriter cannot answer "what is my most urgent item?" without checking both. The unified queue eliminates this context-switching tax.
Same infrastructure, different context. Renewals and new submissions share the queue framework (priority, SLA, assignment, status) but renewals carry additional columns (prior premium, rate change, loss ratio, expiry). The queue shows both in one view without forcing artificial sameness.
Urgency scoring is the key to unified prioritization. The composite score combines SLA pressure, account size, and priority (for all items) with expiry urgency, loss trends, and flags (for renewals). This ensures flagged renewals naturally sort above clean new submissions.
The manager's view is the strategy view. When the queue is unified, the manager can see the full team workload, identify bottlenecks, reassign work across types, and make retention decisions — all from one screen.
Filtering preserves the option to focus. The unified queue does not prevent focused views. Underwriters can filter to renewals-only or new-business-only when they need to batch similar work. The unified view is the default, not the only option.

Ready to stop toggling between renewal and submission systems? InsightUW's unified work queue puts every item in one prioritized view — with the renewal context columns that make renewal-specific decisions possible.

Schedule a Unified Queue Demo →