One Consultant’s Advice Cost Three Clients $1,500,000. Her Policy Only Covered $1,000,000 of It, Combined.

8 min read · Last updated August 26, 2026

In this article

• What Makes Claims “Related” Under a Professional Liability Policy
• One Retention, One Limit: The Math Behind Aggregation
• The Deemed-Date-of-Claim Clock
• How to Read Your Own Policy Before the Third Complaint Arrives
• Frequently asked questions

Three related lawsuits, one shared $1,000,000 policy limit, and a $500,000 gap nobody had budgeted for: that’s what one flawed compliance worksheet cost independent human resources (HR) consultant Yasmin Rahal, once her insurer decided all three claims were really one. She had built the worksheet once and reused it for three retail clients, and in the space of fourteen months, each client was sued by an employee over the same assistant-manager job classification. Each lawsuit had its own attorney and its own settlement number. Yasmin’s professional liability insurer looked at all three and made one decision that surprised her: it treated them as a single claim.

Her policy carried a $1,000,000 per-claim and aggregate limit with a $10,000 retention, the amount she’d pay out of pocket before coverage kicked in. She assumed that meant $1,000,000 of protection for each lawsuit. It didn’t.

What Makes Claims “Related” Under a Professional Liability Policy

Standard professional liability and errors and omissions policies contain a “related claims” or “interrelated wrongful acts” provision. The International Risk Management Institute (IRMI), a widely used insurance reference publisher, describes the mechanic this way: “If more than one claim results from a single wrongful act, and if claims are made during more than one policy period, the insured is entitled to the limit applicable when the first claim was made.” IRMI notes this language has largely replaced the older term “noncumulation of limits provision” and is sometimes called the interrelated claims provision.

The policy language itself is typically broader than “the same mistake, twice.” A specimen professional liability policy quoted in a legal case alert from the law firm Wiley Rein defines it this way: claims are considered related when they arise from “any fact, circumstance, situation, transaction or series of related facts, circumstances, situations, events or transactions.” That single sentence is why three separate lawsuits, filed by three separate clients, with three separate attorneys, can still collapse into one claim under Yasmin’s policy. All three traced back to the same flawed worksheet.

The same provision states plainly what happens once claims are ruled related: “Claims based upon or arising out of the same Wrongful Act or Interrelated Wrongful Acts… shall be considered a single Claim, and only one Retention and Limit of Liability shall be applicable.” One retention. One limit. Not one of each per client.

One Retention, One Limit: The Math Behind Aggregation

The retention side of aggregation actually helps a professional in Yasmin’s position. She paid her $10,000 retention once, not three times, because all three claims counted as one. Without the related-claims provision, three separate $10,000 retentions would have cost her $30,000 out of pocket before any coverage responded at all.

The limit side of aggregation is where the trouble starts. Client A’s wage claim settled for $400,000. Client B’s settled for $500,000. Client C’s claim, filed last, sought $600,000. Because all three were related, they drew against the same $1,000,000 ceiling.

Claim	Amount	Limit remaining before	Limit remaining after
Claim 1 (Client A)	$400,000	$1,000,000	$600,000
Claim 2 (Client B)	$500,000	$600,000	$100,000
Claim 3 (Client C)	$600,000 sought	$100,000	$0
Retention applied	$10,000 total, once across all three claims	Not $10,000 per claim

Claims one and two used $900,000 of the $1,000,000 limit between them. That left $100,000 for a third claim seeking $600,000, a $500,000 gap the policy never pays. That gap becomes Yasmin’s personal exposure, or her client’s, depending on how the settlement is structured, unless a separate source of funds covers it.

The Deemed-Date-of-Claim Clock

Aggregation gets sharper when the claims land in different policy years. Insurers pair the related-claims provision with a “deemed date of claim” clause. The same specimen policy language states it directly: “Each such single claim shall be deemed to be first made on the date the earliest of such Claims was first made, regardless of whether such date is before or during the Policy Period.”

In plain terms: if Client C’s lawsuit had arrived a year later, after Yasmin renewed her policy with a fresh $1,000,000 limit, the deemed-date clause would still bind it to the earlier policy period, the one Clients A and B already drew down to $100,000. A later claim does not get a later policy’s fresh limit just because it happened to be filed later.

