Establishing secure connection…Loading editor…Preparing document…

Beazley Specific Project Client Excess Limit of Liability Application

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

Specific Project/Client Excess Limit of Liability Application

Architects and Engineers Professional Liability, Architects, Engineers and Contractors Pollution Liability, Technology Based Services, Technology Products, Computer Network Security, and Multimedia and Advertising and Privacy Liability Insurance Policy

Important Note: This is an application for a claims made and reported policy. Subject to its terms, the Policy applies only to a Claim first made against the Insureds during the Policy Period or the Optional Extension Period (if purchased) and reported in writing to the Insurer during or within 60 days after expiration of the Policy Period or during the Optional Extension Period (if purchased).

Additional Notice to New York Applicants: The Policy for which this Application is made is a claims made policy. The Policy provides no coverage for Claims arising out of incidents, occurrences or wrongful acts which took place prior to the Retroactive Date.

Additional Notice to Minnesota Applicants: Under Minnesota law a Claim may be reported orally or in writing to the Insurer or to the Insured’s Broker of Record.

Please fully answer all questions and submit all requested information. Terms appearing in bold face in this Application are defined in the Policy and have the same meaning in this Application as in the Policy.

Applicant Information

1. Firm Information

Firm Name:

Project Name:    Project Location:

Client Name:    Contract Number:

2. Estimated beginning and completion dates for both the design and construction phases:

Design Phase

From
To

Construction Phase

From
To

3. Description of the firm’s services for the project:

4. Description of the project:

5. Total estimated construction value for the project: $

6. Total estimated fees the firm will receive for this project only: $

7. Annual breakdown of the firm’s project fees for this project only:

Last Year (20 ) $

Current Year (20 ) $

Next Year (20 ) $

8. Total estimated contract fees for all design firms for this project: $

9. Who is the prime design professional for this project?

10. Total Each Claim and Aggregate limits required? $ Each Claim / $ Aggregate

11. How long is the firm required to carry this limit?

12. Has the firm performed design services for this client in the past? Yes No

If yes, please provide project names below.

Claim and Circumstance are defined as follows for the purposes of question 13.

Circumstance means any fact, event or situation that could reasonably be the basis for a Claim.

Claim means a demand for money or services including the service of suit or institution of arbitration proceedings.

13. Is the firm, its predecessor(s), or any other person or entity for which coverage would be provided aware of any Claim(s) or Circumstance(s) on this project? Yes No

If yes, please attach details below:

Nothing contained herein or incorporated herein by reference shall constitute notice of a Claim or potential Claim so as to trigger coverage under any contract of insurance.

A Copy of the Contract may be required with this Application

Fraud Warning Disclosure

Any person who, with intent to defraud or knowing that (s)he is facilitating a fraud against the insurer, submits an application or files a claim containing a false or deceptive statement may be guilty of insurance fraud.

NOTICE TO ALABAMA, ARKANSAS, LOUISIANA, NEW MEXICO AND RHODE ISLAND APPLICANTS: Any person who knowingly presents a false or fraudulent claim for payment of a loss or benefit or knowingly presents false information in an application for insurance is guilty of a crime and may be subject to fines and confinement in prison.

NOTICE TO COLORADO APPLICANTS: It is unlawful to knowingly provide false, incomplete, or misleading facts or information to an insurance company for the purpose of defrauding or attempting to defraud the company.

NOTICE TO DISTRICT OF COLUMBIA APPLICANTS: Warning: It is a crime to provide false or misleading information to an insurer for the purpose of defrauding the insurer or any other person.

NOTICE TO FLORIDA APPLICANTS: Any person who knowingly and with intent to injure, defraud, or deceive any insurer files a statement of claim or an application containing any false, incomplete or misleading information is guilty of a felony of the third degree.

NOTICE TO KANSAS APPLICANTS: Any person who knowingly and with intent to defraud presents or prepares a written statement as part of an application for insurance that contains materially false information commits a fraudulent insurance act.

NOTICE TO MAINE, TENNESSEE, VIRGINIA AND WASHINGTON APPLICANTS: It is a crime to knowingly provide false, incomplete or misleading information to an insurance company for the purpose of defrauding the company.

NOTICE TO MARYLAND APPLICANTS: Any person who knowingly or willfully presents a false or fraudulent claim for payment of a loss or benefit or knowingly or willfully presents false information in an application for insurance is guilty of a crime.

