Miscellaneous Run Off BOR
What the Miscellaneous Run Off BOR Is and when it's used
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.
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.
Step-by-step: Completing a Miscellaneous Run Off BOR
-
01Identify parties: Enter insured, outgoing broker, incoming broker details
-
02List policies: Record each affected policy or claim number
-
03Define scope: State whether authority covers claims, servicing, commissions
-
04Sign and date: All authorized parties sign and date the BOR
How to configure an online BOR workflow
| 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
-
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
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
Draft BOR
Prepare BOR with policy identifiers and scope
Signatures Obtained
Collect signatures from all authorized parties
Carrier Submission
Submit BOR to carrier or TPA for acceptance
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
Real examples of BOR usage in run-off scenarios
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
| 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
-
Is an e-signed BOR legally binding?
Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met.
-
Do carriers require notarization or witnesses?
Carrier and state rules vary. Some carriers accept e-signed BORs; others may request notarization or additional verification. Confirm carrier policy before relying solely on electronic execution.
-
How do I correct an error after signing?
Prepare an amendment or a corrected BOR signed by all original parties. Avoid handwritten corrections on the executed original; obtain a new executed document to prevent disputes.
-
Can RON be used for BOR signatures?
Remote online notarization is acceptable where state law permits and where the carrier accepts it. RON requires identity proofing and recording retention per state notary rules.
-
What evidence should be retained?
Retain the signed document, audit trail (timestamps, IP, authentication method), and any attachments or license verifications required by the carrier or regulator.
-
Who should review high-value transfers?
Have legal counsel or compliance review large run-off portfolio transfers or complex commission arrangements to confirm governing law, dispute resolution, and regulatory implications.