This provision has already been tested in federal court. In WFS Financial Inc. v. Progressive Casualty Insurance Co. (C.D. Cal. Mar. 30, 2005), a national auto lender was sued in one policy year over alleged discriminatory interest-rate markups, exhausting that policy’s limit. A second, related lawsuit alleging the same underlying practice under California law was filed in the next policy period. The same specimen policy language quoted above was central to the ruling: because the two lawsuits were interrelated, the court held the second suit was bound to the first, already-exhausted policy, rejecting the policyholder’s argument that a claim filed after a policy expires can never relate back to it. Court docket records confirm the case (5:04-cv-00976, Central District of California) was filed in August 2004, with the court’s order issued March 30, 2005 and the case formally closed about six weeks later, on May 13, 2005.

How to Read Your Own Policy Before the Third Complaint Arrives

Two policy sections decide how much exposure a professional carries once a second related claim shows up: the definition of “related claims” or “interrelated wrongful acts,” and the deemed-date-of-claim clause. Both are usually a few sentences buried in the definitions section, not the coverage grant itself, which is exactly why they go unread until a second lawsuit lands.

The National Association of Insurance Commissioners (NAIC) defines “aggregate” in its consumer glossary as “the maximum dollar amount or total amount of coverage payable for a single loss, or multiple losses, during a policy period, or on a single project.” That single word, aggregate, sitting next to the per-claim limit on a declarations page, is the tell. If a policy states an aggregate limit alongside its per-claim limit, related claims are sharing one bucket, not one bucket each.

A higher per-claim limit does not fix a related-claims exposure the way it looks like it should, because the aggregate ceiling still applies across every related claim regardless of the per-claim number. Reviewing whether an existing pool of clients received the same advice, template, or recommendation, before a second complaint arrives, is the only way to size the real exposure while there is still time to raise the aggregate limit or separate a genuinely unrelated dispute from a related one.

Professional liability renewals also don’t come with the same published rate signal other commercial lines get. The Council of Insurance Agents & Brokers’ (CIAB) Q2 2026 market survey, reported by Insurance Journal, names employment practices liability and D&O among the ten lines with falling premiums that quarter, but gives no published percentage for either, and doesn’t name professional liability or errors and omissions at all. A business owner comparing renewal pricing on this coverage doesn’t have an index number to point to the way they would for general liability or commercial property, which makes reviewing your own related-claims exposure directly, rather than benchmarking against a market trend, the more useful exercise.

Reviewing coverage internally is worth doing before you need it. Compare professional liability policy options built for exactly this kind of aggregation exposure to see how per-claim and aggregate limits are structured on current market terms.

Related mechanics worth reading before your own renewal: how a contract’s own warranty language can void the policy entirely, how defense costs erode the same limit that pays a settlement, how a claims-made policy’s reporting window closes after cancellation, and how contractors use a per-project aggregate endorsement to solve the same shared-limit problem on a general liability policy.

Frequently asked questions

Does a higher per-claim limit protect against related-claims aggregation? No. A per-claim limit only matters if a claim stands alone. Once claims are ruled related under the interrelated-wrongful-acts language, they draw against the shared aggregate limit together, regardless of how high the per-claim number is stated on the declarations page.

Can I buy separate policies to avoid aggregation? Sometimes, but it depends entirely on your policy’s own definition of related claims and whether you disclosed the underlying issue accurately at each renewal. A new policy year does not automatically create a fresh limit for a claim the deemed-date clause pulls back to an earlier period.

What counts as an “interrelated wrongful act”? Per the specimen policy language cited above, acts sharing “any fact, circumstance, situation, transaction or series of related facts, circumstances, situations, events or transactions.” Courts have read this broadly, so a single flawed process, template, or piece of advice reused across multiple clients is a common trigger.

Does the related-claims provision ever help the insured? Yes, on the retention side. Multiple related claims typically trigger only one retention total, not one retention per claim, which can meaningfully reduce out-of-pocket costs even as it caps the total limit available.

Should I report a potential future claim before it happens? Ask your broker about reporting a circumstance that could give rise to a claim under your current policy period, before it lapses. Many policies let you report a known issue proactively, which can lock in that policy’s limit for whatever follows, rather than leaving it to a deemed-date determination later.