NOTICE TO OKLAHOMA APPLICANTS: Warning: Any person who knowingly, and with intent to injure, defraud or deceive any insurer, makes any claim for the proceeds of an insurance policy containing any false, incomplete or misleading information is guilty of a felony.

NOTICE TO KENTUCKY, NEW JERSEY, NEW YORK, OHIO AND PENNSYLVANIA APPLICANTS: Any person who knowingly and with intent to defraud any insurance company or other person files an application for insurance or statement of claim containing any materially false information commits a fraudulent insurance act.

Signature Section

The undersigned authorized employee of the applicant declares that the statements set forth herein are true. The undersigned authorized employee agrees that if the information supplied on this application changes between the date of this application and the effective date of the insurance, he/she will immediately notify the underwriter of such changes.

Nothing contained herein or incorporated herein by reference shall constitute notice of a Claim or potential Claim so as to trigger coverage under any contract of insurance.

Signing of this application does not bind the applicant or the underwriter to complete the insurance, but it is agreed that this application shall be the basis of the contract should a policy be issued.

Electronic Signature and Acceptance – Firm’s Authorized Representative Date:

Electronic Signature and Acceptance – Insurance Agent/Broker/Producer Date:

Firm’s Signature*:

Date:

Firm’s Authorized Representative Printed Name:    Title:

If this Application is completed in Florida, please provide the Insurance Agent’s name and license number. If this Application is completed in Iowa or New Hampshire, please provide the Insurance Agent’s name and signature only.

Agent’s Printed Name:    Florida Agent’s License Number:

Agent’s Signature*:

Enter text✕

What the Beazley Specific Project Client Excess Limit of Liability Application Is

The Beazley Specific Project Client Excess Limit of Liability Application is a formal insurance underwriting form used to request an excess limits layer for a named project client. It documents the project scope, limits sought, prior coverage, loss history, and risk controls so Beazley underwriters can evaluate capacity, exclusions, and pricing. The application typically supplements primary and umbrella policies, clarifies the attachment point and aggregate limits, and supplies evidence of compliance with project-specific safety and contractual obligations. Accurate completion supports timely underwriting and reduces follow-up requests for missing data.

Why This Application Matters for Project-Specific Coverage

Completing the Beazley Specific Project Client Excess Limit of Liability Application ensures the insurer has the factual and contractual detail needed to assess excess exposure accurately, set appropriate limits and terms, and align security with the primary policy structure.

Why This Application Matters for Project-Specific Coverage

Who Typically Prepares and Reviews This Application

Final submission is usually routed by the broker to Beazley underwriters and may require insurer follow-up for additional documentation or clarification.

  • Brokers and Producers: Assemble underwriting package and negotiate terms with Beazley.
  • Risk Managers: Provide project-specific loss control and contract details.
  • General Contractors: Supply schedule, subcontractor lists, and safety program information.

Core Sections You’ll Find on the Application

The form structures information to let underwriters evaluate scope, limits, and exposures quickly; each section targets a specific underwriting requirement.

Project Summary

Concise description of the project, location, contractual parties, anticipated start and completion dates, and total project value or estimated exposure.

Coverage Requested

Requested excess limit amount, proposed attachment point (per occurrence and aggregate), scope of covered operations, and any sublimits or endorsements sought.

Primary Insurance

Details of underlying primary and umbrella programs including insurer names, policy numbers, limits, retentions/deductibles, and effective periods.

Loss History

Prior claims and loss runs covering at least five years, with descriptions, values, and corrective actions taken to mitigate recurrence.

Risk Controls

Site-specific safety programs, third-party audits, contractor prequalification, and quality-control procedures that reduce frequency or severity.

Contractual Terms

Key indemnity, hold-harmless, waiver of subrogation, and additional-insured wording that affect coverage obligations and potential indemnity triggers.

Step-by-Step: Completing the Application

Follow these core steps in order to prepare a complete underwriting package and reduce follow-up inquiries.

  • 01
    Gather documents: Collect primary policy declarations, prior loss runs, contracts, and safety audits.
  • 02
    Populate fields: Enter project details, limits requested, and underwriting answers carefully.
  • 03
    Review for consistency: Confirm names, dates, and limit figures match attached documents.
  • 04
    Submit with attachments: Send the completed form and supporting files to Beazley via broker portal or agreed channel.

Configuring an Online Submission Workflow

Set up a digital workflow that collects signatures, attachments, and required attestations in one pass.

