Dual cover — when a PI claim engages more than one policy

Sometimes a single PI claim engages more than one insurance policy: layered programmes, joint ventures, successive insurers, or multiple named-insured firms. This page maps how UK PI policies interact in dual-cover scenarios and how claims are managed.

The five common dual-cover scenarios

1. Layered programme. Primary insurer up to defined attachment; excess insurer above.
2. Joint venture. Multiple named-insured parties on one policy or overlapping policies.
3. Successive insurers. Prior policy (with notification) responds to eventual claim; later policy in force may also engage.
4. Successor practice. Ceased firm's run-off responds to prior acts; successor firm's new policy responds to acts done in successor context.
5. Client-directed cover. Client contractually requires the firm to hold specific cover; firm holds general PI too.

Primary vs excess layer response

1. Primary layer responds first, up to its exhaustion.
2. Excess layer engages when primary is exhausted.
3. Where the claim value sits inside primary, excess is not called.
4. Where multiple related claims aggregate above primary, excess must engage.
5. Wording consistency between layers matters materially — gaps in aggregation, exclusions, notification triggers can leave gaps.

Joint-venture cover response

1. JV named-insured parties typically share a single policy limit.
2. Where the claim is against one party specifically, that party's share of the limit applies.
3. Cross-claims between JV parties may or may not be covered (typically excluded).
4. Aggregation across JV activities different from single-firm aggregation.
5. Wording specifically for JV context is prudent.

Successive insurer scenarios

1. Notified during prior policy. Prior policy deems the eventual claim within its coverage — current policy typically not engaged.
2. Circumstance discovered after prior policy ended, notified to current policy. Current policy may cover; prior policy may cover if the ‘could reasonably have been known’ test is met.
3. Both policies engaged. Rare but possible — typically primary/excess ordering by wording precedence.
4. Neither policy engaged. Coverage-dispute scenario if notification duties failed on both sides.

Successor-practice dual-cover

1. Ceased firm's run-off covers pre-cessation acts.
2. Successor firm's new policy covers post-succession acts.
3. Overlap zone where the client relationship continues into the successor practice.
4. Fair-presentation duty at successor's renewal to disclose acquired-book exposure.
5. Some structures have the successor's PI extending to prior acts, superseding ceded-firm run-off.

Claims-handling in dual-cover scenarios

1. Notify all potentially-engaged insurers.
2. Insurers coordinate defence — sometimes lead-insurer arrangements formalised.
3. Cost allocation across policies according to their contribution.
4. Settlement authority typically vested in the primary insurer with excess consent for material amounts.
5. Wording-specific procedures for reallocation if the picture changes.

Common dual-cover pitfalls

1. Notification to only one insurer. Other policies may deny for late notification.
2. Wording inconsistency. Aggregation, exclusions, notification triggers differ across layers — coverage gaps result.
3. Contribution disputes. Multiple insurers argue over allocation; delay in defence.
4. Settlement without insurer consent. Voids cover with policies whose consent wasn't obtained.
5. Fair-presentation gap. Successive insurers not properly informed of prior-policy notifications.

Frequently asked

Related reading

• PI excess layer programmes
• Project-specific PI cover
• Successor practice PII framework
• PI notification vs claim