The mental model to install first
General Liability covers the insured against money it owes to other people because of bodily injury or property damage the insured caused. Everything else in the form is a refinement of that one sentence.
Read the sentence again carefully. Three things matter. First, GL is third-party coverage, not first-party. The insured is not protecting its own things. It is protecting itself against claims brought by other parties. Second, the trigger is bodily injury or property damage, abbreviated BI/PD throughout the rest of the policy and the rest of your career. Third, the policy pays both indemnity (the dollars owed) and defense (the cost of fighting the claim, even when groundless).
GL is the line that responds when a customer slips on a wet floor, when a contractor's saw kicks back into a homeowner's wall, when a manufactured component fails and damages adjacent equipment, when an apartment tenant alleges mold exposure. It is the workhorse line for almost every commercial buyer. A standalone GL policy is the exception in the middle market and above; more commonly GL is bundled into a package with property, or layered under an umbrella, or written as an excess-only follow-form.
"Sums the insured becomes legally obligated to pay as damages." That phrase, taken from the CGL insuring agreement, is the spine of the policy. The insured's liability has to be legal liability, not moral liability or contractual indemnity that is broader than what tort law would require. This is why so much of GL underwriting comes back to whether a contract pulls the insured into liability they would not otherwise have.
Why GL exists at all
Tort law in the United States lets injured parties recover from negligent actors. Businesses cause incidental injuries to customers, contractors, neighbors, and bystanders all the time. Without insurance, every such incident would either bankrupt the business or leave the injured party uncompensated. GL is the market's solution: a transferable contract under which a carrier accepts the risk of those incidents in exchange for a fixed premium. The insured gets predictability. The injured party gets a deeper pocket. The carrier gets the spread between premium collected and losses paid. This is the model that has held since the 1940s when commercial liability moved from named-peril schedules to comprehensive forms.
The cast of parties
- Named insured. The entity on the declarations page. Usually the buyer.
- Insured. A broader term that includes the named insured, employees acting in scope, executive officers, and various others picked up by the form's "Who Is An Insured" section.
- Additional insured. A third party who has been added by endorsement, usually because a contract required it. We will return to additional insureds in §08.
- Claimant. The person or entity asserting a claim against the insured.
- Plaintiff. A claimant who has filed suit.
The CGL form, anatomized
Every general liability policy in the United States traces back to one document: the ISO Commercial General Liability Coverage Form, currently designated CG 00 01. ISO is the Insurance Services Office, a rating and forms organization owned by Verisk. Carriers can write their own forms, and many do, but most "manuscript" forms are still recognizably variations on CG 00 01. When you see references to "the CGL form" or "the standard form" in any conversation with an underwriter, this is what they mean.
The form has six sections. Memorize the order; underwriters read it in this order, and so should you.
| Section | What it does | Why it matters |
|---|---|---|
| I. Coverages | Insuring agreements for A (BI/PD), B (Personal & Advertising Injury), C (Medical Payments). Plus exclusions for each. | This is the meat. Read the insuring agreement, then read every exclusion before reaching a coverage opinion. |
| II. Who Is An Insured | Defines the natural and legal persons who have rights under the policy. | Disputes about coverage frequently come down to whether someone is even an insured in the first place. |
| III. Limits Of Insurance | Per-occurrence, general aggregate, products/completed operations aggregate, personal/advertising injury, fire damage, medical expense. | The aggregate cap is what makes GL different from auto. We will dig into limits in §06. |
| IV. Conditions | Notice of occurrence, duties when claim made, other insurance, transfer of rights, premium audit, cancellation. | Most coverage disputes that are not about exclusions are about conditions, especially notice and cooperation. |
| V. Definitions | Defines every term that appears in italics or quotes elsewhere in the form. | Read these as terms of art, not English. "Occurrence," "your work," "your product," "personal injury" all mean exactly what is defined here, no more, no less. |
| Endorsements | Form-modifying schedules attached to the policy. | The endorsements are where the policy is actually customized. The base form is identical across most insureds; the endorsements are bespoke. |
When you pick up a GL policy, do not start at page one. Start with the declarations page (which gives you the insured, the limits, the deductible or SIR, the policy period, and the form list), then jump to the schedule of forms and endorsements, then read each endorsement. Only after that do you read the base form. The endorsements are where the action is, and they take primacy over conflicting language in the base form.
Coverage A, B, and C
Coverage A: Bodily Injury and Property Damage Liability
The big one. Coverage A is what people mean when they say "GL." It pays for sums the insured becomes legally obligated to pay as damages because of bodily injury or property damage caused by an "occurrence" that takes place in the coverage territory during the policy period.
Three pieces of that sentence carry weight:
- Bodily injury is defined as bodily injury, sickness, or disease, including death resulting from any of these. Mental anguish unaccompanied by physical injury is a long-running battle in case law. Some jurisdictions read it in. Some do not.
- Property damage is defined as either physical injury to tangible property (including loss of use), or loss of use of tangible property that is not physically injured. Note "tangible." Pure economic loss is not property damage. Data, in most jurisdictions, is not tangible property.
- Occurrence is defined as an accident, including continuous or repeated exposure to substantially the same general harmful conditions. The accident piece is intuitive. The "continuous or repeated exposure" clause is what historically made GL respond to long-tail claims like asbestos, lead paint, and environmental contamination.
Coverage B: Personal and Advertising Injury
Coverage B handles a defined list of "intentional torts" that do not fit the BI/PD framework. The list includes false arrest, malicious prosecution, wrongful eviction, slander and libel, violation of right of privacy, copyright infringement in advertising, use of another's advertising idea. It is narrower than Coverage A in scope and tends to be thought of as a sweetener, but it is the line that gets activated when a competitor sues over false advertising or a tenant sues for wrongful eviction.
Coverage B is also where the modern GL form fights the cyber and privacy battle. Most insurers have endorsed out coverage for data breaches under Coverage B because the "publication" trigger had been read by some courts to include unauthorized disclosure of private data. The "Access or Disclosure of Confidential or Personal Information" exclusion (CG 21 06 and successors) is now near-universal.
Coverage C: Medical Payments
A small no-fault coverage that pays medical expenses for someone injured on the insured's premises or because of the insured's operations, without a finding of liability. Limits are typically modest, $5,000 or $10,000 per person. The point is to pay quickly for small claims and avoid them turning into bigger Coverage A suits. It is the equivalent of "go ahead, get checked out, here is a check, please do not call a lawyer."
When an underwriter pulls limits off an ACORD 125, they are looking at the per-occurrence and aggregate for Coverage A, and the lower per-person and aggregate for Coverages B and C. The ratios between them matter. A $1M / $2M limit with $1M Personal Injury and $5K Med Pay is the most common middle-market shape.
Occurrence vs claims-made
The CGL standard form is occurrence-based. That means the policy in force at the time of the BI/PD event is the policy that responds, regardless of when the claim is reported. A 2023 occurrence policy responds to a slip-and-fall that happened in 2023 even if the claimant does not file suit until 2027.
Some GL is written on a claims-made basis instead. The policy in force when the claim is first made against the insured (and reported to the insurer) is the policy that responds, regardless of when the underlying event occurred. Claims-made GL is rare today, but it persists in environmental liability, in some product liability layers, and in a handful of professional-flavored hybrids.
Risk to carrier: losses from past policy periods can keep developing. The "long tail."
Examples: standard CGL, most umbrella, most products liability.
Risk to carrier: bounded to the policy period, but the insured needs continuous coverage with an unbroken retroactive date.
Examples: D&O, E&O, EPL, cyber, environmental.
Why this matters in practice
The trigger drives almost every downstream conversation about coverage. When a buyer switches from one carrier to another, on a claims-made line they need to either purchase tail coverage from the prior carrier (the Extended Reporting Period, or ERP) or have the new carrier accept the prior retroactive date. On occurrence forms, the prior carrier just keeps responding to events that happened on its watch. This is one reason occurrence forms are simpler for buyers and why most casualty stays occurrence wherever it can.
Premises ops vs products / completed operations
Coverage A treats one important boundary as if it were two separate exposures. Bodily injury and property damage that arise from the insured's ongoing operations on its own premises is one bucket, called Premises & Operations. Bodily injury and property damage that arise from the insured's products after they have left the insured's possession, or from completed work after the insured has finished it, is the other bucket, called Products & Completed Operations.
The two buckets share the per-occurrence limit but each gets its own aggregate. The "Products/Completed Operations Aggregate" is a separate cap from the "General Aggregate." When you read a GL declarations page and see two aggregate numbers, that is what the second number is.
Premises and operations losses tend to be frequency-driven and short-tail. A customer slips, the insured pays, the claim closes. Products and completed operations losses can be severity-driven and long-tail. A defective component can damage equipment for years before a claim is filed. The market needed a way to charge for these exposures separately, manage aggregation separately, and exclude them separately when appetite required.
"Your work" and "your product"
The form uses two defined terms that show up everywhere. "Your work" is work performed by the insured or on its behalf. "Your product" is goods or products manufactured, sold, handled, distributed, or disposed of by the insured. Many of the most-litigated exclusions in CGL turn on these definitions. The damage-to-your-work and damage-to-your-product exclusions, for example, are the reason a contractor's GL does not pay for the contractor's own defective work, only for damage that defective work causes to other property.
Construction defect, in one paragraph
The single most contested coverage question in modern GL is whether construction defect is a covered "occurrence." Different states have arrived at different answers. The trend over the last twenty years has been toward finding that defective work resulting in damage to other property is an occurrence, but the patchwork is real. Wisconsin, Texas, Florida, and South Carolina lean toward coverage. Pennsylvania, Ohio, and Kentucky lean against. Wisconsin's American Family v. American Girl from 2004 is the seminal pro-coverage case if you ever need to drop one in conversation.
The limits structure
GL has six declared limits on the dec page. They do different things. Read them as a system rather than a list.
The aggregate is the constraint
For most middle-market insureds, the per-occurrence is rarely the binding constraint; the aggregate is. A restaurant chain with 200 locations could plausibly have ten covered slip-and-falls in a year before any single one comes near $1M. The aggregate is what limits total carrier exposure. Some buyers purchase a "per-location" or "per-project" aggregate endorsement (CG 25 03 or CG 25 04) which restores the aggregate for each location or project, materially expanding effective coverage. These are the kinds of endorsements that get auto-extracted in IDP workflows and matter for policy comparison.
Defense and the limits
A critical and easy-to-miss point: defense costs in standard GL are paid in addition to the limit. A $1M occurrence loss with $400K of defense costs erodes only $1M of the policy limit. The defense is on top. This is the opposite of most claims-made coverages (D&O, E&O, cyber), where defense costs are typically inside the limit and erode it. When a buyer is comparing GL excess limits, the defense-outside-limits feature is a significant part of the value.
The exclusions that move premium
The CGL form has two exclusions sections, one for Coverage A and one for Coverage B. There are roughly fifteen lettered exclusions on Coverage A. You do not need to memorize them. You do need to know which ones drive market behavior. These are the ones an underwriter will mention by name.
The pollution exclusion, in two minutes
The pollution exclusion is the single most-litigated exclusion in commercial insurance. The standard CGL excludes BI/PD arising out of the actual, alleged, or threatened discharge of pollutants. It then carves back narrow exceptions for hostile fire, products in their original packaging, and (in some forms) fuel for heating equipment. Carriers have layered on additional exclusions for total pollution, time-element pollution, fungi/bacteria, and (most recently) PFAS. If you see "absolute pollution exclusion" on a submission, it means the carve-backs are gone too.
Contractual liability
The contractual liability exclusion bars coverage for liability the insured assumed under contract, with a carve-back for liability the insured would have had anyway under tort law and for liability assumed under an "insured contract." The defined "insured contract" picks up most of the routine indemnity provisions in leases, construction contracts, and equipment rental agreements. This is what makes GL respond to additional insured tenders even when the underlying liability theory is contractual.
The CGL form is not the same form everywhere. Carrier-manuscripted versions strip out things you might assume are present, especially defense outside limits, broad named insured, separation of insureds, and full Coverage B. When you are comparing two policies, you cannot trust that the form numbers are equivalent. Read the actual schedule of forms.
Additional insureds
Almost every commercial transaction in the United States contains a contractual requirement that one party be added as an additional insured on another party's GL. Landlords require it of tenants, project owners require it of contractors, manufacturers require it of distributors. The reason is simple: the requesting party wants to access the granting party's GL limits when it gets sued for something the granting party caused.
Additional insureds are added by endorsement. There are dozens of standard ISO additional insured endorsements, each with slightly different scope. The most important distinctions are these.
| Endorsement | Scope | Common use |
|---|---|---|
CG 20 10 | AI for ongoing operations performed by named insured for AI | Owners, lessees, contractors during construction |
CG 20 37 | AI for products / completed operations | Pairs with CG 20 10 to cover post-completion liability |
CG 20 11 | AI for managers or lessors of premises | Landlord coverage on tenant policy |
CG 20 26 | AI as designated person or organization | Catch-all when nothing more specific fits |
CG 20 01 | Primary and Non-Contributory wording | Forces this policy to pay first, before AI's own coverage |
CG 24 04 | Waiver of Transfer of Rights (Subrogation) | Bars carrier from going after AI in subro |
"Primary and non-contributory"
The phrase you will hear constantly. By default, when a loss is covered by two policies, they share. P&NC wording overrides the default and says the named insured's policy responds first and the additional insured's own coverage stays in reserve. This is what most general contractors require of their subs. From a coverage analysis perspective, P&NC is one of the highest-friction endorsements because the wording varies by carrier and the legal effect can be jurisdiction-specific.
Certificates of Insurance (COIs) are the artifact that proves the AI relationship to the certificate holder. Reading thousands of inbound COIs is one of the most automatable workflows in commercial insurance. Extracting the AI endorsements actually attached, the limits, the dates, and the wording, then comparing against the contract requirements is exactly the kind of structured-comparison job that IDP plus an LLM agent does much faster than a human can. The accuracy bar is high, because a missed P&NC clause can leave a buyer's contractual indemnity bare in a major suit.
How underwriters evaluate the risk
A GL underwriter is asking a small number of questions in a particular order. If you can predict the order, you can predict what they need from a submission and what they will push back on.
- What does the insured actually do? Operations narrative, supplemental applications, website. Class code is a starting point, not the answer. Two insureds with the same NAICS can have radically different exposures.
- How big are they? Exposure base. For most GL classes, this is gross sales (mercantile, restaurants, products). For contractors, payroll. For habitational, units or area. For real estate, area and per-location.
- Where do they operate? States with bad legal climates (CA, NY, IL, OR, GA pre-reform, FL pre-reform) get loaded. Concentration in a "judicial hellhole" county warrants conversation.
- What does their loss history look like? Five years of loss runs, valued within 90 days. Frequency tells one story, severity another. A book of small claims is sometimes preferable to a clean book with one $250K claim, because the clean book might just be lucky.
- What contracts is the insured a party to? Indemnity flows in, indemnity flows out. The contract review is what tells the underwriter how much of the insured's GL is really protecting other parties through AI endorsements.
- What are the loss-sensitive features? SIR or deductible, defense in/out of limits, aggregate erosion. A $5M SIR insured behaves differently from a first-dollar insured.
- What are the underwriting modifiers? Schedule credits or debits applied for risk management, prior losses, contract terms. The Increased Limit Factor (ILF) for non-standard limits.
The submission pack, ideal version
| Document | Source | Purpose |
|---|---|---|
| ACORD 125 | Broker | Insured's basic info, locations, prior carrier |
| ACORD 126 | Broker | GL specific: classes, exposures, prior limits |
| Supplemental application | Insured / broker | Class-specific narrative (contractors, restaurants, habitational) |
| 5-year loss runs | Prior carriers | Frequency, severity, open claims, development |
| Operations narrative | Insured | What the insured actually does, in plain English |
| Audited financials | Insured (when available) | Sales by line, by geography, year-over-year change |
| Sample contracts | Insured | Indemnity provisions, AI requirements |
| Risk control / safety manual | Insured | Evidence of formal program (preferred, not required) |
Where IDP earns its keep
The point of the almanac is not just to teach insurance. It is to teach insurance specifically so we can speak fluently about where Indico's platform creates leverage. GL is full of those points.
The five GL workflows where Indico routinely shows up
- Submission intake. Classify documents, extract structured fields from ACORDs and supplementals, normalize across brokers and formats. Triage for appetite and routing. The most common GL use case.
- Loss run analysis. Pull claim-level detail from PDF and Excel loss runs across multiple prior carriers, normalize to a single schema, flag development, severity outliers, and reserves changes. This is the highest-impact extraction job in GL.
- COI verification. Read inbound certificates of insurance, pull AI endorsement scope, P&NC, waiver of subro, limits and dates, compare against contract requirements, route exceptions.
- Policy comparison. Side by side compare expiring vs renewal terms across hundreds of forms and endorsements. Flag changes in coverage, limits, exclusions.
- Claims FNOL and triage. Pull facts from inbound first-notice documents, classify type, route to the right adjuster, kick coverage analysis with the underlying policy already extracted.
GL is the line where loss runs from five different carriers in five different formats are the most common single artifact. If a carrier or MGA tells us they cannot make the underwriting workspace pre-populate from the submission, the loss run is usually the bottleneck. Show that work first, in the demo and in the POC. The rest of the story flows from it.