Need help with a specific integration?

ISO Protection Class lookup setup

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 to assess the following fire protection capabilities:

  • Public Protection Classification (PPC) Service.
  • Future Effective PPC Service.
  • Fire Station Type Service.

Vendor setup

  1. Contact ISO to set up an account.
  2. Complete the required paperwork.
  3. Make contact with the project manager ISO assigns you.
  4. Request that your project manager email you the Kickoff Package .zip file.

    Note: Please retain the Kickoff Package .zip file; it contains several documents and credentials you will need for both test (UAT) and production sites.

BriteCore setup

  1. In the BriteCore menu, select Settings.
  2. In the Settings menu, select Vendors.
  3. On the Vendors screen, under Protection Class, select ISO Protection Classes.
  4. Next to ISO Protection Classes, select the edit icon Edit icon.
  5. In the ISO Protection Classes dialog box, add the following information:
    1. In the Account Number box, type the applicable account number.

      Note: Typically, the Account Number and the Sub-Account Number are the same.

    2. In the Sub-Account Number box, type the applicable sub-account number.
    3. In the Username box, type the appropriate username.
    4. In the Password box, type the appropriate password.
    5. If applicable, select one, both, or neither of the following options:
      1. Bypass Demo Credentials (Test Sites Only).
      2. Disable at Renewal.
    6. At the bottom of the dialog box, select Done.

BriteCore processing

New business

The risk is accessed by an agent or staff member:

  1. For each risk address, add the following information:
    • Address line 1
    • City
    • State
    • Zip 
  2. Select Get Protection Class.
    1. The address information is sent to ISO as a request (properties.isoPcData {request}).
    2. The ISO location matches 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 a water source, though it’s not shown on the screen (properties.isoPcData {response}).
      • Zip Code Level: If an exact address match can’t 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. If this happens, the user will need to choose the appropriate fire district and the distance to the nearest hydrant/water source. The latter will be essential for when a split classification exists.


If a policy is set to renew but an exact protection class can’t be identified, processing stops, and recipients of the Processing Errors administrative alert (Settings > System Wide) receive an email: BriteCore Alert: Ambiguous ISO Protection Class.

Note: A user must access the policy and update the protection class before committing the revision.

If the default-pc-lookup-to-prior advanced setting is enabled, the protection class will default to the previous year’s protection class, and the policy will renew.


What do I do if an agent or I disagree with the protection class that was returned from ISO?

If there’s a disagreement about the returned protection class, please contact ISO.

Next steps

  1. Set up ISO protection class lookup.
  2. Use Building Code Effectiveness Grading Schedule (BCEGS).
  3. Set up the agent policy workflow with BCEGS and construction year.
  4. Set default as prior protection class.

Additional information

Need help with a specific integration?

Related topics

Need help with a specific integration?