A policy escrow addresses something a financial escrow doesn't: operational custody during the transition. It governs six categories — policy-file custody (physical and digital, access rights, copy versus original), management-system record transfer (database migration, a parallel-access period, validation checkpoints, legacy retention), client-service continuity, broker-of-record transfer, carrier-appointment transfer, and commission routing (the measurement dates for pre- and post-close allocation). The term runs 90–180 days post-close, extending to 12 months for complex or large transitions, and it has to cover the management-system migration window, the carrier-appointment transition, the initial renewal cycle for major accounts, and any transition-services period.
§ 01 · The cutover problemDifferent things move at different times.
"Transfer occurs at closing" is too simplistic — and an ambiguous cutover date is the most common policy-escrow mistake. Legal title, the management system, carrier appointments, and client broker-of-record all cut over at different times, so each needs its own milestone. Treating them as a single event guarantees a gap where nobody is clearly responsible for servicing a client or routing a commission.
Seven mistakes recur, and the ambiguous cutover is only the first. The others: treating policy escrow as financial escrow (different purposes entirely); no access protocol for the seller (which either blocks the seller's legitimate obligations or enables piracy); a missing management-system migration plan; a weak carrier-notification process; unaddressed commission overlap (direct-bill commissions received post-close relating to pre-close production); and ignored pending renewals. Each is a place where a transition without an explicit custody plan leaves a service or routing gap that surfaces as a lost client.
§ 02 · The BOR campaign and AMS migrationThe two operational engines.
| Workstream | Benchmark |
|---|---|
| Broker-of-record campaign | 60–120 days post-close; 85–95% response rate on standard commercial |
| Management-system migration | Five steps: mapping, execution, validation, cutover, post-cutover support |
| Personal vs. commercial | Personal lines transfer passively; commercial needs per-client BOR letters |
The broker-of-record campaign runs 60–120 days post-close with an 85–95% response-rate benchmark on standard commercial accounts in a well-managed campaign — and non-responsive accounts are retention risk requiring targeted outreach. The management-system migration runs a five-step process: field-by-field data mapping, migration execution, validation sample-checking, a defined cutover when operational control moves, and post-cutover support that references the seller's system for historical queries. Even a same-system migration isn't free — it still needs an agency-code transfer, user-access reassignment, data filtering if the buyer gets only part of a multi-agency database, and history retention. Personal lines transfer more passively through the agency appointment, while commercial accounts require a broker-of-record letter signed by each client.
§ 03 · The custody provisionsAccess without piracy.
Five custody-provision components structure the operational handoff: pre-transfer custody (the seller retains files until milestones), transfer milestones (management-system migration complete, broker-of-record confirmed), post-transfer custody (the buyer holds, the seller retains defined access), access rights (buyer gets full operational access, seller gets limited access for specific purposes), and access logs for accountability. The seller's legitimate post-close access purposes are specific and bounded — completing commission calculations, responding to pre-close claim inquiries, verifying no piracy under the restrictive covenants, and supporting earnout calculations. The access-log requirement is what keeps that bounded access from becoming a piracy vector: the seller can do what the deal requires, and every access is recorded.
§ 04 · The notification lettersClients and carriers.
Two notification letters complete the transition. The client-communication letter has five elements — an introduction of the buyer, an assurance of service continuity, contact-information changes, a broker-of-record request where applicable, and the timing of service transitions — and a joint signature from seller and buyer often improves client response and retention, because the seller's endorsement carries the relationship the buyer is inheriting. The carrier-notification letter has six elements — the effective date of the appointment transfer, the buyer's licensing, the appointment status, the broker-of-record submission process, commission-routing changes, contingency treatment, and a carrier contact for questions. Together, the custody provisions and the two letters turn the transition from an undefined handoff into a sequenced operational plan — which is the whole point of distinguishing policy escrow from the financial kind.
◆
Terminology on this shelf
- Policy escrow
- The agreement governing operational custody during transition — distinct from a cash-holding financial escrow.
- Cutover date
- The defined moment operational control moves — and the mistake of treating legal title, system, and BOR as one.
- Broker-of-record campaign
- The 60–120 day post-close letter campaign transferring commercial accounts, at an 85–95% response benchmark.
- Management-system migration
- The five-step mapping-to-support process moving the book's records to the buyer's system.
- Custody provisions
- The five components — pre-transfer, milestones, post-transfer, access rights, and access logs.
- Access logs
- The accountability record that lets the seller meet obligations without enabling piracy.