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

Account Transfer: How InsightUW Ensures Continuity When Underwriters Are Out of Office

Sarah Chen is on vacation for a week. Her 14 submissions, 4 tasks, and active BOR don't wait. One click transfers everything to Jennifer Walsh — with full audit trail.


The Problem

An underwriter goes on PTO for a week. Their 15 active submissions sit untouched. A broker calls about a quote due Tuesday — no one knows where the file stands. A rush submission arrives Wednesday — it sits in the queue unassigned. By the time the UW returns, three SLAs are breached and a broker relationship is strained.

The problem isn't PTO. It's that there's no system to transfer workload when someone is absent.

The InsightUW Approach

InsightUW provides bulk account transfer — one operation moves all active submissions, open tasks, and pending BORs from one UW to another. Both parties are notified. Every transfer is audited.

graph TD subgraph Before["Before Transfer"] UW1["Sarah Chen<br/>14 submissions<br/>4 tasks<br/>1 active BOR"] end subgraph Transfer["One-Click Transfer"] OP["Transfer all to<br/>Jennifer Walsh<br/>Reason: OOO<br/>Apr 25 - May 2"] end subgraph After["After Transfer"] UW2["Jennifer Walsh<br/>+14 submissions<br/>+4 tasks<br/>+1 BOR"] end subgraph Notify["Notifications"] N1["Jennifer: '14 submissions<br/>transferred from Sarah'"] N2["Sarah: 'Your accounts<br/>transferred to Jennifer'"] end UW1 --> OP --> UW2 OP --> N1 OP --> N2

What Gets Transferred

Entity Filter Typical Count
Submissions new, in_review, quoted, quality_check 14
Tasks open, in_progress 4
BORs active, pending 1

Four Transfer Reasons

Reason When Permanent?
OOO Vacation, conference, medical leave Temporary — with return date
Departure UW leaving the company Permanent — no return notification
Workload Rebalancing capacity As needed
Reassignment Strategic reallocation As needed

LOB-Specific Example

Sarah Chen — 1 Week PTO:

Manager Mike Rodriguez opens the transfer screen and sees Sarah's workload: 14 submissions across D&O, E&O, MedMal, and Cyber. 4 open tasks. 1 active BOR countdown.

He clicks "Bulk Transfer" → selects Jennifer Walsh → reason: OOO → dates: Apr 25-May 2.

Result:
- Jennifer receives notification: "14 submissions, 4 tasks transferred from Sarah Chen. OOO: Apr 25-May 2."
- Sarah receives: "Your accounts transferred to Jennifer Walsh."
- Transfer ID: 883BD5B3 — logged in audit trail
- Sarah's workload: 0 submissions. Jennifer's: +14.

When Sarah returns May 2, Mike can transfer back — or Jennifer can continue on submissions she's already progressed.

What This Means for Underwriters

  1. Zero gap coverage — submissions don't wait for the UW to return
  2. One operation — all submissions, tasks, and BORs transfer together
  3. Both parties notified — receiving UW knows exactly what they're getting
  4. Audit trail — every transfer logged with who, when, why, and transfer ID
  5. Works for departures too — permanent transfer when a UW leaves the organization

What's Next

Next: Individual Production Metrics — Track Your Numbers by LOB, Period, and Target


Want seamless UW coverage during absences? 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