Concurrency
Written by Justin Goodman, CIC, CISC, CLCS, CEO and Co-Founder, Total CSR
Published: August 31, 2026 · Last reviewed: August 31, 2026
In plain language: Concurrency means every policy covering the same risk agrees with each other. The dates match, the definitions match, and the exclusions line up. Without it, a client can pay premium on multiple policies and still find nothing pays a claim.
Technical definition: Concurrency describes alignment of effective dates, policy periods, named insureds, coverage triggers, definitions, and exclusions across primary, excess, umbrella, or multi-line policies insuring one risk. Non-concurrent policies create coverage gaps, conflicting other-insurance clauses, or disputes over which carrier responds first.
Concurrency at a Glance
| Attribute | Detail |
|---|---|
| Also known as | Policy concurrency, coverage concurrency |
| Category | Coverage placement and program structure concept |
| Lines of business | Commercial General Liability, Commercial Property, Excess/Umbrella, Commercial Auto |
| Industries most affected | Construction, real estate, manufacturing, transportation |
| Who bears the risk | The insured, when concurrency fails and a claim falls into a gap |
| Common solution | Follow form excess or umbrella language, synchronized renewal dates, coordinated audits |
| Also interacts with | Other insurance clauses, layered towers, additional insured endorsements |
Key Takeaways
- Concurrency means the terms, dates, and definitions across all policies covering one risk match closely enough that a claim triggers consistent coverage everywhere it should.
- Concurrency matters in daily agency work because most accounts carry more than one policy, and a mismatch between a primary and an umbrella can leave a client exposed even though every premium was paid on time.
- The most common misunderstanding is assuming an umbrella automatically fills every gap left by an underlying policy, when many umbrellas only drop down for specific, listed underlying coverages.
- A quick win is running a side-by-side comparison of effective dates, named insureds, and key definitions across all layers at every renewal, not just at initial placement.
What Is Concurrency in Insurance?
Concurrency is the practice of aligning the terms of two or more policies that respond to the same risk so they work together instead of against each other. It exists because commercial insurance programs rarely sit on a single policy. A contractor might carry a primary CGL, an excess liability policy, and an umbrella, each written by a different carrier, each with its own definitions of "occurrence," "insured," and "property damage." When those definitions diverge, a claim can fall through the seam.
The legal doctrine behind concurrency traces to how courts read "other insurance" clauses and follow form language. When two policies both claim to be excess over the other, or both exclude coverage the other assumed would apply, courts must interpret ambiguous contract language, often against the drafting insurer, but the insured still absorbs the delay, defense cost, and uncertainty while that dispute plays out.
Consider a property owner with a primary general liability policy carrying a $1 million per-occurrence limit and a separate umbrella with a $5 million limit. The primary policy excludes injuries to independent contractors performing work on the premises, but the umbrella's own definitions section does not include that same exclusion. A subcontractor is hurt on site. The primary denies. The umbrella, drafted as "follow form," inherits the primary's exclusions by design, and the client discovers the $5 million limit never engages because the underlying gap flows straight up the tower.
How Does Concurrency Work?
- The placement. An agency binds multiple policies for one client, often across different carriers for primary, excess, and umbrella layers.
- The comparison. A producer or account manager reviews each policy's effective dates, named insured schedule, definitions, and exclusions to confirm they align.
- The gap identification. Differences surface, such as a primary excluding a class of claimant that the excess policy does not exclude, or mismatched policy periods that leave a 30-day window uncovered at renewal.
- The correction. The agency requests endorsements, adjusts effective dates, or moves the account to carriers offering true follow form excess to close the gap before a loss occurs.
- The claim test. A covered loss occurs, and concurrent terms allow the claim to move cleanly from primary to excess to umbrella without a coverage dispute at any seam.
Real Claim Examples Involving Concurrency
Mismatched renewal dates on a construction tower
A general contractor's primary CGL renewed on March 1, but the umbrella policy above it renewed on April 1 due to a delayed submission the prior year. A serious injury claim occurred on March 15, inside the gap where the old umbrella had already expired based on its original term and the new umbrella had not yet bound. The contractor's excess layer never engaged, and the primary limit alone had to absorb a claim that exceeded it by several hundred thousand dollars.
Independent contractor exclusion left off the umbrella
A property management company's primary GL policy excluded bodily injury to independent contractors, but the umbrella policy the agency placed with a separate carrier used broader definitions with no matching exclusion. When a maintenance subcontractor was injured, the primary denied as expected, but the umbrella carrier argued the loss should have been excluded under the intent of the program and delayed payment for months while attorneys negotiated a settlement, illustrating how non-concurrent exclusions create real defense cost even when coverage ultimately responds.
Auto fleet added mid-term without matching umbrella schedule
A trucking company added five new tractors to its commercial auto policy mid-term, but the agency failed to confirm the umbrella's schedule of covered autos was updated to match. One of the new units was involved in a serious accident before the umbrella endorsement was issued. The umbrella carrier initially denied drop-down coverage because the vehicle was not yet a scheduled auto under that policy, and the client faced exposure above the auto policy's limit until the agency demonstrated the omission was a processing delay rather than an intentional exclusion.
Concurrency vs. Follow Form Coverage: What Is the Difference?
Concurrency describes the goal or condition of aligned policy terms across a program, while follow form coverage describes a specific drafting mechanism excess and umbrella policies use to achieve that alignment automatically. A program can have follow form language and still fail concurrency if the underlying policy itself changes mid-term without the excess layer updating to match.
| Comparison area | Concurrency | Follow Form Coverage |
|---|---|---|
| Primary use case | Describing whether a multi-policy program's terms actually match | Drafting technique making an excess or umbrella adopt the underlying policy's terms |
| Coverage / concept type | Structural condition of a program | Contractual mechanism within a single policy |
| Typical exclusions | Not applicable, it is a condition, not a coverage | Follow form policies still layer their own manuscript exclusions on top |
| Who is most affected by errors | Insured, at claim time when limits fail to respond | Excess carrier, when forced to defend against unintended broader coverage |
| Common mistakes | Assuming all policies in a tower automatically match without checking | Assuming "follow form" means identical in every respect, ignoring the excess policy's own added exclusions |
What Are the Most Common Mistakes With Concurrency?
- Assuming an umbrella automatically drops down for every underlying exposure, when most umbrellas only schedule specific underlying policies and exclude everything else, creating an E&O exposure if a claim falls outside that schedule.
- Failing to compare definitions of "insured," "occurrence," and "property damage" across layers, allowing a term that is broad in one policy and narrow in another to strand a claim between layers.
- Letting renewal dates drift out of sync across a program, which opens short gap windows that are easy to miss during a busy renewal season.
- Adding a location, vehicle, or entity to one policy mid-term without confirming the excess or umbrella schedule was updated to match, leaving new exposures unprotected above the primary limit.
- Treating concurrency as a one-time check at initial placement rather than a recurring review at every renewal and every material mid-term change.
- Overlooking that different carriers use different proprietary endorsement language even when limits and premiums look comparable, which can hide a substantive coverage gap behind similar-sounding forms.
How to Explain Concurrency to a Client
Explaining Concurrency to a personal lines client
Concurrency matters even in a homeowners and umbrella combination, so it helps to say: "Your umbrella policy is built to sit on top of your home and auto policies, but only if the limits and coverages underneath match what the umbrella expects. We check that every year so there's no surprise gap if you ever have a big claim."
Explaining Concurrency to a small business owner
For a business owner juggling several policies, try: "You've got a general liability policy, an excess policy, and an umbrella, and each one was written by a different insurance company. Our job is to make sure those three policies actually talk to each other, so if you have a large claim, it moves smoothly from one to the next instead of getting stuck in a gap none of them planned for."
Explaining Concurrency to a CFO or risk manager
For a risk manager focused on program structure, use: "We run a concurrency review across your entire tower at every renewal, comparing effective dates, named insured schedules, and key definitions line by line. The goal is zero seams in the program, because a limit on paper only matters if it actually engages when a claim exceeds the layer below it."
Frequently Asked Questions About Concurrency
What causes a lack of concurrency between policies?
A lack of concurrency usually comes from placing different layers of a program with different carriers who each use their own proprietary definitions, exclusions, and effective dates. Mid-term changes like adding a location, vehicle, or subsidiary without updating every layer of the program is another common cause. Renewal timing drift, where one policy renews on a different date than the layer above it, also creates gaps.
Does an umbrella policy always fix a concurrency gap?
An umbrella policy does not always fix a concurrency gap because most umbrellas only drop down for underlying coverages specifically scheduled in the policy. If an exposure exists in the primary policy but was never added to the umbrella's schedule, the umbrella will not respond to that exposure even though the client believes they have five or ten million dollars of protection.
How often should an agency check for concurrency?
An agency should check for concurrency at every renewal and after every material mid-term change, such as adding a new location, vehicle, subsidiary, or line of business. Total CSR's training work with agency teams shows that concurrency reviews get skipped most often during account rewrites, when a producer moves a client to new carriers and assumes the new tower mirrors the old one without verifying definitions and schedules side by side.
Can concurrency issues arise between a primary and excess policy from the same carrier?
Concurrency issues can still arise between a primary and excess policy from the same carrier, though it is less common. Different policy periods, different endorsement forms attached at different times, or an underwriter adding an exclusion to only one layer during renewal negotiations can all create a mismatch even within a single carrier relationship.
Is concurrency the insured's responsibility or the agency's responsibility?
Concurrency review sits squarely with the agency as part of proper account handling and stewardship, since the client typically has no way to compare proprietary policy language across carriers. An agency that fails to catch a concurrency gap and a claim falls into that gap faces real errors and omissions exposure, which is why documented concurrency checks at renewal are a defensible best practice.
What is the difference between concurrency and a coverage gap?
A coverage gap is the actual hole where no policy responds to a loss, while concurrency is the condition that, when absent, tends to create those gaps. Two policies can be non-concurrent in minor ways without ever producing an actual gap, but non-concurrency is the underlying risk factor that eventually produces a real, uncovered claim.
Related Insurance Terms
- Follow Form Coverage: A drafting approach where an excess or umbrella policy adopts the definitions and exclusions of the underlying primary policy, intended to preserve concurrency automatically across a program.
- Other Insurance Clause: Contract language determining how a policy responds when another policy also covers the same loss, often the source of disputes when two non-concurrent policies both claim to be excess.
- Layered Program: An insurance structure using multiple policies stacked by limit, such as primary, first excess, and umbrella, where concurrency across every layer determines whether the full tower actually functions as intended.
- Gap in Coverage: A period or exposure where no policy responds to a loss, frequently the direct result of non-concurrent effective dates or mismatched definitions between layers.
- Umbrella Policy: A high-limit policy sitting above scheduled underlying policies, providing additional limits and sometimes broader coverage, but only for exposures and underlying policies actually scheduled and kept concurrent with the primary layer.
- Named Insured: The person or entity specifically identified on a policy as covered, and a common source of non-concurrency when one layer's named insured schedule fails to match another's after a business acquisition or entity change.
Sources and References
- International Risk Management Institute (IRMI). Other Insurance Clauses.
About the Author
Justin Goodman, CIC, CCIP, CISC, CLCS, CRIS, PCIA, QCLS, MFHR CEO and Co-Founder, Total CSR, Inc.
Justin Goodman is a third-generation insurance broker with over two decades in agency operations. He has trained more than 100,000 CSRs, account managers, and producers in commercial and personal lines coverage, from workers' compensation to construction risk. He was named 2024 Insurance Journal Agent of the Year and one of the nation's top five construction insurance experts by Risk & Insurance. He is the author of Retain, which applies cognitive science research on memory and knowledge transfer to insurance training, and speaks nationally on how agencies build durable technical expertise in their teams.