Objective index + predefined benefit
No individual loss adjustment is used to set each payment.
RESILIO / PILOT DECISION BRIEF / 30 JULY 2026
A four-month, heat-only pilot for 10,000 riders in Delhi NCR.
Status
Proceed with controlled pilot validationBinding cover has not commenced. The ₹700 price is indicative and subject to calibration and insurer quotation.
Open guided flowDangerous heat can make riding unsafe before it creates a medical or accident claim. Logged-off hours can therefore reduce earnings without activating medical, accident or property cover.
Covered purpose Partial fixed support for qualifying heat-related work disruption.
Not designed as Medical, accident, property or exact income-indemnity insurance.
Model reference: RIDER_BASELINE | ASSUMPTION_REGISTER
Parametric describes how payment is triggered. Extreme heat defines what the current pilot covers.
No individual loss adjustment is used to set each payment.
Delhi NCR, March to June. Rainfall is outside current cover.
Model reference: PERIL_SCOPE | INSURANCE_TERM_SHEET
Shared services can support future modules, but each peril needs its own evidence, trigger, price and policy wording.
Model reference: PERIL_SCOPE | ASSUMPTION_REGISTER
The first pilot must be coherent enough to price, govern and learn from.
| Decision lens | Heat-first position | Risk avoided |
|---|---|---|
| Model integrity | Use the peril already supported by the benefit, trigger, terms and scenarios. | Unpriced multi-peril exposure |
| Explainability | Test one peril, one season and one basis-risk framework. | A contradictory pilot narrative |
| Pilot learning | Limit moving variables while testing operations and rider outcomes. | Unclear reasons for success or failure |
| Commercial control | Keep claim cost, premium, capacity and wording heat-specific. | Cross-subsidy and accumulation ambiguity |
Model reference: PERIL_SCOPE | PRESENTATION_GUIDE
A valid heat event is necessary, but not sufficient, for payment.
The working five-stage product is shown here in its actual route. All records are simulated.
GST is separate from premium. Implementation and integration are quoted separately.
Model reference: PRICING | SLIDE_OUTPUTS OUT-01 and OUT-02 | ASSUMPTION_REGISTER
These cases call the same deterministic engine used in the nine-case console.
All conditions are satisfied for an Extreme event.
All trigger and eligibility conditions are satisfied.
Model reference: TRIGGER_ENGINE
Select an outcome to see what the programme must investigate.
The event qualifies and the rider experiences material work disruption. This is the intended payment case.
No rate is asserted before weather, eligibility, payout and rider-outcome data are combined.
Model reference: BASIS_RISK
The insurer is the risk carrier. Marsh is adviser and broker. The sponsor pays the premium.
| Programme funding | Insurance risk | Advisory and placement | Trigger evidence | Eligibility evidence | Payment operations |
|---|---|---|---|---|---|
| Platform or approved sponsorPays premium; proposed policyholder | Licensed general insurerIssues policy and carries payment obligation | MarshBroker and programme adviser only | Independent data providerSupplies insurer-approved zone index | Participating platformCoverage, zone and recent activity data | Insurer or authorised administratorValidates and sends approved payment |
Model reference: INSURANCE_TERM_SHEET
The controlled pilot ends in a decision, not an automatic rollout.
Trigger performance, operations, rider outcomes and financial experience support expansion.
Basis risk, claim cost, thresholds or operating controls need adjustment before another pilot.
The product cannot deliver acceptable rider value, operational control or insurer economics.
The model supports a validation decision, not an issued policy.
Recommendation Proceed with controlled pilot validation. Do not bind cover until every requirement is complete.
Model reference: PILOT_DASHBOARD | SLIDE_OUTPUTS OUT-07 and OUT-08