Peril options

Peril options you can use when importing exposure data into Touchstone.

Peril options in the user interface

The following table lists the peril options in the user interface. The perils that you see depend on your version of Touchstone.

Earthquake Tropical Cyclone Severe Storm Other Perils
Earthquake Shake (ES) Wind (TC) Severe Thunderstorm (ST) Inland Flood (IF)
Fire Following (FF) Storm Surge (SU) Hail (HL) Wildfire/Bushfire (WF): The new Smoke peril, added in June 2024, is valid only in the U.S.
Sprinkler Leakage (SL) Precipitation Flood (PF) Straight-Line Winds (SW) Terrorism (TR)
Landslide (LS) Tornado (TD) Coastal Flood (CF)
Tsunami (TS) NonCat (NC) (Non-catastrophe)
Note:

We retired non-catastrophe loss analyses in Touchstone 2021 (9.0). Therefore, these fields do not affect losses.

Liquefaction (LQ) Winter Storm (WS)

Peril codes for import

The following table lists the three-character peril codes used to import exposure data into Touchstone.

Note:

Starting in version 9.0, the Verisk Severe Thunderstorm Model for the United States allows you to individually code exposures for hail, tornado, and straight-line winds and run detailed loss analyses individually for these perils. You can use the exposures for both the current and previous (archive) versions of the model. The new sub-peril codes are PHL (hail), PSW (straight-line winds), and PTD (tornado). Non-U.S. severe thunderstorm models should continue to use the severe thunderstorm peril code, PWT. The new sub-peril codes cannot currently be imported for column-wise policy terms.

Peril Code Perils
PAL All licensed perils
PEA Earthquake perils (shake, fire, sprinkler leakage, tsunami, liquefaction, and landslide),wildfire/bushfire and smoke.
Note:

The landslide peril applies only for CSV imports.

Note: Starting in version 11.0,while the Verisk Earthquake Model for the Middle East supports earthquake shake and liquefaction, support for liquefaction is limited to certain high-hazard regions. In addition, for Middle East event sets, only the earthquake shake sub-peril is enabled; it is not separable from liquefaction.
PEF Fire (wildfire/bushfire, fire following earthquake, smoke)
PES Earthquake shake only
PFF Fire following only
PFL Inland flood
PHL Added in version 9.0: Severe thunderstorm with hail (Verisk Severe Thunderstorm Model for the United States only)
PLQ Liquefaction
PLS Landslide
PNC Non-catastrophe
Note:

We retired non-catastrophe loss analyses in Touchstone 2021 (9.0). Therefore, these fields do not affect losses.

PPH Precipitation flood
PSH Hurricane storm surge or coastal flood
PSL Earthquake sprinkler leakage only
PSM (Added in June 2024) Smoke peril.
PSW Added in version 9.0: Severe thunderstorm with straight-line winds (Verisk Severe Thunderstorm Model for the United States only)
PTD Added in version 9.0: Severe thunderstorm with tornado (Verisk Severe Thunderstorm Model for the United States) only
PTR Terrorism
PTS Tsunami
PWA All wind perils (tropical cyclone, severe storm, and winter storm)
PWB Wildfire/bushfire only
PWF All wind and fire following earthquake perils, wildfire/bushfire, smoke
PWH Tropical cyclone only
PWT Severe thunderstorm (hail, tornado, and straight-line wind)
PWW Winter storm
PWX Severe storm (wind excluding tropical cyclone). The code will be appended to PWH exposures for the 22 countries where extratropical cyclone and severe thunderstorm perils are supported.

Application of storm surge and precipitation flood

Touchstone applies storm surge and precipitation flood differently depending on the following two conditions:

  • Whether you code your contract and/or location data specifically to include the storm surge peril (PSH or PAL - all licensed perils) or the precipitation flood peril (PPH or PAL - all licensed perils) when you import or add this data to a contract or location.
  • Whether you enable Storm Surge or Precipitation Flood in the Perils area in the loss analysis settings when you configure a detailed loss analysis.

The combination of each of the options for these two conditions results in the following four scenarios:

Note: In versions prior to Touchstone 2022 (10.0), the options in the following table do not apply to the precipitation flood sub-peril of the Verisk Hurricane Model for the United States.
Contract/Location Coded for Storm Surge Peril (PSH or PAL) / Precipitation Flood Peril (PPH or PAL)? Storm Surge / Precipitation Flood Check Box in Detailed Loss Analysis Configuration Enabled? Result
Yes No Touchstone does not include any storm surge / precipitation flood losses.
Yes Yes Touchstone runs the storm surge / precipitation flood model and includes 100% of storm surge / precipitation flood losses in the analysis results.
No No Touchstone does not include any storm surge / precipitation flood losses.
No Yes Touchstone runs the storm surge / precipitation flood model and adds the percentage of storm surge / precipitation flood losses—as specified in the Loss Analysis Options: Storm Surge Options dialog box or in the Loss Analysis Options: Precipitation Flood Options dialog box—to the wind losses in the analysis results.
Note:

If the storm surge and precipitation flood sub-perils are not explicitly coded in the exposure data, you must select the wind peril when configuring the loss analysis. You cannot get surge or precipitation flood leakage losses independently of wind losses.

If a contract or location is not specifically covered for storm surge or precipitation flood, you can configure a detailed loss analysis to include a percentage of storm surge or precipitation flood losses by line of business for the following reasons:

  • You may choose to assume that you will pay some storm surge or precipitation flood losses, even if your policies do not specifically cover this peril. This condition is called "leakage" and typically applies to residential policies.
  • You may not have the precise details that specify exactly which perils every policy covers. Therefore, you may want to assume that a certain percentage of your risks have storm surge or precipitation flood coverage. This condition typically applies to commercial policies or aggregate data.