Submission intake
Super Agent · YP
Reads the broker’s submission, builds the risk file and drafts the request for what is missing.
On every submission · ran 8m ago
Run nowInsurance
From broker submission to risk file
Reads each broker submission and its attachments, builds the risk file in your policy system and drafts the request for anything missing. Your underwriting assistant checks and sends it.
×
When
When a submission arrives
Systems
OutlookExcelSharePointPolicy systemMode
Builds the file. Your underwriting assistant approves
Problem
A submission arrives as an email with a proposal form, a schedule of locations and sums insured, and the claims history, each broker in their own format. Someone reads every attachment, works out what is missing, types the risk details into the policy system and writes back to the broker.
What it does
YP reads the email and every attachment, extracts the risk details and checks them against your submission checklist for that class. It creates the risk file in your policy system, links each field to its source document and drafts the request to the broker for anything missing.
How it works
See exactly how the work gets done.
The work starts the moment a broker submission arrives. A new email in the submissions inbox starts the run, and the proposal forms, schedules and claims histories are read straight away.
Each submission is checked against your own checklist. That checklist sets which information is required per class. Gaps are listed and not filled in.
The risk is checked for binder fit and for duplicates. Class, territory and limits are compared with your binder, and the insured is checked against risks already on file.
The risk file is written into the policy system you already use. Each field is linked to the document it came from, and your team does not have to open a new portal.
Your underwriting assistant sends the request to the broker. The underwriting assistant first reviews the risk file and the draft request, and nothing reaches a broker without their approval.
The outcome
Your underwriting assistants review files instead of building them. Underwriters receive complete submissions.
01
Risk file built
In your policy system, every field traced
02
3 checks per submission
Required information, binder fit and duplicate risks
03
Underwriting assistant approves
Every request to a broker, before it goes out
For your numbers
YP builds the risk file from every broker submission, so brokers get a faster answer and your underwriters quote more risks.
How it runs
Designed for enterprise.
Private
Runs on your infrastructure. Drawings, prices, client and claims data never train a model.
Explainable
Not a black box. An AI auditor checks that every task was done as intended and proposes improvements.
Traceable
Every value links to the document, rule or record it came from. Every step is logged. A named person approves anything that leaves the building.
Your systems
Works in your ERP, CargoWise, policy system, GIS and file shares. Nothing is replaced.
Not sure where to start?
Put AI to work on your most complex workflows.
More Insurance use cases
InsuranceSee use case
Draft quote and policy documents
From a complete risk file to a draft quote and policy documents, rated with your own rater. Your underwriter signs off.
×
InsuranceSee use case
Monthly bordereaux per insurer
Builds each insurer’s monthly risk, premium and claims bordereaux from your systems, checked and reconciled before your analyst submits.
×
InsuranceSee use case
From loss notification to claim file
A first notification of loss becomes a claim file in your claims system, with the request for every missing document drafted.
×