A carrier scope comes back light, and someone has to compare it line by line against what the job actually requires: the starter strip, the drip edge, the ice-and-water, the code-upgrade items that a proper install needs. That comparison, and the write-up that documents it, is slow, repetitive work, and it is exactly where AI helps. The trap is twofold. The same tool that drafts a clean scope narrative will also state a cause of loss or argue what the policy owes, and that is not your call to make. Where the policy and the claim are concerned, you are a contractor documenting trade scope, not the adjuster of record. This is a plain look at where AI genuinely helps with supplement documentation, where it does not, and a set of prompts you can paste in and test on your own real files.
The honest picture
AI is genuinely useful for the documentation, grounding your scope in code and the manufacturer's instructions:
- What AI does well today: read your own field photos and measurement report, compare your scope against the carrier's line items, surface items a code-compliant and manufacturer-compliant installation requires that are missing from the carrier scope, and draft a clear damage narrative from what you observed. It compresses the write-up, not the judgment.
- What AI does not do: adjust the claim. It cannot certify an estimate, interpret the policy, decide the cause of loss as a coverage matter, or negotiate with the carrier. In Florida, adjusting or negotiating a claim on the insured's behalf is licensed public-adjuster work, and the supplement is filed by the party accountable for it. AI drafts the trade documentation; you certify your scope, and the policyholder or a licensed public adjuster owns the claim.
The right way to think about it: AI is a fast writer that documents your trade scope against code and spec, not an adjuster. The flagged items are a draft to verify. The estimate you certify, and the claim itself, stay where they belong.
The line: documenting scope is not adjusting the claim
This is the line that matters most on this topic, so it is worth stating plainly:
- Documenting scope is "the manufacturer's installation instructions and the applicable code require a drip edge and ice-and-water in this valley, and the carrier scope does not include them." That is trade knowledge, grounded in the spec and the code, about what a correct installation needs. AI is good at organizing it.
- Adjusting the claim is "this damage is storm-caused and covered, and the policy owes this amount." That is a coverage and causation judgment that belongs to the carrier's adjuster, the policyholder, or a licensed public adjuster, not to you and not to a model. Keep AI off it entirely.
Keep AI on the documenting side: it ties every flagged item to a code section or a manufacturer instruction and to what you observed, and it never argues coverage or states a cause of loss as a conclusion.
The setup that keeps you on the trade side
Two habits make AI safe here, and the prompts below build them in:
- Ground every item in spec, code, and your own observation. Feed it your photos and measurements, the carrier scope, the manufacturer's installation instructions, and the applicable code section, and tell it to cite the spec or code line and your observation behind every flagged item. An item grounded in "the manufacturer requires this" is trade documentation; an item grounded in "the policy owes this" is not your call.
- Describe, do not conclude. Tell it to describe only what you observed and what the spec and code require, and never to state a cause of loss, interpret the policy, or argue what is covered. You want documented scope, not a coverage argument.
How to test it on your own work
Do not trust a polished demo, including this one. Pull two or three of your own recent files, your photo and measurement report plus the carrier scope, a timer, and the prompts below. Rate each output 1 to 5 on usefulness and accuracy, and compare the time against how you document a scope today. Keep what wins. Use your company's enterprise or no-train settings before you paste any client or claim document, and confirm you are comfortable with that. This is a workflow guide, not legal, insurance, or adjusting advice.
Paste-ready prompts
Copy these as written. Bracketed text is what you swap per file.
Test 1: Draft the damage narrative from your observations (text model)
I am giving you my field notes and photo labels from a roof inspection. Write a
clear, factual damage narrative from only what I observed and recorded.
Rules:
- Describe only what my notes and photos state: location, material, and observed
condition. Do not add a finding I did not record.
- Do not state a cause of loss, do not say anything is "storm damage" or
"covered," and do not reference the policy. Describe the condition, not its
cause or coverage.
- Write it at a plain reading level a homeowner could follow.
Field notes and photo labels: [paste them]
Watch for: did it describe only what you observed, and did it stay off cause-of-loss and coverage language entirely?
Test 2: Scope gap check against code and spec (text model)
I am attaching my measurement report, the carrier's scope, the manufacturer's
installation instructions, and the applicable roofing code section. List the
line items that a code-compliant and manufacturer-compliant installation
requires for this roof but that are missing from or short on the carrier scope.
Rules:
- For every flagged item, cite the specific manufacturer instruction or code
section that requires it, and the measurement or observation that applies it
to this roof.
- Read only these documents. If you cannot tie an item to a spec, a code
section, and my measurements, do not include it.
- Do not price anything, do not interpret the policy, and do not state what is
covered. Only identify required scope and cite its basis.
Documents: [attach the measurement report, carrier scope, manufacturer spec,
and code section]
Watch for: is every flagged item tied to a real spec or code citation and your own measurement, and did it avoid pricing or coverage language?
Test 3: Plain-language basis for each item (text model)
For each flagged scope item below, write one or two plain sentences explaining
what it is and why a correct installation requires it, citing the manufacturer
instruction or code section. Do not argue that it is covered and do not mention
the policy. The goal is to explain the trade basis clearly, not to make a
claim.
Flagged items: [paste them with their citations]
Watch for: does it explain the trade and code basis clearly without sliding into a coverage argument?
What success looks like, and where it could go
If your own testing shows real time savings, the next step is a small pilot: run a week of files through the prompts and measure the documentation hours. If that holds up, the natural next step is a simple agent, running on your company's own cloud, that you use in plain language. The most useful version takes your photo and measurement report and the carrier scope and returns a flagged list of required items, each tied to the specific manufacturer instruction or code section and to your own measurement, with the damage narrative drafted from your observations, so you verify and certify your scope in minutes. The job data stays in software your company owns and runs, not rented per claim. It documents and cites; you certify the scope, and the claim stays with the parties licensed to handle it.
The principle holds the whole way through: AI gives you faster documentation and a second set of eyes on what a correct install requires. It does not adjust the claim, and it does not decide what is covered. Keep that line clear and the rest is upside.
Want a straight answer for your company?
I build practical AI and custom software for businesses, on Google Cloud. If you want a second set of eyes on how AI could fit your scoping and documentation workflow, or on a tool you are considering buying, tell me what you are working with. No pitch, just a straight answer.