Skip to main content

Policy Insights

How location-level exposure is aggregated to policy level, after limits, deductibles, and share are applied.

P
Written by Product Team

Policy Insights combines MIS's event intelligence with your portfolio data to show which policies are exposed, how much value is at risk, and where that exposure is concentrated. Where Location Insights shows you which individual locations were affected, Policy Insights aggregates that up to policy level and applies your policy terms — limits, deductibles, and share — to show the financial impact per policy.

This helps Claims, Exposure, and Underwriting teams move beyond "where are my locations?" to "which policies are impacted, and by how much?" — supporting fast, consistent triage in the hours after an event, typically the first 24–72 hours, before full claims data is available.

[SCREENSHOT: Policy Insights table showing policies with minimum, maximum, and ground-up exposure columns, location counts, and policy terms]


What Policy Insights shows

For each policy that has one or more affected locations, Policy Insights returns:

Column

What it shows

Policy reference

Your policy identifier

Location count

Number of locations under this policy that fall within the event footprint

Total insured value

The policy's Total Insured Value in USD, summed across its exposed locations, before any Damage Factor or policy term is applied. This is the raw value at risk, not yet damage-adjusted.

Ground-up exposure

Total Insured Value after Damage Factors are applied, before policy terms. This is the damage-adjusted figure at policy level, one step on from Total insured value above.

Estimated exposure

Definition pending confirmation, placeholder text only. Shown separately from Minimum and Maximum exposure below, this may be a single blended point estimate per policy rather than a range.

Minimum exposure

Estimated loss after policy terms, based on the lower end of the Damage Factor range

Maximum exposure

Estimated loss after policy terms, based on the upper end of the Damage Factor range

Policy limit

The maximum the policy pays

Deductible

The amount subtracted before the limit applies

Share

Your proportion of the policy

At the top of the table, GEO also shows event-level summary metrics — Total Exposed Policies and Total Estimated Exposure — so you can gauge the scale of an event at a glance before drilling into individual policies.

All financial figures reflect the Damage Factors currently active in Location Insights. If you change your factor set, Policy Insights updates automatically. You can also narrow the table down to a specific portfolio, peril, policy, or location using the Your Locations panel. See [Filtering Your Locations and Policies].


How Damage Factors drive the calculation

Damage Factors are the configurable engine behind Policy Insights' financial estimates. They convert each location's Total Insured Value (TIV) into a Damage Adjusted Estimate — a refined view of exposure that accounts for the expected level of physical damage, rather than just the raw insured value.

The logic runs in order: TIV × Damage Factor → apply location terms → apply policy terms.

  • MIS provides baseline Damage Factors per peril, based on industry references and analyst experience. You can use these as-is or create your own custom factor sets.

  • Factors are applied at the most granular assessment available for a location — the Claims Layer where it exists, otherwise the Exposure Layer.

  • Changing your factor set triggers instant recalculation across Location Insights and Policy Insights.

  • Because factors are expressed as a range, Policy Insights shows a minimum and maximum estimate rather than a single point figure, helping you manage uncertainty rather than over-relying on one number.

  • Factors are configured per user, but any factor set applied to an event is visible to your whole team, so everyone can see which assumptions sit behind a given set of figures.

See [Damage Factors] for how to view MIS's baseline factors and build your own factor sets.


How Policy Insights is calculated

Policy Insights runs in four steps:

  1. Spatial intersection — MIS identifies which of your portfolio locations fall within the event's affected footprint. Each intersecting location is "exposed."

  2. Damage Factors applied to constituent values — the relevant Damage Factor is applied separately to each location's Building, Contents, and Business Interruption (BI) values, producing a Damage Adjusted Estimate for each.

  3. Location-level terms applied — Building, Contents, and BI limits and deductibles are applied to each adjusted value, then Location Limit, Location Deductible, and Location Participation are applied across the site as a whole. If constituent-level limits or deductibles aren't available in your data, GEO falls back to the Location Limit and Deductible fields instead.

  4. Roll-up to policy level — each location's adjusted exposure is aggregated by policy (matched on your Contract/Policy ID), and policy-level terms — Policy Limit, Attachment/Excess Point, Policy Deductible, and Policy Share — are applied to produce the final minimum and maximum exposure.

