What is a tick value in a drought index insurance contract?

A tick value is the dollar amount a contract pays for each unit the index moves past the trigger point. It's the conversion rate between "how bad did it get" and "how much do we pay," and it's usually the first number a cedant asks about once the trigger and exhaustion point are set.

Say a contract triggers at an anomaly of -0.15 against the baseline and pays out in full at -0.45. If the limit is $500,000, the tick value is whatever $500,000 divided across that 0.30 range works out to, call it roughly $1.67 million per full unit of anomaly. Move the index another 0.01 past trigger and you owe another increment of that. That's the whole mechanic. No adjuster, no claim form, just the index reading against the schedule written into the contract.

How a tick converts anomaly into payout

Most drought index contracts use a linear payout structure between trigger and exhaustion. Below the trigger, nothing is owed. At the exhaustion point, the full limit is owed. In between, the payout scales straight-line with how far the index has moved. The tick value is the slope of that line, expressed in dollars per unit (or per 0.01, or per percentage point, depending on how the contract defines its index units).

The band width and the tick value together set how the book behaves at the margins. A wide trigger-to-exhaustion band with a correspondingly small tick value pays out gradually as conditions worsen. A narrow band with a large tick value swings from zero to near-limit over a small move in the index, which suits a cedant who wants that risk profile, but it means a single month's anomaly reading can carry a lot of weight. Structuring teams size the tick value against the band width as one decision, since either number read alone says little about how the contract pays.

Some structures aren't linear at all, step functions that pay in bands rather than continuously, but the tick-value question still applies within each band. The term shows up most often in the context of a continuous, linear design because that's where "per unit" pricing has a clean, consistent answer.

Why the tick value is only as good as the baseline

A tick value priced against a sloppy or short baseline doesn't hold up. If the reference period is five years of unusually wet or dry conditions, the trigger sits in the wrong place relative to what's normal for that region, and the tick value gets attached to a scale that doesn't mean what it's supposed to mean. Pricing teams want a multi-decade reference because a drought index is a departure from normal, and normal has to be built from enough seasons to average out the noise.

This is also where disputes start. If the cedant's loss data and the index's read of the same month disagree, the first thing to check isn't the tick value, it's whether the baseline the anomaly was measured against is the one both sides agreed to at inception. A monthly anomaly run against a fixed, documented baseline removes a lot of that argument before it starts, because the number going into the tick-value math is the same number for both sides, every month, on the same reference period.

Pricing the tick value itself

Pricing the tick isn't really separate from pricing the trigger and exhaustion point. Actuaries typically run the historical index series through the proposed structure, see how often and how far it would have breached trigger over the reference period, and solve backward from a target loss ratio to a tick value that fits the limit. Change the baseline years, the trigger, or even the vegetation index variant, and the whole exercise has to run again, because the tick value that looked right against one baseline can be off by a meaningful margin against another.

The number itself is simple arithmetic once trigger, exhaustion, and limit are fixed. Getting a tick value worth trusting comes down to whether the index behind it is measured against a baseline both sides would sign off on, read the same way, month after month. That's the part worth checking before the structure gets locked in, not after the first claim comes in. If you're setting up that check for the next renewal cycle, Drought Monitoring's monthly regional anomaly output is built for exactly this.