Telematics Belongs in the Core

For the last decade, telematics in commercial auto has lived in vendor portals. The carrier paid for the data, the underwriter glanced at a dashboard once a quarter, and the claims handler never saw it at all.

That arrangement made sense when telematics was a pilot. It does not make sense now. Driver behavior is the most predictive variable a commercial auto book has, and treating it as a side report instead of a core record is a self-inflicted handicap. The decisions that telematics is supposed to inform -- pricing, renewal posture, claim adjudication, reinsurance segmentation -- all happen inside the policy and claims platform. If the data lives somewhere else, those decisions are made without it.

Mercury was built to ingest driver-behavior telematics directly into the policy and claims record. Speed events, hard-braking counts, time-of-day exposure, route patterns, and idling time arrive through API-first integrations and land next to the rated factors and the loss history. One record. Same audit trail. Same access controls.

Three things change once the data is in the core.

First, the underwriter sees driving evidence at quote and renewal, not just self-reported annual miles. A carrier or MGA writing fleets can ask harder questions about a risk that is showing up with a heavy hard-braking footprint and reward a fleet that is showing up with disciplined behavior. The factor lives where the rate lives.

Second, the claims handler sees the same evidence at first notice of loss. When a driver reports an incident at a particular intersection at a particular time, the platform can show whether the vehicle was actually there. That does not turn the handler into a detective; it just gives the handler the same context the underwriter already had. Disputes get shorter. Investigations get cleaner.

Third, the reinsurance and audit teams stop reconciling. When telematics lives in a vendor portal, somebody has to export, transform, and tie it to the loss data quarterly. That work is error-prone and slow. When telematics lives in the core, the tie is automatic and the segmentation work is a query.

What I am not claiming is that Mercury makes an autonomous decision off telematics. The platform does not silently decline a renewal because a fleet's hard-braking score crossed a threshold. That kind of automated adverse action raises real fairness, transparency, and filing questions, and it is a place where carriers, MGAs, and TPAs need to keep human judgment in the loop. Mercury's job is to put the structured evidence in front of the right person at the right step in the workflow -- the underwriter at quote, the handler at FNOL, the actuary at segmentation review -- and to keep an audit trail of how the evidence moved through the decision.

The carriers we work with on commercial auto books treat telematics as a first-class field. They write it into their underwriting guidelines. They reference it in their claims playbooks. They cite it in regulator conversations. They do not treat it as a quarterly slide. The platform supports that posture because the data is in the system of record, not in a tab nobody opens.

If you are evaluating a core platform for commercial auto, the test is short. Ask the demo team to show you a quote screen and a claim screen with the same telematics signals visible -- not in a separate tool. If the answer is two systems and an export, you already know what the next decade looks like.

-- Sean Pitcher, CEO, Quick Silver Systems, Inc.