Can this be e-signed?

Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when the signature shows intent, consent, attribution, and records are retained. Exceptions may apply for specific categories.

What if I lack authorization?

If you lack a signed authorization or legal right, carriers commonly refuse production. Obtain written consent, a subpoena, or court order as appropriate. Consult counsel before pursuing compulsory process to avoid privacy or liability issues.

Are notarizations needed?

Not typically. Routine BOR Requests rarely require notarization, but specific document types or insurer policies may demand notary or certified copies. Remote online notarization availability varies by state; follow state notary rules and retain recordings when RON is used.

How to handle PHI in requests?

Treat PHI carefully: obtain patient authorization, execute a BAA when a vendor will handle PHI, and use encrypted transmission. HIPAA requires six-year retention for certain records (45 CFR §164.530(j)); consult privacy officers before sharing protected data.

What proof of entitlement is acceptable?

Acceptable proof includes signed authorizations that name records and specify dates, a power of attorney if applicable, court orders, or a carrier-provided certification. Maintain the authorization and a chain-of-custody log to support admissibility and compliance.

How long will production take?

Production timing depends on scope, carrier backlog, and verification needs. Routine requests often resolve within 7–30 business days; expedited delivery may be possible for a fee. Track requests and obtain written confirmation of production dates.

Electronic Signature
Templates
Insurance
Insurance BOR Request

Insurance BOR Request

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

INSURANCE BOR REQUEST

Policyholder / Applicant Information

Applicant Name Insured Name (if different) Mailing Address

Phone

Email

Date of Birth

Policy & Insurer Details

Insurer Name

Policy Number(s)

Policy Effective Date

Broker of Record Appointment

I, the undersigned policyholder, hereby appoint Broker of Record to represent my interests with respect to the policy(ies) identified above. Current Broker of Record: , License/Producer Number: .

I hereby designate New Broker of Record: , Firm: , License/Producer Number: .

New Broker Contact Phone

New Broker Email

Requested BOR Effective Date

Coverage Types (select all that apply)

Auto / Commercial Auto
Property / Commercial Property
General Liability
Workers' Compensation
Umbrella / Excess Liability
Professional Liability / E&O
Life Insurance
Health / Disability
Other:

Policy Financial Details

Coverage Limit / Amount

Deductible

Annual Premium

Policy Period Start

Policy Period End

Exclusions, Limitations & Attachments

This request does not amend, cancel or otherwise modify coverage except as expressly acknowledged in writing by the insurer. Standard policy exclusions remain in effect, including but not limited to intentionally caused loss, nuclear hazard, war and cyber exclusions where applicable. Attach any endorsements or amendments required to effectuate the broker change.

Attachments / Documentation Checklist

Declarations Page(s)
Loss Runs (past 5 years)
Power of Attorney / Authorization
Proof of Identity for Policyholder
Other:

Beneficiary Designation (If Applicable)

If this request affects policies that permit a beneficiary designation, complete the fields below. If not applicable, leave blank.

Primary Beneficiary Name

Relationship

Share (%)

Contingent Beneficiary Name

Additional Instructions / Special Conditions

Authorization, Certifications and Acknowledgments

By signing below, the policyholder certifies that the information provided is true and accurate to the best of their knowledge and authorizes the insurer and its representatives to release and exchange underwriting and claims information with the newly appointed Broker of Record. This appointment supersedes any prior broker appointment for the policies listed herein, effective upon acceptance by the insurer or the requested effective date, whichever occurs later.

The policyholder understands that this request does not create any new coverage, increase the insurer's obligations, or alter policy terms except by written endorsement. The policyholder agrees to hold harmless and indemnify the insurer and any previously appointed broker for actions taken in reliance on this appointment prior to formal acceptance by the insurer.

I authorize the release of all records and information necessary to effectuate this Broker of Record appointment, including but not limited to policy declarations, endorsements, loss history, and billing records. This authorization is valid for the purpose of implementing the broker change and shall remain in effect until revoked in writing.

Acknowledgement

I acknowledge and agree to the authorizations, certifications and conditions set forth in this request.

Applicant Name:

By:

Date:

What an Insurance BOR Request Is

