Skip to content

Platform

Four surfaces, built around one idea

The product is deliberately narrow. It assembles the property record and shows where every part of it came from. It does not rate, it does not bind, and it does not decide.

01

Lookup

Address in, file out.

Type or paste an address, resolve it against autocomplete, and every connected source is queried in parallel. Nothing is fetched speculatively, because the commercial sources are metered and a lookup you did not ask for is a cost you did not budget.

  • Address autocomplete resolves ambiguity before any paid call is made
  • All sources run concurrently rather than in sequence
  • A source that fails degrades its own section rather than the whole file

02

Property file

The record, with its provenance.

One page per property, sectioned by layer. Each section states which provider produced it and when. Hazard readings use a fixed four step scale so that a colour always means the same thing across flood, wildfire and response.

  • Structure, valuation, permits, flood, wildfire, response and imagery
  • Provider and retrieval timestamp recorded against every figure
  • Raw provider response retained and openable from the file

03

Case queue

For desks that work a list.

Cases carry priority, assignment and due date, and can be filtered to your own queue, the team queue, urgent, or overdue. The queue is where a small team keeps the work visible without a spreadsheet.

  • Personal, team, urgent and overdue views
  • Priority and due date on every case
  • Direct jump from a case into its property file

04

Provider monitoring

Know when a source is degraded.

Every provider call is recorded with its status, response time and cost. When a public service starts timing out or a licence hits a rate limit, that shows up as an operational signal rather than as quietly missing sections on tomorrow's files.

  • Per provider success rate and response time
  • Per lookup cost attribution for the metered sources
  • Failed calls surfaced rather than swallowed

Boundaries

What PropertyRiskIQ deliberately does not do

Stating this plainly is part of the product. A tool that is vague about its limits gets used past them.

It does not rate

No premium, no rating factors, no bindable output. Pricing stays in your rating engine.

It does not decide

No accept, decline or refer recommendation is issued as an instruction. Selection remains an underwriting judgment.

It does not certify flood

The flood section reports what the published FEMA panel says. It is not a Standard Flood Hazard Determination.

It does not grade protection

Distance to a responding station is reported as distance. An ISO Public Protection Classification comes from Verisk and is not derivable here.

See the file this produces