Carrier scope PDFs are built from the adjuster's template, not from your local code book. When a roof age 12 years gets write-up after a hailstorm, the scope will almost always capture the shingle replacement and the underlayment. It will routinely miss the drip edge mandate, the ice and water shield requirement for your ZIP code, and the ventilation rule that your county adopted. Those are exactly the line items the 93-rule Completeness Advisor in ESXPress hunts for.
What carriers systematically omit
The pattern is consistent: initial scopes underwrite what is visibly damaged and priced, then let the contractor supplement the mandated items. An estimate built by an estimator who has seen four hundred of these files knows which codes are missing before the file is converted. ESXPress runs 93 rules at conversion time and cites the authority behind each one:
- IRC R905.2.8.5 requires drip edge at eaves and rakes on new installations and re-roofs. The Xactimate code is DRIP.
- IRC R905.1.2 requires an ice barrier underlayment when the ZIP code sits in a known freeze zone. The Xactimate code is IWS.
- IRC R806.1 sets the 1/300 net free ventilating area ratio. Ventilation rain caps and intake vents — VENTEC8 and related codes — get missed when the scope is priced as a material-swap instead of a full system.
- IICRC S500 standards split water mitigation scopes by category. Carriers flatten the trade distinctions, so WTR and HMR recoveries leak into a single line group.
- OSHA 1926.501 fall protection requirements drive the access and labor line items on steep-slope jobs that scopes often omit entirely.
Why ZIP-code resolution changes the answer
Ice barrier eligibility is not a national uniform rule. It depends on your climate zone. ESXPress resolves the policy ZIP code to the county's adopted IRC edition and the IECC 2021 climate zone, then applies the rules that actually fire for that location. Two identical scopes in different states can therefore need different supplements. That is why a static checklist you re-use across jobs under-fills in Tulsa and over-fills in Arizona. The completeness engine keys its recommendations to the address, not the template.
What a flag costs when it is missed
An omission is not a small rounding error. Drip edge on a 2,000 square foot roof is a line item with its own material and labor; an ice and water shield strip along the eaves runs the full rake-to-rake length; a missing vent cap turns a finished install into a call-back and an inspection re-check. On a claim that already fights the RCV number, silently accepting a scope that is missing three code-driven line items is the highest-cost failure an estimator can make. The average supplement recovers those lines, but only when someone audits the scope. The 93-rule engine in ESXPress produces that audit as a byproduct of conversion.
The difference between reproduce and audit
Converters that simply copy the PDF keep a 95% line-item promise and hand you back a file that is identical to the adjuster's printout. That is a useful baseline, but it inherits every omission in the source document. ESXPress goes one step further: it converts the scope, then checks it against the 93 rules and flags what is missing, each with a citation. You still decide what belongs in the supplement. The engine just makes sure the loaded scorecard is accurate.
ESXPress's 93 rules, in practice
Run a scope through the Completeness Advisor and you get a report keyed to the carrier's omissions. The report uses the measured Xactimate SEL catalog — 18,054 codes across 88 categories — so the suggestions resolve to real code names with their units. Because the catalog is the ground truth, a rendered line item like a threshold extension or a valley flashing requirement shows up with its actual SEL code, not an approximation. That is the same catalog the free Xactimate code lookup exposes, with usage data from hundreds of analyzed scopes.
If you are supplementing against a carrier scope this week, start by checking the codes you already suspect: the free Xactimate pricing explainer covers why price-list differences mislead comparisons, and the free ESX validator confirms the final file imports cleanly. Then convert the actual claim PDF and let the completeness report do the reading.