Insurance

Underwriting Submission Workbench

Designed for Underwriter

Turn unstructured broker submissions into a triaged, priced risk file by extracting exposures, normalizing loss runs, and testing appetite and guideline fit before an underwriter binds or declines.

Contract INS-02 · primary aggregate SubmissionFile · mode loading

Decision brief

Quote, refer, or decline: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Underwriter

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A broker emails a 900-location retail property submission with five years of loss runs; the workbench normalizes the schedule, geocodes locations into two wind-exposed counties, computes a burn cost that exceeds the appetite threshold, and the underwriter refers the account with the cited capacity clause rather than quoting it..

Decision to make

Turn unstructured broker submissions into a triaged, priced risk file by extracting exposures, normalizing loss runs, and testing appetite and guideline fit before an underwriter binds or declines.

Outcome to show

Issued quote, referral to senior authority, or declination gives Underwriter the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Ingest broker submission package
  2. 2Extract and normalize exposures and losses
  3. 3Score appetite fit and triage priority
  4. 4Produce hazard summary and pricing indication
  5. 5Quote, refer, or decline

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Underwriter verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved SubmissionFile evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Turn unstructured broker submissions into a triaged, priced risk file by extracting exposures, normalizing loss runs, and testing appetite and guideline fit before an underwriter binds or declines.
Primary aggregate
SubmissionFile
Primary container
submissionFiles
Hierarchical key
/tenantId + /submissionId
Schema version
1

Sample scenario

A broker emails a 900-location retail property submission with five years of loss runs; the workbench normalizes the schedule, geocodes locations into two wind-exposed counties, computes a burn cost that exceeds the appetite threshold, and the underwriter refers the account with the cited capacity clause rather than quoting it.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
submissionFiles Primary /tenantId + /submissionId SubmissionFile, ExposureSchedule, LossRunRecord, RiskAssessment
underwritingGuidelineLibrary Reference /tenantId + /guidelineId UnderwritingGuideline

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
SubmissionFile submissionFiles /tenantId + /submissionId submission::{submissionId} None
ExposureSchedule submissionFiles /tenantId + /submissionId exposure::{submissionId}::{scheduleId} None
LossRunRecord submissionFiles /tenantId + /submissionId lossrun::{submissionId}::{priorClaimId} None
UnderwritingGuideline underwritingGuidelineLibrary /tenantId + /guidelineId guideline::{guidelineId}::{clauseIndex} clauseVector
RiskAssessment submissionFiles /tenantId + /submissionId assessment::{submissionId}::{assessmentVersion} hazardSummaryVector

Query patterns