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

AW, FAC, Punitive, Large Loss: How Flag-Based Priority Scoring Ensures Your Riskiest Renewals Get Attention First

How InsightUW detects an Account Warning, a $3.2M open claim, and a FAC placement on Vanguard Industries' $25M Excess Casualty layer — scores it as P1 Critical — and routes it to the top of the senior underwriter's queue before the 90-day renewal window even opens.


The Problem

A commercial carrier's renewal book is not a uniform list. It contains routine accounts that renew unchanged year after year, and it contains accounts that carry material risk to the carrier's balance sheet. The problem is that most underwriting platforms treat them identically.

Consider what a typical renewal queue looks like:

  • 200 renewals expiring in the next 90 days
  • 15 of those have Account Warnings from the policy admin system
  • 8 have FAC (facultative reinsurance) placements that require reinsurer approval before the carrier can even offer renewal terms
  • 6 have large losses (>$250K incurred) in the current or prior term
  • 3 have punitive damages allegations in open litigation
  • 1 has all four flags simultaneously

In most systems, all 200 renewals appear in the same flat list — sorted by expiration date or alphabetically. The underwriter works top-to-bottom. The account with four critical flags might be item 147 on the list. By the time the UW reaches it, the 90-day window has shrunk to 40 days, the reinsurer needs 30 days to respond, and the carrier is forced to issue a non-renewal notice because there is no time left to underwrite.

The real cost of no prioritization:

  • Missed FAC deadlines: Facultative reinsurers typically require 30-45 days for renewal review. If the cedant does not submit early, the reinsurer declines to quote, and the carrier must decide between retaining the risk net or non-renewing.
  • Uninformed pricing: An underwriter who does not see the $3.2M open claim until week 3 of the renewal process sends an initial indication at expiring terms. The broker shares it with the insured. Then the UW discovers the claim and revises upward by 30%. The insured feels ambushed. The broker loses trust.
  • Regulatory exposure on AW accounts: Account Warnings often indicate regulatory or compliance issues (e.g., insured under investigation, claims handling dispute, coverage litigation). These require legal review before renewal terms can be offered.

The InsightUW Flag Architecture

InsightUW defines 8 standard flags that are detected automatically from connected source systems during the nightly renewal scan. Each flag has a defined weight, source, detection logic, and auto-action.

graph LR subgraph Sources["Source Systems"] A["Policy Admin"] B["Claims System"] C["Reinsurance System"] D["Actuarial / Rating"] E["Compliance / Legal"] end subgraph Detection["Flag Detection Engine"] F["8 Flag Rules<br/>Evaluated per policy"] G["Flag Metadata<br/>Type, Source, Detail, Severity"] end subgraph Scoring["Priority Scoring"] H["Base Score<br/>(Premium Tier)"] I["+ Flag Weights"] J["= Priority Score"] K["→ Tier Assignment"] end subgraph Actions["Auto-Actions by Tier"] L["P1: Rush SLA + Manager Alert"] M["P2: Standard SLA + Auto-Assign"] N["P3: Extended SLA + Queue"] O["P4: Queue Only"] end A --> F B --> F C --> F D --> F E --> F F --> G G --> H H --> I I --> J J --> K K --> L K --> M K --> N K --> O

The 8 Flags: Complete Reference

Each flag is independently detected, weighted, and attached to the renewal submission. Flags are additive — an account can carry multiple flags, and each contributes to the total priority score.

Flag 1: Account Warning (AW)

Attribute Value
Weight +25
Source Policy Admin System
Detection account.warning_flag = true OR account.warning_codes is non-empty
Severity HIGH
Auto-Action Manager notification; legal review task auto-created
Meaning The insured has a system-level warning — could indicate litigation against the carrier, regulatory inquiry, claims handling dispute, or account-level compliance issue. The underwriter must not offer renewal terms without reviewing the warning detail.
Example Vanguard Industries: AW code CLM-DISPUTE — insured has filed a complaint regarding claims handling on open claim CLM-2025-VNG-00312. Legal review required before renewal indication.

Flag 2: FAC (Facultative Reinsurance) Placement

