Usually not — at least not the policy most operators expect. When a customer, an occupant of a treated building, a bystander near an exterior application, or their pet alleges injury from a product your crew applied, the general liability policy you assume will respond generally will not: its absolute pollution exclusion treats the pesticide as a pollutant and drops the bodily-injury claim. This guide walks why, what actually responds, and the one distinction operators most often miss.
The answer surprises operators because the loss looks like the textbook thing general liability is for — a third party got hurt. But the chemical cause is what changes the result. And there is a second distinction that matters before we go further: this post is about a third party being exposed. A technician’s own exposure on the job is a different policy entirely and is covered below in its own section. The narrow question here is the customer, the occupant, the bystander, the pet.
The short answer: usually no, and here is why
A chemical-exposure claim from a customer or bystander is a bodily-injury allegation, which is exactly what general liability is built to answer — until the cause is a chemical. The standard general liability form carries an absolute pollution exclusion, and a pesticide fits the way that exclusion defines a pollutant. So when the alleged injury arises from the product your crew dispersed, the chemical piece of the claim has no general liability response. This is not a coverage argued down at the margins; it is excluded by design. The full mechanics of that exclusion — how the form defines a pollutant and why underwriters read it broadly — live on our pollution liability page and the general liability page that names it as one of two seams. This post stays on the single question operators search: a customer says the treatment hurt them — who pays?
The trap: a bodily-injury claim that general liability still drops
Here is where operators get caught. A person is hurt — a customer says the interior treatment gave them a headache and nausea, an occupant of a treated office reports a reaction, a passerby alleges the exterior spray made them ill — and a hurt third party is the textbook trigger for general liability. So the assumption is automatic: file it on the general liability policy. The problem is the cause. The alleged injury arises out of the dispersal of a pesticide, and the absolute pollution exclusion removes bodily injury that arises from a pollutant. The chemical origin pulls the claim out of the policy even though the visible loss — a person who says the treatment made them sick — is exactly the bodily injury the form normally answers. That is the single most misunderstood point about exposure claims, and it is why a claim that feels obviously covered comes back denied.
Real-World Scenario: A crew treats a restaurant’s dining room early in the morning before service. A staff member who arrives during the application later reports headaches and breathing trouble and brings a claim alleging the chemical made them sick. The operator reports it to the general liability carrier expecting a routine bodily-injury claim — and the carrier points to the pollution exclusion, because the alleged injury arose from a pesticide. The complaint is real, the person is owed a response, and the policy the operator assumed would answer does not. An applicator pollution policy is the one that would.
What IS and ISN’T covered: the seam, precisely
The line is drawn by the cause, not by who is hurt. If a third party is injured at your job with no chemical cause, general liability is in play — a customer who slips on a wet-treated floor, a bystander who trips over staged equipment, property a tech knocks over and breaks. Those are routine third-party losses the form is built around. The moment the alleged injury is the chemical exposure itself — the product made someone sick, a pet reacted to a treatment, an occupant attributes a reaction to what your crew applied — the pollution exclusion controls and general liability is out. One visit can produce both. A customer might slip on a treated floor (general liability) and separately allege the treatment made them ill (pollution). The two policies are written to sit together because one incident can land on both seams.
There is one more distinction that defines this post, and it is the easiest to confuse. Everything above is about a third party — someone who is not your employee. A technician’s own chemical exposure on the job is not a liability claim at all; it is a workers compensation matter, governed by an entirely separate line and a separate body of law. If you searched this question wondering whether your crew is covered when a product affects them, that is the workers comp question, covered in depth on its own page and in the related post on a tech’s chemical exposure on the job. This post is about the customer, the occupant, the bystander, the pet — the third party. Keeping the two apart is the difference between filing the right claim on the right policy and watching both get denied for being filed on the wrong one.
What actually responds: applicator pollution liability
The line written for the third-party chemical-exposure claim is applicator pollution liability. It is the coverage that picks up what the general liability pollution exclusion hands off: the bodily injury of a customer, occupant, bystander, or pet exposed to a product your crew applied, and the defense of the matter. For a pest control operation the pesticide is not incidental to the work — it is the work, performed across occupied homes and businesses on every route — so this is not a precautionary endorsement; it is the line your operation runs through every application. The full treatment of how it responds, and how the exposure weighs differently across general pest control, fumigation, and termite and WDO work, lives on the coverage page. The point for the exposure question is narrow and firm: this policy answers it, and general liability does not. A related seam — a drift that exposes a neighbor rather than your customer — is covered in the post on pesticide drift to a neighbor, and the misapplication that often triggers an exposure is covered in the post on a tech applying the wrong product or treating the wrong site.
A practical check before a complaint comes in
You can confirm the gap before a claim ever tests it. On your general liability policy, look for the total or absolute pollution exclusion — on a standard ISO form it is the endorsement numbered CG 21 49, though the exact wording and form number vary by carrier, and some policies build the exclusion into the base form instead. If it is on your policy, your chemical-exposure losses are not covered there. The fix is a separate applicator pollution liability policy, or in some programs a pollution buy-back endorsement that restores a measure of the coverage onto the general liability form. The two are not interchangeable: a standalone pollution policy is usually written on a claims-made basis with its own limit and defense terms, while a buy-back can carry a sublimit worth reading closely. Either way, what you are checking is simple — whether a third party’s chemical-exposure claim has a policy behind it at all. The move that matters is to have a broker who knows the pest control trade read your form and tell you where the exposure sits, rather than assume the general liability policy reaches it. The standard your application is measured against is the federal framework — pesticide labeling and use under the EPA pesticide program, applicator certification under the EPA certification framework, and worker safety under OSHA — and a clean record there strengthens your file without changing the coverage answer.
Why most operators learn this after a claim
The reason this gap is so common is that nothing about it feels like a gap until it is tested. The operator carries a general liability policy, the policy is real, and a hurt customer looks exactly like the bodily injury the policy describes. So the coverage is assumed, the pollution line is skipped to save a line item, and the assumption holds right up until the complaint arrives. Then the denial letter explains the pollution exclusion, and the operator is funding the response — and the defense — out of pocket while learning the distinction the hard way. The honest version of this answer is also the useful one: general liability will not answer the chemical-exposure claim, and knowing that now is what lets you carry the line that will.
Before it happens
Treat the exposure complaint as a question of when, not if, because once a product is dispersed into an occupied space the people in it are part of the job whether or not anyone flagged them. Carry applicator pollution liability alongside your general liability, get your current general liability form read for the total pollution exclusion, and keep your workers compensation in force for the separate question of your own crew’s exposure — so each kind of exposure has its own policy behind it. If you serve restaurants, multifamily properties, schools, or healthcare accounts, more third parties are present and the exposure runs higher, which is worth weighing as you size your program; a state-level read on what your market demands lives in our cost guides. When you are ready, start a quote and tell us how your operation runs, or read the full pollution liability treatment to see exactly what the line responds to.