The Insights features in GEO — Location Insights, Damage Factors, and Policy Insights — only work when your portfolio data is loaded on the platform. This article explains how to share your data with MIS and what happens once it's loaded.

MIS loads your exposure data onto GEO so the platform can cross-reference your portfolio against event footprints. The most common format is an EDM or CEDE file in .bak format — this is the standard export from most catastrophe modelling platforms. MIS accepts most formats, so if your data is in a different structure, contact [email protected] to discuss.
​

MIS does not require claims data. This is exposure data only — the portfolio of locations you insure.
​

The fields you need to provide depend on which Insights features you want to use. There's no limit on what else can be included — the Insights page is fully customisable beyond the fields below.
​

Required:

Optional terms that can be applied to calculations:

Other fields you may want to provide:

Required:

Optional terms that can be applied to calculations:

Other fields you may want to provide:

Most clients share data on a monthly or quarterly basis. More frequent updates mean your Insights reflect your current portfolio more accurately. Less frequent updates are still useful — the As At Date on every Insights output tells you exactly which version of your data was used.
​

If a major portfolio change occurs between scheduled updates — for example, a significant new account in a region about to be hit by a named storm — contact [email protected] to arrange an out-of-cycle update.

MIS can accept your data through several platforms, depending on how you want to share it:

To share your data:

MIS handles all data loading. You don't need to do anything in GEO itself.

Your data is hosted securely on MIS infrastructure and is only accessible to your own organisation within GEO. MIS does not share your portfolio data with other clients or third parties. All Insights outputs you see are generated from your data only.
​

MIS holds ISO 27001, Cyber Essentials, and Cyber Essentials Plus certifications, and keeps its security measures current through regular Business Continuity Exercises and penetration testing. If your contract ends, MIS clears archived data and issues an Account Closure Certificate confirming deletion, typically within three months.

Every Insights view in GEO shows an As At Date — the date of the portfolio data being used. When you run Location Insights or Policy Insights, check this date to confirm you're looking at the right version of your portfolio.
​

If the As At Date is more than a month old and a significant event is occurring, it may be worth requesting a data update before running analysis.

If your portfolio has changed since a past event occurred, you can re-run Insights on that historic event using your current data. This is useful for understanding what your current portfolio's exposure would have been to a past event — for example, for model validation or stress-testing.
​

Contact [email protected] to request a historic re-run.

Does MIS accept formats other than EDM/CEDE?
Yes. Contact [email protected] to discuss your format. MIS can work with most structured exposure data formats.

How long does it take to load data after I send it?
Standard EDM/CEDE files are typically restored the same day. More complex or non-standard formats may take longer.

Can different teams within my organisation have different portfolio views?
Yes. MIS can load multiple portfolios for a single organisation — for example, separate views for different lines of business or regions. Contact [email protected] to set this up.

What happens to my data if I stop using GEO?
Contact [email protected] to arrange data deletion. MIS will confirm once your data has been removed from the platform.

Which platform should I use to share my data?
Tresorit is MIS's primary platform and works well for manual or one-off sharing. If you want to automate your uploads, Azure Dropbox is better suited. Contact [email protected] to discuss which fits your workflow.