How To Spot Missing Roofing Line Items Before Sending A Supplement

The fastest way to spot candidate missing roofing line items is to audit the estimate against the roof sketch, photos, measurements, job-condition notes, and attachments before the supplement leaves your office. Do not start with a public code list. Start with the job file.

A useful pre-send review asks six questions:

• Does the estimate version match the supplement packet?
• Does the sketch support the quantities used in the roof section?
• Do the photos show components, accessories, and access conditions that the estimate does not address?
• Do the line-item notes explain the location, condition, quantity, and supporting file?
• Do waste, labor, access, and pricing notes point to job-specific facts?
• Are insurance, weather, code, and safety limits separated from the contractor's estimate review?

Call these "candidate gaps," not automatic misses. A missing-looking item may already be included in another line item, excluded by the actual scope, handled by a different trade, outside the documented damage, or subject to policy and reviewer decisions. The contractor's job is to make the request reviewable, not to claim every item is owed.

Official Xactware help describes adding line items through Estimate Items or Sketch, using keyword search, reference search, Quick Entry category and selector fields, and Similar or Related search. Xactware line-item property documentation also supports item-level review without turning the article into a static selector-code sheet. Those mechanics are enough to build a strong review workflow without publishing proprietary price-list or selector data.

What Counts As A Candidate Missing Line Item?

A candidate missing line item is a documented scope, quantity, condition, accessory, labor issue, or job requirement that appears in the roof file but is not clearly addressed in the estimate version being reviewed.

It is not enough to say "this estimate is missing items." The pre-send review should name the estimate section, show the support, and state what needs review.

Use this standard:

The phrase "missing line item" should be an internal review label. In the supplement packet, the cleaner wording is usually "requested review," "candidate gap," or "estimate item review."

Pre-Send Line-Item Audit Sequence

Run the audit in the same order every time. It keeps the review from becoming a search for favorite items.

1. Confirm the estimate version.
2. Compare the roof sketch and roof report to the estimate quantities.
3. Compare the photo log to the roof sections, accessories, penetrations, interior damage, and exterior collateral items.
4. Review roof/facet scope: repair or replace, material removal, roof area, accessory counts, and affected elevations.
5. Review roof waste assumptions and measurement support.
6. Review steep, high, access, staging, disposal, and labor-condition notes.
7. Review small-job and labor-minimum context only where the estimate and job facts support it.
8. Review local code, permit, manufacturer, or product documents only if the job file includes sourced documentation.
9. Attach or index evidence for every requested review.
10. Remove unsupported, argumentative, or carrier-rule language before sending.

That order prevents a common problem: adding line-item requests before checking whether the sketch, measurements, and photos support them.

Missing-Line-Item Review Checklist Matrix

Use this Checklist before sending a roofing supplement.

The matrix is not a list of line items to add. It is a list of questions to answer before the supplement asks for anything.

Use Official Roof Examples As Review Categories, Not Entitlements

Verisk's XactScope roof and exterior material describes selecting a facet or entire roof, deciding whether to repair or replace, identifying whether material removal is required, and creating line-item-level roof estimates. It gives examples such as steep charges, ice and water shield, felt, pipe jacks, turtle vents, and related roof/exterior scope.

Those examples are useful because they show the kinds of roof details that can belong in a structured review. They are not proof that every estimate missing one of those words is wrong. The reviewer still needs the roof file:

• Is the component present?
• Is it affected by the documented scope?
• Is the quantity supported?
• Is the estimate already accounting for it elsewhere?
• Is there a photo, sketch variable, report, invoice, product document, or field note?
• Is the request within the contractor's role?

This framing lets you use official examples without drifting into "always add this" advice.

Check The Estimate Mechanics Before Writing The Note

Xactimate line-item review should start with the mechanics of the estimate. In the actual estimate, review the category, selector, activity, description, calculation line, unit of measure, formula, attachments, tags, item details, unit-price settings, and item properties where relevant.

That does not mean a general web page should list exact roofing selectors. It means the estimator or licensed user should know where to check the item in the software and how to document the review.

A practical pre-send check looks like this:

If the note cannot answer those questions, the packet is not ready.