Step Configuration
Upload Document Use PDF or Word DOCX, ensure text is selectable for field detection.
Add Fields Place text, date, and signature fields; mark required fields as mandatory.
Attach Files Require primary policy decs, loss runs, and contract exhibits as mandatory attachments.
Authentication Require signer email verification or stronger authentication for broker or insured signatures.

Where to Send or File the Completed Application

Use the broker’s submission channel or Beazley’s designated underwriting portal to ensure receipt and tracking.

  • Broker Portal: Upload the application and attachments within the broker’s secure underwriting workspace.
  • Beazley Underwriter: Send directly to the assigned underwriter’s secure inbox or portal queue as instructed.
  • Email Transmission: Use encrypted email only when portal upload is not available and follow any insurer file size limits.
  • Follow-up: Confirm receipt and obtain a submission reference for future correspondence.

Distribution Channels and eSubmission Considerations

Ensure the chosen method supports required attachments, audit trails, and any insurer-specific authentication or delivery requirements.

  • Portal Upload: Preferred for tracking and large attachments.
  • Secure Email: Acceptable if encrypted and under file-size limits.
  • eSignature Link: Use for collecting authorized signatures electronically.

Typical Timelines and Processing Expectations

Expect standard processing stages and plan submissions to allow underwriting review without unnecessary delay.

Initial Submission:

Submit full package; early submission accelerates initial screening and desk review.

Underwriting Review:

Underwriters typically review within 5–15 business days depending on complexity.

Information Requests:

Expect follow-up for clarification or missing attachments; response time affects binding speed.

Binding Decision:

Binding, pricing, and endorsements issued after satisfactory underwriting and receipt of any required payment.

Policy Issuance:

Final policy documentation issued once terms are agreed and premium is processed.

Essential Data Elements to Provide

Insured Name: Exact legal name
Project Address: Full street address
Coverage Limits: Requested numeric limits
Underlying Insurer: Primary policy insurer
Loss Runs: Prior five years
Signer Details: Name and title

Common Mistakes That Delay Underwriting

  • Incomplete attachments: omitting primary policy declarations or loss runs often triggers requests and delays.
  • Mismatched names or dates: discrepancies between insured name and attached policies cause verification problems.
  • Vague scope descriptions: unclear project scope or contract roles increase perceived exposure and may lead to higher rates.
  • Missing signer authority: submissions signed by unauthorized individuals can result in rejection or rescindment.

Risks of Incorrect or Incomplete Applications

Coverage Denial: Late or inaccurate info can lead to declination
Policy Rescission: Material misstatements risk rescission
Higher Premiums: Underwriter uncertainty may increase pricing
Delayed Binding: Missing data postpones coverage start
Claim Dispute: Inconsistent records complicate claim payment
Regulatory Risk: Noncompliance with state rules may cause sanctions

Practical Tips for Accurate and Efficient Submission

Adopt a consistent internal checklist and central document repository to speed preparation and reduce common errors.

Use a Pre-Submission Checklist
Confirm required attachments—primary policy declarations, five-year loss runs, signed contracts, and any project-specific audits—before sending to avoid cyclical follow-ups.
Standardize Naming Conventions
Label attachments with insurer name, policy period, and document type (for example: 'PrimaryPolicy_Declarations_01-01-24_12-31-24.pdf') so underwriters locate documents quickly.
Assign an Authorized Signer
Ensure the signer is listed in corporate records and authorized to bind coverage; include a delegation letter when authority is delegated.
Document Version Control
Maintain a single source of truth for the application and attachments; track edits, who made them, and when to prevent conflicting submissions.

Real-World Submission Examples

These condensed examples show how a complete package reduces underwriting questions and speeds decisions.

Tech Data Submission

Optica Ventures provided full five-year loss runs and primary policy decs at first submission.

  • Underwriters flagged a sublimit inconsistency quickly.
  • Because the broker included immediate corrective documentation and revised contractual wording, binding occurred without a second full submission and policy issuance proceeded within two weeks.

Martin Properties Project

A regional developer sent the application with detailed safety audits and contractor prequalification records.

  • The underwriter confirmed required endorsements.
  • The inclusion of these items reduced follow-up questions, produced clearer pricing assumptions, and shortened the underwriting timeline substantially.

Common eSignature Pricing and Feature Comparison

Compare basic starting prices and essential features for common eSignature vendors to estimate costs for electronic submission and signature collection.

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 free trial No No Yes, limited Yes, limited
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions and Troubleshooting

Answers to common questions about execution, electronic signatures, and submission issues that commonly arise with project-specific excess applications.


Need help? Contact support

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