Insurance Loss Run Request
What an Insurance Loss Run Request Is
Why Loss Run Requests Matter
Loss run requests provide essential claims history that informs underwriting, pricing, and risk control decisions; they reduce surprise exposures at renewal and support accurate premium allocation during audits and transactions.
Typical Users and Their Roles
Brokers, risk managers, underwriters, and insured parties commonly request loss runs when assessing policy renewals or obtaining quotes.
- Insurance brokers: collect loss runs to prepare comparative renewal submissions and negotiate coverage terms.
- Risk managers: use historical claim details to implement loss-control measures and forecast reserve needs.
- Underwriters: evaluate frequency and severity of claims to set rates, endorsements, and underwriting appetite.
Use appropriate internal controls for request authorization and preserve copies for compliance and audit trails.
Who Prepares and Reviews Loss Runs
Broker
Brokers or agents prepare loss run requests on behalf of insured clients to support renewal submissions, compare carrier responses, and negotiate terms; they must ensure the policyholder authorizes disclosure and verify completeness before submitting to prospective carriers or auditors.
Underwriter
Underwriters analyze loss run details — dates, reserves, paid amounts, and causes — to assess risk classification, determine pricing, set policy terms, and identify potential exclusions; accurate historical data informs reserve adjustments and future premium calculations.
Consequences of Incorrect or Late Requests
Common Preparation Challenges
- Incomplete claim details hinder accurate underwriting and can lead to premium adjustments or coverage disputes during renewal or audit.
- Data inconsistencies across carriers require manual reconciliation, increasing processing time and potential for overlooked claims.
- Unauthorized requests without proper written consent or signatures may breach privacy rules and delay insurer responses.
- Poorly formatted requests increase follow-up queries, prolong turnaround times, and impair timely underwriting risk decisions.
Step-by-Step: Prepare and Submit a Loss Run Request
-
01Confirm Authorization: Obtain written permission from the policyholder.
-
02Specify Period: State exact start and end dates in MM/DD/YYYY.
-
03Detail Data Requested: List fields: claim number, date, reserves, payments.
-
04Send to Carrier: Deliver via insurer portal, email, or certified mail.
Configuring a Digital Workflow for Requests
| Field | Configuration |
|---|---|
| Signer Authentication Method and Strength | Enable email links, SMS codes, or KBA. |
| Field Mapping and Validation Rules | Map CSV columns to fields; validate dates and numerics. |
| Routing, Sequential Approvals, and Notifications | Route responses to broker, underwriter, and compliance teams. |
| Storage, Retention, and Access Controls | Securely store documents with version history and retention policies. |
Technical Requirements and Integrations
Digital submission requires a platform that supports PDF/CSV uploads, audit trails, and secure authentication for signers and recipients.
- Formats Supported: PDF, CSV, Excel supported.
- Integrations: Salesforce, NetSuite, Google Workspace, Microsoft 365.
- Authentication Options: Email link, SMS, KBA, SSO.
How the Request and Response Flow Typically Works
-
Upload Request: Create request and attach required authorization.
-
Send to Carrier: Use insurer portal or secure email link.
-
Carrier Processes: Carrier locates records, compiles loss runs.
-
Receive & Review: Download structured file and verify completeness.
eSignature Pricing and Capability Comparison
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Best Practices to Improve Accuracy and Speed
Frequently Asked Questions About Insurance Loss Run Requests
-
What is an Insurance Loss Run?
A loss run is a carrier-generated record of claims for a policy or insured over a specified period, listing dates of loss, claim numbers, reserves, payments, and status. It is used by underwriters, brokers, and auditors for risk evaluation.
-
Who may request loss run records?
Policyholders, authorized brokers or agents, lenders, and acquiring parties may request loss runs. Carriers typically require written authorization from the policyholder or proof of legal authority before releasing claim histories to third parties.
-
How to format a loss run request
Include policy numbers, full legal names, exact coverage dates, list of requested fields, and signed authorization. Request CSV/Excel for structured data when possible. Be concise to avoid carrier follow-up and speed processing.
-
Can loss runs or authorizations be e-signed?
Yes. Electronic signatures are enforceable under ESIGN (15 U.S.C. ch. 96) and UETA in most states, provided intent, consent, attribution, and reliable record retention are present. Consumer-facing disclosures may be required in regulated contexts.
-
How long do carriers retain loss run records?
Retention varies by carrier and jurisdiction; maintain copies for the policy term plus at least three years, seven years for certain underwriting or claims purposes, and six years for records involving PHI under HIPAA (45 CFR §164.530(j)).
-
What to do if a carrier refuses to provide loss runs
Confirm the proper authorization was provided and that the request specified required fields and period; escalate to the carrier's compliance or legal department, consult broker representatives, and consider state insurance regulator complaint procedures if necessary.