Attribute Value
Weight +20
Source Reinsurance System
Detection Active FAC certificate linked to expiring policy with certificate.status = active
Severity HIGH
Auto-Action FAC renewal request auto-queued to reinsurance team; 45-day countdown timer
Meaning The expiring policy cedes a portion of risk to a facultative reinsurer. The carrier cannot offer binding renewal terms until the reinsurer confirms willingness to renew the FAC certificate. This adds 30-45 days to the timeline.
Example Vanguard Industries: FAC certificate FAC-2025-VNG-EXC with Swiss Re Corporate Solutions, ceding 60% of the $25M excess layer. Swiss Re requires 35-day advance notice for renewal.

Flag 3: Large Loss (>$250K Incurred)

Attribute Value
Weight +20
Source Claims System
Detection Any claim with incurred_amount > 250000 in the last 5 policy years
Severity HIGH
Auto-Action Loss summary auto-attached to renewal; claims analyst review task created
Meaning A significant claim has occurred. The underwriter must factor this into renewal pricing, consider coverage modifications, and potentially discuss loss control requirements.
Example Vanguard Industries: Claim CLM-2025-VNG-00312, product liability / bodily injury, incurred $3,200,000 (open, $1.8M paid + $1.4M reserve).

Flag 4: Punitive Damages Allegation

Attribute Value
Weight +15
Source Claims System
Detection Any open claim with punitive_damages_alleged = true
Severity HIGH
Auto-Action Legal review task auto-created; coverage counsel notification
Meaning An open claim includes an allegation of punitive damages. In many jurisdictions, punitive damages are uninsurable or subject to special policy provisions. The renewal must address punitive damages coverage explicitly.
Example Vanguard Industries: Claim CLM-2025-VNG-00312 includes a punitive damages demand in the complaint. Jurisdiction: Illinois (punitive damages insurable but subject to public policy exceptions).

Flag 5: High Experience Modification / Loss Ratio

Attribute Value
Weight +15
Source Actuarial / Rating System
Detection WC: EMR > 1.10. GL/Property/Excess: 5-year loss ratio > 65%
Severity MEDIUM
Auto-Action Actuarial review task auto-created; loss development triangle attached
Meaning The account's loss experience is worse than expected. Pricing adjustments are likely needed.
Example Vanguard Industries: 5-year excess loss ratio of 78% driven by the $3.2M open claim.

Flag 6: Multi-State / Multi-Location

Attribute Value
Weight +10
Source Policy Admin System
Detection Policy covers 10+ locations OR 5+ states
Severity MEDIUM
Auto-Action Multi-state compliance checklist attached
Meaning Operational complexity. Multi-state accounts may have varying regulatory requirements, surplus lines considerations, and filing obligations.
Example Vanguard Industries: 14 manufacturing facilities across 8 states.

Flag 7: First Renewal (New Business)

Attribute Value
Weight +10
Source Policy Admin System
Detection policy.term_number = 1 (policy is in its first term)
Severity LOW
Auto-Action New business review checklist attached; broker feedback survey triggered
Meaning First renewals have higher non-renewal rates. The underwriter should evaluate whether the new business pricing assumptions held and whether the account meets long-term appetite.

Flag 8: High Premium (>$100K)

Attribute Value
Weight +10
Source Policy Admin System
Detection policy.expiring_premium > 100000
Severity MEDIUM
Auto-Action Senior UW authority required for non-renewal decision
Meaning Material premium accounts deserve proportional attention. A $250K premium account lost to non-renewal has 25x the revenue impact of a $10K account.

The Scoring Formula

The priority score combines a base score (driven by premium size) with the sum of all detected flag weights:

graph TD subgraph Formula["Priority Score Calculation"] A["Base Score<br/>(Premium Tier)"] B["+ AW Flag (+25)"] C["+ FAC Flag (+20)"] D["+ Large Loss Flag (+20)"] E["+ Punitive Flag (+15)"] F["+ Exp Mod Flag (+15)"] G["+ Multi-Location (+10)"] H["+ First Renewal (+10)"] I["+ High Premium (+10)"] end subgraph Tiers["Priority Tier Thresholds"] J["Score >= 70 → P1 Critical<br/>Rush SLA: 48h<br/>Manager + Legal notified"] K["Score 50-69 → P2 High<br/>Standard SLA: 5 days<br/>Manager notified"] L["Score 30-49 → P3 Standard<br/>Extended SLA: 10 days<br/>Auto-assigned, queued"] M["Score < 30 → P4 Routine<br/>No SLA<br/>Queued only"] end A --> J B --> J C --> J D --> J E --> J F --> J G --> J H --> J I --> J J --> K K --> L L --> M

