Establishing secure connection…Loading editor…Preparing document…

Miscellaneous Run Off BOR

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

Miscellaneous Run Off BOR

This Run-Off Business Operations and Records Agreement, hereinafter referred to as the BOR Agreement, is entered into as of Effective Date: by and between Client Name: and Service Provider Name: .

WHEREAS

WHEREAS, Client has certain business operations, accounts receivable, claims, records and/or contractual obligations that require managed wind-down, reconciliation and preservation (the "Run-Off"); and

WHEREAS, Service Provider represents that it has experience and capability to perform loss run-off, account reconciliation, record retention, claims management and related administrative tasks described herein; and

WHEREAS, the parties desire to set forth the terms and conditions under which Service Provider will manage the Run-Off in accordance with the terms of this BOR Agreement.

SCOPE OF WORK

Service Provider shall perform the run-off services described below. The scope includes, without limitation, identification and segregation of Run-Off accounts, reconciliation of outstanding invoices, claim file management, preparation of final accounting reports, preservation of records, communications with counterparties as authorized, and orderly transfer or disposition of assets in accordance with Client instructions and applicable law.

PAYMENT TERMS

Client shall pay Service Provider the fees set forth below in consideration for the performance of the Scope of Work. Fees are inclusive of reasonable costs unless otherwise stated.

Invoices are due within days of invoice receipt. Overdue amounts shall incur a late charge of % per month (or the maximum permitted by law), compounded monthly, plus reasonable collection costs and attorney's fees.

TERM AND TERMINATION

This BOR Agreement commences on Start Date: and continues until End Date: , unless earlier terminated in accordance with this Section.

Either party may terminate this Agreement for convenience upon prior written notice of days to the other party. Either party may terminate for material breach if the breaching party fails to cure within thirty (30) days of written notice of such breach. Termination does not relieve Client of the obligation to pay fees accrued through the effective date of termination and reasonable wind-down costs.

CONFIDENTIALITY

For the purposes of this Agreement, "Confidential Information" means non-public business, financial, technical, contractual and personal information disclosed by either party in connection with the Run-Off. Service Provider shall maintain Confidential Information in strict confidence, shall not use Confidential Information except to perform its obligations under this Agreement, and shall not disclose Confidential Information to any third party except to its employees, agents or subcontractors who have a need to know and are bound by confidentiality obligations at least as protective as those herein. Confidential Information does not include information that is or becomes publicly available through no breach of this Agreement, was already in the receiving party's lawful possession, or is required to be disclosed by law, provided the disclosing party gives prompt notice and cooperates in any lawful effort to limit disclosure. Breach of this confidentiality provision will cause irreparable harm for which monetary damages may be inadequate; the non-breaching party shall be entitled to injunctive relief in addition to any other remedies.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction selected below without regard to its conflicts of law principles.

INDEMNIFICATION

