Excess Flood Application

Use a Excess Flood Application 2012 template to make your document workflow more streamlined.

What the Excess Flood Application does

The Excess Flood Application is used to request coverage for flood risks beyond the limits of an underlying flood policy. It gathers applicant, property, existing-coverage, requested-limit, and payment information so an insurer or broker can assess eligibility and issue excess protection. Complete every applicable field from current policy records, review the coverage amounts, and retain the submitted copy. signNow can convert the application into a fillable workflow, route it to the required parties, capture signatures, and preserve the completed record with its audit trail.

Insurance teams

Complete flood coverage applications, underlying-policy declarations, property schedules, and related contracts with controlled signer routing and an auditable record.

Property applicants

Review and sign requested coverage information from a desktop or mobile device, while keeping the final application associated with the relevant property and policy records.

How this application works in signNow

The signNow workflow turns the Excess Flood Application into a controlled, traceable signing process.

Upload form: Upload the Excess Flood Application PDF to signNow.
Detect fields: Auto-detect fillable fields and review the application layout.
Assign signers: Assign applicant, broker, and insurer signing roles.
Complete record: Send the completed application and store its audit trail.

Steps to complete the application

Use this sequence to prepare, route, sign, and retain an Excess Flood Application in signNow.

Upload form:
Upload the current Excess Flood Application PDF.
Review fields:
Review detected fields and add missing fields.
Add signers:
Enter each signer’s role and email address.
Finalize record:
Send, monitor, and download the signed application.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

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.

Setting	Recommendation
Authentication method	Email verification with SMS OTP
Signature type	Typed or drawn electronic signature
Audit trail	Enabled for every application
Document retention	Follow insurer policy and applicable law
Encryption and provisioning	TLS and AES-256 with admin controls

Privacy and disclosure issues to check

Uploading an Excess Flood Application with visible personal or property data can expose information to unintended recipients or shared storage locations.
A signer who has not consented to electronic records may create an incomplete execution record under the ESIGN Act’s consumer-disclosure requirements.
Sending the application through an unrestricted link can allow an unintended person to view, complete, or sign coverage information.
Leaving existing flood-policy limits or requested excess limits blank can produce an incomplete underwriting record and delay review.

Find and fill out the correct excess flood application

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

Versions	Form popularity	Fillable & printable
*2012 Lexington Insurance Company Lex XSF App [2012-11] 2012	4.8 Satisfied (3436 Votes)

Authenticate signer:

Record the signer’s email, authentication event, and identity checks linked to the application.

Capture timestamps:

Capture each application view, field change, signature, and delivery event with timestamps.

Hash document:

Associate the completed application with a document hash for integrity checking.

Seal record:

Seal the final record so later changes can be detected during review.

Track completion:

Track completion status for every applicant, broker, and insurer signer.

Export evidence:

Retrieve and export the application with its audit trail for archival.

Security controls for application records

Encryption:

AES-256 and TLS

Security certification:

SOC 2 Type II

Information security:

ISO 27001

Health information:

HIPAA with BAA

Electronic signatures:

ESIGN and UETA

Privacy framework:

GDPR controls

Record-keeping practices for this application

A defensible Excess Flood Application file includes the submitted form, signer evidence, audit trail, and applicable retention authority.

Apply the correct retention period

Keep the completed application and its signing evidence together. For records containing protected health information, retain them for six years from creation or the last effective date under HIPAA, 45 CFR §164.530(j); otherwise apply the insurer’s documented retention schedule.

Export the audit trail

Export the completed application and audit trail after all required signatures are collected. Preserve signer identity evidence, timestamps, delivery events, and completion status so the record can be reviewed without relying on an active workspace.

Archive with restricted access

Store the Excess Flood Application in access-controlled archival storage with the final PDF and related coverage documents. Limit permissions to staff handling underwriting, compliance, or the applicant’s account.

Reconcile source information

Record the underlying policy number, requested excess limit, and property identifiers exactly as shown in source documents. A consistent record makes later underwriting review and policy reconciliation easier.

Retention periods for related records

Apply only the retention rule that genuinely covers the Excess Flood Application record and its attachments; insurer and state requirements may be longer.

Tax records: 3 years

Retain federal tax records three years from filing under IRC §6501(a), only when the application is part of tax documentation.

HIPAA records: 6 years

Retain HIPAA-covered records six years from creation or last effective date under 45 CFR §164.530(j), when protected health information is included.

I-9 records: later date

Retain employment verification records three years after hire or one year after termination, whichever is later, under 8 CFR §274a.2(b)(2)(i)(A).

Payroll records: 3 years

Retain payroll records three years under 29 CFR §516.5 when the application is maintained with covered payroll documentation.

Exposure records: 30 years

Retain OSHA exposure records thirty years under 29 CFR §1910.1020 when exposure documentation is attached.

Legal standing of electronic completion

An electronically signed Excess Flood Application can support a U.S. business transaction when the signer intends to sign, consents to electronic records, can be identified, and the record remains reproducible. The ESIGN Act, 15 U.S.C. §§7001–7031, and applicable state UETA law provide the framework; wills, court orders, and specified family-law documents remain excluded.

Why teams look for DocuSign alternatives

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

Troubleshooting Excess Flood Application workflows

These answers address field detection, signer verification, plan limits, regulated data, legal validity, and advanced application logic.

signNow’s Business plan includes templates, mobile apps, audit trails, and legally binding eSignatures at $8 per user per month when billed annually. Review the detected fields, add missing ones manually, and confirm the final PDF before sending.

Use signNow authentication controls, including available SMS or stronger signer verification, and retain the audit trail. For consumer-facing records, the ESIGN Act requires disclosure of paper-record rights, electronic access, and consent withdrawal procedures.

Business Premium is $15 per user per month billed annually and includes bulk send. Business is $8 per user per month annually but does not include the stated bulk-send feature, so choose the plan based on application volume.

signNow states that HIPAA compliance requires a BAA. If the Excess Flood Application contains protected health information, execute the required BAA and apply access controls before sending it.

Electronic signatures are generally recognized under ESIGN and applicable UETA law when intent, consent, attribution, and record reproducibility are established. Wills, court orders, and specified family-law documents remain excluded.

The Enterprise plan is listed at $30 per user per month billed annually and adds advanced signer authentication, formula fields, and conditional fields. Confirm that those fields are needed before selecting it.

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.