ISO 2025 GenAI Exclusions: Your Contractor Insurance Has Blind Spots

What GenAI Exclusion Language Means for Your 2025 Restoration Renewal

Short answer: some general liability and professional liability carriers are now adding endorsement language to 2025 and 2026 renewals that limits coverage when a claim ties back to generative drafting tools, meaning software that helps produce moisture logs, scope narratives, or supplement letters. If a scope of loss or documentation package produced with that kind of drafting assistance turns out wrong, and a homeowner or carrier says they relied on it, the endorsement can let the insurer deny or limit defense on that claim instead of handling it the way they'd handle a hand-typed report. Read the declarations page and any new endorsement schedule on your renewal before you sign it, not after a Category 3 claim gets disputed.

Where This Actually Shows Up on a Water, Fire, or Mold Job

Restoration runs on paperwork more than almost any other trade in construction. A water loss generates moisture readings, thermal imaging scans, room dimensions, drying logs, equipment placement notes, and a written scope tied to IICRC S500 guidance. A mold job adds IICRC S520 containment notes and remediation protocol language. Fire losses add contents inventory sheets and structural cleaning narratives written for the carrier's scope of loss review.

Every one of those documents can be drafted, transcribed, or assembled with help from generative software, whether that's voice-to-text field notes turned into a written narrative, auto-populated Xactimate line items, or a drafted customer email confirming the drying plan. None of that behavior is new. What's new is that some carriers no longer treat the resulting document the same way they treat a report your estimator typed line by line. If the endorsement excludes claims "arising from" generative drafting assistance, it doesn't care that a certified technician took the actual moisture readings with a calibrated meter. It cares how the final document got produced.

Category and Class Errors Are Where the Real Exposure Sits

Here's where this gets specific to your trade instead of staying abstract. A Category 2 gray water loss comes in from a failed dishwasher line. Your tech takes moisture readings across the kitchen and adjoining hallway with a moisture meter, backs it up with thermal imaging to find the wet wall cavities, and dictates field notes that get converted into a written scope. The scope lists 320 affected square feet and a projected 3 day dry time with air movers and low-grain refrigerant dehus running.

Weeks later, during a supplement dispute, remeasurement shows closer to 400 affected square feet, because the conversion from dictated notes to written scope dropped a hallway segment. The carrier's adjuster now has two documents that don't match, and if your renewal has generative drafting exclusion language, the carrier has a hook to argue the discrepancy came from the drafting process itself rather than a technician judgment call. That distinction matters for coverage. It shouldn't matter for how you build your file, but under this new language it can.

Category 3 losses raise the stakes further. Sewage backups involve demo decisions, containment, and often a faster equipment day count because materials get pulled rather than dried in place. If your documentation shows a Category 3 call that later gets disputed by the carrier as overstated, and any part of that scope narrative ran through drafting software, you want a clean paper trail showing the technician's raw field data independent of the narrative tool.

What to Check on Your Renewal Before You Sign

Pull the endorsement schedule, not just the summary page. Look for language referencing "automated," "generative," "machine-assisted," or "algorithmic" drafting, documentation, or content creation. Some endorsements are narrow and only touch marketing copy or customer-facing chat tools. Others are written broadly enough to sweep in field documentation software your crews already use every day.

• Ask your broker directly whether moisture logs, Xactimate-generated scopes, or drying reports fall inside the excluded category.
• Ask whether the exclusion applies only if the drafting tool made the underlying judgment call, or whether it applies any time drafting software touched the final document at all.
• Get the answer in writing, even if it's just a broker email confirming the carrier's position. Verbal assurances don't help you during a claim dispute a year from now.
• If the endorsement is new this cycle, confirm the effective date on the schedule itself. Most of this language applies going forward from the new policy period rather than retroactively, but carriers word this differently, so don't assume based on the renewal date alone.
• Ask whether the endorsement can be narrowed or removed, and what specific documentation practices would keep your claims outside its scope. Some carriers will clarify or adjust the language once they understand how field documentation actually gets produced in restoration work.

