Loss Runs Request Form
Use a Loss Runs Request Form 0 template to make your document workflow more streamlined.
What the Loss Runs Request Form does
A Loss Runs Request Form asks an insurer, broker, or claims administrator to release an insured’s prior loss history for underwriting, renewal, or policy review. The requester identifies the insured, policy numbers, coverage period, requested lines, and authorized recipient. In signNow, upload the form, review auto-detected fillable fields, assign authorization and signature fields, and send it to the responsible parties. The signed request can be downloaded with an audit trail showing signing activity. Carrier response timing and record retention depend on the recipient’s process and applicable state requirements.
Who uses this loss runs request
Insurance agents
Insurance agents and brokers use the Loss Runs Request Form to request prior claim history from carriers during new-business underwriting, renewal review, and coverage assessment. They identify the insured, policy period, requested lines, and authorized recipient before routing the form for signature and delivery.
Policyholders and risk teams
Commercial policyholders and risk managers use the form to authorize release of loss history to a broker, underwriter, or prospective carrier. The completed request helps connect the correct insured and policy records to a documented authorization.
Business types using loss runs requests
Loss Runs Request Form supports insurance workflows where prior claim history must be requested, authorized, and connected to a specific insured or policy period.
Independent insurance agents use the form to obtain prior loss history before presenting a commercial account to prospective carriers, keeping the insured’s authorization and policy details together. Regional brokerage teams use shared signNow templates to request loss runs across renewals, assign delegated senders, and preserve completed forms for underwriting files. Enterprise risk departments use controlled requests when changing carriers, coordinating multiple subsidiaries, or documenting authorization for historical claims information.
These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.
How a loss runs request works
The signNow workflow turns the Loss Runs Request Form into a controlled request: prepare the fields, identify authorized parties, collect signatures, and preserve evidence.
Upload document: Upload the Loss Runs Request Form. Detect fields: Auto-detect and review fillable fields. Route request: Send authorization fields to assigned parties. Preserve record: Store signatures and audit evidence.
Complete a loss runs request in signNow
Use signNow to prepare the Loss Runs Request Form, route authorization and signature fields, and preserve the completed request with its audit trail.
Upload form:
Upload the blank request. Check fields:
Review detected fields and labels. Assign roles:
Assign requester and carrier roles. Send request:
Send the completed request for signature. Store records:
Download the signed form and audit trail.
Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.
Recommended loss runs workflow setup
Configure the request around authorization, controlled disclosure, signer attribution, and an exportable record of the completed Loss Runs Request Form.
| Setting | Recommendation |
|---|---|
| Authentication method | Email link with SMS verification |
| Signature type | Electronic signature with signer intent |
| Audit trail | Capture timestamps, IP, and actions |
| Document retention | Follow the applicable state insurance rule |
| Encryption | TLS 1.2/1.3 and AES-256 |
What the signNow audit trail records
For a Loss Runs Request Form, the audit trail connects signer activity and document history to the authorization record without replacing the carrier’s own claims files.
Authenticate signer:
Capture timestamp:
Hash document:
Seal evidence:
Track activity:
Retrieve records:
Processing stages for loss runs
Processing depends on accurate policy details, signer availability, carrier procedures, and the retention rules governing the resulting insurance records.
Prepare the request
Send to carrier
Await carrier response
Archive completed records
Security controls for loss runs
Transport encryption:
Stored encryption:
Security certification:
Control framework:
Health data:
Signature compliance:
Privacy and disclosure pitfalls
Loss runs may contain claim details and personal information that should not be exposed through unrestricted email forwarding. A requester can omit policy numbers, insured names, or date ranges, forcing the carrier to clarify before releasing records. Missing authorization language can prevent an insurer from confirming that the requester may receive another party’s loss history. Shared inboxes and broad folder permissions can expose completed loss runs to employees without an underwriting or claims need.
Best practices for loss runs requests
Accurate policy identifiers, controlled disclosure, and complete signing records make Loss Runs Request Form easier for carriers to process and review.
Confirm insured and policy details
Make required fields explicit
Limit disclosure during delivery
Archive the request securely
Platform requirements for loss runs
The Loss Runs Request Form can be prepared in supported desktop browsers, including Chrome, Firefox, Safari, and Edge, or through signNow mobile apps on iOS and Android. Use an internet connection for invitation delivery and record synchronization.
Browsers Chrome, Firefox, Safari, and Edge Desktop Windows and macOS desktop access Mobile iOS and Android signNow apps
Teams handling insurance records should use managed Windows, macOS, iOS, or Android devices and restrict downloaded loss runs to approved storage. Enterprise deployments can evaluate API access, SSO provisioning, and authentication settings against their internal insurance-record and privacy controls.
Loss Runs Request Form troubleshooting
Resolve field, routing, authentication, and compliance questions before sending a Loss Runs Request Form to an insurer or authorized recipient.
On signNow’s Business plan, upload the Loss Runs Request Form and review auto-detected fields before sending. If a field is missing, add it manually and assign it to the requester, insured, or authorized recipient before routing.
The Business Premium plan includes bulk send, which is useful when the same Loss Runs Request Form is sent for multiple insureds. For one request, use a standard send flow and verify every policy identifier before delivery.
signNow states that HIPAA compliance requires a business associate agreement. If the request contains protected health information, confirm the BAA and configure access controls before sending; HIPAA’s six-year rule applies to covered-entity documentation under 45 CFR 164.530(j).
An electronic signature can support attribution when the signer demonstrates intent, consents to electronic records, and the record remains reproducible. ESIGN and UETA provide the legal framework, but carrier authorization requirements and state insurance rules still apply.
If a recipient cannot open the signing invitation, verify the email address, resend the invitation, or use a controlled signing link. Keep the completed Loss Runs Request Form and audit trail together after signing.
The Business plan includes audit trails and legally binding eSignatures. Enterprise adds advanced signer authentication, while the Site License can add SSO, full API access, and HIPAA or 21 CFR Part 11 options.
Key performance indicators that demonstrate SignNow's proven track record.
BE READY TO GET MORE
Get this form now!
If you believe that this page should be taken down, please follow our DMCA take-down process.