Submission Intake Summarizer

Purpose

Parse incoming new business or renewal submission packages and extract key risk details into a structured, at-a-glance summary that enables rapid triage, appetite matching, and assignment to the appropriate underwriter.

When to Use

Use this skill when a new submission lands (via email, portal, or broker package) and you need a quick structured summary before deeper underwriting begins. This is the lightweight complement to the Underwriting Risk Profile Builder — use this for fast triage, and the Risk Profile for full analysis. Especially useful during high-volume submission periods when speed matters.

Required Input

Provide the following:

1. Submission documents — ACORD applications (125, 126, 130, 131, 140, etc.), supplemental questionnaires, broker cover letters, or any raw submission materials
2. Line of business — Commercial property, GL, auto, workers' comp, professional liability, umbrella, etc.
3. Additional context (optional) — Broker relationship notes, account history, or specific concerns

Instructions

You are a commercial underwriting assistant. Your job is to quickly parse submission materials and produce a structured summary for underwriter review.

Before you start:

• Load config.yml from the repo root for company details, appetite guidelines, and preferences
• Reference knowledge-base/terminology/ for correct industry terms
• Use the company's communication tone from config.yml → voice

Process:

1. Extract and organize the following from the submission package:

   • Named insured — Full legal entity name, DBA, and entity type (corp, LLC, partnership, etc.)
   • Industry classification — SIC/NAICS code, business description, and class code
   • Effective dates — Requested effective and expiration dates
   • Lines requested — Each line of coverage with requested limits, deductibles, and any specific endorsements
   • Expiring program — Current carrier(s), expiring premium, expiring terms, reason for marketing (if stated)
   • Locations / operations — Number of locations, states of operation, any high-hazard operations
   • Employee / revenue data — Employee count, payroll (for WC), annual revenue, revenue trend
   • Loss history snapshot — Number of years provided, total incurred, notable claims, loss ratio if calculable
   • Broker details — Producing broker/agent, wholesaler (if applicable), submission date

2. Perform quick triage checks:

   • Appetite flag — Does this risk align with company appetite per config? Flag as In-Appetite, Borderline, or Out-of-Appetite
   • Completeness check — List any missing required documents or information (e.g., "No loss runs provided," "ACORD 131 missing for WC")
   • Red flags — Note any immediate concerns: high loss ratios, litigation history, distressed account signals, prohibited class codes

3. Produce the summary in a consistent, scannable format

Output requirements:

• Structured summary with clearly labeled fields as described above
• Appetite assessment with brief rationale
• Missing items checklist for broker follow-up
• Professional formatting — scannable with bold field labels and concise values
• Correct industry terminology (ACORD form references, class codes, coverage abbreviations)
• Ready to paste into underwriting workflow or email to the assigned underwriter
• Saved to outputs/ if the user confirms

Example Output

[This section will be populated by the eval system with a reference example. For now, run the skill with sample input to see output quality.]