Tag: estimate documentation

For most of its history, claims regulation asked one question: was the outcome fair? Was the settlement reasonable, was the claim paid on time, was the consumer made whole. How an insurer got there was largely its own business.

That era is ending, and Utah HB119 is a useful specimen of what replaces it. On its face, the law is about aftermarket crash parts: standardized definitions, written notice to policyholders that aftermarket parts may be used, and mandatory disclosure language on any estimate that specifies non-OEM parts, effective for policies issued or renewed from October 1, 2026. Modest, technical, one state.

Look at what the law actually regulates, though. Not the part. Not the repair outcome. The disclosure, the definition, the document. HB119 does not say insurers cannot use aftermarket parts. It says the process by which they do so must be visible, standardized and provable. Virginia’s HB808 does the same thing to estimate revisions in the same season. Neither law changes what a fair claim outcome is. Both change what an acceptable claims process is.

This is process regulation, and it has a very different operational signature than outcome regulation. Outcome regulation is survivable with good results and occasional exceptions. Process regulation is binary: the required language is on the estimate or it is not, the disclosure went out or it did not. Quality of intentions does not register. Documentation does. Under this regime, every estimate is a compliance artifact, and an organization’s real exposure is the gap between how consistent it believes its process is and how consistent that process actually is across every adjuster, vendor and state.

The strategic question is what the industry does while this spreads, because it will spread. State legislatures copy each other, and transparency bills are politically cheap to pass. The default path is reactive: fifty states, fifty slightly incompatible disclosure regimes, and a compliance function that grows a head for each one. The alternative is for claims organizations to do what other process-regulated industries eventually did, which is standardize above the strictest requirement and make state variation a subset of one discipline rather than fifty projects.

That choice looks expensive until you price the other side. Organizations that documented well before it was mandatory will experience laws like HB119 as paperwork. Organizations that documented casually will experience them as re-engineering, performed under deadline, per state, forever. The regulators have effectively announced the test in advance. The only open question is which organizations were already living at the standard before it had a bill number.