This calculation assumes policy terms apply uniformly across all locations on a policy (sub-limits aren't currently applied), and that layer exposures within Policy Insights can be summed. These assumptions are more likely to overstate exposure than understate it, so treat the output as an early triage figure rather than a final loss estimate.

See [Sharing Your Data with MIS] for the full list of fields Policy Insights needs from your portfolio data.


Accessing Policy Insights

Policy Insights is in the Policy tab in the left sidebar of an event report. It requires:

  • Your portfolio data to be loaded on GEO (including policy terms)

  • Damage Factors to be configured or the MIS baseline to be active

  • Location Insights to be open for the event

[SCREENSHOT: Left sidebar of an event report with the Policy tab selected, showing the Policy Insights table]


Customising the table

Like Location Insights, the Policy Insights table is fully customisable. You can show, hide, and reorder columns to match your workflow. Sort by any column — for example, sort by Maximum Exposure to see your highest-exposure policies at the top.


Downloading Policy Insights

Click Download to download the Policy Insights table as a CSV. The export includes all columns and the As At Date of the underlying portfolio data within the download name.


Tracking changes over time

Policy Insights reflects the current insights iteration. To see how the Damage Adjusted Estimate and total exposed policies have moved since the previous iteration, use the Impact Summary on the Summary tab rather than comparing exports by hand. See [Impact Summary].


FAQ

Policy Insights is showing fewer policies than I expected. What should I check?
Policy Insights only shows policies that have at least one location within the event footprint. If a policy's locations fall outside the footprint, it won't appear. Also check the As At Date — if your data is from before a recent portfolio update, some policies may not be included. And check whether a filter is still active in the Your Locations panel from an earlier search.

The financial figures look very different from what I'd expect. What might cause this?
Check which Damage Factor set is active. If you're using MIS baseline factors and expect higher or lower loss estimates, create a custom factor set that reflects your view. Also check whether the event has a Claims Layer published — if only the Exposure Layer exists, assessments are less precise and financial estimates will be wider.

Can I run Policy Insights on a historic event?
Yes. Policy Insights works on any event in the archive. The results will use whichever version of your portfolio data is currently loaded, unless you request a historic re-run on an older data version. See [Sharing Your Data with MIS].

My policy terms aren't showing in the table. Why?
Policy terms (limit, deductible, share) are drawn from your loaded portfolio data. If these fields weren't included in your data export, they won't appear. Contact [email protected] to update your data load to include policy terms.

What is a Damage Adjusted Estimate?
A refined view of exposure that accounts for the expected level of physical damage at each insured location, rather than just its Total Insured Value.

What's the difference between Total insured value, Ground-up exposure, and Estimated exposure?
Total insured value is the raw value at risk before any adjustment. Ground-up exposure applies the Damage Factor on top of that, before policy terms. Estimated exposure's exact definition is still being confirmed internally, check back on this article or ask your MIS representative before relying on it for a live decision.

Where do the default Damage Factors come from?
MIS's baseline factors are based on broad industry references and analyst experience. They're indicative, directional guidance rather than validated, claim-by-claim figures — customise them in GEO to reflect your own loss experience.

What layers does Policy Insights support?
Currently the Exposure Layer and Claims Layer. Building Level Assessment granularity is planned for a future release.

How should I use Policy Insights alongside my financial models?
Treat it as an early triage and prioritisation tool — a bridge between observed event intelligence and your financial models. It helps focus modelling resources where they matter most and keeps portfolio-level assumptions consistent across teams.

I can't see Policy Insights on my event report. Why?
Talk to your MIS representative — either the feature isn't switched on for your account yet, or your portfolio data doesn't include what's needed for the calculation. See [Sharing Your Data with MIS].


Related articles

  • [Location Insights]

  • [Filtering Your Locations and Policies]

  • [Damage Factors]

  • [Impact Summary]

  • [Sharing Your Data with MIS]

  • [Downloading Layers]

Did this answer your question?