Theoretical maximum score: 50 (base, premium > $500K) + 125 (all 8 flags) = 175. In practice, scores above 100 are rare and indicate accounts requiring executive-level attention.

Priority Tier Auto-Actions

Tier Score Range SLA Assignment Notifications Special Actions
P1 Critical >= 70 48 hours (rush) Auto-assign to UW of record + senior UW backup Bell (HIGH) + Email to UW, Manager, and VP Legal review auto-created for AW/Punitive; FAC renewal auto-queued
P2 High 50-69 5 business days Auto-assign to UW of record Bell (HIGH) + Email to UW and Manager Loss summary auto-attached
P3 Standard 30-49 10 business days Auto-assign via FIFO Bell (NORMAL) to UW Standard renewal checklist
P4 Routine < 30 None Queued, not auto-assigned None (visible in queue) Candidate for auto-renewal if enabled

The Scenario

Vanguard Industries is a mid-market industrial manufacturer with 14 facilities across 8 states. Their Excess Casualty policy provides a $25M excess layer over a $5M primary GL/Products policy. The expiring premium is $487,000. The policy expires August 15, 2026.

The account carries three critical flags:

  1. AW (Account Warning): Vanguard has filed a claims handling complaint with the state DOI regarding the carrier's handling of claim CLM-2025-VNG-00312. Legal review is required.
  2. FAC Placement: 60% of the $25M excess layer is ceded to Swiss Re via FAC certificate FAC-2025-VNG-EXC. Swiss Re requires 35 days advance notice for renewal consideration.
  3. Large Loss / Open Claim: Claim CLM-2025-VNG-00312 — a product liability claim arising from a manufacturing defect. Current incurred: $3,200,000 ($1.8M paid, $1.4M reserve). The claim includes a punitive damages allegation under Illinois law.

Priority Score Calculation:

Component Value Running Total
Base Score (premium $150K-$500K) 40 40
AW (Account Warning) +25 65
FAC Placement +20 85
Large Loss ($3.2M) +20 105
Punitive Damages +15 120
High Experience Mod (78% loss ratio) +15 135
Multi-Location (14 facilities / 8 states) +10 145
High Premium ($487K) +10 155

Priority Tier: P1 Critical (Score 155). This is the highest-scoring renewal in the portfolio. Every auto-action fires.

What InsightUW Does Automatically

Time Auto-Action Detail
May 17, 2:01 AM Nightly scan detects expiration (90-day window) Policy EXC-2025-VNG-00198 expires Aug 15, 2026
May 17, 2:01 AM Flag detection: 7 of 8 flags detected AW, FAC, Large Loss, Punitive, High Exp Mod, Multi-Location, High Premium
May 17, 2:01 AM Priority score calculated: 155 → P1 Critical Rush SLA: 48 hours
May 17, 2:01 AM Renewal submission RNW-2026-EXC-01204 auto-created All expiring policy data pre-populated
May 17, 2:01 AM Assigned to Marcus Webb (Senior UW, Excess Casualty) UW of record; backup assigned to VP of Casualty
May 17, 2:01 AM Manager notification: Andrea Nguyen (VP Casualty) Bell (HIGH) + Email: "P1 Critical Renewal: Vanguard Industries — 7 flags"
May 17, 2:01 AM Legal review task auto-created Assigned to coverage counsel: "AW + Punitive review required before renewal terms"
May 17, 2:01 AM FAC renewal request auto-queued Reinsurance team notified: "FAC-2025-VNG-EXC renewal required. Swiss Re 35-day deadline: July 11"
May 17, 2:01 AM Loss summary auto-attached 5-year loss development triangle for Vanguard attached to renewal
May 17, 7:15 AM Marcus Webb opens InsightUW Bell shows P1 Critical badge. Vanguard is #1 in his queue.
May 17, 7:20 AM Marcus opens renewal package Sees all 7 flags, loss summary, FAC certificate details, AW detail, and punitive damages allegation — all on one screen

