Skip to content

Firearm Liability Coverage #29

@coverageguy

Description

@coverageguy

Hopefully I'm not coming off as being too critical for hammering so many liability issues--to be clear, I do like what's going on here and the idea of more user-friendly personal lines policies. I didn't see any dialogue on the firearm liability exclusion and I think it's probably worth discussing.

On firearm liability, the current exclusion reads as follows: We don’t cover damage caused by assault weapons (as defined by the Federal Assault Weapons Ban of 1994). Harm caused by other licensed firearms is covered, as long as they were stored securely and used responsibly.

Firstly, there are a number of exclusions that open with essentially, "We don't cover damage..." and I think "damage" should be replaced in these instances with "bodily injury or property damage" as defined in the coverage document for the sake of clarity on the consumer side. On excluding coverage for claims involving assault weapons as defined by the AWB, this seems really tricky. This legislation was notorious for being full of loopholes, so utilizing the AWB definition for firearms brings those loopholes into the policy. For one, it doesn't define what an assault weapon is so much as it defines certain specific guns as being assault weapons--the legislation includes a list of specific weapons, but the list is limited to weapons that were manufactured in 1994 and earlier, so coverage for weapons introduced after the ban expired would be covered, right? They certainly wouldn't be on the list of weapons in the 1994 AWB, but is covering those under the policy the intent? Now I don't think including a schedule of continuously changing firearms on the policy is logical or practical, but it's worth discussing.

Finally, the exclusion carries a caveat covering "other licensed firearms" as long as they were "stored securely and used responsibly" based on recommendations from the California Office of the Attorney General's website. Unlike the 1994 AWB, this website isn't static--as is, your definition of secure storage and responsible use will change every time an edit is made to the site. Maybe it'll create an issue, maybe it won't, but it'll be a lot for the adjuster to have to weigh when making a coverage decision. ISO's exception to the intentional bodily injury or property damage exclusion allows coverage for the use of "reasonable force" to protect persons or property, maybe something to that effect would be sufficient in this policy? Otherwise, do you expect an adjuster to determine if the policyholder was keeping their firearm and ammunition stored separately using California-approved lock boxes and trigger locks as part of their coverage decision? Should an Illinois or New Jersey policyholder be held to that same standard? Are all policyholders expected to ensure they're complying with the latest California OAG recommendations to continue coverage? If so, is a compliance review something you'd expect them to do at renewal? Or continuously?

If the goal is to know a risk and limit exposure, why not use something like, "We will not provide coverage for bodily injury or property damage caused by any firearm not scheduled on the policy, but this exclusion will not apply to the use of reasonable force of a scheduled firearm to protect persons or property." Firearms are usually a topic of discussion for producers writing property coverage, if there are certain firearms that fall outside of Lemonade's property or liability risk appetite, this gives Underwriting the opportunity to keep them out of the portfolio.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions