Insurance doesn’t have a trust problem. It has a bandwidth problem.
Why risk transfer keeps failing, and what information theory says about fixing it.
Here’s a scenario 300 million Indians experience every year.
Your flight gets delayed four hours. You’re staring at the floor at IGI Terminal 3, laptop dying, meeting cancelled, just mildly irritated co-passengers and hyper energetic kids past their bed-time buzzing all around. You have travel insurance. You paid for it. You pull up the policy document and start reading the claims process:
File a claim within 48 hours
Attach boarding pass, delay certificate from airline, original policy document
Wait anywhere from 2 to 15 business days for acknowledgment
Insurer may request additional documentation
Settlement within 45 days of final document submission
You do the math. Four hours of delay. 2-3 forms to fill. Six to eight weeks of paperwork. For maybe ₹2,000.
Most people don’t file. The ones who do, roughly 40% get rejected on technicalities. The insurer calls this “claims management.” I call it a clogged pipe at best, or scummy at worst.
Pipes, not promises
Let’s borrow a concept from a field that solved a version of this problem sixty years ago. In 1948, Claude Shannon published “A Mathematical Theory of Communication.” He was trying to figure out how much information you could reliably push through a telephone wire. His answer became the channel capacity theorem:
C = B × log₂(1 + S/N)
C is capacity: how many bits per second you can transmit reliably.
B is bandwidth: the range of frequencies the wire can carry.
S/N is the signal-to-noise ratio: how much of what arrives is actual message versus static.
The theorem says something profound: every communication channel has a hard ceiling. No amount of clever engineering lets you exceed it. You can approach the ceiling with better encoding. You cannot break through it.
Shannon was talking about copper wire. But the structure applies to anything that transfers information between two parties.
Including insurance.
Reframing insurance as a channel
Insurance is, at its core, a risk transfer channel. One party (the insured) has a risk they want to offload. Another party (the insurer) is willing to absorb that risk for a price. The “message” being transmitted is:
a loss happened, here is its magnitude, please settle.
Every channel has the three Shannon variables.
Bandwidth (B): How many distinct states can the channel carry per unit time?
In traditional indemnity insurance, the answer is shockingly low.
A single claim cycle produces one binary distinction (pay or reject) over weeks or months. That’s roughly 0.001 distinctions per hour. A telephone wire from 1948 could do billions of times better.
Signal (S): How much of the transmitted information is actual, meaningful content?
The “signal” in a claim is simple: what happened, and how much did it cost? This could be communicated in a few hundred bits.
For eg., a flight delay claim is ~50 bits of information: flight number, scheduled time, actual time, delay duration, policy number.
Noise (N): How much interference, ambiguity, and distortion corrupts the message?
This is where the system collapses. The noise sources in traditional insurance claims are extraordinary:
Document fraud (the insurer doesn’t trust the insured’s evidence)
Interpretive ambiguity in policy wording (”act of God” means what, exactly?)
Subjective loss assessment (two or more departments across TPA and insurer acting as adjusters, two different numbers)
Adversarial incentives (insured inflates, insurer deflects)
Bureaucratic friction (forms, approvals, escalations, each adding delay and error)
The noise doesn’t just degrade the signal. It overwhelms it. In the flight travel insurance analogy, a simple 50-bit message gets wrapped in thousands(20x) of bits of verification overhead, each of which introduces its own noise.
The capacity equation for risk transfer
Shannon’s formula generalizes beyond telephone wires. For any exchange system:
Effective Capacity = D(t) × log₂(1 + T/N)
where:
D(t) is distinctions per unit time (how many settlement decisions per hour).
T is trust between parties.
N is noise (fraud, ambiguity, friction).
Note that I’ve replaced Shannon’s “signal power” with “trust.” This isn’t a randomly defined, loose metaphor. It is a structural equivalence.
So in a physical channel, signal power determines how much the receiver updates on what arrives. A loud signal cuts through static. A weak signal gets lost. In a social/economic channel, trust does the same job.
A message from a trusted source carries more usable information than the same message from an untrusted source. If I don’t trust you, every message you send is ambiguous to me. I can’t distinguish signal from noise. The channel capacity collapses toward zero.
Low trust equals high noise.
This isn’t a metaphor. This is the mechanism.
Measuring the collapse
Let’s put rough numbers on traditional indemnity insurance as a risk transfer channel.
D(t) ≈ 0.001 distinctions/hour. ie., one pay/reject decision stretched over weeks. That’s the throughput through the “claims: channel
T = Low. Both parties assume adversarial intent. The insured expects rejection. The insurer expects inflation.
N = High. Document fraud, subjective loss assessment, wording ambiguity, bureaucratic friction. Noise everywhere.
C_eff ≈ near zero.
The channel is almost fully clogged, to almost ensure it doesn’t function ideally.
This explains something that has puzzled insurance economists for decades: why does insurance penetration in India sit at ~4% of GDP when the need for risk transfer is enormous? The standard explanations are “lack of awareness” and “affordability.”
Both are wrong, or at least incomplete. Hundreds of millions of Indians know what insurance is. Premiums for basic travel or health cover are within reach of the middle class.
The real technical answer is: the risk transfer channel has such low effective capacity that the cost of using it (in time, friction, and uncertainty) exceeds the expected value of the payout for most small-to-medium losses.
People aren’t unaware. They’re making a very rational calculation based on what they see around: the pipe is too clogged to be worth their time and effort pushing claims through.
This is why informal risk-sharing persists. Family lending, community pooling, or just simply absorbing losses. These channels have lower bandwidth than formal insurance in theory, but in reality; they have much higher trust (family T >> insurer T), which means their effective capacity can actually be higher for small losses.
What changes when you replace the channel
Parametric insurance doesn’t improve the traditional channel. It replaces it entirely. The mechanism is simple:
instead of : “file a claim, prove your loss, wait for assessment”;
the contract says: “if event X occurs as measured by data source Y, payment Z is automatically triggered.”
No need to “raise” a claim. No adjudication. No human in the loop.
The channel variables shift dramatically:
D(t) jumps from ~0.001/hour to ~3,600/hour. One data/oracle check per second is achievable. That’s a six-order-of-magnitude increase in throughput.
T decouples from the insurer entirely. It’s now determined by data/oracle trust (more on this below).
N drops from high and diffuse (fraud, ambiguity, subjectivity) to low and measurable (basis risk + data quality). Two specific, quantifiable noise sources instead of dozens of unmeasurable ones.
Therefore, C_eff goes from near zero to orders of magnitude higher.
And three major things happen when you make this switch.
First, the noise sources change qualitatively: Traditional noise is diffuse and unmeasurable: how do you quantify “interpretive ambiguity in policy wording”?
Parametric noise reduces to exactly two measurable quantities: One is basis risk (the gap between the parametric trigger and the actual loss) and the second is oracle data quality (how accurate is the data feed).
Basis Risk is now a noise engineering problem. Both can now be precisely quantified, tracked, and engineered against. You go from fighting fog to calibrating instruments.
Second, the trust variable decouples from the insurer: In traditional insurance, T(trust) is “do I trust THIS company to pay?”
That’s hard to build, easy to destroy, and non-transferable. In parametric, T is “do I trust the data source?”
Flight delay data from OAG or FlightAware is trusted because airlines themselves consume it. The trust is borrowed from an existing high-trust channel rather than built from scratch. This is not a small point. It means parametric insurance can achieve high T on day one in verticals where trusted oracles already exist.
Third, speed becomes a trust-building mechanism: When a parametric payout lands in your bank account four minutes after your flight delay crosses the threshold, that experience itself raises T for the next interaction. Speed is not just a convenience feature. It’s a trust-formation event.
Each fast, accurate payout increases the T term in the capacity equation, which increases C_eff, which means more people use the channel, which produces more trust-formation events. The flywheel is information-theoretic, not just commercial.
The constraints that remain
If this analysis is right, two hard constraints determine where parametric insurance can and can’t work:
Constraint 1: Data/Oracle availability: The entire system’s trust rides on the data source. For flight delays, high-trust oracles exist (airline schedule data, airport systems). For hotel cancellations or e-commerce delivery failures, they don’t, yet.
“Did my package arrive damaged?” doesn’t have a FlightAware equivalent today. This means vertical expansion is gated by oracle infrastructure, not by market demand or regulatory approval.
Constraint 2: Basis risk as irreducible noise: No parametric trigger perfectly matches every individual’s actual loss. Your flight was delayed 3 hours 50 minutes; the trigger is 4 hours. You got nothing.
This isn’t a bug to be fixed. It’s the thermodynamic floor of the channel: the minimum noise below which you cannot go while maintaining the speed and objectivity that make parametric work. Reducing basis risk to zero means measuring actual individual losses, which means... you’re back to traditional claims adjudication.
The engineering challenge today is to minimize basis risk (N) without reintroducing the noise sources you eliminated. This is an optimization problem with a formal structure:
min E[|L_actual - L_parametric|²]
subject to: no subjective assessment, no human adjudication
Every trigger threshold decision is an instance of this optimization. Set the threshold too low and you overpay (noise from false positives). Set it too high and you underpay (noise from false negatives, which also destroy trust).
The optimum exists, and it’s findable today with existing data.
What this lens predicts
If risk transfer is a channel capacity problem, several things follow:
Distribution channels are trust channels: Where you sell parametric insurance isn’t just a go-to-market decision. Each distribution channel has its own T/N (trust/risk) profile. Embedding in an airline booking flow borrows the airline’s trust (high T).
Selling direct-to-consumer on your own website means building trust from scratch against Indian consumers’ well-calibrated scam detectors (low T, high N).
This predicts a strict sequencing: high-trust embedded channels first, own-brand D2C only after trust has been established externally.
Insurance penetration is a channel capacity metric, not a demand metric: India’s 4% penetration doesn’t mean 96% of the population doesn’t want risk transfer. It means the available channels have such low capacity that most risk transfer demand goes unserved.
Widen the channel (increase C_eff), and penetration rises mechanically.
This reframes the entire insurtech thesis from “how do we sell more policies?” to “how do we increase the effective capacity of the risk transfer channel?”
Whoever certifies the oracle controls the market: If trust in parametric insurance flows from trust in the oracle, then the entity that standardizes oracle certification holds a structural position equivalent to a ratings agency. This role doesn’t exist yet in parametric insurance. It will need to, someone will build it out soon (or someone is already building it).
Reinsurance is a meta-channel. Reinsurers need to trust your triggers, your oracles, your loss ratios before they’ll allocate capital. Their trust formation process has its own bandwidth and noise characteristics.
Established reinsurance brands (Lloyd’s syndicates, Swiss Re) function as trust amplifiers: their endorsement raises T for our entire system at once. Getting a Lloyd’s coverholder stamp isn’t just a commercial milestone. It’s a discontinuous jump in our meta-channel’s capacity.
The general principle
Travel insurance is just one instance. The structure is everywhere.
Any sector or system that transfers value, risk, or information between parties is a channel. Every channel has bandwidth, noise, and capacity constraints. Trust is the social equivalent of signal power: it determines how much information actually gets through.
When you find a channel with near-zero effective capacity despite high demand, you’ve found an opportunity for parametric insurance. The question is always the same: can I build a replacement channel with higher D(t), higher T, and lower N?
Payments had this, twice. In the US, accepting online payments meant merchant accounts, payment gateways, PCI compliance, and weeks of integration. Stripe replaced that entire channel with seven lines of code. The noise (compliance friction, integration complexity, settlement opacity) collapsed. Transaction capacity exploded.
In India, the channel for transferring money was clogged differently (bank visits, cash handling, multi-day settlement). UPI replaced it. Volume went from millions to billions per month. Same structure, different pipe. In both cases, the demand was always there. The channel wasn't.
Risk transfer is having its UPI moment. The demand for loss protection exists. The current channel can’t serve it. Parametric triggers, trusted oracles, and instant settlement rails are the replacement channel.
The math says it should work. The question is where the oracles are good enough to make it real.
I build parametric insurance settlement infrastructure at OrbitCover. If you’re thinking about risk transfer, oracle design, or channel capacity in financial services, I’d like to hear from you.