Use Search Tools Carefully

Xactware Help says line items can be found through keyword search, reference search, Quick Entry category/selector fields, and Similar or Related search. Those tools are helpful during the office review, especially when a photo shows a component that is not obvious in the estimate.

Use search tools to find possible estimate matches, then verify item details in the actual estimate. Do not use a search result as a shortcut for proof. The same-looking word can hide a different activity, unit, material, included component, or trade assumption.

For public-facing documentation, keep the wording clean:

Review candidate roof accessory item. Support: P-018 through P-023, roof face E2, count sheet ACC-01, and estimate item detail review. Confirm whether this condition is already included elsewhere before adding a separate request.

That note does three useful things. It identifies the component, attaches support, and tells the reviewer to check inclusion before adding a separate request.

Quantities: Start With The Sketch And Variables

Many "missing line item" disputes are really quantity disputes. The supplement asks for another item because a roof face, accessory, slope, dormer, valley, or waste assumption was not translated correctly into the estimate.

Before adding an item, audit the quantity chain:

• Does the sketch show the same roof faces used in the photo log?
• Do the roof report, sketch, and estimate use consistent labels?
• Are squares, ridge, hip, skylight, linear-foot, and square-foot quantities traceable?
• Are accessory counts tied to photos?
• Are interior or exterior damage areas tied to room, elevation, or component labels?
• Does the estimate use the right grouping for the roof, elevation, or affected area?

Xactware sketch-variable documentation lists roof variables and reference units, including roof squares, ridge, hip, skylights, linear feet, and square feet. Those variables do not prove a supplement item belongs in the estimate, but they help the estimator find the measurement trail.

The best quantity note is not long. It is traceable:

Quantity review: ridge quantity in estimate does not match MEAS-ROOF-01 and roof sketch variable review. Support: sketch export SK-01, roof report RR-01, photo group P-RIDGE-01. Requested review: confirm ridge quantity before supplement submission.

Waste: Do Not Use A Fixed Rule

Roof waste is a common source of weak supplements. The packet says "waste is missing" or "waste should be higher," but it does not explain the assumption.

Xactware's roof-waste documentation shows that waste review belongs in the estimating workflow rather than in a fixed, universal percentage claim. That source supports a review workflow, not a fixed percentage. Your note should say what assumption changed:

Waste review: current estimate uses [setting/assumption from estimate]. Roof file includes sketch and material assumptions documented in SK-01 and MAT-01. Requested review: confirm waste setting against the roof sketch and documented material assumptions.

If you cannot identify the current assumption, do not ask for a revised number yet. First ask for the assumption review.

Labor, Access, And Small-Job Conditions

Labor and access line-item gaps should be tied to field facts, not frustration. Verisk labor productivity material says productivity can be affected by accessibility, location, quantity of work, and supporting tasks. Verisk labor minimum material says labor can be the largest variable on a job and small repairs are often inefficient from a labor perspective, while users are responsible for understanding how labor minimums are applied.

That creates a useful pre-send review:

Do not write "labor minimum is owed" without checking how the estimate handles the trade, item, and job. Better:

Labor review: small repair at rear slope appears isolated from main roof scope. Support: P-044 to P-051, production note PROD-02, estimate item detail review. Requested review: confirm labor handling and included tasks for this specific repair.

Pricing Gaps Need Job Facts

Xactware price-list documentation describes requesting price lists by location or name inside Xactimate. Verisk pricing methodology explains that pricing can vary by structure size, complexity, accessibility, location, contractor, supplier, company overhead, quality of work, and service level. It also describes item detail review and says published costs are not certain to fit every contractor, repair, or structure.

That does not support broad claims that a price is always wrong. It supports a job-specific pricing note when you have facts.

Strong support can include:

• Supplier quote tied to the job location and date.
• Invoice for material, disposal, access, or specialty work.
• Estimate item detail showing an assumption that differs from the job.
• Photo evidence of access, staging, or complexity.
• Production note explaining sequence or supporting tasks.

Weak support looks like "our price is higher." A better note says:

