Agents in the Trades
Estimating

The carrier scope, line-checked for everything it left off

It is 4:40 p.m. at the supplement desk and the estimator has two documents open: the carrier's Xactimate scope on the left, her own field scope on the right. The carrier's version is shorter. It usually is — and the missing lines are the ones code required anyway.

Source: Happycapy Guide, "How to Use AI for a Roofing Contractor in 2026" — https://happycapyguide.com/blog/how-to-use-ai-for-roofing-contractor-2026 (a practitioner playbook, not a case study — this post presents the workflow, not deployed results.)

The problem

A carrier scope is not a build scope. It prices what the adjuster saw and allowed, and it routinely leaves off the unglamorous lines the job cannot legally or physically skip: drip edge, ice and water shield in the valleys, starter strip, the high-wind nailing pattern the manufacturer requires, detach-and-reset for the gutters in the way. None of it is exotic. All of it is money the shop either recovers through a supplement or eats.

The manual version is an experienced estimator reading two scopes side by side, line by line, while production waits. It depends on one person's memory of the code and the specs — and on a busy storm week it is exactly the step that gets rushed, which is how required work ends up donated.

How the agent workflow works

  1. Feed it both scopes and the evidence. The agent gets the carrier's Xactimate scope, the shop's field scope, the measurements, and the photo set — the same packet the estimator would open.
  2. Line-check the carrier scope against the field scope. Every field-scope line with no match in the carrier's version becomes a candidate delta; quantity and price-list mismatches on shared lines get flagged the same way.
  3. Run the required-add checklist. The agent works a standing list of commonly omitted, code-driven items — ice and water shield, drip edge, starter strip, step and counter flashing, ridge and vent components, decking re-nail, detach/reset items, dumpster and permit where allowable — and marks each present, missing, or not applicable.
  4. Draft the supplement memo, delta by delta. Each missing line gets its basis, not an opinion: the code section, manufacturer spec, or measurement it comes from, with quantity, price-list figure, and photo references. The draft offers a joint re-inspection walk with the adjuster.
  5. A human signs before anything leaves. The owner or adjuster liaison reviews every delta, deletes the ones that do not hold up, and signs. The agent drafts; it never sends or negotiates.

What you need to set it up

Where it breaks

It cannot see what the field scope missed. Damage nobody photographed does not become a supplement line — it becomes a change-order argument later, a worse place to have it.

A basis is not an approval. Citing the right code section makes a delta defensible, not paid. Carriers push back, price lists differ by version and ZIP, and some deltas die in review.

The checklist can go stale. Code cycles and manufacturer specs change. A list built two cycles ago will demand items no longer required — and miss the ones that newly are.

The compliance lines are not decoration. An agent will happily draft deductible-waiver phrasing if nobody forbade it, and public-adjusting rules vary by state. The guardrails and the signature keep a paperwork win from becoming a licensing problem.

The bottom line

Run this if supplements depend on one estimator's memory and spare hours. The agent's job is narrow: compare two scopes, work a written checklist, draft each delta with its basis and photos. The judgment — what to ask for, and how hard to push — stays with the person who signs.

Related use cases

← All use cases

One working agent workflow, every day.

Real AI agent use cases from solar, construction, and field operations — what they do, what they cost, and where they break. No hype, no theory.