If your current carrier can't or won't answer clearly, that's information too. A carrier that can't explain its own endorsement language in plain terms is a carrier you'll struggle to negotiate with when a real supplement dispute lands.

How to Document So the Exclusion Can't Touch Your Claim

The fix isn't to stop using drafting tools. It's to keep the technician's raw field record separate from and independent of whatever narrative gets built on top of it. That separation is what lets you argue the technician made the call, and the software just helped format it.

• Keep timestamped moisture meter readings and thermal imaging captures as their own file set, tied to specific room locations, before any narrative gets written.
• Log affected square footage directly from the field measurement, not from a recalculated number that appears only in the finished scope.
• Note category and class determinations as a technician judgment entry, with the reasoning (source of water, contamination level, materials affected) written by the technician, even if the final formatted paragraph gets assembled with drafting help afterward.
• Track drying days and equipment days against the original drying plan, and flag any deviation with a dated note explaining why (secondary damage found, containment expanded, materials reclassified).

This is the same discipline good restoration contractors already use to win supplement disputes with adjusters. It just now doubles as your defense if a carrier tries to invoke a generative drafting exclusion against your own claim.

Adjuster Walkthroughs and Supplement Documentation

Adjuster walkthroughs are where sloppy documentation habits get exposed fastest. If your scope of loss was drafted from field notes and the adjuster's remeasurement doesn't match your affected square footage, containment lines, or equipment count, you're now negotiating from a weaker position, exclusion language or not.

Before the walkthrough, reconcile your moisture logs, photos, and thermal imaging against the written scope line by line. If a supplement is likely (hidden moisture found after demo, mold discovered under cabinetry, a Category 2 loss that gets reclassified to Category 3 after lab results), build the supplement package with the same raw-data-first approach: photos with timestamps, moisture readings at each check point, and a written explanation of what changed and why. Carriers accept supplements more readily when the documentation shows a clear, traceable chain from field measurement to final scope, and that same chain is exactly what protects you if a generative drafting exclusion ever gets raised on a disputed claim.

What This Exclusion Language Does Not Cover

It's worth being direct about the limits here. This endorsement language, where it exists, is not a blanket exclusion on using drafting or documentation software in your business. It's not retroactive to prior policy periods in most cases, and it's not automatically triggered just because a report was typed with help from software. Carriers are targeting a specific dispute scenario: a claim where the customer or carrier says they relied on a flawed automated output, and the contractor can't show independent technician judgment behind it.

Some contractors read headlines like this and assume they need to go back to handwritten field notes. That overcorrection isn't necessary and isn't practical on a busy loss with multiple rooms and a tight drying window. Tools like RestoreWright are built to keep the raw moisture data, category and class calls, and technician notes as their own record, so the drafting layer sits on top of documented field work instead of replacing it. That structure is what actually satisfies both a carrier's scope of loss review and, if it ever comes to it, your own insurance defense. If you want to see how that separation works on your next job, you can start a free trial at restorewright.pro.

Frequently asked questions

Does this exclusion apply to Xactimate line items generated automatically?

It depends on the specific endorsement wording on your policy. Some carriers draw the line at tools that make judgment calls (category, class, scope decisions) rather than tools that format or populate line items from data a technician already entered. Read the actual endorsement schedule rather than relying on a summary, and get your broker's confirmation in writing.

Can I still use voice-to-text or dictation software for moisture logs?

Yes. The concern isn't the tool, it's whether the technician's raw readings and judgment calls exist independently of the finished narrative. Keep the original moisture meter data and thermal imaging captures as a separate, timestamped record even after a dictated note gets converted into a formatted report.

What's the biggest documentation mistake that creates exposure here?

Letting the finished scope become the only record. If a formatted narrative is your sole documentation and the raw field data (affected square footage, category determination, drying day projections) never existed as a separate entry, you have nothing to point to if a carrier disputes the numbers or invokes an exclusion.