Each party shall indemnify, defend and hold harmless the other party from and against any and all claims, liabilities, losses, damages, costs and expenses (including reasonable attorney's fees) arising out of the indemnifying party's gross negligence or willful misconduct in the performance of its obligations under this Agreement. Indemnification obligations are subject to applicable law and any required limits of liability set forth elsewhere in this Agreement.

NOTICES

All notices required or permitted under this Agreement shall be in writing and delivered to the addresses set forth below by hand delivery, nationally recognized overnight courier, or certified mail, return receipt requested, or by electronic transmission with confirmation of receipt.

MISCELLANEOUS PROVISIONS

Assignment: Neither party may assign its rights or delegate its obligations under this Agreement without the prior written consent of the other party, except that Service Provider may assign or subcontract to affiliates or subcontractors provided Service Provider remains responsible for performance.

Severability: If any provision of this Agreement is held invalid or unenforceable, the remainder of this Agreement shall remain in full force and effect.

ENTIRE AGREEMENT

This Agreement, including any attachments or written scope documents signed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals and understandings, whether written or oral. No amendment of this Agreement shall be effective unless in writing and signed by authorized representatives of both parties.

Client

Printed Name:

By:

Date:

Service Provider

Printed Name:

By:

Date:

Enter text✕

What the Miscellaneous Run Off BOR Is and when it's used

The Miscellaneous Run Off BOR is a Broker of Record (BOR) authorization used in insurance run-off matters to transfer servicing or claim-handling authority from one broker or administrator to another. It documents the insured party, affected policies or claims, the scope of authority being transferred, and the effective date for run-off management. Commonly used by carriers, third-party administrators, and brokers during portfolio transfers, policy cancellations, or when managing legacy liabilities, the BOR creates a written record of intent and delegation for audit and regulatory review.

Why a clear Miscellaneous Run Off BOR matters

A precise BOR creates an auditable record of broker authority and reduces disputes over servicing rights and commissions.

Why a clear Miscellaneous Run Off BOR matters

Who typically completes a Run Off BOR

Parties that prepare or sign a Run Off BOR include insureds, incumbent brokers, successor brokers, carriers, and third-party administrators.

  • Insureds and policyholders authorizing a new broker to act on legacy policies and claims.
  • Outgoing brokers confirming the transfer of authority and commissions for run-off portfolios.
  • Carriers or TPAs updating internal records and vendor lists to reflect the new broker of record.

Each signer should have the authority to make the change and retain a copy for their compliance and audit files.

Typical signatories and their roles

Corporate Risk Manager

A company-level representative authorized to direct insurance servicing changes. This person confirms coverage details, signs the BOR on behalf of the insured entity, and retains the approved document for corporate records and audit.

Broker Principal

A senior broker or agency officer who accepts or relinquishes broker-of-record status. The principal certifies commission arrangements, scope of service, and effective date, and ensures communications with carriers and TPAs.

Essential information the BOR must include

Insured Name: Full legal name
Policy or Claim Number: Policy/claim identifier
Effective Date: MM/DD/YYYY
Outgoing Broker: Name and contact
Incoming Broker: Name and contact
Scope of Authority: Claims, endorsements, cancellations

Step-by-step: Completing a Miscellaneous Run Off BOR

Follow these steps to prepare a clear, enforceable BOR that documents the transfer of run-off authority and reduces processing delays.

  • 01
    Identify parties: Enter insured, outgoing broker, incoming broker details
  • 02
    List policies: Record each affected policy or claim number
  • 03
    Define scope: State whether authority covers claims, servicing, commissions
  • 04
    Sign and date: All authorized parties sign and date the BOR

How to configure an online BOR workflow

Set up a clear digital workflow so each party receives and signs in order, and completed records are stored for audit.

Field Configuration
Signer Order Outgoing broker → Insured → Incoming broker
Authentication Email link plus SMS code for higher assurance
Attachments Include policy excerpts or broker appointment letters
Retention Store signed PDF plus audit trail

Where the completed BOR goes and what happens next

A signed BOR triggers updates across carrier, broker, and administrator systems; routing should be planned in advance to avoid lapses.

  • Carrier Submission: Carrier receives BOR and updates servicing records
  • Broker Records: Outgoing and incoming brokers retain copies
  • TPA Notification: Third-party administrators update claim contacts
  • Audit Trail: Signed PDF and metadata preserved for compliance

Digital signing and platform needs for BOR processing

Choose a platform that supports secure eSignatures, audit trails, and the integrations your carriers require.

  • Authentication: Email + SMS or KBA
  • File formats: PDF, DOCX supported
  • Integrations: Salesforce, NetSuite, Google Workspace

Ensure the platform can produce a tamper-evident signed PDF, retain an auditable history, and meet any HIPAA or state-specific requirements the carrier or insured imposes.

Typical timelines and processing expectations

Allow sufficient time for carrier acceptance, internal approvals, and system updates when deciding BOR effective dates.

Broker internal review:

2–5 business days for verification

Carrier acceptance window:

Varies by carrier; typically 5–15 business days

System updates:

Policy system change may take 7–21 days

Commission adjustments:

May require one billing cycle to reflect changes

Dispute window:

Retain documentation until dispute resolution

Key milestones in a BOR run-off transfer

Track these sequential milestones from drafting through carrier confirmation for a controlled transfer of authority.

01

Draft BOR

Prepare BOR with policy identifiers and scope

02

Signatures Obtained

Collect signatures from all authorized parties

03

Carrier Submission

Submit BOR to carrier or TPA for acceptance

04

Record Update

Carrier updates files and notifies stakeholders

Common mistakes to avoid when preparing a Run Off BOR

  • Omitting exact policy or claim numbers which prevents carriers from locating records and delays processing.
  • Using ambiguous scope language such as 'all matters' without listing exclusions that clarify claims or endorsements.
  • Failing to obtain required broker license references or carrier-specific appointment forms causing rejection.
  • Not preserving the signed audit trail and metadata, making it hard to demonstrate consent or timing in a dispute.

Consequences of an incorrect or incomplete BOR

Delayed Acceptance: Operational risk and service gaps
Commission Disputes: Financial recovery actions possible
Regulatory Exposure: Recordkeeping violations, fines
Incorrect Coverage: Claims misdirected or mishandled
I-9/Payroll Impact: Related HR errors where applicable
Data Privacy Risks: HIPAA or state breach obligations

Real examples of BOR usage in run-off scenarios

These brief case arcs show how organizations used BORs to transfer run-off authority and reduce administrative friction.

Optica Run-Off Transfer

Optica prepared a clean BOR listing 120 legacy policies to transfer servicing to a specialist administrator.

  • The carrier required license verification.
  • The signed BOR and supporting license documents enabled the carrier to update records within 10 business days and avoid gaps in claims handling.

Xerox Integration

Xerox's operations team issued a BOR during consolidation of broker panels to centralize run-off claims management.

  • They included policy excerpts and license numbers.
  • Carrier acceptance proceeded after authentication, and the centralized broker shortened response times while preserving audit trails for compliance review.

eSignature solution comparison relevant to BOR completion

Platform choice affects authentication, audit trails, HIPAA compliance, and per-user cost; the table compares signNow with common alternatives on key dimensions.

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 free trial Yes Yes Yes Yes
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Frequently asked questions and troubleshooting

Answers to common questions about validity, signatures, notarization, and correcting mistakes on a Run Off BOR.


Need help? Contact support

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