Before Closing: What Must Be Decided
A handful of decisions have to be made before the close, because afterward the options narrow. First, whether the acquired company's policies continue, are cancelled, or are allowed to run to expiration. Occurrence based policies, general liability, property, workers compensation, and auto, can usually be cancelled at close with the platform program picking up coverage prospectively, because the occurrence policy continues to respond to occurrences during its term. Claims made policies cannot be handled the same way, which leads to the second decision. Second, the tail. Directors and officers, employment practices, professional liability, cyber, and representations and warranties related coverages are claims made. If the acquired company's policies are cancelled, claims reported after cancellation for pre closing conduct are uncovered unless a run off or tail policy is purchased. The purchase agreement should address who pays for it and the tail should be bound at or before closing, because the window for purchasing it is limited. Third, whether the acquired entity is added to the platform program mid term or at the next renewal, which is a cost and administrative question. Mid term addition is usually cleaner for coverage and generates a pro rata premium. Waiting until renewal can work where the acquired policies are sound and run beyond the renewal date. Fourth, immediate gaps. Several things need to be in place on day one: auto coverage if vehicles transfer, workers compensation in every state where employees work, and any coverage a customer contract or lease requires in the new entity's name.
- Occurrence policies can generally be cancelled at close with prospective pickup
- Claims made policies need a tail, bound at or before closing, with the payer settled in the agreement
- Decide whether to add the entity mid term or at renewal, as a cost and administration question
- Confirm day one auto, workers compensation by state, and any contractually required coverage
The First Thirty Days: Information Gathering
The integration cannot be done without the facts, and gathering them systematically is most of the work. The standard request list: all policies in force with full policy documents, not just certificates; five years of loss runs on every line; the workers compensation experience modification worksheets and payroll by state and classification; a schedule of locations with values, lease insurance obligations, and occupancy details; a vehicle schedule with values and drivers; employee counts by state; a list of every contract containing insurance requirements, including customer agreements, leases, loan documents, and vendor agreements; any open claims with current reserves; a list of incidents reported but not claimed; any regulatory or licensing matters in progress; and the certificate holder list. The two items most often missing are the contract insurance requirements and the certificate holder list, and they are the two that cause the most immediate operational problems. A customer with a certificate tracking service will notice an expired certificate within weeks, and resolving it requires knowing who the certificate holders are. The loss runs matter for a different reason: they inform what the combined program should look like. An add on with poor workers compensation experience in a high hazard classification changes the platform program's economics, and the right response may be structural, a deductible program or a different retention, rather than simply absorbing it into the existing policy.
- Request full policies, five years of loss runs, experience modification worksheets, and payroll by state and class
- Collect location, vehicle, and employee schedules plus all contracts with insurance requirements
- The certificate holder list and contract requirements are most often missing and cause the fastest problems
- Loss runs should inform program structure, not just premium
Days Thirty to Ninety: Building the Combined Program
With the information in hand, the integration work is mostly consolidation and cleanup. Named insured schedules come first. Every legal entity in the structure needs to appear on every applicable policy: the platform, intermediate holding companies, the acquired entity, and any subsidiaries. Entities omitted from the schedule may have no coverage, and this is the single most common integration error. It is also the easiest to fix if someone maintains a current org chart and compares it to the policies at each addition. Then the coverage mapping. For each line, determine whether the acquired operation is within the platform policy's scope: are its operations described, are its locations scheduled, are its vehicles listed, are its professional services within the definition, does its product line fall within the products coverage. An add on that performs an activity the platform has never performed is the case that most often needs an endorsement or a separate policy rather than simple addition. Workers compensation requires state by state attention, because employees working in a state not on the policy may be uncovered, and monopolistic state fund jurisdictions require separate arrangements. Certificates and compliance follow. Reissue certificates to every certificate holder in the correct entity name, confirm lease and loan compliance, and confirm customer contract compliance. Where a contract requires a limit the platform program exceeds, that is fine. Where it requires an endorsement the platform program does not carry, that is a finding to resolve. Finally, claims. Open claims from the acquired entity continue under the policies that were in force, which means someone needs to manage a relationship with a carrier that no longer writes the business. Assigning that explicitly prevents claims from drifting.
- Add every legal entity to every applicable policy, which is the most common integration error
- Map each line against the acquired operation's actual activities, locations, vehicles, and services
- Handle workers compensation state by state, including monopolistic fund jurisdictions
- Assign responsibility for open claims under the acquired entity's prior policies
Making It Repeatable
The value in this is not in doing it well once. It is in doing it the same way every time, which turns a recurring scramble into a short checklist. A workable playbook has four components. A standard diligence request list, sent at the same point in every deal, so the information arrives before closing rather than after. A standard pre closing decision memo covering the tail, the cancellation approach, mid term versus renewal addition, and day one requirements, with the answers documented. A standard hundred day checklist assigning each task to a named role, at the sponsor, at the platform, and at the broker. And a maintained master document: the org chart, the named insured schedule across all policies, the contract requirement matrix, and the certificate holder list, updated at each add on rather than rebuilt each time. Two additional practices separate sponsors who do this well. First, involving the broker at the letter of intent stage rather than at closing, which costs nothing and changes what is possible, particularly on the tail and on identifying coverage the acquired company lacks entirely. Second, tracking the integration as part of the hundred day plan with the same visibility as the finance and systems workstreams, because insurance integration fails quietly and the failures surface later. For sponsors running a genuine buy and build strategy, there is also a program level question worth revisiting periodically: at what point does the platform's combined scale justify a different structure, a larger deductible program, a captive, or a differently layered tower. That analysis is worth refreshing annually as the platform grows rather than carrying the structure that fit the original acquisition.
- Standardize the diligence request, the pre closing decision memo, and the hundred day checklist
- Maintain a master org chart, named insured schedule, contract matrix, and certificate holder list
- Involve the broker at letter of intent rather than at closing
- Revisit program structure annually as platform scale changes what is efficient
Frequently Asked Questions
Related Resources
This article is for general information and is not a substitute for policy language or professional advice.