An Insurance BOR Request is a formal written request asking an insurer, broker, or third-party administrator to provide a Binder of Records (BOR) or a business owner’s report that documents policy details, limits, endorsements, claims history, and underwriting notes related to a named policyholder. Typical recipients include carriers and brokers who maintain the policy files. The document serves underwriting, claims review, due diligence, and audit purposes, and can accompany applications, audits, mergers, or litigation. Electronic transmission and eSignature are generally acceptable under ESIGN (15 U.S.C. ch. 96) and UETA where adopted.

Why Request a BOR for Insurance Matters

Use an Insurance BOR Request to obtain verified policy documents and claims records that support underwriting decisions, risk assessments, and regulatory audits. Consolidating records reduces processing time, clarifies coverage scope, and provides an evidentiary record for disputes, audits, or transaction due diligence.

Who Commonly Prepares and Receives BOR Requests

Typical requestors include underwriters, claims examiners, brokers, risk managers, and legal counsel seeking authoritative policy and claims documentation.

Underwriters — verify limits, endorsements, prior claims, and underwriting notes for risk selection.
Claims examiners — obtain prior loss details, reserves, and correspondence to assess coverage and subrogation.
Brokers and risk managers — compile client portfolios, confirm endorsements, and support renewals or audits.

Use formal requests on company letterhead or secure electronic systems to preserve chain of custody and authenticity.

Essential Sections to Include in an Insurance BOR Request

Core sections in an Insurance BOR Request describe the policy, insured parties, claims history, endorsements, underwriting notes, and requested document scope.

Policy Summary

Include insurer name, policy number, effective and expiration dates, coverage lines, limits, deductibles, premium, and policy status. This snapshot helps underwriters confirm which risks were covered during the requested period.

Named Insured

Provide full legal name(s) of insured entities and DBA names, Tax ID or SSN if relevant, primary mailing address, and contact information for record matching and legal identification.

Claims History

List all reported claims within the requested timeframe including date of loss, claim number, paid and reserved amounts, loss descriptions, and claim status. Attach redacted claim files, photos, and adjuster notes where available.

Endorsements

Detail all endorsements and riders affecting coverage, including policy amendments, endorsements dates, and language changes. Clarify whether endorsements were issued retroactively or prospectively relative to reported claims.

Underwriting Notes

Include underwriting files, declarations, inspection reports, risk surveys, and correspondence that explain underwriting decisions, declinations, rating changes, or prior renewal negotiations. Redact privileged legal communications if necessary.

Request Scope

Specify precise date range, exact documents sought (policy jackets, endorsements, claim files, loss runs), preferred delivery format, and any confidentiality restrictions or redaction requirements to streamline production and legal review.

Step-by-Step: Preparing and Submitting a BOR Request

Follow these steps to prepare, request, and receive an Insurance BOR Request securely and with clear authorization.

01

Prepare Request: Assemble policy identifiers, requestor details, and scope.
02

Authorize: Include signed authorization or proof of right to access.
03

Submit Securely: Send via encrypted email, portal, or eSignature platform.
04

Track Response: Log production dates and received documents for audit.

How BOR Requests Are Routed and Delivered

Routing and delivery options affect timing and evidentiary strength of BOR production; choose methods that preserve chain of custody.

Email Request: Simple but requires secure attachments and audit logging.
Secure Portal: Preferred for large files and authenticated downloads.
eSignature Platforms: Provides signed authorization, timestamps, and audit trails.
Certified Mail: Useful for hard-copy originals and chain-of-custody evidence.

Configuring a Digital Workflow for BOR Requests

Configure your digital workflow to capture authorization, select fields, and set delivery and retention policies.

Field	Configuration
Authentication Level	Email-only, SMS code, or KBA options.
Signature Method	Click-to-sign, drawn, or certificate-based for compliance.
Field Types	Signature, initials, date, text fields, conditional logic.
Retention Settings	Auto-archive PDF/A and retain per policy.

Platform Capabilities to Support BOR Requests

Ensure platform supports secure transmission, audit trails, and configurable authentication for BOR Requests in high-volume or regulated workflows.

