Skip to content

Data you can trust ​

A payout is only as defensible as the numbers behind it. Because Index Insure pays claims from a drought index rather than a field visit, the integrity of that index matters enormously. This page explains the safeguards that make the platform's numbers trustworthy.

The numbers are produced by the platform, not entered by hand ​

The drought signals for every area are computed by the platform from the satellite data, no one types them in, and they cannot be hand-edited. Analysts can set up the inputs (data sources, areas) and start a run, but the resulting figures are read-only. This removes the single biggest risk in a parametric product: someone quietly changing the number that decides a payout.

The heavy computation is carried out by a dedicated analysis service that the platform hands the work to; the platform orchestrates the run, receives the results, and is the system of record for them.

Every number traces back to its source ​

The platform keeps a complete lineage for each result: which data source it came from, which exact file was used, which run produced it, and which area and season it belongs to. If a figure is ever questioned, it can be traced all the way back to the satellite file that produced it.

data source  →  exact file used  →  analysis run  →  area & season result

Data stays current automatically ​

A registered data source is acquired automatically: the platform watches for newly published satellite data (typically every ten days) and ingests it without anyone downloading files by hand. Each new arrival can start a fresh analysis, so an area's history stays up to date consistently.

Re-running is safe and clean ​

When an analysis is re-run (for example to apply a different method or baseline) the platform starts from a clean slate for that run, across all signals, so no stale figures from a previous run linger. Earlier results are preserved rather than overwritten, which supports methodology comparison and audit.

Repeated data never double-counts ​

Results arrive area by area, and the platform handles retries and duplicates safely, the same result sent twice is recorded once. An analysis is also only marked complete once every area is genuinely accounted for, so a run can't be reported as finished while areas are still missing.

Projects are isolated ​

Every record belongs to one project. One project's data is never visible from another, so a multi-country or multi-client deployment keeps each book of business cleanly separated.

Significant actions are recorded ​

The platform keeps an audit trail of crucial actions, sign-ins, access and role changes, data-source changes, and analysis runs, with who did it, when, and from where. This is the record auditors and administrators rely on. See Audit log.

NOTE

Coverage of the climate signals (rainfall, soil moisture, the drought index) is still expanding. Treat their presence as expected-but-not-universal: an older or partial run may carry vegetation only, and the platform shows that as an empty state rather than an error.

Where to go next ​