# Turning telematics and new risk signals into pricing power
A driver slams the brakes twice on a Tuesday commute, drives 40 miles after 11pm on Friday, and logs 3,000 fewer annual miles than the average policyholder. Ten years ago, your insurer knew none of this. It priced you on your age, your ZIP code, and your credit-based insurance score. Today, that same behavior can move your premium up or down by real dollars, because a telematics feed turns your actual driving into a rating variable.
This lesson shows how raw sensor events become pricing power, and why behavior-based signals often beat demographic proxies.
Traditional auto rating leans on proxies: variables that correlate with risk but do not measure it directly. Age is a proxy for maturity and reaction time. ZIP code is a proxy for traffic density, theft, and repair costs. These work statistically, but they are blunt. A careful 22-year-old pays for the recklessness of her peer group.
Telematics (the collection of driving data through a device or smartphone app) replaces proxies with observation. Instead of guessing risk from who you are, the insurer measures how you actually drive. This is the core of usage-based insurance (UBI), where premium reflects behavior and exposure.
The industry usually splits UBI into two flavors:
Most modern programs blend both.
A telematics feed is not tidy. It arrives as a stream of timestamped events and high-frequency sensor readings. A simplified record might look like this:
trip_id, timestamp, speed_mph, accel_g, lat, lon, event
T-8821, 2026-02-10T23:14, 38, -0.42, 41.878, -87.629, hard_brake
T-8821, 2026-02-10T23:15, 41, 0.05, 41.881, -87.631, none
T-8821, 2026-02-10T23:16, 52, 0.31, 41.884, -87.634, rapid_accelEach phone or dongle can generate thousands of these rows per trip. On its own, a single hard-brake event tells you nothing. Pricing needs features: engineered variables that summarize behavior in a way a rating model can use.
This is where data work creates value. You aggregate messy events into stable, predictive signals per driver per period.
Ten hard-brake events mean different things for a 500-mile month and a 5,000-mile month. So most features are expressed as rates, not raw counts.
hard_brakes_per_100mi = (hard_brake_events / miles_driven) * 100Normalizing by exposure (miles or hours driven) prevents you from simply penalizing people who drive more, and isolates the behavior itself.
Time-of-day matters because risk is not uniform across the clock. Data from the US National Highway Traffic Safety Administration consistently shows nighttime driving carries higher fatality risk per mile. A night-driving feature captures that directly, where a ZIP code never could.
Individual features feed a model that outputs a behavior score, which then adjusts premium. Conceptually:
risk_score = f(hard_brakes_per_100mi,
night_share,
speeding_intensity,
annual_miles,
highway_share)The function f is usually a generalized linear model (GLM), still the regulatory workhorse in insurance pricing, or increasingly a gradient-boosted model whose outputs are reviewed for explainability. The score maps to a premium multiplier: a clean driver earns a discount, a high-risk pattern earns a surcharge.
Two reasons.
First, signal quality. Braking and speeding are direct measurements of the thing that causes crashes: driving. Age is a stand-in. When you measure the target directly, you carry less noise, so the variable explains more loss variation.
Second, fairness and defensibility. Behavior is something the policyholder controls and can change. That makes it easier to defend to regulators and customers than opaque proxies. Several US states restrict or ban certain rating factors, and the debate over credit-based scoring continues. A hard-brake rate is causally connected to risk in a way a proxy is not.
There is a catch. New signals invite new scrutiny. Regulators ask whether a telematics model produces a disparate impact (an unintended discriminatory outcome against a protected class) even when no protected variable is used. Night-driving share, for example, can correlate with occupation and shift work. Responsible insurers test their models for these effects before filing.
🎬 [VIDEO: "How Telematics Is Changing Car Insurance" — youtube.com — a short explainer on how driving data feeds usage-based pricing]
Better pricing creates a flywheel.
Adverse selection defense. If your competitor prices low-mileage safe drivers accurately and you still price them on age, those good drivers leave you and buy from the competitor. You keep the riskier pool at prices that no longer cover it. Telematics lets you compete for the profitable segment.
Behavior change. Many programs show drivers their scores in an app. The act of measuring braking nudges some people to brake less harshly. Fewer claims means lower loss costs, a rare win where the pricing tool also reduces the risk.
Richer claims handling. The same feed supports crash detection and first notice of loss automation. When the accelerometer registers a severe impact, the app can trigger an outreach, speeding the claim and capturing accurate crash data.
For the non-technical reader, here is the shape of the workflow from feed to filed rate:
1. Ingest: stream trip events into a data store.
2. Clean: drop GPS drift, handle dropped signal, deduplicate trips.
3. Aggregate: compute per-driver, per-period features normalized by exposure.
4. Model: fit a GLM or reviewed machine-learning model to historical losses.
5. Validate: test predictive lift and screen for disparate impact.
6. File: submit the rating plan to state regulators for approval.
7. Deploy and monitor: apply scores, watch for drift as driving patterns shift.
The unglamorous steps (clean and validate) protect you. A model trained on dirty GPS or unfiltered phone-handling noise will misprice and will not survive a regulatory review.
Knowledge check
1. What is the fundamental difference between a demographic proxy and a telematics-based signal in auto insurance pricing?
2. A driver logs significantly fewer annual miles than average. Which UBI approach most directly captures the pricing benefit of this fact?
3. Why does the lesson argue that behavior-based signals often 'beat' demographic proxies for pricing?
4. Select ALL correct answers about what characterizes a raw telematics feed as described in the lesson.
Select all the correct answers.
5. Select ALL correct answers about pay-how-you-drive (PHYD) signals.
Select all the correct answers.
Consent and privacy. Location data is sensitive. Programs need clear consent, transparent data use, and often an opt-in structure. Poor handling triggers regulatory and reputational risk. Treat the feed as personal data governed by privacy law, not as free exhaust.
Self-selection bias. Early adopters of telematics tend to be safer drivers who expect a discount. Your model can look brilliant on that population and generalize poorly when the program scales to everyone. Correct for who opts in.
Feature leakage across states. A feature that is legal in one state may be restricted in another. Time-of-day and mileage rules vary. Rating plans must be built and filed state by state in the US.
Overfitting to devices. Different phones and dongles measure acceleration differently. If your hard-brake threshold is calibrated to one sensor, a new device generation can shift your feature distribution overnight. Normalize across hardware.
Braking and mileage were the beginning. The 2026 frontier adds context: connected-vehicle data straight from the manufacturer, road-condition overlays, and computer-vision features from dash cameras where legally permitted. Each new signal repeats the same lesson: raw data is worthless until feature engineering turns it into a variable that predicts loss and survives a regulator.