File Formats: PDF, DOCX, or structured exports.
Integrations: Salesforce, NetSuite, Google Workspace supported.
Authentication: Email, SMS, and stronger methods available.

Common Pitfalls to Avoid

Incomplete identifiers delay production and can trigger additional verification steps; include exact policy numbers, EIN/SSN, DBAs, and full insured names to avoid mismatches.
Vague document scope requests cause overproduction; specify exact date ranges and document types to limit fees and speed retrieval.
Failing to attach signed authorization or proof of entitlement will often result in refusal or delayed release under privacy rules.
Using unsecured email or unencrypted attachments can breach confidentiality obligations and may violate HIPAA or company policies for PHI.

Key Risks and Potential Consequences

Privacy Violations: Civil penalties, reputation harm

Delayed Claims: Increased reserve exposure

Regulatory Fines: HIPAA or state penalties

Contractual Breach: Indemnity and litigation risk

Operational Costs: Search and remediation expenses

Tax Consequences: Backup withholding, penalties

Best Practices to Streamline BOR Requests

Adopt standard templates, clear authorizations, and secure delivery methods to reduce friction and legal risk when requesting BOR materials.

Use a Standard Written Authorization Form

Require a signed written authorization from the insured that specifically names the records to be released, cites the policy number, and includes an expiration date. Clear authorizations prevent unnecessary withholding and support responsive production.

Specify Delivery and Format Requirements

Request PDF/A for long-term retention, name files consistently, ask for separate claim folders, and require encrypted delivery. Stating format preferences upfront reduces conversion work and avoids file compatibility issues during review.

Authenticate Requestors and Maintain Audit Trails

Use identity verification and preserve audit logs showing who requested and received records, with timestamps and IP addresses. Auditable trails are essential for compliance, dispute resolution, and demonstrating chain of custody.

Limit Scope and Use Protective Language

Include confidentiality obligations and restrict use of provided records to specified purposes. If necessary, attach a non-disclosure agreement or stipulate return or destruction timelines to limit exposure and provide remediation steps.

eSignature Pricing and Feature Snapshot for BOR Workflows

Compare common pricing and enterprise features for eSignature vendors relevant to Insurance BOR Request workflows.

	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	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Timing Expectations and Common Deadlines

Timelines depend on carrier processes, request scope, and authentication; plan for variable lead times and possible fees for expedited production.

Standard Response Time:

Allow 7–30 business days for routine requests.

Expedited Requests:

Fees may apply for 3–5 business day turnaround.

Remote Notarization Delivery:

RON session recordings retained per state rules.

Follow-up and Disputes:

Document requests often require written follow-up and escalation.

Record Retention Notice:

Notify recipients if records are subject to hold.

Frequently Asked Questions About Insurance BOR Requests

Frequently asked questions and concise answers about preparing, authenticating, and accepting Insurance BOR Requests, including security, timelines, and legal validity.

Need help? Contact support

Can this be e-signed?
Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when the signature shows intent, consent, attribution, and records are retained. Exceptions may apply for specific categories.
What if I lack authorization?
If you lack a signed authorization or legal right, carriers commonly refuse production. Obtain written consent, a subpoena, or court order as appropriate. Consult counsel before pursuing compulsory process to avoid privacy or liability issues.
Are notarizations needed?
Not typically. Routine BOR Requests rarely require notarization, but specific document types or insurer policies may demand notary or certified copies. Remote online notarization availability varies by state; follow state notary rules and retain recordings when RON is used.
How to handle PHI in requests?
Treat PHI carefully: obtain patient authorization, execute a BAA when a vendor will handle PHI, and use encrypted transmission. HIPAA requires six-year retention for certain records (45 CFR §164.530(j)); consult privacy officers before sharing protected data.
What proof of entitlement is acceptable?
Acceptable proof includes signed authorizations that name records and specify dates, a power of attorney if applicable, court orders, or a carrier-provided certification. Maintain the authorization and a chain-of-custody log to support admissibility and compliance.
How long will production take?
Production timing depends on scope, carrier backlog, and verification needs. Routine requests often resolve within 7–30 business days; expedited delivery may be possible for a fee. Track requests and obtain written confirmation of production dates.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now