When a Pattern of Cuts Becomes a DOI Complaint

One cut is a supplement you handle with documentation. The same carrier cutting the same documented operation across job after job is a different kind of problem. It has a channel most shops never use, the state Department of Insurance.

The line between a supplement and a pattern

A single reduction is a claim issue. You answer it with the OEM procedure, the platform page, and the DEG inquiry, and you move on. A repeated reduction of the same operation, by the same carrier, on items the documentation clearly supports, is a pattern. Patterns are what regulators are equipped to look at, and the per-job files you already build are what make one visible.

Why this matters now

Carriers increasingly use automated systems to review and adjust estimates. The National Association of Insurance Commissioners issued a model bulletin on the use of artificial intelligence by insurers, and a growing number of states have adopted some version of it. The principle behind it is simple. An insurer remains responsible for the decisions its automated tools make, and those decisions still have to comply with existing claims-handling law. Whether your state has adopted the bulletin is worth knowing, because it shapes what your Department of Insurance can act on.

What a pattern looks like

• The same operation cut repeatedly, such as calibrations or blend time.
• The same carrier or program across multiple jobs.
• Documentation on every one of them showing the operation was supported.

If your files show all three, you've moved from a disagreement to a documented practice.

How to document a pattern

Per job, keep what you already keep, the supplement, the sources, and the carrier's response. Then add one layer on top, a simple log across jobs with the carrier, the date, the operation, the supporting document, and the outcome. The individual files prove each instance. The log is what turns instances into a pattern.

How to file

Most state Departments of Insurance take complaints through an online portal. Submit the pattern with the documentation behind it. Two things to keep in mind. A complaint is a market-conduct signal and works on a regulatory timeline, so it won't get you paid on the job in front of you, and you should still pursue that supplement on its own. And the stronger your documentation, the more useful the complaint, which is one more reason the per-job paper trail matters.

A measured word on relationships

Filing with a regulator is a real step, and shops on DRP programs especially weigh it carefully. The point here is simply that the option exists, it's legitimate, and the documentation that wins your supplements is the same documentation that makes a complaint credible if you ever decide to use it.

Let the documentation do double duty

The record that wins a single supplement is the same record that, repeated, reveals a pattern. GuideCoat keeps that documentation consistent from job to job, so the evidence is already there if you need it. See how it works

This is one of the four areas where shops leave the most money. For the full picture, start with the collision supplement playbook.

Frequently asked questions

What is the NAIC AI model bulletin? It's guidance from the National Association of Insurance Commissioners on how insurers should govern their use of artificial intelligence, including in claims. It reinforces that insurers stay accountable for automated decisions. States choose whether and how to adopt it, so check your own state's status.

Will one complaint change anything? Probably not on its own. Regulators act on patterns and volume, which is why consistent documentation across shops and jobs matters.

Should I file instead of supplementing? No. Keep pursuing the supplement on the individual job. A complaint is a separate, longer-horizon channel for documented patterns.