Cross liability and severability of interest are two insurance protections that usually come from the same place: a single clause, called Separation of Insureds, in a standard Commercial General Liability policy. Severability means the policy treats each insured as if they held their own separate policy, so one insured’s bad conduct does not cost the others their coverage. Cross liability means the policy can respond when one insured on the policy sues another insured on the same policy. Both are built into the standard CGL form, and both can be quietly stripped out by other policies in the coverage tower or by a few words inside an exclusion.
What the Separation of Insureds Clause Actually Does
The standard ISO CGL form (CG 00 01) contains a provision stating that the insurance applies “as if each Named Insured were the only Named Insured” and “separately to each insured against whom claim is made or ‘suit’ is brought.”1IA Magazine. Intentional Employee Damage: Does the Separation of Insureds Clause Apply? That one sentence delivers both protections.
The severability half means that if one insured breaches a condition, commits fraud, or misrepresents something on the application, the insurer can hold it against that insured only. The innocent co-insured keeps full coverage. An exclusion triggered by one insured’s conduct applies to that insured, not to everyone on the policy.1IA Magazine. Intentional Employee Damage: Does the Separation of Insureds Clause Apply?
The cross-liability half means that when one insured brings a claim against another insured on the same policy, the claimant is treated as a third party for that claim. The policy defends the insured who caused the harm and pays damages to the insured who suffered the loss.
Cross Liability in a Standard CGL
A common misconception is that cross-liability coverage requires a special endorsement. In a standard CGL, it does not. The Separation of Insureds clause already provides it, and the standard form contains no insured-vs-insured exclusion barring claims between co-insureds.2International Risk Management Institute. Cross-Liability Coverage
Consider a construction joint venture where Company A and Company B share a CGL. Company A’s crane operator drops a load onto Company B’s equipment, causing $500,000 in property damage. Company B files a liability claim against Company A. Under the Separation of Insureds clause, the policy treats it like any other third-party claim: it defends Company A and pays Company B’s damages up to the policy limits. No endorsement was needed.
Asking the insurer to add a “cross-liability endorsement” to a standard CGL can actually backfire. Some insurers respond by attaching a cross-liability exclusion endorsement instead, removing the coverage the standard form already supplies. The safer move is to confirm the Separation of Insureds clause is still intact in the policy as issued.
Where Cross-Liability Coverage Disappears
The real exposure sits above and alongside the CGL. Umbrella liability policies, professional liability and E&O policies, and directors and officers coverage often include insured-vs-insured exclusions that specifically bar claims between co-insureds. These are standard features of those forms, not unusual add-ons.
An umbrella sitting on top of a CGL can introduce an insured-vs-insured exclusion that effectively overrides the protection built into the underlying policy. If a cross-liability claim exceeds the primary CGL limits, the umbrella will not pick up the excess, and the business is left with a gap at exactly the layer where large losses live.
Professional liability presents the same problem. A partnership carrying a professional liability policy may find that if one partner’s malpractice injures the firm or another partner, the policy will not respond without an endorsement removing or modifying the exclusion, and not every insurer will agree to grant one.
The Cross-Party Exclusion in Construction
Construction contracts routinely require subcontractors to name the general contractor as an additional insured on the sub’s CGL. The Separation of Insureds clause should let the GC, as an additional insured, bring a claim against the named insured sub on that same policy. But some insurers attach a “cross-party exclusion” that bars any insured from suing another insured under the policy. The additional insured status becomes essentially useless. The insurer still collects the premium, and the policy will not respond to the exact scenario the contract was designed to cover. Contracts should prohibit cross-party exclusions by name, but the only reliable confirmation is reading the policy itself, not relying on a certificate of insurance.
“Any Insured” Versus “The Insured”
Most coverage disputes under a shared policy come down to two words inside an exclusion. When an exclusion uses the phrase “the insured,” the Separation of Insureds clause works as expected: the exclusion bars coverage only for the specific insured whose conduct triggered it, and other insureds keep their coverage.
When an exclusion uses “any insured,” the result flips. The majority of courts hold that “any insured” language overrides the Separation of Insureds clause entirely. If any one insured triggers the exclusion, coverage disappears for every insured on the policy. The severability clause does not rescue the innocent co-insured.
In Phoenix Baystate Construction v. First Financial Insurance Company, the court drew the line clearly. For exclusions using “any insured,” severability clauses have no effect. For exclusions using “the insured,” the severability clause makes clear that “the insured” refers only to the insured actually seeking coverage. When a policy uses both phrases in different exclusions, courts presume the difference is deliberate.
The employer’s liability exclusion in many CGL policies uses “any insured” language. If an employee of the named insured is injured and an additional insured (such as a general contractor) seeks coverage under the same policy for a claim arising from that injury, the “any insured” language may bar coverage for the additional insured too. A minority of courts take the opposite view, but relying on the minority rule is not risk management.
Cross-Liability Claims and the Shared Aggregate
Even when the policy clearly covers a cross-liability claim, the payment comes out of the same aggregate limit that covers every other claim under the policy. The Separation of Insureds clause does not create a separate limit for each insured. It only separates how the policy’s terms apply to each one. Every dollar paid on an internal claim reduces the aggregate available for later third-party claims against anyone on the policy.
In a joint venture sharing a $2 million aggregate CGL, if Insured A’s negligence causes $800,000 in covered damages to Insured B, only $1.2 million remains for every other claim against either party for the rest of the policy period. An insured counting on the full $2 million for outside claims could end up seriously underinsured.
This is why some joint ventures and large projects buy separate policies rather than sharing one. Where a shared policy is the only practical option, higher aggregate limits or an aggregate-per-project endorsement can offset some of the risk.
What to Check in Your Policy
A certificate of insurance confirms coverage exists. It says nothing about whether cross-liability exclusions have been added or whether key exclusions use “any insured” language. The policy itself, with every endorsement, is the only reliable source. When reviewing it:
- Confirm the Separation of Insureds clause is present and unmodified in the conditions section. Standard CGLs include it; manuscript policies and heavily endorsed forms may not.
- Search every endorsement for cross-party or insured-vs-insured language. If an exclusion is attached, you need it removed or modified before the policy will respond to internal claims.
- Read each exclusion for “any insured” versus “the insured.” An “any insured” exclusion will likely override the severability protection in most jurisdictions, leaving innocent co-insureds without coverage.
- Check the umbrella and excess layers for their own insured-vs-insured exclusions. Cross-liability coverage in the primary CGL is worth little if the umbrella drops out above primary limits.
- Account for shared aggregate limits. Cross-liability claims erode the same aggregate that covers outside claims, so the limit has to be large enough to absorb both.
Direct endorsement requests at the umbrella and specialty policies, where insured-vs-insured exclusions are the default, rather than at the CGL where the protection already exists.