Establishing secure connection…Loading editor…Preparing document…

Insurance Excess Liability Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

INSURANCE EXCESS LIABILITY REQUEST

Date of Request:    Broker / Producer:

Applicant / Insured Information

Entity Type (select all that apply)

Policy & Coverage Details

Type of Excess Coverage Requested (check all that apply)

Underlying Insurance (List applicable underlying policies)

Carrier 1:   Policy #:   Limits:

Carrier 2:   Policy #:   Limits:

Carrier 3:   Policy #:   Limits:

Exposure, Operations & Controls

Loss History & Claims

Losses in the last 5 years:

Coverage Conditions, Endorsements & Exposures

Supporting Documentation Checklist

Declaration and Certification

I certify that the information contained in this request and any attachments is complete and accurate to the best of my knowledge. I understand that the insurer will rely upon this information in evaluating the risk and issuing any excess liability coverage. I authorize the release of loss history and underwriting information to the insurer and its authorized representatives. I acknowledge that incomplete or inaccurate statements may constitute grounds for declination of coverage or rescission of any policy issued.

Fraud Warning: Where applicable by law, any person who knowingly presents false information in an application for insurance may be subject to criminal and civil penalties.

Applicant Name:

By:

Date:

Enter text✕

What an Insurance Excess Liability Request Is and When it’s Used

An Insurance Excess Liability Request is a formal document used to request liability coverage that sits above a primary policy’s limits. Organizations and contractors use it to confirm excess limits, policy period, and any endorsements required by a contract or certificate holder. The request typically includes insured details, underlying coverage, requested excess limits, effective and expiration dates, and signatures from an authorized representative. When submitted electronically it should meet ESIGN and UETA requirements for intent, attribution, consent, and retention; many organizations use secure eSignature platforms such as signNow for compliant electronic execution and tracking.

Why an Accurate Request Matters for Contracts and Claims

A clear, complete request prevents coverage gaps, supports contractual compliance, and reduces claim disputes. It provides underwriters and certificate holders the information needed to confirm excess limits and any special endorsements required by a contract or project.

Why an Accurate Request Matters for Contracts and Claims

Typical Users and Roles Involved

Who completes or receives these requests varies by role and industry; the following outlines common participants.

  • Insurance brokers coordinating excess placements and confirming cover limits with carriers and certificate holders.
  • Risk managers or corporate counsel ensuring contract language matches requested excess limits and endorsement terms.
  • Vendors, contractors, or subconsultants submitting proof of excess coverage to owners or general contractors.

The document often circulates between the insured, broker, insurer underwriting team, and the certificate holder; accuracy at each step reduces delays and disputes.

Core Elements to Include in a Professional Request

A complete Insurance Excess Liability Request contains standardized sections so underwriters and certificate holders can quickly verify coverage and limits.

Insured Details

Full legal entity name, mailing address, and contact information for the insured and any named insureds; use exact legal names as shown on primary policy.

Certificate Holder

Name and address of the party requesting evidence of excess coverage; specify whether coverage must name the holder as additional insured or provide endorsement language.

Limits Requested

Specify excess limit amounts (for example, $1,000,000 per occurrence / $2,000,000 aggregate) and explain whether limits are per-project or blanket.

Policy Period

Effective and expiration dates in MM/DD/YYYY format, matching contract term; state if coverage must be retroactive to a project start date.

Underlying Insurance

Detail the primary insurer, policy number, limits and self-insured retentions that must remain in place before excess attachment.

Authorization

Signature block for an authorized representative, printed name, title, and date to validate the request and permit release of policy information.

Step-by-step: Fill and Submit an Excess Liability Request

Follow these sequential steps to prepare a complete request and speed insurer review.

  • 01
    Prepare Background: Gather primary policy, limits, and certificate holder instructions.
  • 02
    Complete Fields: Enter insured, policy, limits, dates, and certificate holder precisely.
  • 03
    Authorize Request: Obtain signature from an authorized representative.
  • 04
    Send to Underwriter: Deliver via broker portal, email, or eSubmission as directed.

How to Configure an Online Request Workflow

Set up a repeatable online workflow to reduce errors and automate routing for approvals and insurer submission.

Field Configuration
Authentication Method Use email link or SMS code for signer verification.
Conditional Fields Show excess-limit fields only if excess coverage is requested.
Routing Order Route to broker then underwriter then certificate holder.
Notifications Enable status emails for each completed step.

Where to Send or File the Completed Request

Choose a submission path based on the relationship between insured, broker, and carrier.

  • To the Broker: Send completed request to the broker for review and formal submission.
  • Direct to Underwriter: Underwriters accept broker portal uploads or insurer-designated email addresses.
  • Certificate Holder: Provide final certificate or endorsement to the holder as proof of coverage.
  • Record Storage: Store executed copies in the insured’s compliance repository.

Digital Submission and Platform Considerations

Electronic submission should use secure platforms that support audit trails, common formats, and integrations with broker systems.

  • Integrations: Salesforce, NetSuite, Microsoft 365 and other broker/agency systems
  • Formats: PDF, DOCX and printable certificates
  • Authentication: Email link, SMS code, or multi-factor

Choose a platform that preserves the signed record, stores an audit trail, and integrates with your document management system to support compliance and future audits.

Timing Expectations and Typical Processing Windows

Understand internal and insurer timelines to avoid coverage lapses and project delays.

When to Submit:

Submit at least 10 business days before coverage is required by contract.

Insurer Review Time:

Varies by carrier; allow multiple business days for underwriting checks.

Effective Date Alignment:

Ensure policy effective date matches contract start to avoid gaps.

Renewal Handling:

Request renewals 30 days before policy expiration to secure continuous coverage.

Recordkeeping Deadline:

Keep copies until retention obligations expire per company policy.

Common Mistakes That Delay Approval

  • Submitting an incomplete policy number or misspelled insured name — insurers cannot locate the underlying policy and will return the request.
  • Requesting limits that don’t match the contract language or failing to specify occurrence versus aggregate limits, creating ambiguity for the underwriter.
  • Failing to include required endorsement wording or additional insured language, which leads to follow-up and delayed certificate issuance.
  • Using an expired primary policy period or mismatched effective dates so coverage does not align with the contract term.

Potential Consequences of an Incorrect Request

Coverage Gap: Loss of excess protection
Claim Denial: Carrier may deny covered losses
Contract Breach: May trigger contractual penalties
Premium Adjustment: Higher rates or retroactive charges
Regulatory Risk: Noncompliance notices possible
Delayed Performance: Project delays until proof provided

Comparing eSignature Vendors for Submitting Requests (vendor column order required)

Common vendor features and starting prices are shown below to help compare baseline capabilities; signNow appears first per comparison guidelines.

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 Yes, 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

Frequently Asked Questions: Common Issues and Solutions

Answers to common operational and legal questions about preparing, submitting, and storing Insurance Excess Liability Requests.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users