Skip to content

The journey: data to payout ​

This is the spine of Index Insure, the end-to-end path from a satellite data source to a client payout. Every part of the product exists to advance one step of this journey. Read this to see how the pieces connect; follow the links for depth.

The journey at a glance ​

1. Project        Create the workspace for one insurance deployment
        │
2. Areas          Define the geographic units to be insured (UAIs)
        │
3. Data source    Register where the satellite data comes from
        │
4. Analysis       The platform computes drought signals for every area
        │
5. Drought index  Vegetation, rainfall, soil moisture & a drought index, per area & season
        │
6. Pricing        Turn the index into a priced insurance product
        │
7. Quote          Package a priced selection for a named insured
        │
8. Term sheet     Generate the client-facing contract from the quote
        │
9. Payout         When a live season's index triggers, the payout is owed

Step 1: Set up a project ​

Everything happens inside a project, a self-contained workspace for a single insurance deployment (a pilot, a country, or a client engagement). Multiple projects run side by side without their data mixing. → Set up a project · Projects

Step 2: Define the areas ​

The geography is divided into areas, Units Areas of Insurance (UAIs), also called clusters. Each is an administrative area with a boundary, and it is the unit at which drought is measured and cover is priced and paid. → Manage areas · Units of insurance

Step 3: Register a data source ​

A data source records where the satellite data comes from and how often it is published (typically every ten days). Once registered, the platform acquires the files automatically, no manual downloading. → Manage data sources · The drought signals

Step 4: Run an analysis ​

An analysis is the platform's processing of a data source: it computes the drought signals for every area. New data triggers an analysis automatically, and an analyst can also start one. Because the work is heavy, an analysis runs as a tracked job with live progress, and its results are produced by the platform rather than entered by hand. → Run an analysis · Data you can trust

Step 5: Drought signals & index ​

A completed analysis produces, for every area and season:

  • vegetation greenness and its long-term baseline,
  • rainfall, soil moisture, and a combined drought index,
  • and how far each sits from the area's own normal (its anomaly).

These are browsable and exportable, and shown on maps and charts. → Explore results & reports · From signals to a drought index

Step 6: Price the risk ​

Pricing turns a completed analysis into money. You define a product (the trigger, exit, payout structure, loadings, fees, and taxes), set each area's exposure (how many beneficiaries and how much cover), and run a calculation that derives each area's premium and a portfolio rate. → Price a product · Pricing the risk

Step 7: Create a quote ​

A quote packages a priced selection (all areas, selected regions, or specific areas) for a named insured, applying the full premium build-up to that selection's total sum insured. → Create quotes & term sheets

Step 8: Produce the term sheet ​

One quote produces one term sheet: the client-facing contract summary (insured, covered regions, area count, beneficiaries, sums insured, premium, and the schedule of insured areas). The legal wording is fixed; the platform fills in the priced values. → Create quotes & term sheets

Step 9: Settle payouts ​

When a live season resolves and an area's index crosses its trigger, a payout is owed at the rate implied by the trigger/exit rules and that area's sum insured. Operations tracks and settles these, optionally notifying beneficiaries. → Payouts · Policyholders · Messaging

What runs through every step ​

  • Project scope: every record belongs to one project; switching projects switches the whole book. See Projects.
  • Access: what each person can do depends on their role in that project. See Who uses it & access.
  • Audit: significant actions are recorded. See Audit log.

NOTE

Steps 1-8 are the built core of the platform. The downstream operations, client onboarding, messaging, and payout disbursement, currently run on sample data for demonstration; see those guides for exactly what exists today.

Where to go next ​