Oct 19, 2026

How to brief an insurance broker using a supplier hazard register

Exterior of a metal warehouse building with blue loading doors on a clear day.

Renewal season has a familiar rhythm. Your broker asks for a supplier list, you send a spreadsheet, and somewhere in the back-and-forth someone asks "which of these sites actually flood?" and nobody has a confident answer. A hazard register fixes that gap before the question gets asked, if you brief the broker with it the right way.

What the broker needs from the register

A broker is building an underwriting submission that an insurer can price without sending back a request for more information. That means the register needs to answer three things fast: which sites carry physical hazard exposure, what kind, and how severe.

Send the register as a standalone document, not buried in a supplier onboarding file or an ESG appendix. Lead with the sites that carry exposure, not the full vendor list. A broker scanning three hundred rows for the dozen that matter is a broker who calls you back with questions instead of a quote.

For each flagged site, give them:

  • The hazard type (flood plain, wildfire fuel load, landslide terrain, storm surge)
  • The exposure tier, so they're not guessing at severity from a raw score
  • What the tier call is based on: the imagery or survey behind it

That last point matters more than it sounds. Brokers have seen plenty of registers built from flood-zone lookups that were never checked against where the supplier's building sits on the parcel. If your register can say how the exposure tier was determined, the submission moves faster because the underwriter isn't re-verifying your source.

Framing exposure tiers for a property submission

An exposure tier is shorthand for severity. Before you send anything, make sure your broker can state in plain terms what each tier means: which hazard, how close to the site, and whether it changed since last year's submission. If three suppliers moved up a tier since the last renewal, say so explicitly in your cover note. Underwriters care about trend as much as current state, and a broker who can point to "this site moved from moderate to elevated wildfire exposure" has a much easier time explaining a premium change than one who's reading the tier for the first time during the call.

Keep the register and the submission language consistent. If your register calls something "elevated storm surge exposure," don't let that turn into "high risk" in the broker's summary, and don't let it get softened to "minor concern" either. Mismatched language between your internal document and what the broker tells the insurer is how coverage gaps happen, usually discovered after a claim rather than before one.

One more thing worth saying out loud in the brief: tell the broker how often the register gets refreshed. An annual screen against current hazard data is a different claim than a one-time assessment from three years ago, and insurers price those differently. If a site's exposure was flagged this year rather than carried forward from an old spreadsheet, that's worth a sentence in your submission notes.

A short checklist before you hit send

  • Flagged sites sorted to the top, not alphabetical by vendor name
  • One hazard type and one tier per line, no combined "risk score"
  • A note on what the tier is based on
  • Year-over-year tier changes called out, not left for the broker to spot
  • A plain-language key so nobody on the call has to ask what "tier 3" means

None of this requires a new process on the broker's end. It just means handing them something that answers the first three questions an underwriter will ask, instead of a vendor list they have to interpret themselves.

If building that register from scratch every renewal cycle is the part eating your time, a ranked hazard register built from your full supplier footprint is the shorter path to the same document.

Start a pilot

← Back to the blog