How Flags Flow from Policy Systems

The flag detection engine uses a standardized integration layer to query source systems. Each source system exposes data through either a direct API or a nightly data feed:

graph TD subgraph Policy Admin["Policy Admin System"] PA1["account warnings API"] PA2["policy details API"] PA3["location schedule API"] end subgraph Claims["Claims System"] CL1["large loss query API<br/>(incurred > $250K)"] CL2["punitive damages query API<br/>(alleged = true)"] CL3["loss summary API<br/>(5-year development)"] end subgraph Reinsurance["Reinsurance System"] RI1["fac certificates API<br/>(active, linked to policy)"] RI2["fac deadlines API<br/>(notice requirements)"] end subgraph Actuarial["Actuarial System"] AC1["experience mod API (WC)"] AC2["loss ratio query API<br/>(GL, Property, Excess)"] end subgraph Engine["InsightUW Flag Detection Engine"] FE["Evaluate 8 flag rules<br/>per expiring policy"] end PA1 --> FE PA2 --> FE PA3 --> FE CL1 --> FE CL2 --> FE CL3 --> FE RI1 --> FE RI2 --> FE AC1 --> FE AC2 --> FE

Integration Patterns

Source System Integration Method Latency Fallback
Policy Admin REST API (real-time) < 200ms per query Nightly CSV feed
Claims System REST API (real-time) < 500ms per query Nightly data extract
Reinsurance System Nightly batch feed (most carriers) N/A (batch) Manual entry in InsightUW
Actuarial / Rating REST API or nightly feed < 300ms or batch Manual EMR/loss ratio entry
Compliance / Legal Manual flag entry (most carriers) N/A UW can manually add flags

Metrics: Before and After Flag-Based Priority Scoring

Metric Before InsightUW After InsightUW Improvement
Renewals with flags identified before UW first touch < 10% (manual discovery) 100% (auto-detected) Complete coverage
Average days to discover large loss on renewal 18 days into renewal cycle Day 0 (attached at creation) 18 days saved
FAC renewal requests submitted on time 62% (missed deadlines common) 98% (auto-queued with countdown) 58% improvement
P1 renewals started within 48 hours 25% (no priority system) 94% (rush SLA enforced) 3.8x improvement
Non-renewals due to missed FAC deadlines 8-12 per year 0-1 per year 90% reduction
UW time spent researching flags per renewal 35 minutes (manual lookup across systems) 0 minutes (pre-attached) 100% eliminated
Pricing accuracy on first indication 71% (revised later after flag discovery) 93% (flags inform initial pricing) 31% improvement
Accounts escalated to VP due to late flag discovery 15-20 per quarter 1-2 per quarter (proactive, not reactive) 90% reduction

Key Takeaways

  1. Flags are facts, not opinions. Each flag comes from a source system with a specific detection rule. The underwriter does not need to search for problems — problems are surfaced automatically.

  2. Additive scoring creates natural separation. An account with one flag scores 40-65 (P2-P3). An account with four flags scores 100+ (deep P1). The math naturally pushes the riskiest accounts to the top without manual intervention.

  3. Auto-actions eliminate the first 48 hours of work. When a P1 renewal is created, the legal review is already queued, the FAC request is already submitted, and the loss summary is already attached. The underwriter's first action is reading, not requesting.

  4. The flag panel is the renewal's executive summary. Marcus Webb opens the Vanguard renewal and sees, in one panel, everything he needs to understand why this account is P1 and what actions are already in flight. No toggling between systems.

  5. Priority scoring is configurable. Different carriers weight flags differently. A carrier with a large FAC book may weight FAC at +30 instead of +20. A carrier with low litigation exposure may weight Punitive at +10. InsightUW makes every weight and threshold configurable per carrier and per LOB.


InsightUW's flag-based priority scoring ensures your riskiest renewals are identified, scored, and staffed from Day 1 — not discovered in a crisis at Day 60. See the flag engine in action with your own renewal portfolio.

See InsightUW run on your data

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

Request a demo