Pricing review: item detail appears to assume typical access. Rear elevation has restricted staging and disposal path documented in P-ACCESS-01 and PROD-03. Supplier invoice INV-02 attached for job-specific material support. Requested review: confirm whether unit-price or related item handling matches documented job conditions.

Evidence Note Template

Every candidate missing line item should fit this template before it goes into the supplement:

Requested review: [estimate section or item context]. Location: [roof face/elevation/room/component]. Condition: [observed fact]. Quantity support: [sketch/report/formula/count]. Attachments: [photo/file IDs]. Boundary: [not a coverage decision / weather context only / local code source attached / unsafe area not accessed].

Example:

Requested review: roof accessory item context. Location: west slope, upper pipe penetration. Condition: photos show existing penetration and related roof-surface condition. Quantity support: count sheet ACC-02 and roof face W1. Attachments: P-067 to P-071 and SK-01. Boundary: request is an estimate item review only; coverage and payment decisions remain outside this packet.

This is more useful than a long paragraph because it gives the reviewer the facts in the order needed.

Insurance, Weather, Code, And Safety Boundaries

NAIC guidance supports photos, videos, inventories, receipts, deductible awareness, and contact with the insurer or agent. It also recognizes that a contractor may meet with the homeowner and adjuster. That does not make the contractor the coverage decision-maker. Keep policy interpretation, deductible questions, and coverage decisions with the insurer or agent.

NOAA Storm Events records can support date, area, event-type, and narrative context. They do not prove that one roof was damaged or that one line item belongs in an estimate. Weather files belong in the context folder, not as the entire supplement argument.

Code, permit, and manufacturer requirements should be handled the same way: attach the actual local, project, or product source before requesting review. If the office does not have the local document, product document, permit note, or authority source, the supplement should not present the item as a verified requirement.

Safety is the hard stop. OSHA roof inspection guidance describes hazards from ladders, raised work platforms, raised surfaces, steep or slippery surfaces, damaged roofs, tools, and power lines. If a roof face, attic area, or exterior side cannot be documented safely, record the access limit and use safer substitute evidence. Do not pressure the field team to collect a photo just to fill a packet row.

Where RoofPredict Fits

RoofPredict can make the line-item review less dependent on memory. Use it to organize estimate versions, roof age, storm exposure, photo groups, measurement files, roof reports, production notes, invoices, missing-evidence flags, and follow-up status.

For this workflow, RoofPredict should help the team answer:

• Which estimate version is being reviewed?
• Which candidate gaps still lack a photo, measurement, or note?
• Which roof faces and elevations have photo groups?
• Which quantities tie to a roof report or sketch?
• Which weather files are context only?
• Which review requests are blocked by missing source documents?
• Which follow-ups are still open?

RoofPredict does not replace Xactimate, inspect the roof, choose line items, decide coverage, act as an adjuster, act as a public adjuster, give legal advice, verify storm damage, or approve a supplement. Its value is control of the review queue and evidence trail.

Source Limits

FAQ

Should I send a supplement with a list of missing line items?

Send a review packet, not a bare list. Each candidate gap should have location, condition, quantity support, attachment IDs, and a plain requested review.

Can I use a public Xactimate code list?

Use licensed Xactimate access and official product documentation for actual estimating work. General web guidance should not republish proprietary price-list or selector data. It can teach the audit workflow and limited category context.

What is the best first check?

Confirm the estimate version and sketch. Many supplement problems start because the packet responds to the wrong estimate version or because quantities do not tie back to the roof file.

Are XactScope roof examples always missing when absent?

No. Official examples such as material removal, steep charges, ice and water shield, felt, pipe jacks, and turtle vents are useful review categories. The job file still has to support the request.

How should weather reports be used?

Use weather records for date and area context. Do not use them as proof that one roof was damaged or that one line item belongs in the estimate.

What should I remove before sending?

Remove unsupported line-item requests, carrier-rule claims without a direct source, coverage opinions, unsafe photo demands, current price claims without support, duplicate attachments, and notes that do not point to evidence.

What can RoofPredict track?

Track estimate versions, roof-face labels, photos, measurements, roof reports, candidate gaps, missing evidence, weather context, invoices, product or local documents, reviewer notes, and follow-up status.