Verisk (ISO) Underwriting provides the most useful property and hazard information related to a risk address.

BriteCore's current integration with Verisk Underwriting is for Fire Protection Classes, which assesses fire protection capabilities including Public Protection Classification (PPC) Service, Future Effective PPC Service, and Fire Station Type Service.

Vendor Contact

Juan Betancur
Account Executive, Verisk (ISO)
678.869.5558 (P) | 678.232.8169 (C)

Kate Armstrong
Senior Product Specialist
201.469.2458 (P)

Getting Started

  1. Contact Juan
  2. Complete paperwork
  3. ISO will assign a project manager
  4. The ISO project manager will email you a zip file titled Kickoff Package containing several documents and credentials for test (UAT) and production. Retain the documents and credentials

BriteCore Setup

  1. In BriteCore, navigate to Settings > Vendors > ISO Location
  2. Check the box
  3. Click the pencil
  4. Enter the information. Typically the Account and Sub-Account Numbers are the same

BriteCore Processing

New Business

The risk is accessed by an agent or staff member:

  1. For each risk address, enter the address information (address line 1, city, state, zip)
  2. Click the Get Protection Class button
    • The address information is sent to ISO as a request (properties.isoPcData {request})
    • ISO Location matches on two different data points
      • Address Line 1 Level The request validates against this table first. If an exact address match can be found, ISO will return an exact Fire District and Protection Class. Also stored in this data is the distance to water source though it is not shown on the screen (properties.isoPcData {response})
      • Zip Code Level If an exact address match cannot be found, ISO will return a list of Fire Districts within that zip code, ordered by the percentage of the population serviced by that district. The BriteCore user will need to choose the appropriate Fire District and the distance to nearest hydrant/water source. The latter will be essential for when a split classification exists


If a policy is to renew but an exact protection class cannot be identified, processing stops and recipients of the Processing Errors administrative alert in Settings > System Wide receive a BriteCore Alert: Ambiguous ISO Protection Class email. A user must access the policy, update the protection class, and then commit the revision.


I or an agent disagrees with the Protection Class that was returned from ISO. What is my next step?
Contact Kate Armstrong at ISO.


Report unclear or missing documentation.